Uploaded image for project: 'XenServer Org'
  1. XenServer Org
  2. XSO-783

Designating a new pool master via CLI on the current master fails on 7.0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.1
    • Fix Version/s: None
    • Component/s: Dom0
    • Labels:
      None
    • Environment:

      Description

      The command:

      xe pool-designate-new-master host-uuid=(UUID-of-slave-server)

      when run on the current pool master causes XenCenter to lose connectivity with the pool (as expected), but when reconnected, the original pool master is still the pool master.

      If run on a slave server, the operation correctly designates the named host to be the new pool master and XenCenter connects and shows correctly the newly designated host as the new pool master.

      Just applied up to XS70E036 in the hope of things improving, and now both hosts have crashed so I cannot continue this research and cannot access them remotely, so will have to manually check them in the server room tomorrow.

        Attachments

          Activity

            People

            • Assignee:
              stephentu Stephen Turner
              Reporter:
              tjkreidl Tobias Kreidl
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: