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:

K8sDatapathConfig Encapsulation Check iptables masquerading with random-fully

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.

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

👍 created #17353

test-1.16-netnext

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

test-1.19-5.4

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

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)

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.

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.