Comment 17 for bug 1743249

Do you have logs of the *exact* moment this happened on the *exact* rack &
region controller?

Since you know when this happened please provide the logs when that
happened.

Thanks!

On Mon, Jan 29, 2018 at 3:25 PM Jason Hobbs <email address hidden>
wrote:

> We are seeing another variant of this, where nodes end up powered off
> instead of hung. What happens there is:
>
> 1) Node tries to get grub.cfg-<mac> over and over until it gives up.
> 2) Node tries to get grub.cfg-default-amd64, and succeeds.
> 3) This results in the node getting directed to enlist as a new node,
> since MAAS doesn't have anything to recognize it by at this point.
> 4) After running the enlistment scripts, the node powers off.
>
> We are seeing this variant even with kpti disabled.
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1743249
>
> Title:
> Failed Deployment after timeout trying to retrieve grub cfg
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; status=Incomplete; importance=Undecided;
> assignee=None;
> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl cgregan jason-hobbs
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Jason Hobbs (jason-hobbs)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer