Bug 1286566
Summary: | Nova APIs used by fence_compute have changed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Andrew Beekhof <abeekhof> |
Component: | fence-agents | Assignee: | Marek Grac <mgrac> |
Status: | CLOSED NOTABUG | QA Contact: | cluster-qe <cluster-qe> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 7.2 | CC: | abeekhof, cfeist, cluster-maint, eglynn, fdinitto, sbauza |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-02 03:08:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1185030 |
Description
Andrew Beekhof
2015-11-30 09:20:53 UTC
abeekhof: can you give a concise description of what exactly has changed in the nova-api? Is it that the nova hypervisors API now returns host UUIDs wheeas previously it reported symbolic hostnames? Not sure I understand the problem. The output of _server_evacuate() (ie. the dict keyed with server_uuid) has been introduced with https://github.com/ClusterLabs/fence-agents/commit/855c7f617e6afc840540439c359de970d3dc8cee We haven't changed that since the beginning, so I don't get what's the problem here. Could you please be more explicit, and tell us what has been regressed so we could identify how to fix that ? To be clear, I'm speaking of https://github.com/ClusterLabs/fence-agents/blob/f32efc776fd146aa9f386f2e635707763baf231f/fence/agents/compute/fence_compute.py#L63-L67 which is independent of what provides the Nova API. Eoghan, Sylvain, apologies I thought I had closed this bug. I misattributed the change in output to changes to nova. In practice, the person who set up the environment had accidentally pointed the fencing configuration to nova on the undercloud instead of the overcloud (and I was slow to realise what was going on). No bug here. Sorry for the noise. |