Ephemeral deployment instance provides no console cue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
High
|
Unassigned | ||
cloud-init |
Expired
|
High
|
Unassigned |
Bug Description
Just upgraded to MAAS 2.6a1, noticed that a server in my MAAS has a different console behaviour on deployment. Previously, I would see the deployment logs spraying across the console, which was not pretty but it gave a cue towards progress and potentially issues if it got stuck.
With 2.6a1 we seem to present only a login screen. That's more tasteful, but it leaves an odd impression. At first I thought the deployment was failing (it came up to a login screen too fast) but then I figured out that was the login screen to the ephemeral instance.
It would be better if the ephemeral instance presented a login screen along these lines:
Ubuntu 18.04.2 LTS <hostname> tty1
MAAS installation of <image-name> in progress for <maas-user>,
logs will be available in the MAAS machine overview post-install.
<maas-user> can SSH to ubuntu@<hostname> during deployment.
<hostname> login:
Changed in maas: | |
milestone: | none → 2.6.0 |
assignee: | nobody → Newell Jensen (newell-jensen) |
status: | New → Triaged |
Changed in maas: | |
milestone: | 2.6.0 → 2.6.0alpha2 |
milestone: | 2.6.0alpha2 → 2.6.0beta1 |
Changed in maas: | |
milestone: | 2.6.0beta1 → 2.6.0beta2 |
Changed in maas: | |
importance: | Undecided → High |
status: | Triaged → In Progress |
Changed in maas: | |
milestone: | 2.6.0beta2 → 2.6.0rc1 |
Tested deploying in MAAS 2.5 to see if this was a change with MAAS and there are no cloud-init messages to the console. Seems that cloud-init has made a change. Linking cloud-init to the bug for further investigation.