[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
original Discourse thread: https://discourse.maas.io/t/maas-cisco-ucs- iscsi/7942 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: New Status in open-iscsi package in Ubuntu: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Confirmed Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: open-iscsi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Confirmed Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Commit 4e7e25c4f ("configure_networking: move the "are we done" check to end of loop body") from 0.142ubuntu15 allows this bug to appear. This patch was for fixing bug #2037202. Can you provide the content of /proc/cmdline? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Confirmed Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
BOOT_IMAGE=http://10.107.72.10:5248/images/ubuntu/amd64/hwe-22.04/jammy/stable/boot- kernel nomodeset ro root=squash:http://10.107.72.10:5248/images/ubuntu/amd64/hwe-22.04/jammy/stable/squashfs ip=crack-gnu:BOOTIF:dhcp ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc cloud-config-url=http://10.107.72.10:5248/MAAS/metadata/latest/by- id/ky77c8/?op=get_preseed log_host=10.107.72.10 log_port=5247 --- initrd=http://10.107.72.10:5248/images/ubuntu/amd64/hwe-22.04/jammy/stable/boot- initrd BOOTIF=01-00-25-b5-00-00-00 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Confirmed Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
network interfaces: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp6s0: mtu 9000 qdisc mq state UP mode DEFAULT group default qlen 1000\link/ether 00:25:b5:21:a5:2c brd ff:ff:ff:ff:ff:ff 3: enp7s0: mtu 9000 qdisc mq state UP mode DEFAULT group default qlen 1000\link/ether 00:25:b5:21:b5:2c brd ff:ff:ff:ff:ff:ff 4: enp12s0: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000\link/ether 00:25:b5:00:00:00 brd ff:ff:ff:ff:ff:ff enp6s0 and enp7s0 are iscsi interfaces -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Confirmed Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
So BOOTIF is set which should translate to DEVICE being set. Let me come up with a patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Confirmed Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Please test the attached patch. (My initial patch was shorter. It was using grep but grep is only available in the initramfs when using busybox). ** Patch added: "0001-Fix-configuring-BOOTIF-when-using-iSCSI.patch" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5753358/+files/0001-Fix-configuring-BOOTIF-when-using-iSCSI.patch ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Triaged ** Changed in: open-iscsi (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Triaged Status in open-iscsi package in Ubuntu: Invalid Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Triaged Status in open-iscsi package in Ubuntu: Invalid Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
I've tested launching a Oracle Cloud baremetal instance (which boots from iSCSI) using such patch, and all worked well: https://pastebin.ubuntu.com/p/3cdFdYBVFG/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Triaged Status in open-iscsi package in Ubuntu: Invalid Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Changed in: initramfs-tools (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
It seems 0.142ubuntu19 would be exposed to the bug. To test whether or not my use case would be affected by it, I've booted a Jammy instance with initramfs-tools 0.142ubuntu19, and I can't hit the problem. It is booting well through iscsi. My cmdline is as below, so it might not be exposed to the issue (and hence, please ignore my comment above as a valid test for the patch, given that I wasn't exposed to it to begin with): BOOT_IMAGE=/boot/vmlinuz-6.5.0-1018-oracle root=UUID=2792ceda-655f-4995-bf29-6a714f9a200b ro console=tty1 console=ttyS0 nvme.shutdown_timeout=10 libiscsi.debug_libiscsi_eh=1 crash_kexec_post_notifiers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Hello all, I'm currently testing a patch to generate an initrd image for MAAS with partial success. The fix for the network is working well. However, when attempting to start a server via PXE using MAAS, strange errors are raised: Warning: Type of the root file system is unknown, so skipping the check. mount: bad address 'squash' This leads to an initramfs prompt. Here are the steps I follow to generate an initramfs: 1. Apply the patch to the script based on /usr/share/initramfs-tools/scripts. 2. Run the mkinitramfs command. 3. Copy the new initrd file to MAAS. 4. Start the server to boot by network. I couldn't find clear documentation regarding generation and troubleshooting. Additionally, I'm unsure if this is the right place to ask questions about this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
did you execute this procedure in your host? or in a VM deployed by MAAS? if you did the former, I think your initrd doesn't have the support to netboot from squashfs images. anyway, if you can confirm that we got past the original issue, I think it's enough to merge this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Bingo! I'm running this on my host. Yes, the problem was solved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Also affects: initramfs-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Definitely, I'm doing something very wrong. I deployed a new VM (VMware) through MaaS, using the original initrd. Applied the patch and did the same things I mentioned in my comment above. This time, the keyboard does not work (seems to be stuck; I'm not able to scroll up to see what happens). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
[ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Other Info ] * -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Something I forgot to mention, and it may be relevant after seeing the comment above: I'm using the HWE kernel for Jammy. Is it better to rollback to Focal with the default kernel? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
I think you can continue with your current kernel. We should back-port this to all LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
nice! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Merge proposal linked: https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Merge proposal unlinked: https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Attached the uploaded diff for jammy. Besides the few lines changed in scripts/functions I backported the improvements of the autopkgtest to increase the test coverage and to test on all architectures. See https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+ref/ubuntu/jammy for the individual commits for details. I tested the autopkgtest changes in my PPA. ** Description changed: + [ Impact ] + + * MAAS cannot PXE-boot a machine that has iSCSI disks + + * Focal is the default Ubuntu distribution deployed by MAAS, so we should +back-port this to ensure it works out-of-the-box. + + [ Test Plan ] + + * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager + in the original report), and a MAAS controller (3.4 or better) + + * the issue can be observed by simply enlisting the machine in MAAS. It will + fail to boot due to the missing BOOTIF configuration. + + [ Where problems could occur ] + + * the problematic code was an attempt to fix LP#2037202, so we should watch out + for regressions. + + [ Original report ] + we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: - for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do - if [ -e "$x" ]; then - IP=done - break - fi - done + for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do + if [ -e "$x" ]; then + IP=done + break + fi + done ** Patch added: "initramfs-tools_0.140ubuntu13.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5756863/+files/initramfs-tools_0.140ubuntu13.5.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: New Status in open-iscsi source package in Focal: New Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Updated jammy patch to include the increased timeout on arm64/armhf from the upcoming 0.142ubuntu23 release. ** Patch added: "initramfs-tools_0.140ubuntu13.5_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5757173/+files/initramfs-tools_0.140ubuntu13.5_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: New Status in open-iscsi source package in Focal: New Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
And here is the diff for focal (which I also tested in my PPA). ** Patch added: "initramfs-tools_0.136ubuntu6.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5757181/+files/initramfs-tools_0.136ubuntu6.8.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: New Status in open-iscsi source package in Focal: New Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
This bug was fixed in the package initramfs-tools - 0.142ubuntu23 --- initramfs-tools (0.142ubuntu23) noble; urgency=medium [ Daniel van Vugt ] * hooks/framebuffer: Only add simple/tiny framebuffer drivers. This is to limit the size of initrd when FRAMEBUFFER=y is soon enabled for desktop installations (LP: #1970069, #1869655). [ Benjamin Drung ] * autopkgtest: Increase QEMU timeouts on arm64/armhf * hooks/framebuffer: - Move adding framebuffer drivers into auto_add_modules - Drop looking in $MODULESDIR/initrd/ for kernel modules - Support MODULES=dep in framebuffer hook initramfs-tools (0.142ubuntu22) noble; urgency=medium * autopkgtest: update systemd-udevd path from /lib to /usr/lib initramfs-tools (0.142ubuntu21) noble; urgency=medium [ Benjamin Drung ] * configure_networking: - Increase minimum timeout to 30 seconds - Fix configuring BOOTIF when using iSCSI (LP: #2056187) - Set interface MTU if provided by the DHCP server (LP: #2056194) - log sleep durations before retries * Copy /etc/passwd into the initramfs to allow dhcpcd running as dhcpcd user * Replace obsolete pkg-config build-dependency by pkgconf [ Dan Bungert ] * Restore nvdimm and dax pmem-related modules (LP: #1981385) -- Benjamin Drung Thu, 21 Mar 2024 10:57:54 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Released Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: New Status in open-iscsi source package in Focal: New Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Hello Alexsander, or anyone else affected, Accepted initramfs-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.140ubuntu13.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Released Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: New Status in open-iscsi source package in Focal: New Status in initramfs-tools source package in Jammy: Fix Committed Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Hello Alexsander, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Released Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: Fix Committed Status in open-iscsi source package in Focal: New Status in initramfs-tools source package in Jammy: Fix Committed Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
clevis/18-1ubuntu1 ran into a timeout. I retried the test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Released Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: Fix Committed Status in open-iscsi source package in Focal: New Status in initramfs-tools source package in Jammy: Fix Committed Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp