Bug 1256841
Summary: | Storage domain remains in 'preparing for maintenance' when there is a non operational host | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Liron Aravot <laravot> |
Component: | BLL.Storage | Assignee: | Liron Aravot <laravot> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Elad <ebenahar> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | acanan, amureini, bugs, cmestreg, gklein, laravot, lsurette, rbalakri, Rhev-m-bugs, tnisan, yeylon, ykaul, ylavi |
Target Milestone: | ovirt-3.6.2 | Flags: | rule-engine:
ovirt-3.6.z+
ylavi: planning_ack+ amureini: devel_ack+ rule-engine: testing_ack+ |
Target Release: | 3.6.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1247957 | Environment: | |
Last Closed: | 2016-02-18 11:01:49 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: |
Description
Liron Aravot
2015-08-25 14:59:58 UTC
should this be in POST? this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag. oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA Liron, should I verify according to the steps written in the description? Elad, yes - but it doesn't have to be a gluster domain. Storage domain deactivation, while having a non-operational host in the DC due to storage issues, succeeds.Domain changes its status to maintenance. Tested the following scenario: - 2 hosts in DC, 2 active domains (iSCSI and Gluster) - Blocked one of the hosts to the Gluster domain. Host status changed to non-op - Deactivated the Gluster domain Domain moved to maintenance successfully, in event log got the following: Storage Domain data4 (Data Center Default) was deactivated and has moved to 'Preparing for maintenance' until it will no longer be accessed by any Host of the Data Center. - Activated the Gluster domain and deactivated the iSCSI domain (while the Gluster domain is still blocked from one of the hosts) iSCSI domain moved maintenance successfully. Verified using: rhevm-3.6.2.5-0.1.el6.noarch vdsm-4.17.17-0.el7ev.noarch |