This has been shown to not be a problem with MAAS and rather a problem with the host firmware (petitboot). While we wait for this to be fix released, there is a workaround that can be followed:
1) Boot order set to "Any Disk Device"
2) Create a curtin_userdata_ubuntu_ppc64el curtin preseed in /etc/maas/preseeds on your MAAS region controller for the system which will add the lines below to the late commands. A preseed file will need to be created for each release and it can be customized per system by adding system name.
ipmi_01_install_ipmitool: ['apt-get', '-y', 'install', 'ipmitool']
ipmi_02_modprob_devintf: ['modprobe', 'ipmi_devintf']
ipmi_03_ipmitool_bootdev_none: ['ipmitool', 'chassis', 'bootdev', 'none']
This has been shown to not be a problem with MAAS and rather a problem with the host firmware (petitboot). While we wait for this to be fix released, there is a workaround that can be followed:
1) Boot order set to "Any Disk Device" userdata_ ubuntu_ ppc64el curtin preseed in /etc/maas/preseeds on your MAAS region controller for the system which will add the lines below to the late commands. A preseed file will need to be created for each release and it can be customized per system by adding system name. 01_install_ ipmitool: ['apt-get', '-y', 'install', 'ipmitool'] 02_modprob_ devintf: ['modprobe', 'ipmi_devintf'] 03_ipmitool_ bootdev_ none: ['ipmitool', 'chassis', 'bootdev', 'none']
2) Create a curtin_
ipmi_
ipmi_
ipmi_
This will allow you to deploy with MAAS.