juju-core

1.21-rc1: Ambiguous resolution of private-address

Bug #1413910 reported by James Page
6
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.

Revision history for this message
Aaron Bentley (abentley) wrote :

Does this happen with 1.20? If not, it is a regression and we should consider it critical.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.22-beta1
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.22-beta1 → 1.22-beta2
Revision history for this message
James Page (james-page) wrote :

This does not happen on 1.20.

Curtis Hovey (sinzui)
tags: added: network openstack-provider
Revision history for this message
Dimiter Naydenov (dimitern) wrote :

I'll need some more info about this issue - at the very least machine and unit logs at DEBUG level please.

Revision history for this message
James Page (james-page) wrote :

As I can no longer reproduce with 1.21.0, marking Invalid.

Sorry for the noise.

Changed in juju-core:
status: Triaged → Invalid
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.22-beta2 → none
Revision history for this message
James Page (james-page) wrote :

OK - so I reproduced this on 1.23.2 - it happens in a very specific set of circumstances - four units have a second port allocated:

| 2f0e5d14-c830-4e29-bca9-d661b70a3b50 | juju-devel3-machine-12 | ACTIVE | - | Running | james-page_admin_net=10.5.19.99, 10.5.19.110 |
| 4d1a00f3-f6bd-4ed2-8db9-a01358d81beb | juju-devel3-machine-14 | ACTIVE | - | Running | james-page_admin_net=10.5.19.101, 10.5.19.112 |
| d99e5fb0-b35c-4ef8-8d16-8d424a23cc6b | juju-devel3-machine-15 | ACTIVE | - | Running | james-page_admin_net=10.5.19.102, 10.5.19.111 |
| 03b1db44-ef2d-42c1-9c5e-c58df08e5ecf | juju-devel3-machine-16 | ACTIVE | - | Running | james-page_admin_net=10.5.19.103, 10.5.19.113

only juju-devel3-machine-12 observed a change in unit private-address from juju - this was the only one that rolled over the 99->100 barrier.

Changed in juju-core:
status: Invalid → New
Martin Packman (gz)
Changed in juju-core:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.