Daniel Hilst
a3e16d83f9
getipaddr returns a cached address before it resolves, and the bypass tests OnlyV6 and GetAllAddresses only. A caller asking OnlyV4 therefore receives whatever the first lookup stored. An unrestricted lookup asks for AF_UNSPEC, so on a dual-stack management node it stores the AAAA record, and %::hostiphash is a global in a long-lived xcatd. debian.pm resolves the install server with OnlyV4 and writes nfsroot=<address>:/install. Given the cached IPv6 that renders nfsroot=2001:db8::1:/install, which does not parse, so the Subiquity installer never mounts and the node never completes. dhcp.pm and mknb.pm hold four more OnlyV4 callers with the same exposure. Skip the cache when OnlyV4 is asked for and the cached address is IPv6. The lookup that follows requests AF_INET and replaces the entry with the IPv4 address, so the next caller of either kind gets a usable one. An IPv4 entry is still served from the cache: the bypass is about the family of the cached answer, not about disabling the cache for OnlyV4. networkutils_getipaddr_onlyv4.t fails without this change. 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!