Skip to content
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 expected dhcp6 key #4855

Merged
merged 1 commit into from
Feb 9, 2024
Merged

Conversation

holmanb
Copy link
Member

@holmanb holmanb commented Feb 5, 2024

Proposed Commit Message

test: Add expected dhcp6 key

Additional Context

@TheRealFalcon think it is safe to ignore this one? Also this one strikes me as one to maybe run as part of ci, but not sure we should really add more to ci runtime.

https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-focal-gce/384/testReport/junit/tests.integration_tests/test_upgrade/test_clean_boot_of_upgraded_package/

Test Steps

Not yet tested

Merge type

  • Squash merge using "Proposed Commit Message"
  • Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)

@holmanb holmanb requested a review from TheRealFalcon February 5, 2024 22:03
@holmanb holmanb force-pushed the holmanb/dhcp6-fix branch 2 times, most recently from 2ce55b2 to 5cf7141 Compare February 6, 2024 14:59
Copy link
Member

@TheRealFalcon TheRealFalcon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heh...so this got added then reverted and instead of adding it again I thought we could wait till 23.4 released...but that's proving to have been a bad idea. So yes, we should add it here.

I don't think this solution is complete though. Most cloud's won't give you a fallback config, so this shouldn't actually be true on most clouds.
https://github.com/canonical/cloud-init/pull/4612/files

As far as moving it to CI, I think that's probably a good idea, though I think we could probably make this one CI, and the one further down in the file not CI...or maybe just remove that one entirely.

@TheRealFalcon TheRealFalcon self-assigned this Feb 6, 2024
@holmanb
Copy link
Member Author

holmanb commented Feb 9, 2024

I don't think this solution is complete though. Most cloud's won't give you a fallback config, so this shouldn't actually be true on most clouds.
https://github.com/canonical/cloud-init/pull/4612/files

Good point, thanks. I just pushed with that fix.

As far as moving it to CI, I think that's probably a good idea, though I think we could probably make this one CI, and the one further down in the file not CI...or maybe just remove that one entirely.

I just realized that the test I was proposing moving to CI was Bionic-only, and the other one is release agnostic, so nevermind on that proposal.

@holmanb holmanb requested a review from TheRealFalcon February 9, 2024 15:21
@TheRealFalcon TheRealFalcon merged commit b7c7be9 into canonical:main Feb 9, 2024
29 checks passed
blackboxsw pushed a commit that referenced this pull request Feb 15, 2024
blackboxsw pushed a commit that referenced this pull request Feb 15, 2024
blackboxsw pushed a commit that referenced this pull request Feb 16, 2024
blackboxsw pushed a commit that referenced this pull request Feb 16, 2024
a-dubs added a commit to a-dubs/cloud-init that referenced this pull request May 6, 2024
This reverts the temporary changed introduced by PR canonical#4855 that
manually dropped the "dhcp6" key from the post_network yaml
in the integration test "test_clean_boot_of_upgraded_package"
a-dubs added a commit to a-dubs/cloud-init that referenced this pull request May 6, 2024
This reverts the temporary changed introduced by PR canonical#4855 that
manually dropped the "dhcp6" key from the post_network yaml
in the integration test "test_clean_boot_of_upgraded_package"
a-dubs added a commit to a-dubs/cloud-init that referenced this pull request May 6, 2024
This reverts the temporary changed introduced by PR canonical#4855 that
manually dropped the "dhcp6" key from the post_network yaml
in the integration test "test_clean_boot_of_upgraded_package"
aciba90 pushed a commit that referenced this pull request May 7, 2024
This reverts the temporary changed introduced by PR #4855 that
manually dropped the "dhcp6" key from the post_network yaml
in the integration test "test_clean_boot_of_upgraded_package"
holmanb pushed a commit that referenced this pull request Jun 28, 2024
This reverts the temporary changed introduced by PR #4855 that
manually dropped the "dhcp6" key from the post_network yaml
in the integration test "test_clean_boot_of_upgraded_package"
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.

2 participants