Relation fails as units/machines are on different subnet on a multi NIC setup, juju 2.0 beta11
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
High
|
Unassigned | ||
2.0 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
On a multi NIC setup, we notice with Juju 2.0 beta11 and MAAS 1.9, some machines' preferred private addresses are not the IP address provisioned and provided by MAAS but the one from a second NIC where we set the IP manually for SSH remote access. The machines and the containers have a valid IP from both subnets, but when the relation is established between the nova compute and the nova cloud controller, it performs certain reverse DNS operation and it gives the error: http://
With Juju 2.0 beta5, this did not happen.
Setup details:
As the charm is still be worked on, I had attached the yaml file to deploy the charms of openstack bundle only, and the yaml file is attached to this bug.
Note: here we are not using the neutron-gateway and few other nodes from openstack(Which our charm will take care of).
With Juju 2.0 beta11:
MAAS (Running in a VM in Virtual machine manager)
JUJU (in a VM in Virtual machine manager)
.local/
cplane-
unresolved-
uuid: 1a5c7aba-
api-endpoints: ['10.9.
Juju status: in tabular format: http://
Juju status in yaml format: http://
Here machine 0 is the bootstrap node, where the dns name is an IP from the managed(DNS and DHCP) network that is from 10.9.1.x series.
But in case of other nodes(1, 2 and 3) the dns name are the IP from the unmanaged network that is from 10.10.11.x series
With Juju 2.0 beta5:
MAAS (Running in a VM in Virtual machine manager)
JUJU (in a VM in Virtual machine manager)
Content of .local/
controllers:
local.
unresolved-
uuid: eab2b453-
api-endpoints: ['192.168.
Juju status:
[Machines]
ID STATE DNS INS-ID SERIES AZ
0 started 10.14.0.100 /MAAS/api/
1 pending 10.14.0.102 /MAAS/api/
2 pending 10.14.0.103 /MAAS/api/
3 pending 10.14.0.101 /MAAS/api/
Additional info:
We tried to use --bind to deploy the charm to a specific network space, but it doesn't work.
We defined 2 spaces in MAAS:
unused: 10.10.11.x series
default: 10.9.1.x series
These spaces can be listed through the juju command "juju list-spaces" in the juju controller node, which is listing all the spaces in our setup properly. We 'juju deploy juju-gui --bind Default<please confirm>' but the preferred private-address is still from the 10.10.11.x series. Used juju run --unit juju-gui/0 "unit-get private-address" to check.
Changed in juju-core: | |
importance: | Undecided → High |
Changed in juju-core: | |
status: | New → Incomplete |
Changed in juju-core: | |
assignee: | nobody → Mick Gregg (macgreagoir) |
Changed in juju-core: | |
assignee: | Mick Gregg (macgreagoir) → nobody |
assignee: | nobody → Dimiter Naydenov (dimitern) |
Changed in juju-core: | |
milestone: | none → 2.0.0 |
summary: |
- Relation fails as untis/machines are on different subnet on a multi NIC + Relation fails as units/machines are on different subnet on a multi NIC setup, juju 2.0 beta11 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.0 → none |
milestone: | none → 2.0.0 |
Changed in juju: | |
milestone: | 2.0.0 → 2.0-rc1 |
Changed in juju: | |
status: | Incomplete → Triaged |
Changed in juju: | |
assignee: | Dimiter Naydenov (dimitern) → nobody |
Changed in juju: | |
milestone: | 2.0-rc1 → 2.0-rc2 |
Changed in juju: | |
milestone: | 2.0-rc2 → 2.0.0 |
tags: | added: teamb |
tags: |
added: rteam removed: teamb |
Changed in juju: | |
assignee: | nobody → Richard Harding (rharding) |
milestone: | 2.0.0 → 2.1.0 |
milestone: | 2.1.0 → 2.0.0 |
Changed in juju: | |
milestone: | 2.0-rc3 → 2.0.0 |
Changed in juju: | |
milestone: | 2.0.0 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
Do we have a screenshot of the MAAS 1.9 network setup for these nodes? I am interested to see the order of the interfaces, what is configured (static, dhcp, et al) and which is the PXE interface. Given that I will look at reproducing. Thanks.