Thursday 9 June 2011

OVM-2008 The Server Pool Master

OVM-2008 The Server Pool Master (192.168.1.101) has been registered with some other pool, and can not register it again.
# service ovs-agent stop
# rm -rf /etc/ovs-agent/db
# service ovs-agent start

OVM-1011 OVM Manager communication with 192.168.1.101 for operation Pre-check cluster root for Server Pool failed:

[root@HemCloud OVS]# cd /opt
[root@HemCloud opt]# ls
oracle ovs-agent-2.2 ovs-agent-2.3 ovs-agent-latest
[root@HemCloud opt]# ovs-agent-2.3/utils/repos.py -n /dev/sda3
[ NEW ] 2988a0bf-77ec-4b98-b896-4e2a6a9a07d6 => /dev/sda3
[root@HemCloud opt]# ovs-agent-2.3/utils/repos.py -l
[ ] 2988a0bf-77ec-4b98-b896-4e2a6a9a07d6 => /dev/sda3
[root@HemCloud opt]# ovs-agent-2.3/utils/repos.py -r 2988a0bf-77ec-4b98-b896-4e2a6a9a07d6
[ R ] 2988a0bf-77ec-4b98-b896-4e2a6a9a07d6 => /dev/sda3

then after add your existing vm from /running_pool .....

Job done!!

No comments: