-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add fix for Debian Bookworm/cloud-init/Netplan/DHCP issue #233
Merged
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
jsf9k
added
bug
This issue or pull request addresses broken functionality
terraform
Pull requests that update Terraform code
labels
Jan 12, 2024
jsf9k
requested review from
dav3r,
felddy,
jasonodoom and
mcdonnnj
as code owners
February 16, 2024 18:02
jsf9k
added
the
blocked
This issue or pull request is awaiting the outcome of another issue or pull request
label
Feb 16, 2024
dav3r
approved these changes
Feb 16, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 👍
michaelsaki
approved these changes
Feb 20, 2024
The Netplan config is created by cloud-init, but it needs to be slightly modified and reapplied. This script takes care of the modification. See these issues for more details: - cisagov/skeleton-packer#300 - canonical/cloud-init#4764
The Netplan config is created by cloud-init, but it needs to be slightly modified and reapplied. There is a Python script that fixes the DHCP4 options in the netplan configuration already generated by cloud-init. This cloud-init fragment simply reapplies the Netplan configuration after the modification. See these issues for more details: - cisagov/skeleton-packer#300 - canonical/cloud-init#4764
The Netplan config is created by cloud-init, but it needs to be slightly modified and reapplied. See these issues for more details: - cisagov/skeleton-packer#300 - canonical/cloud-init#4764
See #234 for more details.
jsf9k
force-pushed
the
testing/netplan-dhcp-fix
branch
from
March 12, 2024 16:23
ac1e0f7
to
5280cef
Compare
dav3r
approved these changes
Mar 12, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
8 tasks
jsf9k
removed
the
blocked
This issue or pull request is awaiting the outcome of another issue or pull request
label
Mar 22, 2024
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.
🗣 Description
This pull request adds a fix for the Debian Bookworm +
cloud-init
+netplan
+ DHCP issue described in cisagov/skeleton-packer#300.Important
This pull request cannot be merged until cisagov/skeleton-packer#242 is merged and trickles down to all the COOL AMI repos.
💭 Motivation and context
See cisagov/skeleton-packer#300.
🧪 Testing
I deployed these changes together with those from this branch of cisagov/debian-packer and verified that
debiandesktop0
couldping
terraformer0
without having to specify the.env6
domain.✅ Pre-approval checklist