*** This bug is a duplicate of bug 1768893 ***
https://bugs.launchpad.net/bugs/1768893
After further looking into this, I can determine that:
1. Curtin installed successfully despite the kernel issues
1. Curtin told MAAS the installation completed successfully.
3. cloud-init told the machine to reboot.
At this point, we lose all logs, but from what we can see is that:
1. The machine never attempted to PXE boot post-deployment
2. There's no indication that the machine actually booted into the installed
environment.
This leads me to believe that due to the kernel error above, the kernel
could have crashed right before the machine rebooted, which prevented
the machine from rebooting into the installed system. This is not
something available in the rsyslog because at the time, networking is
down. This would only show on a console log.
That said, the logs definitely show that the machine never came up
again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772490
Title:
'Deploying' timed out after 40 minutes / Failedbcache:
register_bcache() error
Status in curtin:
Invalid
Status in MAAS:
Invalid
Status in linux package in Ubuntu:
Incomplete
Bug description:
We have a few runs over the weekend failed to deploy with maas 2.3.3.
May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from
DEPLOYING to FAILED_DEPLOYMENT
May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node
operation 'Deploying' timed out after 40 minutes.
https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e-
4de1-9b30-0ecb28eb3c35
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1772490/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
