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

podman search with wildcards: redhat registry: unknown, not found #18484

Open
edsantiago opened this issue May 5, 2023 · 8 comments
Open

podman search with wildcards: redhat registry: unknown, not found #18484

edsantiago opened this issue May 5, 2023 · 8 comments
Labels
flakes Flakes from Continuous Integration

Comments

@edsantiago
Copy link
Member

Almost certainly a problem with that known-flaky registry. Probably best to fix the test.

  [It] podman search with wildcards
...
$  podman [options] search registry.access.redhat.com/*openshift*
time="2023-05-02T17:46:50-05:00" level=error msg="error getting search results from v2 endpoint \"registry.access.redhat.com\": unknown: Not Found"
Error: 1 error occurred:
	* couldn't search registry "registry.access.redhat.com": unknown: Not Found
@edsantiago edsantiago added the flakes Flakes from Continuous Integration label May 5, 2023
@vrothberg
Copy link
Member

Looks like a registry flake to me. Nothing much we can do, I think.

@edsantiago
Copy link
Member Author

That's just a known-bad registry: we've removed it from buildah and podman tests, and life has been much happier since. We just need to remove it from this test, and find a replacement.

@vrothberg
Copy link
Member

I think we're in between a rock and a hard place. The /search endpoints are not standardized and registry.access.redhat.com is the only one I know having implemented wildcard search.

@github-actions
Copy link

github-actions bot commented Jun 9, 2023

A friendly reminder that this issue had no activity for 30 days.

@edsantiago
Copy link
Member Author

Oh, no. This is flaking even in PRs other than my hammer-CI one. Flakes=3 helps, but only a little.

(I removed #17831 from the list above, for the sake of avoiding clutter)

@edsantiago edsantiago mentioned this issue Jun 20, 2023
Closed
@github-actions
Copy link

github-actions bot commented Aug 3, 2023

A friendly reminder that this issue had no activity for 30 days.

@edsantiago
Copy link
Member Author

Even with FlakeAttempts(3), this continues to flake (although not as much):

@edsantiago edsantiago mentioned this issue Feb 20, 2024
Merged
@edsantiago
Copy link
Member Author

This is hitting us very hard today. No logs to post, because no PRs have merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flakes Flakes from Continuous Integration
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edsantiago @vrothberg