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

[apiv2] play/kube test: name is in use, pod already exists #18041

Closed
edsantiago opened this issue Apr 4, 2023 · 7 comments
Closed

[apiv2] play/kube test: name is in use, pod already exists #18041

edsantiago opened this issue Apr 4, 2023 · 7 comments
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

Two slightly different variants. Possibly a race in the test itself:

not ok 1202 [80-kube] POST libpod/play/kube : status
#  expected: 200
#    actual: 500
#  response:
     {"cause":"pod already exists",
      "message":"playing YAML file: adding pod to state: name \"peacefulgoldberg-pod\" is in use: pod already exists",
      "response":500}

and

# response:
     {"cause":"pod already exists",
      "message":"playing YAML file: encountered while bringing up pod modestfeistel-pod-deployment-pod: adding pod to state: name \"modestfeistel-pod-deployment-pod\" is in use: pod already exists",
      "response":500}

[APIv2] [80-kube] POST libpod/play/kube : status

@edsantiago edsantiago added flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. labels Apr 4, 2023
vrothberg added a commit to vrothberg/libpod that referenced this issue Apr 4, 2023
Check the DELETE reports for both deletes.  containers#18041 indicates that the
pod hasn't been removed which made me suspicious about the 1st delete.

Signed-off-by: Valentin Rothberg <[email protected]>
@vrothberg
Copy link
Member

#18043 as an attempt to help debug the flakes

openshift-merge-robot added a commit that referenced this issue Apr 6, 2023
@vrothberg
Copy link
Member

@edsantiago, did it flake after #18043?

@edsantiago
Copy link
Member Author

The last flake I see was the April 3 one

@github-actions
Copy link

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

@rhatdan
Copy link
Member

rhatdan commented May 30, 2023

@edsantiago can we close?

@edsantiago
Copy link
Member Author

I don't know. There are more flakes than I can handle right now, and I'm far behind on my sorting.

@Luap99
Copy link
Member

Luap99 commented Jun 15, 2024

I assume this can be closed

@Luap99 Luap99 closed this as completed Jun 15, 2024
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 14, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Sep 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

4 participants