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.

Sign up for GitHub

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

Jump to bottom

ReconcileIngressFailed in Serving kind e2e testing #275

Open
dprotaso opened this issue Apr 6, 2022 · 5 comments
Open

ReconcileIngressFailed in Serving kind e2e testing #275

dprotaso opened this issue Apr 6, 2022 · 5 comments
Assignees
@carlisia
Labels
triage/accepted Issues which should be fixed (post-triage)

Comments

@dprotaso
Copy link
Contributor

dprotaso commented Apr 6, 2022

When trying to re-work serving's kind e2e workflow I couldn't get the gateway tests (e2e) to pass

Digging at the logs I saw the kingress had the status ReconcileIngressFailed

Looking at the logs it was full of 409 conflicts. It looked like something was mutating the httproutes constantly. This can happen when two controllers fight over the same resource etc.
@dprotaso
Copy link
Contributor Author

dprotaso commented Apr 6, 2022

cc @nak3 @carlisia

@carlisia
Copy link
Member

/assign @carlisia

@carlisia carlisia added this to the v1.6.0 milestone Jun 13, 2022
@carlisia carlisia modified the milestones: v1.6.0, v1.7.0 Aug 5, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2022

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2022
@dprotaso dprotaso removed this from the v1.7.0 milestone Nov 29, 2022
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 2, 2022
@nak3 nak3 mentioned this issue Feb 16, 2023
Closed
@github-actions
Copy link
Contributor

github-actions bot commented Mar 2, 2023

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 2, 2023
@ReToCode
Copy link
Member

ReToCode commented Mar 2, 2023

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 2, 2023
@ReToCode ReToCode added the triage/accepted Issues which should be fixed (post-triage) label Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carlisia carlisia

Labels
triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@carlisia @dprotaso @ReToCode