cloud-atomic: Forcibly power off after %post to work around bug

The system loops with:

mkdir: cannot create directory '/oldsys': Read-only filesystem
mkdir: cannot create directory '/oldsys/sys': Read-only filesystem
mount: mount point /oldsys/sys does not exist
...
drauct Warning: Killing all remaining processes
...

--- begin loop ---
Unable to unlink device node for atomicos-root
Unable to unlink device node for live-base
rm: cannot remove /lib/drauct/hooks/shutdown/30-dm-shutdown.sh: Read-only filesystem
rm: cannot remove /lib/drauct/hooks/shutdown/30-md-shutdown.sh: Read-only filesystem
--- end loop ---

Not entirely sure what's at fault here, but this is a quick hack to
get an image building.
This commit is contained in:
Colin Walters 2014-11-10 14:11:28 -05:00
parent 09243c9986
commit 377cf487ed
1 changed files with 7 additions and 0 deletions

View File

@ -136,3 +136,10 @@ echo "(Don't worry -- that out-of-space error was expected.)"
%end
%post --nochroot
# Work around anaconda/dracut/lvm bug
sync
sync
sync
systemctl reboot -f -f
%end