This bug was fixed in the package initramfs-tools - 0.136ubuntu6.8
---
initramfs-tools (0.136ubuntu6.8) focal; urgency=medium
* Fix configuring BOOTIF when using iSCSI (LP: #2056187)
* Port the net autopkgtest to the common test framework. This drops
depending on downloading a
This bug was fixed in the package initramfs-tools - 0.140ubuntu13.5
---
initramfs-tools (0.140ubuntu13.5) jammy; urgency=medium
* Fix configuring BOOTIF when using iSCSI (LP: #2056187)
* Backport autopkgtest improvements from version 0.142ubuntu23 to run the
test on all archit
The retriggered focal initramfs-tools/0.136ubuntu6.8 test is green, but
jammy failed with output on stderr (which is only a warning that can be
ignored). This is probably caused by the kernel/firmware package. So I
consider the jammy test successful.
--
You received this bug notification because
I haven't located recent green runs, so I triggered them again for focal
and jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage
we have verified that both versions 0.136ubuntu6.8 (Focal) and
0.140ubuntu13.5 (Jammy) fix the issue. we used a Cisco UCS server with a
bootable iSCSI drive, enlisted by MAAS.
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-d
I confirm both focal and jammy work fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
https:
I'm on it for the testing part
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
https://bugs.lau
The status of this update now is:
a) it needs someone to perform the verification on jammy and focal, as per the
test plan from the bug's description
b) since it's been in proposed for so long (about a year), we should have a new
run of the autopkgtests. I'll try to trigger that. The existing run
Removing the block tag, this is now back into normal SRU processing (and
I'm on shift today, so I'll take a new look).
** Tags removed: block-proposed-focal block-proposed-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Hi all, confirming that as John and Benjamin mentioned above, the
regression reported with Confidential VMs is unrelated to this package
and it can be unblocked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Hi, just checking in on the status of this since LP#2093164 is waiting
on it. Is this still blocked?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using
I'd like to check if this SRU is still blocked?
I have another SRU which should base on this one, thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when u
Canonical produced cloud-images, by default, do not boot with an initrd,
and this is true on Azure as well. the hang occurs late in the startup,
post-cloud-init configuring networking. there are also a bunch of kernel
workers blocked for > 120 seconds, which points to something other than
this pack
I had a look at the boot log. The lines from the beginning of the
initramfs:
```
[1.214268] Run /init as init process
[1.236339] systemd[1]: Inserted module 'autofs4'
```
There are 0.02 seconds between the "Run /init as init process" and the
first systemd log line. So either systemd was u
Hello,
During testing of the proposed pocket packages on Confidential VMs we’ve
seen behavior of this package causing the system to hang while the
system is waiting for the network to be configured after reboot. Please
see the attached console log.
** Attachment added:
"lisa-20241217-220459-829-
Adding block-proposed tags due to a potential regression that was
identified, details to follow.
** Tags added: block-proposed-focal block-proposed-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Related: bug #2065787
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
https://bugs.launchpad.ne
clevis/18-1ubuntu1 ran into a timeout. I retried the test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this
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 pac
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 pa
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
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 notificat
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.140ubunt
** 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
Bugs, which is subscribed to Ubuntu.
https:/
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-to
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fai
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails
nice!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To man
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initra
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
Bugs, which is subscribed to Ubuntu.
https
[ 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 t
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).
** 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
Bugs, which is subscribed to Ubuntu.
https:/
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications abo
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 b
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
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 i
** Changed in: initramfs-tools (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage not
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
https://bugs.launchpad.net
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/+attachm
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To
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:
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'
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Tit
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage n
49 matches
Mail list logo
