Bug 1655329

> Version-Release number of selected component (if applicable):
> arm-image-installer-2.5-1.fc29.noarch

The latest stable version is 2.8, I believe all of the above are fixed with the latest version.

i have re-tested with:
arm-image-installer-2.8-1.fc29.noarch

--resizefs is fixed and now correctly resizes the root partition.

but the bigger issue of --norootpass producing broken images is still there.
same as before, missing users at boot in journal.
journal is easiest seen by adding: systemd.journald.forward_to_console=1 to kernel boot command line and then use the serial port to see whats going on.

Cannot this be a duplicate of Bug 1692903?

well... i think it might be the other way around regarding the duplicate or something.

all i know is that if i pass --norootpass image is broken and without it boots just fine and i have several devices using resulting image.
so i'm not so sure it is selinux related, if it was then it would not matter if i specify --norootpass or not.

for completeness yes i have selinux disabled where the image is created but i don't see how that's relevant to the image generation.
whatever --norootpass does to the image it is not working out.

(In reply to Torbjorn Jansson from comment #4)
> all i know is that if i pass --norootpass image is broken and without it
> boots just fine
...
> for completeness yes i have selinux disabled where the image is created

It would be great if you could test a fix for this issue posted upstream today:
  https://pagure.io/arm-image-installer/pull-request/38

> for completeness yes i have selinux disabled where the image is created but
> i don't see how that's relevant to the image generation.
> whatever --norootpass does to the image it is not working out.

Testing with the latest - arm-image-installer-2.12-1.fc30.noarch

I can't reproduce the issue with Fedora 30 Minimal (with no initial-setup). I also tried with SE Linux in permissive with no change. 

Command used: 

sudo arm-image-installer --target=rpi3 --image=Fedora-Minimal-armhfp-30-1.2-sda.raw.xz --resizefs --norootpass --media=/dev/sdd --args "systemd.journald.forward_to_console=1" --addconsole

To remove the root password requirement the script uses "sed -i 's/root:x:/root::/' /tmp/root/etc/passwd"

Created attachment 1584429 [details]
rpi3 boot

OK, reproduced with selinux disabled on the host (tsk tsk)

Created attachment 1584820 [details]
journalctl --root=/mnt/

(In reply to Paul Whalen from comment #6)
> Testing with the latest - arm-image-installer-2.12-1.fc30.noarch

Also: arm-image-installer-2.12-1.fc30.noarch

 
> I also tried with SE Linux in permissive with no change. 

On x86_64 host system one must have: getenforce == Disabled
Is it really so? getenforce == Permissive will still build a correct ARM image, only getenforce == Disabled will break the built ARM image.


> sudo arm-image-installer --target=rpi3
> --image=Fedora-Minimal-armhfp-30-1.2-sda.raw.xz --resizefs --norootpass
> --media=/dev/sdd --args "systemd.journald.forward_to_console=1" --addconsole

I have done as root:
  arm-image-installer --target=rpi3 --image=Fedora-Minimal-armhfp-30-1.2-sda.raw.xz --norootpass --media=/dev/sdb
  (sorry it was not literally your command but I believe it would be the same)
And then it shows login screen but when I type "root" it asks for "Password:" and I cannot login with any password I try.

I do not know how to catch that console afterwards so I fsck-ed+mounted the device afterwards and typed:
  journalctl --root=/mnt/
Which I am attaching. It starts with:
Apr 12 17:18:02 localhost audit[617]: AVC avc:  denied  { read } for  pid=617 comm="sh" name="passwd" dev="sda3" ino=35796 scontext=system_u:system_r:loadkeys_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0


> To remove the root password requirement the script uses "sed -i
> 's/root:x:/root::/' /tmp/root/etc/passwd"

The problem is that the installing (=host=x86_64) system without SELinux will corrupt by that sed the SELinux context of /tmp/root/etc/passwd.

(In reply to Paul Whalen from comment #8)
> OK, reproduced with selinux disabled on the host (tsk tsk)

Oops, OK, great; I did not have to spend time reproducing it again, sorry I did not refresh my browser window.

FEDORA-2019-2dd9f78d69 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2dd9f78d69

FEDORA-2019-7cd0e1fc4b has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7cd0e1fc4b

arm-image-installer-2.13-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7cd0e1fc4b

arm-image-installer-2.13-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2dd9f78d69

arm-image-installer-2.13-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.