Daniel Hilst
6a41acf2db
makedns reports "error was FORMERR" for an update that named rejected with NOTAUTH. The FORMERR is the answer to the retry, not to the first attempt. send_ddns_update in ddns.pm signs the packet the caller built, and signs that same packet again on each attempt. Net::DNS::Packet::sign_tsig appends the TSIG to the additional section, so the second attempt sends two TSIG records and named answers FORMERR. FORMERR is neither NOTAUTH nor SERVFAIL, so the routine stops and reports it. The NOTAUTH and SERVFAIL retry can never be accepted, on any algorithm. Each attempt now signs a request of its own. A packet cannot be unsigned again, so ddns_update_request copies the prerequisite and update records into a new Net::DNS::Update instead, and the caller keeps the unsigned original. ddns_update_retry.t fails before this change: the second attempt carries two TSIG records, and an update that the retry answers with NOERROR still reports failure. 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!