run_genesis in xCAT-test/bats/helpers/genesis_sandbox.bash compared the status of "timeout 20 /bin/bash /run/script" with one exact number. GNU coreutils timeout reports a child that a signal killed as 128+signal, so genesis_discovery_uuid.bats expects 143 for SIGTERM. The uutils coreutils of Ubuntu 26.04 reports the signal number alone, 15, so the same outcome fails the assertion there. run_genesis now accepts the expected status or, when that status is above 128, the signal number alone. A caller that expects 0 keeps one accepted value, and an unrelated failure is still a failure. The comment names the two conventions. Evidence: a four-case bats file drives run_genesis with a controlled status. With the change, 143 and 15 both pass against an expected 143, while status 1 against 143 and status 15 against 0 still fail. Without the change only the 15 case flips to "Expected exit 143, got 15"; the control and both discriminators are unchanged. The five "= 143" comparisons in genesis_openembedded_runtime.bats stay as they are: terminate_after reads its status from the bash wait builtin, which computes 128+signal itself and does not call timeout. 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!