maas spaces are mis-translated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
MAAS |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Juju seems to have a correct understanding of my spaces:
$ juju spaces --format=yaml
spaces:
internal:
10.0.50.0/24:
type: ipv4
provider-id: "8"
status: in-use
zones:
- ""
storage:
10.0.51.0/24:
type: ipv4
provider-id: "11"
status: in-use
zones:
- ""
undefined:
10.0.4.0/22:
type: ipv4
provider-id: "5"
status: in-use
zones:
- ""
but when I try to actually launch an instance onto one of those spaces where units on the base machine aren't bound to spaces, but then add containers that are bound to spaces, Juju requests machines from MAAS with incorrect space data:
machine-0: 19:25:15 TRACE maas request f9: POST http://
Rather than using space=5 for undefined, Juju seems to be sending space=-1 which MAAS returns a 404 on
Changed in maas: | |
milestone: | none → 2.5.0 |
tags: | added: track |
Changed in maas: | |
milestone: | 2.5.0 → 2.5.x |
Juju is version 2.4.1-bionic-amd64 (installed from snap) a-0ubuntu1~ 18.04.1) (apt)
MAAS is version 2.4.0 (6981-g011e51b7