SIGKILL and the OOM-killer run no handler, so a build killed that way leaves its lock directory behind. Every later build of the same target then fails at mkdir until an operator removes the directory by hand. /var/lock/buildrpms.openeuler-20.03sp4-x86_64.lock.d on one build host was created on 2026-10-14, held no owner file and no live process, and still failed that target's dep build on 2026-10-21, one second into the genesis step. Every other openEuler job in that run reported NOT_BUILT. buildrpms.pl held its own lock, a bare mkdir that recorded no owner, and `use autodie` wrapped that mkdir, so the EEXIST branch below it was dead code and the run died on autodie's raw "Can't mkdir(...): File exists". That is why it never refused anything and never named the build holding the lock. XCAT::BuildUtils::take_build_lock kept a second hand-rolled lock with the same gap. Both now take the lock through XCAT::NFSLock, whose protocol recovers a lock whose owner is provably dead. The lock stays in /var/lock, which is local, because what it guards is host-local -- /etc/mock/<cfg>.cfg, /var/lib/mock/<cfg>/ and its buildroot.lock -- so a lock on the shared checkout would serialise the per-arch builds of one checkout that run on two hosts and share nothing. Depends on the matching xcat-dep change: that copy of NFSLock carries the recovery of a borrow whose taker died, and a DESTROY, without which a guard never releases at scope exit. 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!