You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wait for provisioning to complete and system reboot
Login to the system - No home folder exists
Expected behavior
System boots without ignition.first after configuration allowing configured tree to mount with user's home folder existing.
Screenshots
localhost login: user
Password:
Last login: Wed Jun 5 18:18:43 on ttyS0
-- user: /var/home/user: change directory failed: No such file or directory
Logging in with home = "/".
[user@localhost /]$ ls -lR / 2>/dev/null | grep var/home/user
[user@localhost /]$ ls -lR /sysroot/ 2>/dev/null | grep var/home/user
/sysroot/ostree/deploy/fedora/deploy/5bcc01335c19de1117841d2334062196fc40369bcbe6f71055ac3a2ddaa013f3.0/var/home/user:
[user@localhost /]$
Running rpm-ostree kargs --delete-if-present='$ignition_firstboot' only works if ignition.firstboot is removed during the first boot. If ran after first boot, proper trees do not mount.
Work Around
Create butane file that adds a user with password (password_hash = pass)
Convert to ignition
Host ignition file on accessible httpd server
Boot Simplified Provisioner
Edit "Install Fedora 40" boot parameter appending ignition parameters to linux
Boot system
Wait for provisioning to complete and system reboot
Edit boot parameter removing ignition_firstboot during boot
login
run rpm-ostree kargs --delete-if-present='$ignition_firstboot'
reboot
The text was updated successfully, but these errors were encountered:
$ignition_firstboot is a variable - and it's just empty on subsequent reboots, check /proc/cmdline - I can't see how this is gonna mess up mounts - if that variable is populated you'll get an error straight away on the second boot as ignition tries to run again so I think it's not that.
can you provide /proc/cmdline meanwhile and we'll get this bug scheduled asap
thanks for the report!
Bug Description
After Simplified Provisioner is provisioned with Ignition, the first boot contains the
ignition.firstboot
parameter causing broken tree mounts.To Reproduce
linux
Expected behavior
System boots without ignition.first after configuration allowing configured tree to mount with user's home folder existing.
Screenshots
OS version:
Additional context
rpm-ostree kargs --delete-if-present='$ignition_firstboot'
only works ifignition.firstboot
is removed during the first boot. If ran after first boot, proper trees do not mount.Work Around
linux
ignition_firstboot
during bootrpm-ostree kargs --delete-if-present='$ignition_firstboot'
The text was updated successfully, but these errors were encountered: