juju2, maas2, cloud deployment failure when two domains are used.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
MAAS |
Fix Released
|
Undecided
|
Unassigned | ||
nova-cloud-controller (Juju Charms Collection) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
ii maas 2.0.0~rc2+
$ juju --version # 2.0-beta12-
nova-cloud-
== What happened ==
I have a 8 node maas server, all 8 nodes are in a domain called 'massive'. I actually do-release-upgraded this system from trusty and maas1.9 to xenial and maas2, and it kept all these settings. On upgrade, it created a default 'maas' domain, which was empty.
I then used the autopilot to deploy a cloud. It broke trying to relate nova-c-c to nova-compute, for a host resolution error:
------------------
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 ERROR juju-log cloud-compute:54: Could not obtain SSH host key from grays
------------------
== What I think should have happened ==
1) nova-cloud-
2) juju.
a) Juju should grab IPs for lxds from the same domain *of the physical machine* where it is creating the LXD. *Not* from the default domain.
b) Juju also may want to expose an FQDN parameter in relation settings. I would not suggest changing the semantics of 'hostname'.
3) Maas. Maas should ideally expose a way on the UI to edit the default domain, as I don't particularly want to have two domains on this system, I just don't want my domain called 'maas'.
== Full stacktrace ==
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 INFO juju-log cloud-compute:54: Known host key for compute host 10.5.200.38 up to date.
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 ERROR juju-log cloud-compute:54: Could not obtain SSH host key from grays
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 INFO cloud-compute-
ompute-
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 INFO cloud-compute-
ompute-
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 INFO cloud-compute-
lpers/core/
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 INFO cloud-compute-
ompute-
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 INFO cloud-compute-
_utils.py", line 751, in ssh_compute_add
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 INFO cloud-compute-
_utils.py", line 706, in add_known_host
2016-08-05 18:29:08 INFO cloud-compute-
2016-08-05 18:29:08 INFO cloud-compute-
grays']' returned non-zero exit status 255
2016-08-05 18:29:08 ERROR juju.worker.
Related branches
- Blake Rouse (community): Approve
- LaMont Jones (community): Approve
-
Diff: 68 lines (+50/-0)2 files modifiedsrc/maasserver/forms.py (+8/-0)
src/maasserver/tests/test_forms_device.py (+42/-0)
tags: | added: kanban-cross-team landscape |
description: | updated |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Richard Harding (rharding) |
tags: | removed: kanban-cross-team |
Changed in maas: | |
status: | New → Fix Committed |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in juju: | |
importance: | High → Critical |
Changed in juju: | |
importance: | Critical → High |
milestone: | 2.1.0 → 2.2.0-alpha1 |
Changed in juju: | |
assignee: | Richard Harding (rharding) → nobody |
Changed in juju: | |
milestone: | 2.2-alpha1 → 2.2.0 |
milestone: | 2.2.0 → 2.2-beta1 |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
Landscape team has a workaround provided by MAAS fix.