Skip to content

Conversation

breml
Copy link
Collaborator

@breml breml commented Jul 9, 2025

See FuturFusion/operations-center#136 (comment) for details.

I am pretty sure, that we need the fix from the first commit. The second commit might be debatable.

breml added 2 commits July 9, 2025 09:48
The provided server address is validated against
`core.https_address` and it is made sure, that
the necessary configurations are taken, namely
`core.https_address` and `cluster.https_address`
if necessary.
After everything is checked and put in the
correct state, it is save to use the address
from the join request for the subsequent
operations.

Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
If cluster.https_address has been previously configured,
the server address provided with the cluster join request
should be verified against this address. If the two
address do not match, this is an error.

Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
@breml breml requested a review from stgraber as a code owner July 9, 2025 08:07
@stgraber stgraber merged commit ba5449b into lxc:main Jul 9, 2025
36 of 38 checks passed
@breml breml deleted the cluster-join-address branch July 9, 2025 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants