Bug 1389730
| Summary: | Replace variables ${HostsList} and ${volumesList} with the correct details when user tries to move a host into maintenance which has unsynced entries. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | RamaKasturi <knarra> | ||||
| Component: | Frontend.WebAdmin | Assignee: | Ramesh N <rnachimu> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | RamaKasturi <knarra> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.1.0 | CC: | bugs | ||||
| Target Milestone: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-10-28 11:00:23 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
ovirt-version: ============== ovirt-engine-4.1.0-0.0.master.20161024211322.gitfc0de31.el7.centos.noarch Created attachment 1214966 [details]
Attaching screenshot for the same
*** This bug has been marked as a duplicate of bug 1386265 *** |
Description of problem: Try placing a node in maintenance which has entries to be healed. User gets a operation cancelled message with error "Error while executing action: Cannot switch the following Host(s) to Maintenance mode: ${HostsList}. Gluster Quorum will be lost for the Volumes: ${VolumesList} Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Have three nodes named S1,S2 and S3 in the cluster. 2. Have three arbiter / replica 3 volumes vmstore, data and engine 3. Now on the third node S3, bring down bricks from all the volumes 4. Try placing second / first node into maintenance Actual results: Placing first or second node into maintenance gives error saying "Error while executing action: Cannot switch the following Host(s) to Maintenance mode: ${HostsList}. Gluster Quorum will be lost for the Volumes: ${VolumesList}" Expected results: Replace the variables with the correct values. Additional info: