BuildUtils::sh() runs each build command in its own process group, so SIGKILL on the wrapper leaves that group running. The lock records the wrapper, so the next build proved the wrapper dead and took the lock, and two builds then wrote one checkout and one mock target. cancel_build keeps the lock on purpose when a group survives its cleanup, and that recovery undid the retention. sh() now records the group on every lock this process holds, before it restores the signal mask, so a cancellation cannot land between the fork and the record. It drops the record after the group is reaped. cancel_build drops it only when kill(0, -pgid) answers ESRCH, which is the test it already used to decide it may release; on the retention path the record stays, and a later acquire reads it and refuses the lock. The vendored XCAT::NFSLock carries the rule: an owner is recoverable only when it is provably dead and every attached group is gone. detach refuses while any process is in the group, so the retention does not depend on which call site remembered to run. Depends on xcat-dep/#93, which carries the same change to the original. 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!