Bug 1638221
| Summary: | [HC] Deployment should set fencing policy to ensure HC environment works | |||
|---|---|---|---|---|
| Product: | [oVirt] ovirt-ansible-collection | Reporter: | Gobinda Das <godas> | |
| Component: | hosted-engine-setup | Assignee: | Gobinda Das <godas> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | unspecified | CC: | bugs, godas, irosenzw, sabose, sasundar | |
| Target Milestone: | ovirt-4.4.0 | Flags: | sbonazzo:
ovirt-4.4?
sbonazzo: planning_ack? sbonazzo: devel_ack+ sasundar: testing_ack+ |
|
| Target Release: | 1.1.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | ovirt-ansible-hosted-engine-setup-1.1.0 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1611956 | |||
| : | 1775552 (view as bug list) | Environment: | ||
| Last Closed: | 2020-05-20 20:02:42 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: | ||||
| Bug Depends On: | 1611956 | |||
| Bug Blocks: | 1610782, 1775552 | |||
|
Comment 1
Sahina Bose
2018-11-21 10:28:22 UTC
Issues created https://github.com/oVirt/ovirt-ansible/issues/163 This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. @Simone/Ido Is there any way to add fencing support in ansible module? *** Bug 1611956 has been marked as a duplicate of this bug. *** Tested with RHV Version 4.4.0-0.33.master.el8ev With the cluster that has both gluster and virt services enabled, the following fencing policies are enabled skip_fencing_if_gluster_bricks_up skip_fencing_if_gluster_quorum_not_met 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. |