Try to manage a OVM server once managed by another OVM manager.

Try to manage a OVM server once managed by another OVM manager.

Cause

Embedded in each server are records of its current affiliation. These records will prevent the server from being registered again. Usually dropping a server from a pool removes these records, but should an error prevent that it is possible to remove the setting manually.

Solution

To reset the server pool affiliation for an Oracle VM server, perform these steps on that server:

# /opt/ovs-agent-2.2/db/db_del.py master
these records will be removed:
0) master_hostname
1) pool_ha_enable
2) master_agt_url
which one to remove? ('Y' to remove all)Y
removed 0) master_hostname
removed 1) pool_ha_enable
removed 2) master_agt_url

# /opt/ovs-agent-2.2/db/db_del.py srv
these records will be removed:
0) 10.182.120.252
which one to remove? ('Y' to remove all)Y
removed 0) 10.182.120.252

# /opt/ovs-agent-2.2/db/db_del.py srvp
these records will be removed:
0) 10.172.147.38
1)
2) 10.172.147.37
3) 127.0.0.1
which one to remove? ('Y' to remove all)Y
removed 0) 10.172.147.38
removed 1)
removed 2) 10.172.147.37
removed 3) 127.0.0.1
#


It may also be convenient to clear the vm database too:

# /opt/ovs-agent-2.2/db/db_del.py vm
these records will be removed:
0) /OVS/running_pool/52_oel5u3pv
1) /OVS/running_pool/16_oel4u5hvm
which one to remove? ('Y' to remove all)Y
removed 0) /OVS/running_pool/52_oel5u3pv
removed 1) /OVS/running_pool/16_oel4u5hvm
#

If you see different outputs during running above commands, like:

# /opt/ovs-agent-latest/db/db_del.py master
these records will be removed:
0) master_hostname
1) pool_ha_enable
2) master_agt_url
3) slave_hostname
which one to remove? ('Y' to remove all)Y
removed 0) master_hostname
removed 1) pool_ha_enable
removed 2) master_agt_url
removed 3) slave_hostname


You may see a different response:

# /opt/ovs-agent-latest/db/db_del.py master
no candidates.


It just means there no records in the database, it is safe to proceed with next step.

After emptying the databases, please restart the ovs-agent service:

# # Shutdown running guests and restart the agent
# /sbin/service ovs-agent restart

# # Alternatively, restart the service but leave any guests running
# /sbin/service ovs-agent restart --disable-nowayout



Now you can try to register the OVM Server again.