Vinícius Ferrão
64ebf8c96e
NetworkManager auto-generates connection names that can contain spaces (e.g. "Wired connection 2"). Multiple devices can also share the same auto-generated name. Both cases cause failures when names are passed to nmcli in bridge and bond setup paths. Resolve active connection UUID via nmcli device show (GENERAL.CON-UUID) instead of by name, which avoids both word-splitting on spaces and ambiguity when multiple connections share the same name. Changes: - Bridge slave setup: resolve UUID via device show instead of by name - Bond slave setup: same UUID-via-device approach for con down/mod - Bridge rollback: preserve original xcat-prefixed connection name so rollback paths restore the correct name instead of a UUID - Utility functions: quote connection name arguments in is_nmcli_connection_exist, is_connection_activate_intime, and wait_nic_connect_intime for defensive correctness - Add -F flag to grep in is_nmcli_connection_exist for literal matching - Log both human-readable name and UUID when reusing existing connections Tested on EL10 host with duplicate "Ethernet connection 1/2" profiles across multiple NICs — UUID resolution via device returns exactly one UUID per device regardless of name collisions. Follows up on #7562 and #7483. Co-authored-by: OliverTUBAF <86062666+OliverTUBAF@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!