maas does not reinstall node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) Commission, acquire, and start a node. Log in to node and touch files in /home/ubunut. Release node
INFO Mon, 27 April 2015 11:32:24 Node powered off
INFO Mon, 27 April 2015 11:32:24 Node changed status — From 'Releasing' to 'Ready'
INFO Mon, 27 April 2015 11:32:18 Node changed status — From 'Deployed' to 'Releasing'
INFO Mon, 27 April 2015 11:32:18 Powering node off
INFO Mon, 27 April 2015 11:03:40 Node changed status — From 'Deploying' to 'Deployed'
INFO Mon, 27 April 2015 11:01:52 Installation complete — Node disabled netboot
DEBUG Mon, 27 April 2015 10:57:26 TFTP Request — ubuntu/
DEBUG Mon, 27 April 2015 10:57:24 TFTP Request — ubuntu/
INFO Mon, 27 April 2015 10:57:24 PXE Request — d-i install
DEBUG Mon, 27 April 2015 10:57:24 TFTP Request — /grub/grub.
INFO Mon, 27 April 2015 10:57:24 PXE Request — d-i install
DEBUG Mon, 27 April 2015 10:57:24 TFTP Request — /grub/grub.
INFO Mon, 27 April 2015 10:57:24 PXE Request — d-i install
DEBUG Mon, 27 April 2015 10:57:24 TFTP Request — /grub/grub.
DEBUG Mon, 27 April 2015 10:57:24 TFTP Request — /grub/grub.cfg
DEBUG Mon, 27 April 2015 10:57:24 TFTP Request — /grub/x86_
DEBUG Mon, 27 April 2015 10:57:23 TFTP Request — /grub/x86_
DEBUG Mon, 27 April 2015 10:57:23 TFTP Request — /grub/x86_
DEBUG Mon, 27 April 2015 10:57:23 TFTP Request — /grub/x86_
DEBUG Mon, 27 April 2015 10:57:23 TFTP Request — /grubx64.efi
DEBUG Mon, 27 April 2015 10:57:23 TFTP Request — bootx64.efi
DEBUG Mon, 27 April 2015 10:57:23 TFTP Request — bootx64.efi
INFO Mon, 27 April 2015 10:55:10 Node powered on
INFO Mon, 27 April 2015 10:55:07 Powering node on
INFO Mon, 27 April 2015 10:55:07 Node changed status — From 'Allocated' to 'Deploying'
INFO Mon, 27 April 2015 10:55:07 Node changed status — From 'Ready' to 'Allocated' (to userAAA)
My expectation is that at this point if I acquire and start the node under a different user the node should be reinstalled and the files in /home/ubuntu should not exist. Instead I see zero TFTP requests because /dev/sda was added as the first entry in the bootlist (see log stating node disabled netboot) and the node simply powers on with the files that I created previously still intact.
INFO Mon, 27 April 2015 12:15:40 Node powered off
INFO Mon, 27 April 2015 12:15:40 Node changed status — From 'Releasing' to 'Ready'
INFO Mon, 27 April 2015 12:15:34 Node changed status — From 'Deployed' to 'Releasing'
INFO Mon, 27 April 2015 12:15:34 Powering node off
INFO Mon, 27 April 2015 12:01:00 Node changed status — From 'Deploying' to 'Deployed'
INFO Mon, 27 April 2015 11:59:06 Node powered on
INFO Mon, 27 April 2015 11:58:53 Powering node on
INFO Mon, 27 April 2015 11:58:53 Node changed status — From 'Allocated' to 'Deploying'
INFO Mon, 27 April 2015 11:58:53 Node changed status — From 'Ready' to 'Allocated' (to userBBB)
When a nodes is deployed mass calls/etc/ maas/templates/ power/ipmi. template which in turn calls ipmi_chassis_config and specifies /etc/maas/ templates/ power/ipmi. conf as the configuration file. The existing configuration files does not specify whether the boot type is pc-compatible or efi and appears to default to pc-compatible. If I add the option and specify that the boot type is efi then the node installs as expected.
grep config /etc/maas/ templates/ power/ipmi. template config= {{ipmi_ chassis_ config} } {{config_ dir}}/{ {ipmi_config} } chassis_ config} ${workarounds} ${driver_option} -h ${power_address} ${user_option} -p ${power_pass} --commit --filename ${config} 2>&1)
ipmi_chassis_
config=
LC_ALL=C ${ipmi_
root: /etc# bzr diff maas/templates/ power/ipmi. conf /power/ ipmi.conf' power/ipmi. conf 2015-04-09 18:58:39 +0000 power/ipmi. conf 2015-04-28 01:46:47 +0000
Power_ Restore_ Policy Off_State_AC_Apply
Boot_ Flags_Persisten t No
Boot_ Device PXE
=== modified file 'maas/templates
--- maas/templates/
+++ maas/templates/
@@ -2,6 +2,7 @@
EndSection
Section Chassis_Boot_Flags
+ BIOS_Boot_Type EFI
EndSection
Should maas set this boot type flag?
Should maas warn the user if machine does not boot off of the network and instead boots off of the local drive?