Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1174422 - Evacuate Fails 'Invalid state of instance files' using Ceph Ephemeral RBD
Evacuate Fails 'Invalid state of instance files' using Ceph Ephemeral RBD
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
5.0 (RHEL 7)
All Linux
high Severity high
: z4
: 5.0 (RHEL 7)
Assigned To: Eoghan Glynn
Yogev Rabl
: ZStream
Depends On: 1148193 1174424
Blocks: 743661 1038706 rhelosp_ceph_integration
  Show dependency treegraph
 
Reported: 2014-12-15 15:01 EST by Scott Lewis
Modified: 2015-04-16 10:35 EDT (History)
19 users (show)

See Also:
Fixed In Version: openstack-nova-2014.1.3-10.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, the evacuate function did not consider RBD storage as shared and the evacuate procedure failed with RBD-backed instances. With this fix, RBD storage is now marked as shared, and the evacuate function handles the shared storage attribute and therefore now operates on RBD.
Story Points: ---
Clone Of: 1148193
Environment:
Last Closed: 2015-04-16 10:35:04 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 1340411 None None None Never
OpenStack gerrit 130905 None None None Never
OpenStack gerrit 131629 None None None Never
Red Hat Product Errata RHSA-2015:0843 normal SHIPPED_LIVE Important: openstack-nova security, bug fix, and enhancement update 2015-04-16 14:27:45 EDT

  None (edit)
Comment 5 Yogev Rabl 2015-04-12 05:01:57 EDT
I'm not sure about how the system defines a failed compute. 
The scenario I've tested is: 
1. stopped the services openstack-nova-compute or libvirtd
2. tried to evacuate an instance 
With both options the system response to the evacuation was: 
ERROR: Compute service of <host name> is still in use. 

Eoghan, How can I change the status of the Compute?
Comment 6 Pádraig Brady 2015-04-13 07:38:27 EDT
Please ensure the openstack-nova-api service is stopped
Comment 7 Eoghan Glynn 2015-04-13 08:25:51 EDT
After discussing on IRC, the conclusion is:

 * nova-api service should not be shut down, as the POST /v2/​{tenant_id}​/servers/​{server_id}​/evacate call must be mediated by the service for each VM on the old node

 * shutting down nova-compute service should suffice, but in realistic example reproducing this issue, the entire compute node was powered-down
Comment 8 Yogev Rabl 2015-04-14 08:47:43 EDT
verified on RHEL 7, Nova version: 

openstack-nova-common-2014.1.4-3.el7ost.noarch
openstack-nova-novncproxy-2014.1.4-3.el7ost.noarch
python-novaclient-2.17.0-4.el7ost.noarch
openstack-nova-console-2014.1.4-3.el7ost.noarch
openstack-nova-conductor-2014.1.4-3.el7ost.noarch
openstack-nova-cert-2014.1.4-3.el7ost.noarch
python-nova-2014.1.4-3.el7ost.noarch
openstack-nova-compute-2014.1.4-3.el7ost.noarch
openstack-nova-api-2014.1.4-3.el7ost.noarch
openstack-nova-scheduler-2014.1.4-3.el7ost.noarch
Comment 10 errata-xmlrpc 2015-04-16 10:35:04 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://rhn.redhat.com/errata/RHSA-2015-0843.html

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