Anaconda used to write the s390x specific details for network interfaces into ifcfg file, but this doesn't happen any more. As a result system boots after installation without networking. I believe it's a relatively recent change, but I lost the history from my test VM (reinstalled, terminal output cleared). It affects the s390x native network interfaces (qeth), there is no problem with virtio networking under KVM (AFAICT). Version-Release number of selected component (if applicable): anaconda 33.25.2-4.fc33
As Radek told me this is an effect of https://fedoraproject.org/wiki/Releases/33/ChangeSet#NetworkManager_keyfile_instead_of_ifcfg-rh and will require adaptation of ccw_init. Switching to s390utils.
device_cio_free also needs an update
Proposed as a Freeze Exception for 33-final by Fedora user sharkcz using the blocker tracking app because: Without the fix from the bug the freshly installed system will start without networking when a native s390x network adapter (eq. qeth) is used.
FEDORA-2020-5ffc9f5485 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-5ffc9f5485
FEDORA-2020-5ffc9f5485 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-5ffc9f5485` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-5ffc9f5485 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
What's still missing is handling other options than "layer2" in ccw_init. This would need a real parser for "ini" files, so we can get the whole list of options/variable in a specific section.
+4 in the ticket, marking accepted FE.
FEDORA-2020-5ffc9f5485 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.