Nova compute charm is not network space aware
Bug #1670866 reported by
David Ames
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Nova Compute Charm |
Fix Released
|
High
|
David Ames | ||
Bug Description
When nova compute is deployed with multiple network interfaces
configured the charm may select the wrong interface for various relationships including cloud-compute.
It should not use unit_get(
results. Instead, it should leverage network-get for network spaces aware address
selection.
| Changed in charm-nova-compute: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → David Ames (thedac) |
| milestone: | none → 17.05 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to charm-nova-compute (master) | #1 |
| Changed in charm-nova-compute: | |
| status: | In Progress → Fix Committed |
| Changed in charm-nova-compute: | |
| milestone: | 17.05 → 17.08 |
| Changed in charm-nova-compute: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3f3a159704e5a6a
Author: David Ames <email address hidden>
Date: Tue Mar 7 08:33:13 2017 -0800
Make the cloud-compute relation net spaces aware
When nova compute is deployed with multiple network interfaces
configured. It may be necessary to specify which interface to use for
the cloud-compute relation.
Do not use unit_get(
results. Instead, leverage network-get for network spaces aware address
selection.
Charm helpers sync to pull in generalized get_relation_ip() used in
other charms which checks network-get after checking for all of the edge
cases including IPv6 and config overrides. Use get_relation_ip() for
address selection.
This allows for specifying a network space in a bundle when using MAAS
2.x. This guarantees the charm will select the correct interface and IP
for the network space.
nova-compute:
bindings:
Closes-bug: #1670866
Change-Id: Ib43a7a52acf5a0