Bug 1753628 - webadmin - Modify/Edit an existing DC compatibility level on a local storage domain is not possible
Summary: webadmin - Modify/Edit an existing DC compatibility level on a local storage ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.3.6.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.0
: ---
Assignee: Ahmad Khiet
QA Contact: Daniel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-19 13:22 UTC by Avihai
Modified: 2020-05-20 19:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-20 19:57:39 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)
video_capture of the issue (1.28 MB, video/mp4)
2019-09-19 13:22 UTC, Avihai
no flags Details
comment #1 flow preview (163.67 KB, image/gif)
2019-09-26 10:24 UTC, Ahmad Khiet
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 103570 0 'None' MERGED webadmin: fix datacenter edit versions list 2020-09-28 10:20:12 UTC

Description Avihai 2019-09-19 13:22:40 UTC
Created attachment 1616717 [details]
video_capture of the issue

Description of problem:
Via webadmin changing an existing DC compatibility level(from 4.3 to 4.2 or 4.1) with a local storage type is not available but with a shared storage type it is available.

See short video attached.

There is a workaround, see at additional info section.

Version-Release number of selected component (if applicable):
ovirt-engine 4.3.6.5-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1.Create data center DC-A + cluster with a local storage type and Compatibility Version 4.3

2.Edit DC-A and try to change the Compatibility Version to 4.2 or 4.1

Actual results:
You can't only 4.3 is available in the dropdown.

Expected results:
As with editing an existing DC with a shared storage type you should also have 4.2 and 4.1 options available at the dropdown.

Additional info:
1) Workaround:
   a) Change the DC to be a shared storage type.
   b) Change it to Compatibility Version 4.2 or 4.1.
   c) Change the storage type back to local.

2) Creating a DC with local/shared storage with Compatibility Version 4.3/4.2/4.1 works, only in edit/modify a DC with a local storage type has an issue. 

3) Editing a DC with a shared storage type does show the Compatibility Versions 4.2 and 4.1 at the dropdown.

Comment 1 Ahmad Khiet 2019-09-25 14:25:05 UTC
the DC can ben only upgraded to a higher version, showing older version (downgrade) is not possible. 

but what I see is:

1. select a data center with storage -> click edit
2. in versions list, all the version are present (which is not good) 
3. change the storage type to local, then list the versions (the list will contain the current version only for the current dc)
4. change the storage type to shared, then list the versions  (the list will contain the current version only for the current dc but when the popup first opened, the versions list showed all the versions)

Comment 2 Ahmad Khiet 2019-09-26 10:24:35 UTC
Created attachment 1619443 [details]
comment #1 flow preview

attached a preview for the described steps in comment #1

Comment 3 Andrej Krejcir 2019-12-02 14:58:05 UTC
Hi,

The patch in this BZ does not allow downgrading an existing DC, even if it does not contain any hosts or storage.
I have a new deployment of master and cannot downgrade the 'Default' DC to 4.3.

Is it the expected behavior?

Comment 4 Ahmad Khiet 2019-12-02 15:07:53 UTC
Data Center version can only be upgraded.
this is an expected behavior

Comment 5 Daniel 2019-12-25 07:47:41 UTC
Verified via web-admin, version 4.4.0-0.13.master.el7.

When trying to change DC compatibility level only upgrade is allowed, as expected.
Checked both options of local and shared and for both verified that only upgrade is available and it depends on it cluster compatibility level as well.

Comment 6 Sandro Bonazzola 2020-05-20 19:57:39 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


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