Description of problem: The PreparingForMaintenance status was added in order to make sure that when a domain moves to Maintenance status it's not accessed by any host in the data center. Currently we don't allow to deactivate a domain when it's status is Inactive, while on that status it may be still accessed by some of the DC hosts. How reproducible: Always Steps to Reproduce: 1. Have a DC with two hosts and two domains, each on a different storage server. 2. Block the connection between the two hosts and the non master domain. 3. Wait for the domain to become Inactive (the default time interval for that is 5 minutes). 4. Attempt to deactivate the domain. Actual results: The engine blocks the deactivation of the domain. Expected results: The engine shouldn't allow to deactivat the domain. Additional info:
(In reply to Liron Aravot from comment #0) > Actual results: > The engine blocks the deactivation of the domain. > > Expected results: > The engine shouldn't allow to deactivat the domain. I think the actual and expected result here are pretty much the same. Can you please clarify this for me (I don't want to make assumptions that might be wrong) Thanks
(In reply to Natalie Gavrielov from comment #1) > (In reply to Liron Aravot from comment #0) > > Actual results: > > The engine blocks the deactivation of the domain. > > > > Expected results: > > The engine shouldn't allow to deactivat the domain. > > I think the actual and expected result here are pretty much the same. > Can you please clarify this for me (I don't want to make assumptions that > might be wrong) > > Thanks Yes, this is clearly not the intention of the BZ. Actual results: Engine blocks the deactivation of an Inactive domain. Probably something like "Cannot deactivate Storage Domain. The relevant Storage Domain's status is Inactive". Expected results: Engine should NOT block the deactivation of an Inactive domain. I.e., clicking the button (or sending a REST request) should not fail, and the domain should (after a short period) move to MAINTENANCE.
Verified using builds: ovirt-engine-4.2.0-0.0.master.20170725202023.git561151b.el7.centos.noarch vdsm-4.20.1-218.git1b7671f.el7.centos.x86_64
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.