Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1326421 - Prevent upgrade to 4.0 if datacenters and clusters older than 3.6 are managed
Prevent upgrade to 4.0 if datacenters and clusters older than 3.6 are managed
Status: CLOSED CURRENTRELEASE
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine (Show other bugs)
4.0.0
Unspecified Unspecified
high Severity urgent (vote)
: ovirt-4.0.0-alpha
: 4.0.0
Assigned To: Allon Mureinik
Jiri Belka
:
Depends On:
Blocks: 1343898
  Show dependency treegraph
 
Reported: 2016-04-12 11:45 EDT by Sandro Bonazzola
Modified: 2017-05-11 05:29 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Deprecated Functionality
Doc Text:
Red Hat Virtualization Manager 4.0 does not support data center or cluster compatibility levels 3.5 or lower. A data center or cluster compatibility version of 3.5 or lower will prevent an upgrade to Red Hat Virtualization 4.0.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-05 03:58:33 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Integration
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.0.0+
rule-engine: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 55752 None None None 2016-04-14 06:46 EDT

  None (edit)
Description Sandro Bonazzola 2016-04-12 11:45:10 EDT
Description of problem:
with https://gerrit.ovirt.org/#/c/55752/ support for datacenters older than 3.6 will be dropped. We should stop the upgrade and tell user to upgrade datacenters first to at least 3.6, before upgrading engine.
Comment 1 Michal Skrivanek 2016-04-13 01:25:49 EDT
Same for Cluster level
Comment 2 Sandro Bonazzola 2016-04-14 06:46:01 EDT
Assigning to Allon who already pushed a patch including a fix for this.
Comment 3 Michal Skrivanek 2016-05-14 03:19:38 EDT
how is this MODIFIED with patch 55752 only? It just removes <=3.5 code from engine but there's no upgrade code to stop users from upgrading when they have 3.5 clusters/DCs. Is there a patch missing?
Comment 5 Michal Skrivanek 2016-05-20 10:11:54 EDT
Ah, I missed that. Thanks. Just beware it won't be enough in the next version since the introduction of a per VM cluster level override
Comment 6 Allon Mureinik 2016-06-14 07:50:51 EDT
The doctext claimed that "Red Hat Virtualization Manager 4.0 does not support data center or cluster compatibility levels 3.6 or lower.", implying that 3.6 clusters/DCs aren't supported. This is /not/ correct - 3.6 clusters/DCs are supported, compatibility version lower than that (i.e., **3.5 or lower** are not.

I fixed the numbering and reset the flag to ? to make sure someone from the documentation team confirms this phrasing.
Comment 7 daniel 2016-06-25 05:35:33 EDT
Documentation about this bug in https://access.redhat.com/documentation/en/red-hat-virtualization/4.0-beta/release-notes/ is wrong since it states 3.6 cannot be upgraded:

---
BZ#1326421
Red Hat Virtualization Manager 4.0 does not support data center or cluster compatibility levels 3.6 or lower. A data center or cluster compatibility version of 3.6 or lower will prevent an upgrade to Red Hat Virtualization 4.0.
---

To my understanding this should be 3.5 and lower
Comment 8 Allon Mureinik 2016-06-25 22:59:30 EDT
(In reply to dmoessne from comment #7)
> Documentation about this bug in
> https://access.redhat.com/documentation/en/red-hat-virtualization/4.0-beta/
> release-notes/ is wrong since it states 3.6 cannot be upgraded:
> 
> ---
> BZ#1326421
> Red Hat Virtualization Manager 4.0 does not support data center or cluster
> compatibility levels 3.6 or lower. A data center or cluster compatibility
> version of 3.6 or lower will prevent an upgrade to Red Hat Virtualization
> 4.0.
> ---
> 
> To my understanding this should be 3.5 and lower

You understanding is correct.
This seems to be the text provided before I corrected it in comment 6.

Byron - is there anything special that needs to be done to get the updated text pushed to the documentation, or will this be done automatically once the next beta/GA is released?
Comment 11 Jiri Belka 2016-07-01 07:10:37 EDT
ok, 4.0.0-19

...
[ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160701130929-lhrkf9.log
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160701130943-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed
[root@10-34-61-116 ~]# rpm -qf `which engine-setup`
ovirt-engine-setup-base-4.0.0.6-0.1.el7ev.noarch
Comment 12 Sandro Bonazzola 2016-07-05 03:58:33 EDT
oVirt 4.0.0 has been released, closing current release.

Note You need to log in before you can comment on or make changes to this bug.