Red Hat Bugzilla – Bug 1310790
Management network is out of sync with host once refreshing caps on host with 3.5 vdsm version in cluster 3.6
Last modified: 2016-12-05 01:19:03 EST
Created attachment 1129403 [details]
Description of problem:
Management network is out of sync with host once refreshing caps on host with 3.5 vdsm version in cluster 3.6.
If trying to refresh caps on host with 3.5 vdsm version in a 3.6 cluster, it will cause to the management network to be reported as out-of-sync with the host and a change in bootproto will be recognized. on host will reported static ip, while the actual bootproto is dhcp. This is because the 3.6 cluster expecting to some arguments/fields that don't exist in vdsm 3.5
The following errors will be shown:
"Host orchid-vds2.qa.lab.tlv.redhat.com is compatible with versions (3.4,3.5) and cannot join Cluster Test_cluster which is set to version 3.6."
"Host orchid-vds2.qa.lab.tlv.redhat.com's following network(s) are not synchronized with their Logical Network configuration: ovirtmgmt."
"VDSM orchid-vds2.qa.lab.tlv.redhat.com command failed: The method does not exist / is not available."
When trying to activate the host it moves to Non-operational, but from time to time host stuck in connecting state.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add host 3.5 to cluster 3.5 in engine 3.6
2. Set host to maintenance and move to 3.6 cluster
3. Refresh caps on host or try to activate
management network reported as out of sync
management network should in sync with host, no matter if the host is compatible with the cluster version or not.
This can probably be solved if we call getVdsCaps prior to going Up, but consume ONLY the clusterLevel element end its friends.