Daniel Hilst
d8a01bcf15
The gating reg_linux_diskfull_installation_flat case cannot pass on Ubuntu: the compute node never reaches a booted, installed OS, and the case only ever reports "ssh: connect ... port 22: Connection refused". It is not one defect but a chain, each reachable only once the one before it is fixed. The installer never boots. Without boot=casper, casper never processes netboot=nfs -- it scans the local disks, finds no live media and panics "Unable to find a medium containing a live file system". nfsroot must also be a literal IP: casper mounts the live filesystem with klibc's nfsmount, which cannot resolve a hostname. And with the NFS root still mounted at end of install, systemd-shutdown blocks forever on an lvm/pvscan wedged in uninterruptible I/O on it, so the node never power-cycles into the disk it just installed. The installer has no usable DNS. A nameserver line in /etc/resolv.conf must hold an IP -- glibc's resolver discards a hostname written there -- so writing the xcatmaster name leaves the installer, and the in-target apt that inherits the file, hanging on archive.ubuntu.com. In-target apt cannot find its packages on classic-sources releases, because Subiquity renders the target sources.list from the install media alone. The node never leaves the installer. The boot flip to local disk goes through updateflag.awk, which needs gawk's |& /inet coprocess, but Ubuntu's /usr/bin/awk is mawk -- so the flip fails silently and the node reinstalls forever. And syncfiles runs inside the in-target chroot, asking the MN to scp files into a node that has no sshd yet, so it times out and the node reports failed on a good install. Cover each stage. All fail today. 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!