lxd: handle 404 from missing devices route for LXD 4.0 #1948
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blackboxsw
force-pushed
the
lxd-4-jammy-no-devices
branch
from
460423f
to
d6f52ff
Compare
LXD 4.0 will not get a backport of the devices route on LXD socket API. This prevented launching Jammy from hosts with LXD 4.0. Allow cloud-init to support LXD backplanes without the "devices" route and use fallback network config when absent. LP: #2001737
blackboxsw
force-pushed
the
lxd-4-jammy-no-devices
branch
from
d6f52ff
to
901938c
Compare
blackboxsw
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
LXD 4.0 will not get a backport of the devices route on LXD socket API. This prevented launching Jammy from hosts with LXD 4.0.
Allow cloud-init to support LXD backplanes without the "devices" route and use fallback network config when absent.
LP: #2001737
Proposed Commit Message
Additional Context
Test Steps
Checklist: