rinstall prints "Failed to run 'nodeset' against the node: <node>" and returns 1, while nodeset against the same node exits 0 and reports no error. rinstall returns before rnetboot and rpower, so the node is never powered on and every provisioning case waits for a machine that nobody booted. xCAT::Utils::runxcmd returns $::RUNCMD_RC. runxcmd_output ORs the errorcode of each response into that global, and xCAT::Utils::runcmd and the service helpers assign their own exit status to it, so the last command of any plugin in the subrequest replaces the result. makedhcp supplies that command: its ISC branch restarts dhcpd6 whenever /etc/dhcp/dhcpd6.conf is absent or written by another program, which is every run of a cluster with no IPv6 network, and the restart fails with no subnet to serve. A Kea cell restarts kea-dhcp6 only for a run that has DHCPv6 work, so only ISC cells fail. runxcmd now collects the errorcodes in $::xcmd_errorcode and assigns that to $::RUNCMD_RC after the subrequest, so a command of the subrequest can neither set nor clear the result. dhcp6_restart_needed restarts dhcpd6 only for a run that serves an IPv6 network. runxcmd_subrequest_errorcode.t and dhcp_isc_dhcp6_restart.t fail on the parent commit. 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!