Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1487981 - [downstream clone - 4.1.7] Host enters to power management restart loop
[downstream clone - 4.1.7] Host enters to power management restart loop
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
4.1.2
x86_64 Linux
high Severity high
: ovirt-4.1.7
: ---
Assigned To: Eli Mesika
Petr Matyáš
: Automation, ZStream
Depends On: 1477700
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-03 23:20 EDT by Germano Veit Michel
Modified: 2018-03-19 09:43 EDT (History)
15 users (show)

See Also:
Fixed In Version: ovirt-engine-4.1.7.2
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1477700
Environment:
Last Closed: 2017-11-07 12:27:54 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 80345 None None None 2017-09-03 23:20 EDT
oVirt gerrit 80401 None None None 2017-09-03 23:20 EDT
oVirt gerrit 81931 None None None 2017-09-19 15:11 EDT
oVirt gerrit 81932 ovirt-engine-4.1 MERGED core: disable host fencing in reboot 2017-09-19 17:52 EDT
Red Hat Product Errata RHEA-2017:3138 normal SHIPPED_LIVE Red Hat Virtualization Manager (ovirt-engine) 4.1.7 2017-11-07 17:22:33 EST

  None (edit)
Comment 5 Martin Perina 2017-09-04 08:10:09 EDT
Aligning with status of BZ1477700
Comment 6 Martin Perina 2017-09-06 03:42:58 EDT
We are still not able to reproduce the issue, so retargeting to 4.1.7 for now, but we are continuing investigations and we can release as 4.1.6 async if ready soon
Comment 7 Petr Matyáš 2017-10-02 12:04:19 EDT
Verified on ovirt-engine-4.1.7.1-0.1.el7.noarch
Comment 9 errata-xmlrpc 2017-11-07 12:27:54 EST
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/RHEA-2017:3138

Note You need to log in before you can comment on or make changes to this bug.