Bug 1186789
Summary: | "Refreshing capabilities" should keep host in maintenance. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ulhas Surse <usurse> |
Component: | ovirt-engine | Assignee: | Eli Mesika <emesika> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.4.3 | CC: | iheim, jentrena, lpeer, lsurette, mchappel, mgoldboi, pdwyer, pstehlik, rbalakri, Rhev-m-bugs, usurse, yeylon, ykaul |
Target Milestone: | ovirt-3.6.2 | Keywords: | Reopened |
Target Release: | 3.6.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-09 20:55:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ulhas Surse
2015-01-28 14:36:58 UTC
Was unable to reproduce 1) Installed a host and wait until it is active 2) Set host to Maintenance 3) Right click menu => Refresh Capabilities Result : host stays in maintenance after this operation Interesting, it's consistently doing this for me... What I did just notice is the following events: 2015-Jan-27, 17:46 State was set to Up for host h02.rhev.qa.int.phx1.redhat.com. 13 h02.rhev.qa.int.phx1.redhat.com UCS1 oVirt 2015-Jan-27, 17:45 Failed to refresh the capabilities of host h02.rhev.qa.int.phx1.redhat.com. 607 mchappel h02.rhev.qa.int.phx1.redhat.com UCS1 1b564869 oVirt Could it be something in the "failure" path that would trigger the host to come back up? (In reply to Mark Chappell from comment #3) > Could it be something in the "failure" path that would trigger the host to > come back up? Seems so, will check... Thanks for the additional information Occurs probably only if the "refresh Capabilities" fails on a host with power management configured I had tested "failure" path for regular host with no PM , host remained in Maintenance please attach full engine.log and the vdsm.log of the host that is serving as a proxy for the fencing operation Verified on 3.6.2-9 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://rhn.redhat.com/errata/RHEA-2016-0376.html |