Bug 1057029 - Cannot decreasedata center compatibility version - On newly created DC
Summary: Cannot decreasedata center compatibility version - On newly created DC
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.2
Assignee: Liran Zelkha
QA Contact: bugs@ovirt.org
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-23 11:09 UTC by Vinzenz Feenstra [evilissimo]
Modified: 2014-07-25 04:13 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-11 06:44:17 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25637 0 None ABANDONED core: enable to decrease DC compatibility... Never
oVirt gerrit 26947 0 master MERGED core: Support decreasing dc compatbility version Never

Description Vinzenz Feenstra [evilissimo] 2014-01-23 11:09:44 UTC
Description of problem:
Once a data center compatibility version was selected during the creation of a new datacenter, it cannot be changed to a lower value anymore, even if there is no cluster or anything attached to.

Version-Release number of selected component (if applicable):
ovirt-engine-setup-base-3.4.0-0.5.beta1.el6.noarch
ovirt-engine-userportal-3.4.0-0.5.beta1.el6.noarch
ovirt-image-uploader-3.4.0-0.1.beta1.el6.noarch
ovirt-engine-tools-3.4.0-0.5.beta1.el6.noarch
ovirt-release-el6-10.0.1-2.noarch
ovirt-engine-sdk-python-3.4.0.2-1.20140114.gitbaccf38.el6.noarch
ovirt-iso-uploader-3.4.0-0.1.beta1.el6.noarch
ovirt-engine-websocket-proxy-3.4.0-0.5.beta1.el6.noarch
ovirt-engine-cli-3.4.0.2-1.20140112.git01360ed.el6.noarch
ovirt-engine-restapi-3.4.0-0.5.beta1.el6.noarch
ovirt-engine-backend-3.4.0-0.5.beta1.el6.noarch
ovirt-host-deploy-1.2.0-0.1.beta.el6.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.4.0-0.5.beta1.el6.noarch
ovirt-host-deploy-java-1.2.0-0.1.beta.el6.noarch
ovirt-engine-webadmin-portal-3.4.0-0.5.beta1.el6.noarch
ovirt-engine-3.4.0-0.5.beta1.el6.noarch
ovirt-log-collector-3.4.0-0.1.beta1.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-0.5.beta1.el6.noarch
ovirt-engine-dbscripts-3.4.0-0.5.beta1.el6.noarch
ovirt-engine-lib-3.4.0-0.5.beta1.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.4.0-0.5.beta1.el6.noarch


How reproducible:
Always

Steps to Reproduce:
1. Create new datacenter with version compatibility version 3.4 (or simply the highest)
2. Choose newly created data center and click edit 
3. Try to change the compatibility to a lower version

Actual results:
Error: Cannot decreasedata center compatibility version

Expected results:
Success

Additional info:

Comment 1 Itamar Heim 2014-01-26 08:11:14 UTC
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Sandro Bonazzola 2014-03-04 09:28:07 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 3 Eli Mesika 2014-04-02 08:15:51 UTC
When DC is downgraded :
  Block downgrading if there are Hosts or Networks (other than the default
  management network) or SD in the DC.
  In case that only default management network exists we should check that all
  network features are still supported (This can be done by adding a method
  to the NetworkValidator that will check for support of all relevant
  features)

Comment 4 Liran Zelkha 2014-05-13 08:08:27 UTC
Please see this discussion thread on conditions where decreasing a DC is allowed. http://lists.ovirt.org/pipermail/devel/2014-March/006807.html

Comment 5 Sandro Bonazzola 2014-06-11 06:44:17 UTC
This is an automated message

oVirt 3.4.2 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.


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