An IPv6-only EL 8 or EL 9 node presents a different DHCPv6 DUID at each boot stage: the UEFI firmware, then iPXE, then anaconda. makedhcp reserves the first two, so the installer takes an address from the dynamic range and every step that reads the reserved address or its PTR record fails. xCAT::SvrUtils::uses_static_ipv6_boot accepted the rh family only at major 10, so Template.pm rendered "dhcp --noipv4 --ipv6=dhcp" for EL 8 and EL 9. The floor is now 8, by operator decision of 2026-11-05. pre.rhels8 was IPv4 only in two places. The install monitor opened an AF_INET socket, so the node reported no status. The install server was cut out of its URL at the first colon, which splits an IPv6 literal. Both forms come from pre.rhels10. pre.openeuler includes pre.rhels8 whole, so this also fixes the reported openEuler defect. ipv6_pre_rhels8.bats and the EL 8 and EL 9 cases of template_ipv6_rendering.t capture it. With AF_UNSPEC back to AF_INET the three IPv6 monitor cases fail and the IPv4 one passes. Without the bracket branch the three IPv6 URL cases fail and the four IPv4 ones pass. With the floor back at 10 the EL 8 and EL 9 rendering cases fail and the EL 10 ones pass. 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!