Public bug reported: I am trying to commission a node after it was successfully commissioned once before. I ran into an error reported in this bug but the solution was to recomission.
I deleted the machine, re-created it, and pushed the comission button. The machine boots up, connects, downloads image, starts to boot. Then reboots. The only thing in the logs before the reboot start is: May 3 15:48:04 maas-enlisting-node systemd[1]: Started Dispatcher daemon for systemd-networkd. May 3 15:48:04 maas-enlisting-node snapd[1382]: AppArmor status: apparmor not enabled May 3 15:48:04 maas-enlisting-node snapd[1382]: 2018/05/03 15:48:04.294445 helpers.go:115: error trying to compare the snap system key: system-key missing on disk May 3 15:48:04 maas-enlisting-node snapd[1382]: 2018/05/03 15:48:04.295330 daemon.go:323: started snapd/2.32.5+18.04 (series 16; classic; devmode) ubuntu/18.04 (amd64) linux/4.15.0-20-generic. May 3 15:48:04 maas-enlisting-node systemd[1]: Started Snappy daemon. May 3 15:48:04 maas-enlisting-node iscsid: iSCSI daemon with pid=1447 started! May 3 15:48:04 maas-enlisting-node systemd[1]: Started LXD - container startup/shutdown. May 3 15:48:16 maas-enlisting-node cloud-init[1737]: No hostname has been provided... MAAS will pick one automatically May 3 15:48:16 maas-enlisting-node systemd-timesyncd[838]: Synchronized to time server 91.189.94.4:123 (91.189.94.4). May 3 15:48:17 maas-enlisting-node cloud-init[1737]: == Thu, 03 May 2018 15:48:17 +0000: already registered on 'http://172.20.59.10:5240/MAAS/api/2.0/machines/'; skipping enlistment May 3 15:48:17 maas-enlisting-node cloud-init[1737]: No hostname has been provided... MAAS will pick one automatically May 3 15:48:17 maas-enlisting-node cloud-init[1737]: === Thu, 03 May 2018 15:48:17 +0000: rebootingMay 3 15:48:03 maas-enlisting-node systemd[1]: Created slice system-getty.slice. May 3 15:48:03 maas-enlisting-node systemd[1]: Started Getty on tty1. May 3 15:48:03 maas-enlisting-node systemd[1]: Reached target Login Prompts. May 3 15:48:03 maas-enlisting-node pollinate[1302]: client sent challenge to [https://entropy.ubunt u.com/] May 3 15:48:03 maas-enlisting-node polkitd[1505]: started daemon version 0.105 using authority impl ementation `local' version `0.105' May 3 15:48:03 maas-enlisting-node dbus-daemon[1273]: [system] Successfully activated service 'org. freedesktop.PolicyKit1' May 3 15:48:03 maas-enlisting-node systemd[1]: Started Authorization Manager. May 3 15:48:03 maas-enlisting-node accounts-daemon[1343]: started daemon version 0.6.45 May 3 15:48:03 maas-enlisting-node systemd[1]: Started Accounts Service. May 3 15:48:04 maas-enlisting-node networkd-dispatcher[1308]: No valid path found for iwconfig May 3 15:48:04 maas-enlisting-node networkd-dispatcher[1308]: No valid path found for iw May 3 15:48:04 maas-enlisting-node systemd[1]: Started Dispatcher daemon for systemd-networkd. May 3 15:48:04 maas-enlisting-node snapd[1382]: AppArmor status: apparmor not enabled May 3 15:48:04 maas-enlisting-node snapd[1382]: 2018/05/03 15:48:04.294445 helpers.go:115: error tr ying to compare the snap system key: system-key missing on disk May 3 15:48:04 maas-enlisting-node snapd[1382]: 2018/05/03 15:48:04.295330 daemon.go:323: started s napd/2.32.5+18.04 (series 16; classic; devmode) ubuntu/18.04 (amd64) linux/4.15.0-20-generic. May 3 15:48:04 maas-enlisting-node systemd[1]: Started Snappy daemon. May 3 15:48:04 maas-enlisting-node iscsid: iSCSI daemon with pid=1447 started! May 3 15:48:04 maas-enlisting-node systemd[1]: Started LXD - container startup/shutdown. May 3 15:48:16 maas-enlisting-node cloud-init[1737]: No hostname has been provided... MAAS will pic k one automatically May 3 15:48:16 maas-enlisting-node systemd-timesyncd[838]: Synchronized to time server 91.189.94.4: 123 (91.189.94.4). May 3 15:48:17 maas-enlisting-node cloud-init[1737]: == Thu, 03 May 2018 15:48:17 +0000: already re gistered on 'http://172.20.59.10:5240/MAAS/api/2.0/machines/'; skipping enlistment May 3 15:48:17 maas-enlisting-node cloud-init[1737]: No hostname has been provided... MAAS will pic k one automatically May 3 15:48:17 maas-enlisting-node cloud-init[1737]: === Thu, 03 May 2018 15:48:17 +0000: rebooting the machine to resume action May 3 15:48:17 maas-enlisting-node systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup. Any ideas what is going wrong here? I can see no error messages, just that it's decided to reboot. It goes into a reboot loop after this. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769144 Title: Unable to commission node, ends up in an endless reboot cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1769144/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
