Ephemeral deployment instance provides no console cue

Bug #1820579 reported by Mark Shuttleworth on 2019-03-18
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Unassigned
cloud-init
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
Newell Jensen (newell-jensen) wrote :

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.

Ryan Harper (raharper) wrote :

We've no changes to cloud-init related to logs; we write to /var/log/cloud-init.log and "console" which is setup by boot parameters, typically /proc/cmdline would have console=ttySX,115200 console=tty0; where you'd see messages going to both serial as well tty0.

But let's take a look and see what's going on. Can we get the rsyslog output from the deployed node?

Another thought, does the same thing happen when deploying different releases? Like Xenial versus Bionic?

Changed in cloud-init:
importance: Undecided → High
status: New → Incomplete
Newell Jensen (newell-jensen) wrote :

I am seeing the same behaviour in xenial and bionic. I see cloud-init messages in /var/log/syslog of the deployed node and also in the virsh console log file but still not sure why nothing is being output to the console. Still investigating.

$ cat /proc/cmdline

BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=c2436442-8a7c-48a0-a072-a3160bd980db ro console=tty1 console=ttyS0

$ cat /var/log/syslog | pastebinit
http://paste.ubuntu.com/p/vY3v38gPvr/

Blake Rouse (blake-rouse) wrote :

@newell-jensen have you tried without the console= parameters in the global kernel parameters setting? do you get the same result with them removed?

Changed in maas:
milestone: 2.6.0beta2 → 2.6.0rc1
Newell Jensen (newell-jensen) wrote :

Blake,

No console parameters makes it work. Additionally, changing the default KVM pod console logging parameters from console=tty1 console=ttyS0 to console=tty0 console=ttyS1 made it work as well.

Newell Jensen (newell-jensen) wrote :

Actually, I take part of that back, I was also not able to get it to work properly using console=tty0 console=ttyS1.

Blake Rouse (blake-rouse) wrote :

I also have confirmed that console messages appear with MAAS 2.6 with Bionic ephemeral, deploying Bionic. This is with the global kernel parameters being empty.

@sabdfl - Can you confirm that you have no "console=" parameters on the MAAS settings page? If some exists can you try to reproduce with those removed?

Changed in maas:
status: In Progress → Incomplete
assignee: Newell Jensen (newell-jensen) → nobody
milestone: 2.6.0rc1 → none

That cannot be set globally because machines in his environment are all
different and that can break the deployment.

That said, those machines should have per node kernel parameters with the
console set. Maybe some newer machines don’t.

On Tue, Apr 30, 2019 at 9:20 AM Blake Rouse <email address hidden>
wrote:

> I also have confirmed that console messages appear with MAAS 2.6 with
> Bionic ephemeral, deploying Bionic. This is with the global kernel
> parameters being empty.
>
> @sabdfl - Can you confirm that you have no "console=" parameters on the
> MAAS settings page? If some exists can you try to reproduce with those
> removed?
>
> ** Changed in: maas
> Status: In Progress => Incomplete
>
> ** Changed in: maas
> Assignee: Newell Jensen (newell-jensen) => (unassigned)
>
> ** Changed in: maas
> Milestone: 2.6.0rc1 => None
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1820579
>
> Title:
> Ephemeral deployment instance provides no console cue
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1820579/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=cloud-init; status=Incomplete; importance=High;
> assignee=None;
> Launchpad-Bug: product=maas; status=Incomplete; importance=High;
> assignee=None;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: blake-rouse newell-jensen raharper sabdfl
> Launchpad-Bug-Reporter: Mark Shuttleworth (sabdfl)
> Launchpad-Bug-Modifier: Blake Rouse (blake-rouse)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for cloud-init because there has been no activity for 60 days.]

Changed in cloud-init:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers