Bug 1746718
Summary: | [downstream clone - 4.3.6] Typo and exception due to non-iterable object on gluster fencing testing | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
Component: | vdsm | Assignee: | Kaustav Majumder <kmajumde> |
Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.3.1 | CC: | godas, kmajumde, lleistne, lsurette, mtessun, rdlugyhe, sabose, srevivo, ycui |
Target Milestone: | ovirt-4.3.6 | Keywords: | ZStream |
Target Release: | 4.3.6 | Flags: | lsvaty:
testing_plan_complete-
|
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | vdsm-4.30.29-1.el7ev | Doc Type: | Bug Fix |
Doc Text: |
Previously, the gluster fencing policy check failed due to a non-iterable object and threw an exception. The code also contained a minor typo. The current release fixes these issues.
|
Story Points: | --- |
Clone Of: | 1688052 | Environment: | |
Last Closed: | 2019-10-10 15:36:50 UTC | Type: | --- |
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: | 1688052 | ||
Bug Blocks: | 1723678 |
Description
RHV bug bot
2019-08-29 07:23:44 UTC
Any update? (Originally by Sahina Bose) As discussed with Gobinda, the fix for this bug will be targeted for ovirt-4.3.6 (Originally by Satheesaran Sundaramoorthi) sync2jira (Originally by Daniel Gur) sync2jira (Originally by Daniel Gur) Tested with RHV 4.3.6 build with vdsm-4.30.29 1. HC env configured with HE VM running on gluster replica 3 volume 2. Fencing policies are enabled on the volume 3. Server quorum is disabled on the engine volume, to make sure stopping glusterd doesn't pause HE VM 4. Stop glusterd on all the nodes. 5. Move the host to maintenance. 6. No errors - 'non iterable' see with engine logs or vdsm logs Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3009 |