An Ubuntu 26.04 diskless compute node boots the netboot image and stops at
systemd[1]: Failed to isolate default target: Unit rescue.service not found.
systemd[1]: Freezing execution.
1.78 seconds into the kernel, which is the initial ramdisk and not the root
image. imgutils::dracut_netboot_modules returns "xcat nfs base network
kernel-modules" when the image holds no network-legacy module, and dracut
reads that list as the whole module set. dracut-ng, which resolute ships as
dracut 110, has no network-legacy module, so 40network selects
systemd-networkd, which depends on the systemd module. The base module
installs the shell /init only when systemd is out, so /init becomes systemd,
and the list names no systemd-initrd, so there is no initrd.target. systemd
falls back to rescue.target, whose rescue.service is also absent.
Name systemd, systemd-initrd and dracut-systemd as well, each one only when
the image holds it, and only for an image whose dracut has no network-legacy
module. The EL genimage names the same three for dracut 107 on el10. noble
keeps network-legacy and its dracut.conf does not change, so the 24.04 lists
that 9c311c894 gave dracut still build the ramdisk they build today.
xCAT-test/unit/imgutils_dracut_netboot_modules.t fails three of six
assertions without this commit.
Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
xCAT
xCAT is a toolkit for deployment and administration of clusters of all sizes.
The xCAT sunset was only a quick eclipse
Dear xCAT Community,
The xCAT sunset has changed course. VersatusHPC has been invited to join the xCAT Consortium, and future development will move toward direct upstream contributions coordinated with the Consortium and its existing member companies.
That matters most for Enterprise Linux 10 (EL10). EL10 support is coming to xCAT, restoring a future operating-system path for sites that still rely on xCAT. This is an important change from the previous sunset guidance, where the lack of an EL10 path was one of the strongest reasons to move away from xCAT.
The xCAT Consortium continues to recommend Confluent as the long-term successor to xCAT, and that remains the Consortium position. Users planning new cluster-management deployments should evaluate Confluent and its xCAT comparison documentation.
At the same time, xCAT is no longer sunsetted. The Consortium and participating companies will continue updating xCAT while there is community and user demand for it.
In summary:
- xCAT development is continuing upstream through the Consortium and participating companies.
- Enterprise Linux 10 support is coming.
- Confluent remains the Consortium-recommended successor and migration path.
- xCAT updates will continue while there is community and user demand.
We want to thank the xCAT Consortium and community for keeping this project moving. The sun went behind the moon for a moment, but xCAT is still here.
For more information on Confluent and how to get started, please visit the Confluent: Project Page, Documentation or Confluent vs xCAT comparison.
With thanks,
The xCAT Consortium
Documentation
xCAT Documentation is hosted on Read The Docs: https://xcat-docs.readthedocs.io
Status
| xCAT Version | Build Status |
|---|---|
| Latest (master branch) | |
| Stable (latest release) |
Looking for older versions?
Open Source License
xCAT is made available under the EPL license: https://opensource.org/licenses/eclipse-1.0.php
Developers
Want to help? Check out the developers guide!