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

Workflow failure: cron #1462

Closed
pulumi-bot opened this issue Oct 27, 2024 · 3 comments
Closed

Workflow failure: cron #1462

pulumi-bot opened this issue Oct 27, 2024 · 3 comments
Assignees
Labels
kind/engineering Work that is not visible to an external user p1 A bug severe enough to be the next item assigned to an engineer resolution/no-repro This issue wasn't able to be reproduced

Comments

@pulumi-bot
Copy link
Contributor

pulumi-bot commented Oct 27, 2024

Workflow Failure

cron has failed. See the list of failures below:

@pulumi-bot pulumi-bot added kind/engineering Work that is not visible to an external user needs-triage Needs attention from the triage team p1 A bug severe enough to be the next item assigned to an engineer labels Oct 27, 2024
@flostadler
Copy link
Contributor

TestAccNetworkPolicies seems to be flaky.

It's failing because one of the two coredns pods isn't ready: 6 out of 7 Pods are ready.
The coredns container of that pod seems to be restarting, I saw this in the logs: "restartCount": 4

I'm gonna dig a bit deeper if coredns needs some special configuration for network policies

@flostadler flostadler self-assigned this Oct 28, 2024
@flostadler flostadler removed the needs-triage Needs attention from the triage team label Oct 28, 2024
@flostadler
Copy link
Contributor

Opened issue to track this: #1465

@flostadler flostadler added the resolution/no-repro This issue wasn't able to be reproduced label Oct 28, 2024
@flostadler
Copy link
Contributor

Retry worked. Will continue investigating in #1465

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/engineering Work that is not visible to an external user p1 A bug severe enough to be the next item assigned to an engineer resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Development

No branches or pull requests

2 participants