A diskful Ubuntu 24.04 install reaches Subiquity, runs curtin, and dies in exclusive_open on the root partition with curtin.util.NotExclusiveError. The console names apt-get as a user of the partition. pre.ubuntu.subiquity starts rsyslogd inside the live installer to forward the install log to the management node. In the 24.04 installer that process holds 11.9G of a 16G node while its message queue is empty: impstats reports "main Q: size=0 enqueued=7 maxqsize=6" beside "maxrss=11951868", so no rsyslog setting bounds it. rsyslogd runs in the cgroup of snap.subiquity.subiquity-server.service, so the kernel OOM killer stops the installer. systemd starts a second subiquity-server, and that server runs curtin partitioning while the first server's curtin is still installing the kernel into the target, so clear_holders cannot open the root partition. xcat_start_installer_rsyslog starts the forwarder with systemd-run, in a transient unit with MemoryMax=128M and MemorySwapMax=0. The kernel then kills the forwarder alone. Where systemd-run is absent the install forwards no syslog, because the install is worth more than its remote log. ubuntu_subiquity_installer_syslog.bats reads the command line the routine asks for. Dropping the two memory properties fails the limit assertions and leaves the launcher and the no-fallback assertions green. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com> (cherry picked from commit 2db399cd6c07e98494353c292990c150a9adce15)
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!