In further testing, I have found that this is in fact an issue with MAAS.
There are 2 issues that I have noticed in testing:
1. My understanding of how MAAS works is:
- After phase 1 of deployment the machine reboots
- The machine attempts to PXE to MAAS
- MAAS offers up (in the case of x86) a grub config to boot to the local HDD
- the machine boots to local HDD to continue on with phase 2 of deployment(curtin post-install)
In the case of petitboot on openpower, after phase 1 of deployment, MAAS is not serving up anything via tftpboot that petitboot understands (pxelinux.0) so it will never see PXE as an option and not boot.
2. Since this issue has never been addressed with petitboot on openpower, I do not think MAAS knows how to talk to petitboot to tell it to boot to the local HDD only on the next reboot and not on subsequent boots.
To work around this temporarily (finish deployments) we can configure petitboot to boot to "any disk" as a backup when PXE is not an option.
In further testing, I have found that this is in fact an issue with MAAS.
There are 2 issues that I have noticed in testing:
1. My understanding of how MAAS works is:
- After phase 1 of deployment the machine reboots
- The machine attempts to PXE to MAAS
- MAAS offers up (in the case of x86) a grub config to boot to the local HDD
- the machine boots to local HDD to continue on with phase 2 of deployment(curtin post-install)
In the case of petitboot on openpower, after phase 1 of deployment, MAAS is not serving up anything via tftpboot that petitboot understands (pxelinux.0) so it will never see PXE as an option and not boot.
2. Since this issue has never been addressed with petitboot on openpower, I do not think MAAS knows how to talk to petitboot to tell it to boot to the local HDD only on the next reboot and not on subsequent boots.
To work around this temporarily (finish deployments) we can configure petitboot to boot to "any disk" as a backup when PXE is not an option.