juju 1/2 using MAAS 1.9/2 incorrectly reports the private address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned | ||
OPNFV |
New
|
Critical
|
Unassigned | ||
juju-core |
Won't Fix
|
High
|
Unassigned |
Bug Description
juju-core 1.25.0 and using a MAAS environment based on 1.9.0~beta2+bzr4456
juju reports the DNS name from the MAAS environment in juju status as the public-address, this would likely map to the PXE boot interface, usually the management network, for Openstack deployments.
But the IP address it picks for the private address is different and therefore not on the management network.
In a situation with multiple NICs on a node and some that may be in separate spaces in MAAS (i.e. cannot route between each other).
Then it is the case that the private address used by juju will matter, as it needs to be reachable from the bootstrap node.
This would usually be the management network on eth0.
In a test deployment with nodes in MAAS with multiple NICs, juju selected the address on eth1, not the PXE boot interface, eth0.
Networks used were:
192.168.92.0/24 - management network - always eth0
192.168.95.0/24 - public network
192.168.140.0/24 - data network
192.168.160.0/24 storage network
The private address reported on the nodes with multiple NICs were on the data network, 192.168.140.0/24
The most obvious symptom is that juju ssh does not work to nodes as it proxies through the bootstrap node that cannot reach the 192.168.140.0/24 network.
To re-create:
using MAAS 1.9-beta2
Create nodes in MAAS with at least 2 NICs in different spaces (i.e.. subnets are not routed to each other)
Bootstrap juju 1.25.0
Add a machine with 2 NICs using juju add-machine
Use juju ssh to try connecting to the machine.
Juju ssh will hang.
tags: | added: addressability maas-provider networking |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.0.0 |
Changed in juju: | |
assignee: | nobody → Richard Harding (rharding) |
Changed in juju: | |
milestone: | 2.0.0 → 2.1.0 |
summary: |
- juju 1.25.0 using MAAS 1.9-beta2 juju incorrectly reports the private - address + juju using MAAS 1. incorrectly reports the private address |
summary: |
- juju using MAAS 1. incorrectly reports the private address + juju using MAAS 1.9 incorrectly reports the private address |
summary: |
- juju using MAAS 1.9 incorrectly reports the private address + juju 1/2 using MAAS 1.9/2 incorrectly reports the private address |
tags: | added: oil oil-2.0 |
Changed in opnfv: | |
importance: | Undecided → Critical |
Changed in juju: | |
assignee: | Richard Harding (rharding) → nobody |
Changed in opnfv: | |
status: | New → Invalid |
status: | Invalid → New |
I am getting the DNS name instead of the IP in the public address running on juju 1.24.5 and maas 1.8.2.
But I am only getting it from the first of three units of my charms. So I am getting the DNS name in public-address field from relation-get when the peer relation changes with the first unit and getting IP when the relation changes with any other unit.