1.21-rc1: Ambiguous resolution of private-address
Bug #1413910 reported by
James Page
This bug report is a duplicate of:
Bug #1435283: juju occasionally switches a units public-address if an additional interface is added post-deployment.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Triaged
|
High
|
Unassigned |
Bug Description
This is an artifact of the way that we test OpenStack ontop of OpenStack using Juju with the openstack provider.
One on the units in the deployment is allocated an additional interface on the same network as the primary network interface; this in interface is allocated an IP address by neutron, however its never actually configured in the units.
After adding the interface, unit-get private-address starts resolving to the un-configured IP address.
Juju should probably look to see what's actually running before deciding to make that switch.
Changed in juju-core: | |
milestone: | 1.22-beta1 → 1.22-beta2 |
tags: | added: network openstack-provider |
Changed in juju-core: | |
milestone: | 1.22-beta2 → none |
Changed in juju-core: | |
status: | New → Triaged |
To post a comment you must log in.
Does this happen with 1.20? If not, it is a regression and we should consider it critical.