Host Patch Installation Failure | "global name 'commmand' is not defined"

kagbasi-wgsdac

Good-day Folks,

My Environment:

Host Hardware: HP ProLiant DL360p Gen8
Host Version: XCP-ng 8.2.1 (GPLv2)
Xen Orchestra, commit ba8c5
xo-server 5.96.0
xo-web 5.97.2

I was recently introduced to XCP-NG and XO. After much reading and watching various YouTube videos, I decided to give it a try yesterday. So I spun up a host, successfully connected it to XCP-Center and created a VM running Debian 11. Then using this installation script from Ronivay, I successfully compiled XO from sources and successfully connected it to the host.

As expected, after a few minutes XO prompted me that there were some missing host patches, so I followed the appropriate buttons to install the patches. Unfortunately, I ran into the following error:

"global name 'commmand' is not defined"

I performed a quick search online and came across this forum posting where the same issue was discussed and the conclusion was that it had been resolved in a later commit. Given that I just built XO yesterday, I wanted to submit this inquiry, in case the issue had reared up again or if someone knew of a workaround.

I noticed in the error message that the word "command" has an extra "M" in it - perhaps a typo? Finally, here's the complete error log: 2022-06-28T00_48_16.728Z - XO.txt

Any assistance is very much appreciated, thank you.

Danp

In the thread you found, @BenjiReis indicated that this is an xcp-ng issue, not XO. Did you try installing the patches with from the CLI?

stormi

The error message about commmand masks the actual error that occurred (it's an error raised during error handling itself).

Please try to do the update from CLI so that we may see the actual error from yum.

https://xcp-ng.org/docs/updates.html#how-to-apply-the-updates

kagbasi-wgsdac

@Danp - thanks for pointing that out, I must have glossed over it. Now that I think about it, the patches were host patches so definitely not XO related. My apologies.

@stormi - I wanted to try the update via CLI, as per the documentation, however I've not been successful gaining access to the host. It's rather strange. Both the root and the non-root account I created won't let me in - whether via console or SSH, even though it's the same root credentials that I've used to connect XCP-Center to the host. Another strange thing - XO would not connect to the host using the root account, so I had to use a service account I'd created in Active Directory. Still scratching my head on that one, but I don't want to convolute this thread with this.

Anyway, while waiting I decided to reboot the host. From XO, it wouldn't let me; complains that there's no where to move the VM to and that I need to use the force flag. Since there's no way to do this from the XO ui (that I've found), I went into XCP-Center and rebooted it that way. When it came back, I tried the patches again and this time they installed without any problem. So for now, this problem is resolved.

Thanks to both of you for your responses. I'm gonna blow away my entire setup and redo it to see if I can replicate these anomalies.

olivierlambert

Since there's no way to do this from the XO ui (that I've found)

Host/advanced/Force reboot

kagbasi-wgsdac

@olivierlambert Aaah, thanks Olivier. Still learning.

Great product by the way. Hoping I can get comfortable with it enough to make a recommendation to my company.