[Touch-packages] [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 existenc

[Touch-packages] [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 Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure

[Touch-packages] [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 cc:{'datasource_list'

[Touch-packages] [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 3:

[Touch-packages] [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 b

[Touch-packages] [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 t

[Touch-packages] [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 Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to confi

[Touch-packages] [Bug 2016908] Re: Unable to deploy hosts with lunar images after 20230319 - fails to connect and download squashfs

2023-04-19 Thread Alexsander de Souza
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lunar-udev-debug.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2016908/+attachment/5665324/+files/lunar-udev-debug.log -- You received this bug notification because you are a mem

[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-04-20 Thread Alexsander de Souza
MAAS started to set `apparmor=0` to fix https://bugs.launchpad.net/maas/+bug/1677336 due to https://bugs.launchpad.net/maas/+bug/1408106 This seems to no longer affect Lunar (and probably a few releases before that) -- You received this bug notification because you are a member of Ubuntu Touch s

[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-04-20 Thread Alexsander de Souza
conditional on the Ubuntu release. ** Changed in: maas Status: New => Triaged ** Changed in: maas Importance: Undecided => High ** Changed in: maas Milestone: None => 3.4.0 ** Changed in: maas Assignee: (unassigned) => Alexsander de Souza (alexsander-souza) --

[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-04-20 Thread Alexsander de Souza
The plan is for MAAS to enable apparmor for Lunar onwards. Older releases were always deployed without apparmor and I think changing this would be dangerous, as we don't know how many customers are relying on the current behaviour. -- You received this bug notification because you are a member of

[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-05-19 Thread Alexsander de Souza
** Changed in: maas Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2016908 Title: udev fails to make prctl() syscall with apparmor=0

[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-05-19 Thread Alexsander de Souza
** Merge proposal linked: https://code.launchpad.net/~alexsander-souza/maas/+git/maas/+merge/443301 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2016908 Title: udev f

[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-06-09 Thread Alexsander de Souza
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2016908 Title: udev fails to make prctl()