-
Notifications
You must be signed in to change notification settings - Fork 3.7k
CI: Cilium E2E Upgrade: Endpoint missed a policy revision; triggering regeneration #36493
Copy link
Copy link
Closed
Closed
Copy link
Labels
area/CIContinuous Integration testing issue or flakeContinuous Integration testing issue or flakearea/agentCilium agent related.Cilium agent related.ci/flakeThis is a known failure that occurs in the tree. Please investigate me!This is a known failure that occurs in the tree. Please investigate me!help-wantedYou can help! Post a detailed plan on the issue or create a PR to solve this issue.You can help! Post a detailed plan on the issue or create a PR to solve this issue.sig/policyImpacts whether traffic is allowed or denied based on user-defined policies.Impacts whether traffic is allowed or denied based on user-defined policies.
Metadata
Metadata
Assignees
Labels
area/CIContinuous Integration testing issue or flakeContinuous Integration testing issue or flakearea/agentCilium agent related.Cilium agent related.ci/flakeThis is a known failure that occurs in the tree. Please investigate me!This is a known failure that occurs in the tree. Please investigate me!help-wantedYou can help! Post a detailed plan on the issue or create a PR to solve this issue.You can help! Post a detailed plan on the issue or create a PR to solve this issue.sig/policyImpacts whether traffic is allowed or denied based on user-defined policies.Impacts whether traffic is allowed or denied based on user-defined policies.
Type
Projects
Status
Done
CI failure
In #36014 (Cilium operator metrics changes PR), the cilium-agent emitted a warning that must be investigated:
Failure: https://github.com/cilium/cilium/actions/runs/12244949111/job/34158005309#step:23:490
Sysdump: https://github.com/cilium/cilium/actions/runs/12244949111/artifacts/2296692023
@squeed it looks like this warning was newly introduced in #36044 and is emitting a warning log on a condition that can regularly occur. Might be good to revisit this and figure out whether there's some condition we're unexpectedly hitting or whether the log message is just too noisy.