XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    "global name 'commmand' is not defined" while installing patches

    Scheduled Pinned Locked Moved Xen Orchestra
    13 Posts 5 Posters 893 Views 5 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      jrubenc
      last edited by jrubenc

      Hello,

      xo-server 5.90.2
      xo-web 5.95.0

      Trying 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.

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        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 🙂

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          jrubenc @olivierlambert
          last edited by

          @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 again 🙂

          Well, I report these versions:

          fc51c07d-3b55-415d-9114-bd77abf9644c-image.png

          Okay 🙂

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            As explained here: https://xen-orchestra.com/docs/community.html what matters is the commit number 🙂 We'll remove the rest to avoid confusion.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              It's now fixed since commit 2bd3d57f8ae21cdbe6836afae724dc906fe80eb3 (available on master)

              planedropP 1 Reply Last reply Reply Quote 0
              • planedropP Offline
                planedrop Top contributor @olivierlambert
                last edited by

                @olivierlambert FYI I'm still seeing this issue on the latest commit.

                cab1f819-fb27-4ee1-a43f-f0ed8024acab-image.png

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  Double check you have correctly rebuild.

                  planedropP 1 Reply Last reply Reply Quote 0
                  • planedropP Offline
                    planedrop Top contributor @olivierlambert
                    last edited by

                    @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.

                    1 Reply Last reply Reply Quote 0
                    • olivierlambertO Offline
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by olivierlambert

                      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 anything 🤔

                      Anyway, it works, that's what matters!

                      BenjiReisB 1 Reply Last reply Reply Quote 0
                      • BenjiReisB Offline
                        BenjiReis Vates 🪐 XCP-ng Team @olivierlambert
                        last edited by

                        @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.

                        1 Reply Last reply Reply Quote 0
                        • olivierlambertO Offline
                          olivierlambert Vates 🪐 Co-Founder CEO
                          last edited by

                          I think it was workarounded by XO team 🤔 @julien-f ?

                          BenjiReisB julien-fJ 2 Replies Last reply Reply Quote 0
                          • BenjiReisB Offline
                            BenjiReis Vates 🪐 XCP-ng Team @olivierlambert
                            last edited by

                            I think it was another issue regarding the RPU algorythm.
                            This is an issue with the xapi-plugins code.

                            1 Reply Last reply Reply Quote 0
                            • julien-fJ Offline
                              julien-f Vates 🪐 Co-Founder XO Team @olivierlambert
                              last edited by

                              @olivierlambert This error does not ring a bell to me.

                              1 Reply Last reply Reply Quote 0
                              • K kagbasi-wgsdac referenced this topic on
                              • First post
                                Last post