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

namespace already exists error #1931

Open
rajeshmundhe9 opened this issue Sep 14, 2023 · 1 comment
Open

namespace already exists error #1931

rajeshmundhe9 opened this issue Sep 14, 2023 · 1 comment

Comments

@rajeshmundhe9
Copy link

rajeshmundhe9 commented Sep 14, 2023

I am getting errors as "namespace already exists".

When I ran the Sonobuoy test cases

time="2023-09-14T16:39:58Z" level=error msg="Preflight checks failed"
time="2023-09-14T16:39:58Z" level=error msg="namespace already exists"

Environment:

  • Sonobuoy version:
  • Kubernetes version: (use kubectl version): 1.23
  • Kubernetes installer & version: 1.23
  • Cloud provider or hardware configuration: AWS
  • OS (e.g. from /etc/os-release):
  • Sonobuoy tarball (which contains * below)
@rajeshmundhe9
Copy link
Author

I got the option to skip the namespace check. --skip-preflight=true. after applying this flag, it gives a different error. In error, it has two statements. One statement says sonobuoy namespace already exists and another statement says the namespace is terminated. Not understand why this is contradicting. Below are the logs of that error.

time="2023-09-14T15:00:44-05:00" level=info msg="object already exists" name=sonobuoy namespace= resource=namespaces
time="2023-09-14T15:00:44-05:00" level=error msg="error attempting to run sonobuoy: failed to create object: failed to create API resource sonobuoy-serviceaccount: serviceaccounts "sonobuoy-serviceaccount" is forbidden: unable to create new content in namespace sonobuoy because it is being terminated"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant