maas 2.1.3 nodes do not deploy, Juju reports 'started but not deployed'
Bug #1670499 reported by
John George
This bug report is a duplicate of:
Bug #1673724: [2.2] MAAS sets the last disk (i.e. sdf) as the boot device, instead of the first (i.e. sda).
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
Undecided
|
Unassigned | ||
MAAS |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Fresh install of maas 2.1.4+bzr5591-
Juju 2.1.1-xenial-amd64
Juju bootstrap does not complete when selected MAAS node is KVM.
summary: |
- maas 2.1.3 kvm nodes do not deploy, Juju reports 'started but not - deployed' + maas 2.1.3 nodes do not deploy, Juju reports 'started but not deployed' |
Changed in maas: | |
status: | Incomplete → Confirmed |
Changed in maas: | |
status: | Confirmed → Won't Fix |
status: | Won't Fix → Incomplete |
To post a comment you must log in.
Hi Jon,
The following is that I see in the logs. This leads me to believe that the issue here is not MAAS bu rather Juju. Also, please attach the machines node event log (look at the machine's details page in the UI, you can view the full event log).
That said, can you try the following:
1. Deploy kvm-node-1 manually. Does it successfully deploy? If so, then this seems to definitely be a juju issue.
2. If the above succeeds, try to deploy manually.
6 20:45:55 localhost maas.node: [info] kvm-node-1: Status transition from READY to ALLOCATED
[...]
Mar 6 20:45:56 localhost maas.node: [info] kvm-node-1: Status transition from ALLOCATED to DEPLOYING
[...]
Mar 6 21:05:48 localhost maas.node: [info] kvm-node-1: Releasing node
Mar 6 21:05:48 localhost maas.node: [info] kvm-node-1: Status transition from DEPLOYING to RELEASING
Mar 6 21:05:48 localhost maas.power: [info] Changing power state (off) of node: kvm-node-1 (4k8kmm)
Mar 6 21:05:53 localhost maas.node: [info] kvm-node-1: Status transition from RELEASING to READ