pod VM fails commissioning; requests pxelinux.0 but doesn't progress past that

[Jason Hobbs]

maas version: 2.2.2-6099-g8751f91-0ubuntu1~16.04.1

A vm fails commissioning; at PXE boot time it successfully dhcp's, then requests pxelinux.0, but we don't hear anything from it after that.

from rackd.log:
2017-09-26 09:52:26 provisioningserver.rackdservices.tftp: [info] pxelinux.0 requested by 52:54:00:e6:8a:2e

The VM is still powered on, but there is no way to see what it's doing since it doesn't have a graphical console.

MAAS logs are available here:

https://10.245.162.101/artifacts/31de4a10-4c36-413d-874e-d96d603f20ea/cpe_cloud_183/infra-logs.tar

We've seen this a few times in the last few days. If I go to commission the node again, it works fine.

here is the xml config for the VM and network, and some more info about the broam device.

http://paste.ubuntu.com/25621383/

[Andres Rodriguez (andreserl)]

FWIW, the path is:

vm -> bridge -> physical interface -> switch -> physical interface -> bridge -> rack controller

[Jason Hobbs (jason-hobbs)]

To be clear on that path, the rack controller is running bare metal.

On Tue, Sep 26, 2017 at 2:01 PM, Andres Rodriguez <email address hidden>
wrote:

> FWIW, the path is:
>
> vm -> bridge -> physical interface -> switch -> physical interface ->
> bridge -> rack controller
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1719669
>
> Title:
> pod VM fails commissioning; requests pxelinux.0 but doesn't progress
> past that
>
> Status in MAAS:
> New
>
> Bug description:
> maas version: 2.2.2-6099-g8751f91-0ubuntu1~16.04.1
>
> A vm fails commissioning; at PXE boot time it successfully dhcp's,
> then requests pxelinux.0, but we don't hear anything from it after
> that.
>
> from rackd.log:
> 2017-09-26 09:52:26 provisioningserver.rackdservices.tftp: [info]
> pxelinux.0 requested by 52:54:00:e6:8a:2e
>
> The VM is still powered on, but there is no way to see what it's doing
> since it doesn't have a graphical console.
>
> MAAS logs are available here:
>
> https://10.245.162.101/artifacts/31de4a10-4c36-413d-874e-
> d96d603f20ea/cpe_cloud_183/infra-logs.tar
>
> We've seen this a few times in the last few days. If I go to
> commission the node again, it works fine.
>
> here is the xml config for the VM and network, and some more info
> about the broam device.
>
> http://paste.ubuntu.com/25621383/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1719669/+subscriptions
>

[Björn Tillenius (bjornt)]

I've looked through the logs, but couldn't find anything obvious. It would really help knowing what the VM does. Do you think you could reproduce this with a VM that has a console?

[Chris Gregan (cgregan)]

@Andres
Can you assign this back to Jason for additional triage

[Jason Hobbs (jason-hobbs)]

We haven't seen this again so there isn't anything I can do.

On Mon, Oct 30, 2017 at 1:12 PM, Blake Rouse <email address hidden>
wrote:

> ** Changed in: maas
> Assignee: (unassigned) => Jason Hobbs (jason-hobbs)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1719669
>
> Title:
> pod VM fails commissioning; requests pxelinux.0 but doesn't progress
> past that
>
> Status in MAAS:
> Incomplete
>
> Bug description:
> maas version: 2.2.2-6099-g8751f91-0ubuntu1~16.04.1
>
> A vm fails commissioning; at PXE boot time it successfully dhcp's,
> then requests pxelinux.0, but we don't hear anything from it after
> that.
>
> from rackd.log:
> 2017-09-26 09:52:26 provisioningserver.rackdservices.tftp: [info]
> pxelinux.0 requested by 52:54:00:e6:8a:2e
>
> The VM is still powered on, but there is no way to see what it's doing
> since it doesn't have a graphical console.
>
> MAAS logs are available here:
>
> https://10.245.162.101/artifacts/31de4a10-4c36-413d-874e-
> d96d603f20ea/cpe_cloud_183/infra-logs.tar
>
> We've seen this a few times in the last few days. If I go to
> commission the node again, it works fine.
>
> here is the xml config for the VM and network, and some more info
> about the broam device.
>
> http://paste.ubuntu.com/25621383/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1719669/+subscriptions
>

[Andres Rodriguez (andreserl)]

@Jason,

Since you have not seen this issue again, I'll mark this as invalid for the time being. If you see the issue again, please re-open the bug report.

[Jason Hobbs (jason-hobbs)]

Can we please leave "cannot reproduce" bugs as incomplete? they will expire over time if we can't reproduce them. Marking them invalid makes them no longer show up in searches.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team