[Users] Host's Cluster Compatibility Version doesn't match the Cluster's Compatibility Version.
Hi, I've just installed OVirt 3.4 AllInOne on a clean install of Fedora19 on a multihomed box. I had some issues getting networking working, but that seems to be up now. I've got two Alerts that are in the way now: Host's Cluster Compatibility Version doesn't match the Cluster's Compatibility Version. According to "yum list installed" every package that begins "ovirt" is version 3.4.something and every package that begins "vdsm" is version 4.14.6, but "vdsClient -s 0 getVdsCaps" reports clusterLevels = ['3.0', '3.1', '3.2', '3.3' ]. So it looks like ovirt 3.4 isn't compatible with ovirt 3.4, which seems a bit odd. What have I done wrong here? The other Alert is "Power Management is not configured for this Host.". I don't have any kind of power management for this box, is it possible to stop this message? Thanks Jim
----- Original Message -----
From: "Jim@Ovirt" <jim-ovirt@spudsoft.co.uk> To: users@ovirt.org Sent: Wednesday, April 2, 2014 1:03:14 PM Subject: [Users] Host's Cluster Compatibility Version doesn't match the Cluster's Compatibility Version.
Hi,
I've just installed OVirt 3.4 AllInOne on a clean install of Fedora19 on a multihomed box. I had some issues getting networking working, but that seems to be up now. I've got two Alerts that are in the way now:
Host's Cluster Compatibility Version doesn't match the Cluster's Compatibility Version. According to "yum list installed" every package that begins "ovirt" is version 3.4.something and every package that begins "vdsm" is version 4.14.6, but "vdsClient -s 0 getVdsCaps" reports clusterLevels = ['3.0', '3.1', '3.2', '3.3' ]. So it looks like ovirt 3.4 isn't compatible with ovirt 3.4, which seems a bit odd. What have I done wrong here?
The other Alert is "Power Management is not configured for this Host.". I don't have any kind of power management for this box, is it possible to stop this message?
Hi Jim Regarding the Power Management issue : Currently we consider a Host that has no Power Management defined as problem and alert on that. This is done even you are using local storage and will not have any other host in future as you can see in https://bugzilla.redhat.com/show_bug.cgi?id=1053434 (which is targeted for 4.0 ATM) However, we see the need for preventing Power Management as a feature in some installations This will require an overall work of giving that as a special configuration setting and then removing all associated messages, alerts , pop-ups , PM TAB in Host New/Edit, Alerts tab etc. can you please open a RFE on that (open a regular bug + set the FutureFeature as a keyword) Thanks Eli
Thanks
Jim
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 02/04/2014 11:03, Jim@Ovirt wrote:
Host's Cluster Compatibility Version doesn't match the Cluster's Compatibility Version. According to "yum list installed" every package that begins "ovirt" is version 3.4.something and every package that begins "vdsm" is version 4.14.6, but "vdsClient -s 0 getVdsCaps" reports clusterLevels = ['3.0', '3.1', '3.2', '3.3' ]. So it looks like ovirt 3.4 isn't compatible with ovirt 3.4, which seems a bit odd. What have I done wrong here?
Ah, found it: yum-config-manager --enable fedora-virt-preview yum update Given that ovirt installs that and won't work without it (in the All-In-One configuration) shouldn't it be done by engine-setup? It's documented in the test day notes, but not in the release notes for 3.4 Jim
Il 02/04/2014 12:44, Jim@Ovirt ha scritto:
On 02/04/2014 11:03, Jim@Ovirt wrote:
Host's Cluster Compatibility Version doesn't match the Cluster's Compatibility Version. According to "yum list installed" every package that begins "ovirt" is version 3.4.something and every package that begins "vdsm" is version 4.14.6, but "vdsClient -s 0 getVdsCaps" reports clusterLevels = ['3.0', '3.1', '3.2', '3.3' ]. So it looks like ovirt 3.4 isn't compatible with ovirt 3.4, which seems a bit odd. What have I done wrong here?
Ah, found it: yum-config-manager --enable fedora-virt-preview yum update
Given that ovirt installs that and won't work without it (in the All-In-One configuration) shouldn't it be done by engine-setup?
It's documented in the test day notes, but not in the release notes for 3.4
It's in release notes: http://www.ovirt.org/OVirt_3.4_Release_Notes ... Known Issues EL >= 6.5 or cloud-init >= 0.7.2 are needed for cloud-init feature support (BZ 1029885) All-in-one requires fedora-virt-preview repository ...
Jim _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (3)
-
Eli Mesika -
Jim＠Ovirt -
Sandro Bonazzola