Esta máquina foi comissionada com sucesso uma vez e, em seguida, devido a um número de série do disco rígido que estava mudando, precisei excluí-la e recomec-la.
Eu removi a máquina do MAAS e a reinscrevi como se fosse a primeira vez. Agora a máquina não comissionará e falhará.
Não consigo ver nada no log que indique por quê. Aqui está o trecho apropriado, onde a máquina começa abruptamente a desligar.
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.
Quando a reinicialização é iniciada, a máquina entra em um loop de reinicialização. Ele continuará fazendo isso pelos 20m até que seja marcado como falha no comissionamento. Também fiz esta pergunta aqui: link