Created attachment 1239831 [details] logs from the installation Logging into iSCSI targets (set up with no authentication) configured in iBFT fails with: Jan 12 08:59:52 localhost.localdomain blivet[1820]: Could not log into ibft iscsi target iqn.2009-02.com.example:ibft: Failed to call Login method on /org/freedesktop/UDisks2/Manager with ('iqn.2009-02.com.example:ibft', 1, '10.34.102.75', 3260, 'default', {'node.startup': <'automatic'>}) arguments: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Login failed: initiator reported error (24 - iSCSI login failed due to authorization failure) The node.session.auth values of iscsiadm -m fw seem suspicious. output of "iscsiadm -m fw" for the case I'm attaching logs for: # BEGIN RECORD 6.2.0.873-33 iface.initiatorname = iqn.2008-09.com.redhat.gasoline:intel22 iface.isid = iqn.2008- iface.transport_name = tcp iface.hwaddress = 00:15:17:96:75:0b iface.bootproto = DHCP iface.ipaddress = 10.34.102.102 iface.subnet_mask = 255.255.255.0 iface.gateway = 10.34.102.254 iface.primary_dns = 10.34.39.2 iface.secondary_dns = 10.34.39.2 iface.vlan_id = 0 iface.net_ifacename = ibft0 node.name = iqn.2009-02.com.example:ibft node.conn[0].address = 10.34.102.75 node.conn[0].port = 3260 node.session.auth.username = 10000000 node.session.auth.password = 10000000 node.session.auth.username_in = 10000000 node.session.auth.password_in = 10000000 node.boot_lun = 10000000 # END RECORD Another case - same target, emulating iBFT table in ipxe: # BEGIN RECORD 6.2.0.873-33 iface.initiatorname = iqn.2010-04.org.ipxe:scratch2 iface.isid = iqn.2010- iface.transport_name = tcp iface.hwaddress = 52:54:00:08:2e:48 iface.bootproto = DHCP iface.ipaddress = 10.34.102.106 iface.subnet_mask = 255.255.255.0 iface.gateway = 10.34.102.254 iface.primary_dns = 10.34.39.2 iface.secondary_dns = 10.34.39.2 iface.vlan_id = 0 iface.net_ifacename = ibft0 node.name = iqn.2009-02.com.example:ibft node.conn[0].address = 10.34.102.75 node.conn[0].port = 3260 node.session.auth.username = 01000000 node.session.auth.password = 01000000 node.session.auth.username_in = 01000000 node.session.auth.password_in = 01000000 node.boot_lun = 01000000 # END RECORD Another case - another target, bare metal iBFT table, LUN 0 this time: # BEGIN RECORD 6.2.0.873-33 iface.initiatorname = iqn.2008-09.com.redhat.gasoline:intel22 iface.isid = iqn.2008- iface.transport_name = tcp iface.hwaddress = 00:15:17:96:75:0a iface.bootproto = DHCP iface.ipaddress = 10.34.102.20 iface.subnet_mask = 255.255.255.0 iface.gateway = 10.34.102.254 iface.primary_dns = 10.34.39.2 iface.secondary_dns = 10.34.39.2 iface.vlan_id = 0 iface.net_ifacename = ibft0 node.name = iqn.2003-01.kickstart.test:ibft-test node.conn[0].address = 10.34.102.105 node.conn[0].port = 3260 node.session.auth.username = 00000000 node.session.auth.password = 00000000 node.session.auth.username_in = 00000000 node.session.auth.password_in = 00000000 node.boot_lun = 00000000 # END RECORD
Chris, do you think node.session.auth values in the description are okay? I used bare metal with no authentication set (1st and 3rd case) and iBFT emulated by ipxe (2nd case).
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.