Daniel Hilst
2baa56534c
The EL 10 riscv64 compute node installs no package. Its kickstart carries "timezone Could not determine timezone checksum --utc" at line 21, anaconda answers "One or zero arguments are expected for the timezone command", and the node holds status=installing until retry_install.sh reinstalls over it (build 114). gettimezone in Utils.pm compares /etc/localtime against every file under /usr/share/zoneinfo and, when that pipeline exits non-zero, returns the string "Could not determine timezone checksum" to its caller as a name. The Rocky 10.2 riscv64 cloud image ships no /etc/localtime and runs on UTC, so the pipeline prints nothing and exits 1. gettimezone now reads the /etc/localtime symlink first, which is what every current distribution uses and what the scan cannot answer for a host with no /etc/localtime, then the scan, then /etc/timezone, and returns UTC when none of them names a zone. It never returns a value with a space in it, which is all the kickstart timezone command accepts. The paths take an optional root prefix so the test drives them against a scratch tree. xCAT-test/unit/utils_gettimezone.t stops without _zone_from_path, and each of the three sources it asserts fails a separate assertion when it is removed. 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!