** Description changed: We use MAAS 2.3.5 to install Ubuntu to a cluster of computers, where - each computer boots via PXE. Each computer has 2 NICs. If you disable - one of the NICs, then when you boot the computer with Bionic (18.04), - immediately after it loads the Ramdisk (boot-initrd), the computer - immediately reboots. This continues in a loop. This seems like a - regression from 16.04. + each computer boots via PXE. On some computers, when you boot the + computer with Bionic (18.04), immediately after it loads the Ramdisk + (boot-initrd), the computer immediately reboots. This continues in a + loop. This seems like a regression from 16.04. Here are the steps to reproduce: 1. Add new computer as MAAS node - 2. Commission the node in MAAS - 3. In MAAS, go to Interfaces, select the unused NIC and select Remove Physical - 4. Deploy the node using 18.04 + 2. Commission the node in MAAS using 18.04 - Note that once you remove the unused NIC, you can reproduce this both in - MAAS Commission and MAAS Deployment. My guess is that when the init - script runs from the ramdisk, it tries to load the unused NIC and it - fails. unfortunately, the minimal PXE install (kernel + ramdisk) does - not print diagnostic info. - - Here are the steps to resolve this: - - 1. Commission the broken node using 16.04 - 2. Ensure both NICs are present under MAAS Interfaces - 3. Deploy the node using 18.04 + To resolve this, you need to disable Intel SW Guard Extensions (SGX) in + the BIOS, before Commissioning or Deploying with 18.04.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809996 Title: PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1809996/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
