The Subiquity templates build three URLs as "http://#XCATVAR:XCATMASTER##COLONHTTPPORT#/install/autoinst/...", and that tag renders the bare value of the master. For an IPv6-only node that is a literal address, so wget read the last group as a port: wget -T 30 -O /tmp/getinstdisk http://2001:db8:147::1/install/autoinst/getinstdisk http://2001:db8:147::1/install/autoinst/getinstdisk: Bad port number. The early-commands script runs under "set -eux", so that one line ended it. subiquity reported CalledProcessError from Early/run, wrote a crash report of kind "unknown", and stopped before curtin ran. Nothing in the installer logs named the cause: curtin-install.log was empty, cloud-init was healthy, and the error report that looked like the failure was the Error CONTROLLER loading its own configuration. Template.pm already computed $master_uri_host, bracketed for an IPv6-only node, and used it for the SLES media URL and the repo baseurl. It is now exposed as #MASTERURIHOST#, and the three URLs take it. #XCATVAR:XCATMASTER# keeps the bare value where it is right: bash reads /dev/tcp/<host>/<port> with no brackets, and the updateflag notification uses that form. subiquity_uri_host.t reads both templates, which are the artifact: every http:// URL has to take the URI host, the /dev/tcp line has to keep the bare one, and Template.pm has to substitute the tag. Restoring the bare tag in one URL fails two checks; dropping the substitution fails the third. 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!