There's no way to tell if a postinst at rootfs time or is requesting to be delayed. Example: typo in eudev meant that the rootfs-time postinst to run qemu and generate a host-specific file failed, but there's no way of telling this without reading the logs as on first boot the postinst will run again and generate the file. I propose that we adopt "exit 75" from a postinst as meaning the postinst wants to be delayed until first boot. Any other exit code is an error, and should result in a clear warning (and re-run at first boot).
Oh I chose 75 as there's an attempt at standardising exit codes in sysexits.h, and 75 is EX_TEMPFAIL ("temporary failure, try again later").
I think my solution in bug 11096 is better (and already comes with a working patchset ;)
Patchset merged to master: http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146895.html