Description of problem: Not able to create a cluster with compatibility version 3.3 in ovrit 3.4 while running in 'Gluster Only' mode Version-Release number of selected component (if applicable): 3.4 How reproducible: Always Steps to Reproduce: 1. Install an Ovirt Engine with Ovirt 3.4 2. Create a new Cluster with 3.3 compatibility 3. Actual results: Only 3.4 compatibility version is shown as in the 'Compatibility Version' list. Expected results: All compatibility versions should be shown in the list. Additional info: This bug blocks using the F19 as a node in oVirt 3.4 as F19 only supports cluster compatibility version 3.3 as in bug https://bugzilla.redhat.com/show_bug.cgi?id=1056918
is this really a bug? if you chose a 3.4 DC (I'm guessing), you can't create a 3.3 cluster in it. i.e., you need to create a 3.3 DC, then you can add a 3.3 (or above) cluster in it?
Itamar: By OVrit 3.4, I meant 3.4 release of OVirt. In 'Gluster Only' mode, there is no data center and you only create Cluster and I am not able to create 3.3 Cluster.
good one. there is a default DC, its just hidden... sahina - thoughts?
Itamar, Yes..The default DC is hidden. We had a patch earlier to change the level of Default DC to lowest (i.e 3.1) for gluster only mode - but this was abandoned as thought to be a hack. Instead, the ask was to change the validations for gluster only mode to allow cluster creation irrespective of DC level. Need to submit a patch for this
sahina - i suggest you share a hacky workaround of changing the dc level via db change for now (I'd suggest via api, but its probably blocked to downgrade via api)
Yes, the api blocks update of DC with message: Cannot decrease compatibility version. Hack is to change the Default DC compatibility value to 3.1 in database for gluster only modes: #psql engine postgres -c "update storage_pool set compatibility_version = '3.1' where name = 'Default';"
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
The same issue is for Both operational mode (Gluster + Virt). I've installed ovirt-engine 3.4 on f19 with allinone plugin.
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.4.2 as it has severity high, please retarget if needed. If this is a blocker please add it to the tracker Bug #1095370
This is an automated message: oVirt 3.4.2 has been released. This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.
As the suggested fix for this affects validations in quite a few UI screens, targeting this for 3.6 A workaround exists as mentioned in comment 6 For Both mode, Gluster + ovirt, you should be able to create a new DC with compatibility mode 3.3 in order to create a 3.3 cluster under it.
*** Bug 1006675 has been marked as a duplicate of this bug. ***
Anmol, can you look at this one? We need to change the validations for cluster creation in case of gluster only mode - that is, do not check Data center version while creating/modifying cluster. (as per comments in https://gerrit.ovirt.org/#/c/19185/)
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4. If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution) If it's an RFE please update the version to 4.0 if still relevant.
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still an issue.