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
Identity GC skips IDs that are used in CESs #25001
Conversation
cc @alan-kut |
ddeb11b
to
f32da00
Compare
f32da00
to
380c576
Compare
Thank you @joamaki for the review. |
/test-runtime |
/test-1.27-net-next Job 'Cilium-PR-K8s-1.27-kernel-net-next' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.27-kernel-net-next/115/ 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. |
Hi @joamaki, both failed tests look like flakes. |
Typically we'll try to triage the flakes and identify whether there are already issues in the repo, and link them - the breadcrumbs help identify frequently-failing tests. Example:
I'll re-kick CI to get the full view on the PR. |
/test |
Thanks. Rebased. |
/test |
90b00f3
to
255a30c
Compare
Rebased again. Another flaky test should be fixed. |
/test Job 'Cilium-PR-K8s-1.25-kernel-4.19' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.25-kernel-4.19/2095/ 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. 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/2199/ 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. |
Two flaky tests. |
Could you triage and link related failures similar to the above? We're
moving more towards 'CI must be green, even if it requires rerunning'. The
current mechanism for tracking known CI issues is to file issues or
triage+link existing issues so that we can gather data on which failures
are most frequent and painful. If the same tests are failing frequently
then we can also look at quarantining them to exclude them from the
required checks. The latter is of course subject to whether the test is
failing for a range of PRs or just for this PR, since the latter is usually
an indication that the failure is related to the changes.
…On Fri, 12 May 2023, 07:21 Dorde Lapcevic, ***@***.***> wrote:
Two flaky tests.
@joestringer <https://github.com/joestringer> could you please help me
merge it?
—
Reply to this email directly, view it on GitHub
<#25001 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJPRSGZMFQPNDMUZQTARYLXFZBOZANCNFSM6AAAAAAXFROAWU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
When Cilium Endpoint Slices are enabled, Cilium Identities shouldn’t be deleted while they are still used by CES. This is a fix in the operator to check if CESs from the CES store are using Identities before deleting them. ```release-note Fix for Identities that can be deleted before CESs are reconciled ``` Signed-off-by: Dorde Lapcevic <dordel@google.com>
255a30c
to
d45e51d
Compare
/test |
When Cilium Endpoint Slices are enabled, Cilium Identities shouldn’t be deleted while they are still used by CES.
This is a fix in the operator to check if CESs from the CES store are using Identities before deleting Identities.
Signed-off-by: Dorde Lapcevic <dordel@google.com>