| Summary: | Replace resource agent NovaCompute with nova-compute-wait | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | resource-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | abeekhof, agk, cfeist, cluster-maint, fdinitto, michele, mjuricek, mkolaja, oalbrigt, oblaut, royoung, rscarazz, snagar |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1304011 | Environment: | |
| Last Closed: | 2016-02-16 11:17:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1304011 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-02-04 16:57:58 UTC
Before: # ls /usr/lib/ocf/resource.d/openstack/ NovaCompute NovaEvacuate After: # ls /usr/lib/ocf/resource.d/openstack/ nova-compute-wait NovaEvacuate 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 |