Skip to content

Conversation

@last-genius
Copy link
Contributor

With this PR, xapi and xcp-networkd now properly handle emergency network resets on an IPv6-only host (when it's an individual host as well as when it's in a pool as a supporter and as a coordinator)

Tested manually, see also the required xsconsole PR: xapi-project/xsconsole#55.

last-genius and others added 4 commits April 10, 2025 11:29
Otherwise, for a pool.conf like `slave:2a01:240:ab08:5:13::201`, `address`
would just be `2a01`.

Note that such `address` isn't actually used anywhere (only the user-specified
address is written to the config, and that isn't truncated), so this is just a
safety measure in case of future changes.

Signed-off-by: Andrii Sultanov <[email protected]>
Use a helper method to parse lists in values, and use options better to ignore
empty values.

Signed-off-by: Pau Ruiz Safont <[email protected]>
Other parts of xapi and various scripts have already been updated to account
for IPv6 entries in management.conf (like xe-reset-networking, xapi_pool.ml,
etc.)

Add the IPv6 alternatives to IPv4 config entries also to read_management_conf,
otherwise networkd will not properly account for IPv6 settings or error out in
case some IPv4 entries are skipped

Signed-off-by: Andrii Sultanov <[email protected]>
@last-genius last-genius added this pull request to the merge queue Apr 16, 2025
Merged via the queue into xapi-project:master with commit b645ba4 Apr 16, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants