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
bgp,test: Properly wait for FRR container to be ready #25777
bgp,test: Properly wait for FRR container to be ready #25777
Conversation
d23e332
to
bfc7175
Compare
/test Job 'Cilium-PR-K8s-1.26-kernel-net-next' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/304/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
bfc7175
to
ffe2cea
Compare
/test Job 'Cilium-PR-K8s-1.26-kernel-net-next' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/360/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
Need to rebase to get #24422 to resolve net-next failure. |
PodIP will be assigned even if the containers are not ready. Don't waiting for the actual readiness state here causes unexpected error in the later test case. For example, when FRR container is not brought up with image pull failure, the later "Connectivity to endpoint via LB" test fails because no one installs the route to the kernel FIB. Signed-off-by: Yutaro Hayakawa <yutaro.hayakawa@isovalent.com>
ffe2cea
to
a755523
Compare
/test |
Cilium Runtime: I triggered this CI too early before finishing to build the images. Rerunning. |
All unexecuted tests are skipped because this PR only contains the changes under |
Please see commit message for more details.