HPE Morpheus VM Essentials Software
1856340 Members
8224 Online
104111 Solutions
New Discussion

vme manager running on node 1 in UI while being active on node 2

 
Convergo
Frequent Advisor

vme manager running on node 1 in UI while being active on node 2

Hi, 

On our VME cluster we moved the VME manager from host 1 to host 2. After reconfiguring the VME, the VME crashed and now we see an reconfiguring action in the history running forever. As a result we cant move the vm anymore with manage placement, and when putting the host in maintenance the VME crashed. When starting up the VME with virsh start [VME] it started however the VME manager believed he was running on host 1 in the UI and running on host 2 according to virsh list --all.

Is there a way to sync the information in the UI with the active configuration. I read about logging in on the VME and doing a sudo morpheus-ctl reconfigure, however not sure if that is the way to go.

2 REPLIES 2
DiegoDelgado
HPE Pro

Re: vme manager running on node 1 in UI while being active on node 2

How long has it been in this state? It usually times out after 24 hours and you'll be back to normal



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Convergo
Frequent Advisor

Re: vme manager running on node 1 in UI while being active on node 2

Hi,

For the VM Essentials Manager our experience was that the manager gets in an unknown state. Actions will indeed time out after 24 hours, however this state will be the same. Based on this state VME information is not equal to the real HVM cluster information for the VME. When selecting edit for the VM Essentials Manager and being sure all actions on this vm are completed, you can edit the vm and put him in provisioned state by using the advanced parameters in the edit menu for this virtual machine. After the issue has been solved.