On Mon, Apr 2, 2018 at 6:01 PM, Tomasz Kłoczko <kloczko.tomasz(a)gmail.com> wrote:
On 1 April 2018 at 20:36, Tomasz Kłoczko
OK here are few more things which I fund:
1) initial-setup and ssh key generation services do not work because
something is really screwed with SElinux settings and when SELinux has
enabled those services seems are not able to write keys or apply other
Should be fixed in GA
With those two modifications so far I've been able to finish
first boot with:
I only see one.
2) --norootpass option does not work because in used to generate
ks profiles is:
rootpw --iscrypted --lock locked
so in /etc/shadow is line:
when in fedora-arm-image-installer is line
sed -i 's/root:x:/root::/' /tmp/root/etc/passwd
Obviously, this is not putting empty root password and root account
still is locked.
Despite this seems this option can be removed now because anaconda
started in initial-setup service provides root password change.
There are other use cases other than just that.
I think that fedora-arm-image-installer script should be evolving
into the direction tweaking ks profile used on first boot and/or force
as well start anaconda in non-interactive mode.
I don't know what that provides, please link to documentation
Probably the best way to fix SELinux issues is to change SELInux
settings to disabled (in ks profile used for generating images).
That won't ever happen, SELinux is a key security feature and if
there's bugs we file them and get them fixed.
Seems that hostname changes are not applied because the system
be rebooted after finish anaconda.
In most cases when the host name is changed you need to reboot to make
sure all things referencing the hostname are updated, there's nothing
new or special here.
If in used in initial-setup ks profile would enable SELinux and
reboot will be created /.autorelabel file all still incorrect SELinux
labels will be corrected on next reboot.
Or the bugs are reported and fixed for the next image creation.