Proposed as a Blocker for 30-beta by Fedora user alciregi using the blocker tracking app because:

 I think that this criteria is not meet: "The installer must be able to complete an installation using the serial console interface. "
Or this one: "The installer must be able to complete an installation using all supported interfaces."

(In reply to Alessio from comment #0)
> Initial setup doesn't offer the option to configure the network.
> 
> Tested with these images
> Fedora-Minimal-armhfp-30-20190301.n.0-sda.raw.xz
> Fedora-Server-armhfp-30-20190301.n.0-sda.raw.xz
> 
> Tested on an OrangePi PC and on a Raspberry Pi 3.
> Using serial console as well as HDMI.
Can you attach a journal dump from the system when this happens ? Initial Setup logs to Journal, so all it's (any any potentially relevant system messages) should be in the dump.

Thanks in advance! :)

Created attachment 1541446 [details]
journalctl > journal.dump

Is this ok?

Seems to only affect initial-setup-tui, graphical images include the network spoke.

(In reply to Alessio from comment #3)
> Created attachment 1541446 [details]
> journalctl > journal.dump
> 
> Is this ok?

Yep, thanks a lot! :)

Looks like we have found the root cause - a recently introduced variable, that's now used to decide if the network spoke should be shown has an unexpected value when running in Initial Setup. (In reply to Paul Whalen from comment #4)

> Seems to only affect initial-setup-tui, graphical images include the network
> spoke.
The graphical network spoke likely still uses the "old" way to detect if it should run and is this not affected.


Anyway, the fix should not be too hard & fix should be coming shortly. :)

PRs:
https://github.com/rhinstaller/initial-setup/pull/64
https://github.com/rhinstaller/anaconda/pull/1880

Thanks a lot to vponcova for the quick fix! :)

Discussed during the 2019-03-11 blocker review meeting: [1]

The decision to classify this bug as a "RejectedBlocker" and an "AcceptedFreezeException" was made as we find that the network spoke is more a convenience than a vital feature of i-s in this workflow, and there is no criterion requiring it to be present or work. However, this is obviously a significant bug that cannot be fixed with an update, so we grant it Freeze Exception status.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-03-11/f30-blocker-review.2019-03-11-16.04.txt

This PR should fix additional issue - network devices not being configurable in TUI:
https://github.com/rhinstaller/initial-setup/pull/65

initial-setup-0.3.68-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3e39ada0bd

anaconda-30.25.3-4.fc30 initial-setup-0.3.68-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3e39ada0bd

anaconda-30.25.3-4.fc30, initial-setup-0.3.68-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Hello.

Fedora-Minimal-armhfp-30_Beta-1.7-sda.raw.xz on a RPi3

Network spoke now appears and it seems all ok.
But configuration is not applied.
Logging in after initial-setup is completed, and issuing "ip a", ipv4 address is not in place.
Even with "systemctl restart NetworkManagert" doesn't configure the eth0

Rebooting the system, then the IP is in place.

so the configuration is set, but not actually applied until after a reboot?

Thanks for catching that, but can you please file a new bug for it instead? It seems unlikely to be the same problem as this one. Thanks!