"global name 'commmand' is not defined" while installing patches
-
Hello,
xo-server 5.90.2
xo-web 5.95.0Trying to install patches on a 8.2 host via VM -> Patches -> "Install all patches"
-1(global name 'commmand' is not defined, , Traceback (most recent call last): File "/etc/xapi.d/plugins/xcpngutils/__init__.py", line 101, in wrapper return func(*args, **kwds) File "/etc/xapi.d/plugins/updater.py", line 96, in decorator return func(*args, **kwargs) File "/etc/xapi.d/plugins/updater.py", line 157, in update raise error NameError: global name 'commmand' is not defined
Sounds like a typo....
Thanks.
-
Hi,
Are you on XOA or XO from the sources? If from the sources, there's no versions for XO or its components.
We might have an issue so you should probably try to rebuild on
pierre-fix-rpu
branch, and then try again -
@olivierlambert said in "global name 'commmand' is not defined" while installing patches:
Hi,
Are you on XOA or XO from the sources? If from the sources, there's no versions for XO or its components.
We might have an issue so you should probably try to rebuild on
pierre-fix-rpu
branch, and then try againWell, I report these versions:
Okay
-
As explained here: https://xen-orchestra.com/docs/community.html what matters is the commit number We'll remove the rest to avoid confusion.
-
It's now fixed since commit
2bd3d57f8ae21cdbe6836afae724dc906fe80eb3
(available onmaster
) -
@olivierlambert FYI I'm still seeing this issue on the latest commit.
-
Double check you have correctly rebuild.
-
@olivierlambert So something interesting.
I have 2 hosts, neither would update and were having this error, found this post and updated XOCE to the latest master.
Rebooted XOCE and the first host updated just fine, but the second host kept showing the same error. Rebooted the second host, still had the issue.
Rebooted XOCE again and then updated the second host and it updated just fine.
-
I can't tell since it's your install from the sources, a lot could happen if your rebuild didn't work of if you did not restart
xo-server
. Reboot shouldn't change anythingAnyway, it works, that's what matters!
-
@olivierlambert the issue is within the
xapi-plugins
package on XCP-ng.
A release candidate with the fis is on testing and will be released with next train of XCP-ng updates.For now the update should be done in CLI with the yum command.
-
I think it was workarounded by XO team @julien-f ?
-
I think it was another issue regarding the RPU algorythm.
This is an issue with thexapi-plugins
code. -
@olivierlambert This error does not ring a bell to me.
-