Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 836118

Summary: oVirt - Backend: Can't upgrade pool after changing compatibility version with no active domains
Product: [Retired] oVirt Reporter: Daniel Paikov <dpaikov>
Component: ovirt-engine-coreAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: abaron, acathrow, amureini, dyasny, hateya, iheim, ykaul
Target Milestone: ---   
Target Release: 3.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-11 21:58:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log none

Description Daniel Paikov 2012-06-28 07:12:51 UTC
Created attachment 594955 [details]
engine.log

Last commit c9fe3861562df5dbbeebb14345ad3b9e27c5091e

* DC with domains and compatibility version 3.0.
* Deactivate all domains (to put DC into Maintenance mode) OR disconnect all hosts  (to put the DC into Non-Responsive mode).
* Changing DC compatibility version to 3.1.
* Compatibility version changes but upgradeStoragePool isn't sent to VDSM.
* It is then impossible to run upgrade again through the GUI, since the compatibility version is already changed. The domains remain in V1 forever.

Comment 1 Itamar Heim 2013-03-11 21:58:17 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.