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

vagrant: bump all Vagrant box versions #17352

Closed
wants to merge 1 commit into from

Conversation

tklauser
Copy link
Member

@tklauser tklauser commented Sep 9, 2021

Mostly to pick up Go 1.17

Mostly to pick up Go 1.17

Signed-off-by: Tobias Klauser <tobias@cilium.io>
@tklauser tklauser added area/CI Continuous Integration testing issue or flake release-note/ci This PR makes changes to the CI. labels Sep 9, 2021
@tklauser tklauser requested a review from a team as a code owner September 9, 2021 11:55
@tklauser tklauser requested a review from nebril September 9, 2021 11:55
@tklauser
Copy link
Member Author

tklauser commented Sep 9, 2021

test-me-please

Job 'Cilium-PR-K8s-1.19-kernel-5.4' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sDatapathConfig Encapsulation Check iptables masquerading with random-fully

Failure Output

FAIL: Pod "testclient-8rmwm" can not connect to "http://google.com"

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.19-kernel-5.4 so I can create a new GitHub issue to track it.

@tklauser
Copy link
Member Author

tklauser commented Sep 9, 2021

/mlh new-flake Cilium-PR-K8s-1.19-kernel-5.4

👍 created #17353

@tklauser
Copy link
Member Author

tklauser commented Sep 13, 2021

test-1.16-netnext

VM provisioning failure, timeout getting CI images: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1399

@tklauser
Copy link
Member Author

tklauser commented Sep 13, 2021

test-1.19-5.4

verifying whether this is a recurring failure or a temporary failure, see #17353 (comment)

@twpayne
Copy link
Contributor

twpayne commented Sep 14, 2021

Does the branch name need to be different? The docs say:

Once you change the image versions locally, create a branch named pr/update-packer-ci-build and open a PR github.com/cilium/cilium. It is important that you use that branch name so the VM images are cached into packet.net before the branch is merged.

cc @gandro

(note from @tklauser: sorry, I've initially edited this comment instead of quote replying to it 🤦 now reverted)

@tklauser
Copy link
Member Author

Does the branch name need to be different? The docs say:

Once you change the image versions locally, create a branch named pr/update-packer-ci-build and open a PR github.com/cilium/cilium. It is important that you use that branch name so the VM images are cached into packet.net before the branch is merged.

Indeed, thanks for reminding me. This also explains why the netnext jenkins jobs failed during VM provisioning. I'll reopen the PR from a branch with the correct name.

@tklauser
Copy link
Member Author

Superseded

Does the branch name need to be different? The docs say:

Once you change the image versions locally, create a branch named pr/update-packer-ci-build and open a PR github.com/cilium/cilium. It is important that you use that branch name so the VM images are cached into packet.net before the branch is merged.

Indeed, thanks for reminding me. This also explains why the netnext jenkins jobs failed during VM provisioning. I'll reopen the PR from a branch with the correct name.

Done: #17394 Closing this PR.

@tklauser tklauser closed this Sep 14, 2021
@tklauser tklauser deleted the pr/tklauser/bump-vagrant-boxes branch September 14, 2021 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants