munki bootstrap is killed by reboots about imagr

[grahamgilbert]

I've not seen a munki bootstrap killed by it, but the first boot script was pulled mostly from my first boot package, so it could definitely do with some work.

[gregneagle]

One should not mix-and-match first-boot installs and Munki bootstrapping. Both are trying to the same thing at the same time. Do one or the other; not both.

[gregneagle]

(To clarify: if you use Imagr to install the Munki bootstrap pieces immediately (not at first boot), and then reboot, the Munki bootstrap behaves as expected.)

[JDHatman]

I follow the same logic in DS. Munki bootstrap is installed on first boot.
1st reboot - DS finalize runs, installing Munki, a managed installs plist, and kickstart.
2nd reboot - munki boostrap runs and installs all software I need.

I think, though, I just realized the difference. In DS, munki isn't installed til the first boot. In Imagr, I have it installed pre_first_boot. I changed it to first boot and now the launchd isn't yet active, thus delaying the kickstart til the next reboot. All works as it should now.
1st reboot - Imagr first_boot script installs munki, munki kickstart (launchd isn't yet active so kickstart doesn't kick-off yet)
2nd reboot - kickstart starts to run munki, but still there is a 3rd reboot for no reason, interrupting munki.
3rd reboot - kickstart doesn't run again by itself.

I may have to rethink how I have this set up.

[gregneagle]

Looks to me like some of the first-boot logic could be adjusted: If we don't find any scripts or pkgs, cleanup but do NOT restart, as there's no reason to.

[grahamgilbert]

I've changed the first boot script to only reboot if it's run things (allowing for failure - it will retry packages if they fail to install) in 80f1da5.

[JDHatman]

I assume this is related to the changes you made earlier, but now after the first-boot items are installed, the log window never goes away. Everything successfully installs, but you have to manually send the reboot command before it will continue.