Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1611926 [details] journal gathered at early stage of installation (anaconda stopped before consolidation of connections from initramfs) Description of problem: If a device is configured in initramfs based on ip=ibft option, it is no more renamed to ibftX (as in F30, RHEL8). I am not sure if the change is intentional, it can create compatibility issues for users. Version-Release number of selected component (if applicable): Fedora-31-20190904.n.0 How reproducible: Always Steps to Reproduce: 1. Create iscsi target (eg iqn.2014-08.com.example:t1) on a server (eg 10.43.136.51) having at least LUN 0. 2. Run PXE installation using this config: label f31 menu label f31 kernel test/rv/scripted/f31/vmlinuz append initrd=test/rv/scripted/f31/initrd.img repo=http://download.eng.brq.redhat.com/pub/fedora/development/31/Everything/x86_64/os/ ip=ibft in virtual-manger and during boot go into PXE prompt (CTRl-B) and emulate ibft table (net0 is PXE device): ifconf -c dhcp sanhook iscsi:10.43.136.51:::0:iqn.2014-08.com.example:t1 autoboot net0 3. See the network device names in installer environment Actual results: The device having ibft connection in initramfs is not renamed to ibft0. Expected results: The device having ibft connection in initramfs is renamed to ibft0. Additional info: Installer environment info (attaching also journal): 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host. valid_lft forever preferred_lft forever 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:9f:21:28 brd ff:ff:ff:ff:ff:ff inet 10.43.136.93/24 brd 10.43.136.255 scope global dynamic noprefixroute ens3 valid_lft 3223sec preferred_lft 3223sec 3: ens7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:2e:dd:62 brd ff:ff:ff:ff:ff:ff inet 192.168.122.53/24 brd 192.168.122.255 scope global dynamic noprefixroute ens7 valid_lft 3223sec preferred_lft 3223sec inet6 fe80::bace:5025:f2c0:8640/64 scope link noprefixroute. valid_lft forever preferred_lft forever 4: ens10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:21:3c:4b brd ff:ff:ff:ff:ff:ff inet 192.168.122.23/24 brd 192.168.122.255 scope global dynamic noprefixroute ens10 valid_lft 3223sec preferred_lft 3223sec inet6 fe80::3fb0:a359:c50c:818a/64 scope link noprefixroute. valid_lft forever preferred_lft forever NAME UUID TYPE DEVICE. Wired connection 1 42dac0e1-5a57-3152-8b35-ddb10dc34060 ethernet ens10.. Wired connection 3 99fcfa4d-3f02-326c-954a-35adb3548a57 ethernet ens7... iBFT Connection 0 0575006d-4fb9-31dd-b1eb-cbe66f5d9e8f ethernet ens3... Wired connection 2 5ef244cc-c5aa-31c8-a0e9-96fea68a9fd6 ethernet --.....
Is this change intentional? Anaconda ibft configuration handling code has been relying on the fact that ibft configured device is renamed to ibftx in initramfs. Will the change be acceptable by the feature (boot from SAN, ...?) users?
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.