Handle HostMappingNotFound when deleting a service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| OpenStack Compute (nova) |
High
|
Matt Riedemann | ||
| Ocata |
High
|
Matt Riedemann | ||
| Pike |
High
|
Matt Riedemann | ||
| Queens |
High
|
Matt Riedemann |
Bug Description
While deleting a service, we also try to delete the HostMapping before it here: https:/
Matt Riedemann (mriedem) wrote : | #2 |
It's valid to have a compute service w/o a host mapping if the nova-compute service was started but discover_hosts was not yet run, we shouldn't block the compute service delete on that, so we should just handle HostMappingNotFound and pass.
Changed in nova: | |
importance: | Undecided → High |
assignee: | Surya Seetharaman (tssurya) → Matt Riedemann (mriedem) |
Fix proposed to branch: master
Review: https:/
Changed in nova: | |
status: | Confirmed → In Progress |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit ee6e0c1e7eb861e
Author: Matt Riedemann <email address hidden>
Date: Fri Jul 13 15:42:03 2018 -0400
Handle HostMappingNotFound when deleting a compute service
If the compute service we're deleting has never been
discovered (mapped to a cell using discover_hosts) or the
host mapping was already deleted, we need to handle the
HostMapping
so that we (1) don't 500 out of the API and (2) continue to
delete the compute service.
Change-Id: I0d7644db3537a6
Closes-Bug: #1780727
Changed in nova: | |
status: | In Progress → Fix Released |
Fix proposed to branch: stable/queens
Review: https:/
Fix proposed to branch: stable/pike
Review: https:/
This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 0be8cbc302aa77b
Author: Matt Riedemann <email address hidden>
Date: Fri Jul 13 15:42:03 2018 -0400
Handle HostMappingNotFound when deleting a compute service
If the compute service we're deleting has never been
discovered (mapped to a cell using discover_hosts) or the
host mapping was already deleted, we need to handle the
HostMapping
so that we (1) don't 500 out of the API and (2) continue to
delete the compute service.
Change-Id: I0d7644db3537a6
Closes-Bug: #1780727
(cherry picked from commit ee6e0c1e7eb861e
This issue was fixed in the openstack/nova 17.0.6 release.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 0b45fcd3ba345b3
Author: Matt Riedemann <email address hidden>
Date: Fri Jul 13 15:42:03 2018 -0400
Handle HostMappingNotFound when deleting a compute service
If the compute service we're deleting has never been
discovered (mapped to a cell using discover_hosts) or the
host mapping was already deleted, we need to handle the
HostMapping
so that we (1) don't 500 out of the API and (2) continue to
delete the compute service.
Change-Id: I0d7644db3537a6
Closes-Bug: #1780727
(cherry picked from commit ee6e0c1e7eb861e
(cherry picked from commit 0be8cbc302aa77b
This issue was fixed in the openstack/nova 16.1.7 release.
Fix proposed to branch: stable/ocata
Review: https:/
yeah, that can be raised from [1]. I feel proceeding further if no host mapping is good way. We can discuss on patch if any side effect of that.
[1] https:/ /github. com/openstack/ nova/blob/ d3fa585f5e2d11a 91ee62744a0cf0c 78921a47e4/ nova/objects/ host_mapping. py#L95