[Net Boot] Ubuntu server 18.04.4 failed to diskless boot via IPv6 iSCSI

Bug #1868065 reported by AndyLiang
This bug affects 1 person
Affects Status Importance Assigned to Milestone
open-iscsi (Ubuntu)

Bug Description

ISO: ubuntu-18.04.4-server-amd64.iso
System environment: two ports connected to the network. The first port connects with IPv4 DHCP server. The second port connects with IPv4 and IPv6 DHCP server.

After installation completed through the 2nd NIC port, the system failed to boot via the remote IPv6 iSCSI disk. The system hangs on the "iscsistart: cannot make a connection to (-1,101)". There are possible problems.

The iscsistart uses the wrong port, the 1st port, to connect the iSCSI service. After adding the parameter ip=:::::eno1:off, the iscsistart uses the 2nd port to connect but still with IPv4 address. Adding the other parameters, ip=:::::eno2:off ip6=eno2, the iscsistart gets the IP, on eno2 to connect the service. The eno2 gets the IPv6 address after the iscsistart connection.

The iscsistart also can't recognize the IPv6 address. The log shows "Logging into iqn.2100-01.xx.xxx:ubuntu 2001:0,1". The parameters, rd.iscsi.firmware=1 or rd.iscsi.target.ip=[2001:db8:feed::100], have no effect.

Please help

Revision history for this message
AndyLiang (andyhpe) wrote :
affects: klibc (Ubuntu) → open-iscsi (Ubuntu)
Revision history for this message
Mark Morlino (markmorlino) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Michael Reed (mreed8855) wrote :

I am curious to know what is the use case for using IPv6 as opposed to just IPv4? Also what server and network adapter are you using? Also what kernel version are you using? Please paste the output of uname -a?

On the Iscsi target can you type the following command and retry?

sudo tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL

Revision history for this message
AndyLiang (andyhpe) wrote :

We verified on the DL360 Gen10 plus and Apollo 4200 Gen10 Plus with onboard Intel NIC. The SUT installed OS is from the ubuntu-18.04.4-server-amd64.iso. Since the OS is not able to boot, there is no info for the "uname -a" command.

Actually, I don't think the command can fix the issue because the problem causes by the OS tried the IPV4 first during the boot. The OS in the iSCSI disk needs a proper setting to recognize the IPV6 before the iscsistart process started.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments