It is theoretically possible to modify the boot image to include proprietary drivers, but it is not a straightforward task. SOLUTION: The best fix for this problem is to install a Linux-friendly network adaptor. This is sometimes the case when no open source drivers are available for the network hardware. Sometimes the hardware can boot from PXE, but fail to load correct drivers when booting the received image. This can usually be done from within the system BIOS, without needing to install an OS. SOLUTION: Check that the hardware clocks are consistent, and if necessary, adjust them. If the current time reported by the hardware clock on your node differs significantly from that on the MAAS server, the connection will not be made. Various parts of MAAS rely on OAuth to negotiate a connection to nodes. Can’t login to machine after deployment.“File not found” when creating commissioning or node script with MAAS CLI.When attempting to run a machine through its life-cycle, you may have encountered one of these issues: Once you’ve done this, you can check your work with the following command: lxc network show $LXD_BRIDGE_NAME Lxc network set $LXD_BRIDGE_NAME ipv6.dhcp=false You should also disable DHCP on IPv4 and IPv6 withing LXD: lxc network set $LXD_BRIDGE_NAME ipv4.dncp=false You can turn off LXD’s DNS management with the following command: lxc network set $LXD_BRIDGE_NAME dns.mode=none If you get into a situation where MAAS and LXD are both managing DNS on your MAAS network, there’s a simple fix. Resolve DNS conflicts between LXD and MAAS So, when using IBM Power servers with multiple NICs that can network boot, it’s strongly recommended to configure just a single NIC as the network boot device via Petitboot. When no specific interface is assigned as the network boot device, petitboot has a known issue which is detailed in LP#1852678, specifically comment #24, that can cause issues when deploying systems using MAAS, since in this case all active NICs are used for PXE boot with the same address. All the PXE interactions are handled by Petitboot, which runs in the user space of this embedded Linux rather than a PXE ROM on the NIC itself. Some IBM Power server servers have OPAL firmware which uses an embedded Linux distribution as the boot environment. If you made a mistake during setup or you just need to reconfigure your MAAS server, you can simply run the setup again: sudo dpkg-reconfigure maas-region-controller If you have a machine that PXE boots, but then fails deployment, either in an infinite boot loop or some unspecified failure, check your subnets to be sure you do not have overlap. You can fix this by deleting the subnet you do not want from the Web UI. MAAS will add the updated subnet, but may not drop the existing subnet, causing overlap. The IP range of one subnet should be unique compared to every other subnet on the same segment.Īt least one way to cause this error is to edit a subnet in the netplan file. This can break deployments, because the controllers can’t reliably determine which subnet should get a packet destined for one of the overlapping addresses. MAAS does not currently prevent you from creating overlapping subnets, for example: Please feel free to add other issues and solutions, if you have them.Īdding overlapping subnets in fabric can break deploymentsĬharacteristic failure: A machine performs PXE boot, then gets trapped in a boot loop, causing deployment to fail. Resolve MAAS/LXD DNS & DHCP conflicts/network issues.Adding overlapping subnets in fabric can break deployments.The following networking issues may be creating problems for you: This article may help you deal with some common problems.
0 Comments
Leave a Reply. |