[Bug 1887558] Re: Multipath JBOD storage devices are not shown via /dev/mapper but each path as a single device.

2024-04-03 Thread Alexsander de Souza
** Merge proposal linked: https://code.launchpad.net/~alexsander-souza/maas/+git/maas/+merge/463615 ** Merge proposal linked: https://code.launchpad.net/~alexsander-souza/maas/+git/maas/+merge/459661 ** Changed in: maas/3.4 Status: Triaged => Fix Released -- You received this bug

[Bug 2056187] Re: fails to configure BOOTIF when using iscsi

2024-03-11 Thread Alexsander de Souza
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

[Bug 2056187] Re: fails to configure BOOTIF when using iscsi

2024-03-11 Thread Alexsander de Souza
[ 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

[Bug 2056187] Re: fails to configure BOOTIF when using iscsi

2024-03-08 Thread Alexsander de Souza
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 2056187] Re: fails to configure BOOTIF when using iscsi

2024-03-05 Thread Alexsander de Souza
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

[Bug 2056187] Re: fails to configure BOOTIF when using iscsi

2024-03-05 Thread Alexsander de Souza
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

[Bug 2056187] Re: fails to configure BOOTIF when using iscsi

2024-03-05 Thread Alexsander de Souza
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

[Bug 2056187] [NEW] fails to configure BOOTIF when using iscsi

2024-03-05 Thread Alexsander de Souza
Public bug reported: 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