Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1568442 - ovirt driver doesn't reboot stopped VMs
ovirt driver doesn't reboot stopped VMs
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic-staging-drivers (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
medium Severity medium
: beta
: 13.0 (Queens)
Assigned To: Ilya Etingof
mlammon
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-17 10:01 EDT by Bob Fournier
Modified: 2018-06-27 09:52 EDT (History)
3 users (show)

See Also:
Fixed In Version: openstack-ironic-staging-drivers-0.9.0-4.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-27 09:52:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1752575 None None None 2018-04-17 10:01 EDT
OpenStack gerrit 563094 None stable/queens: MERGED ironic-staging-drivers: reboot stopped vms in ovirt (I851935a042c3e69e7e4ce72d6338ce2f77baa566) 2018-04-24 12:07 EDT
Red Hat Product Errata RHEA-2018:2086 None None None 2018-06-27 09:52 EDT

  None (edit)
Description Bob Fournier 2018-04-17 10:01:25 EDT
Description of problem:

When using the Ironic ovirt driver, a reboot does not start stopped VMs
Comment 1 Bob Fournier 2018-04-17 10:03:02 EDT
When https://review.openstack.org/#/c/548943/ lands it will need to be backported to Queens.
Comment 6 mlammon 2018-05-08 17:05:50 EDT
installed latest osp13 puddle 2018-05-04.1

with node power off, executed "openstack baremetal node reboot <uuid>" and observed that the node powered on. 

env:
openstack-ironic-staging-drivers-0.9.0-4.el7ost.noarch
Comment 8 errata-xmlrpc 2018-06-27 09:52:00 EDT
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-2018:2086

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