[JUJU-1559] Removes the requirement to disable v6 for lxd. #14423
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Until now Juju has required ipv6 support to be disbaled on the network bridge created by lxd. We can now safely operate with ipv6 in Juju.
Checklist
[ ] Code style: imports ordered, good names, simple structure, etc[ ] Comments saying why design decisions were made[ ] Integration tests, with comments saying what you're testing[ ] doc.go added or updated in changed packagesQA steps
Install a fresh lxd daemon with ipv6 enabled on the default bridge and bootstrap juju. Confirm that no errors happen during bootstrap.
Deploy a workload and confirm that the agent.conf file gets the v6 address of the controller correctly.
Documentation changes
N/A
Bug reference
N/A