Bug 1304811 - Replace resource agent NovaCompute with nova-compute-wait
Summary: Replace resource agent NovaCompute with nova-compute-wait
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.2
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1304011
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-04 16:57 UTC by Marcel Kolaja
Modified: 2016-02-16 11:17 UTC (History)
13 users (show)

Fixed In Version: resource-agents-3.9.5-54.el7_2.6
Doc Type: Bug Fix
Doc Text:
Cause: In order to have instance migration working for ospd8 we need to change the behavior of the NovaCompute resource agent, making it forgot about managing the nova-compute process (which will be managed via systemd) and looking just for migration to finish. Consequence: The nova-compute process needs to be managed via systemd and the resource agent needs to wait for migration to finish. Fix: Let systemd control the nova-compute process and nova-compute-wait wait for migration to finish. Result: Works as intended for instance migration.
Clone Of: 1304011
Environment:
Last Closed: 2016-02-16 11:17:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0217 0 normal SHIPPED_LIVE resource-agents bug fix update 2016-02-16 16:13:57 UTC

Description Marcel Kolaja 2016-02-04 16:57:58 UTC 
This bug has been copied from bug #1304011 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 4 Oyvind Albrigtsen 2016-02-05 09:38:45 UTC 
Before:
# ls /usr/lib/ocf/resource.d/openstack/
NovaCompute  NovaEvacuate

After:
# ls /usr/lib/ocf/resource.d/openstack/
nova-compute-wait  NovaEvacuate
Comment 7 errata-xmlrpc 2016-02-16 11:17:45 UTC 
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/RHBA-2016-0217.html
Note You need to log in before you can comment on or make changes to this bug.