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

Uptest need to skip Namespaces/v1 similar to Secrets/v1 #18

Closed
ytsarev opened this issue Jul 15, 2024 · 0 comments · Fixed by #19
Closed

Uptest need to skip Namespaces/v1 similar to Secrets/v1 #18

ytsarev opened this issue Jul 15, 2024 · 0 comments · Fixed by #19
Labels
bug Something isn't working

Comments

@ytsarev
Copy link
Member

ytsarev commented Jul 15, 2024

What happened?

Uptes is getting suck in endless evaluation loop in cases when standard core Namespace is part of the test example material.

For example, if

apiVersion: v1
kind: Namespace
metadata:
  name: test-namespace

is getting applied by uptest, then the test run will timeout on the following condition:

 case.go:363: command "$***KUBECTL*** wait namespace./test-namespace --for=condition=Ready --timeout 10s" 

How can we reproduce it?

Add Namespace to your uptest example

What environment did it happen in?

  • Uptest Version: v0.11.1

Possible solution

Implement the similar skipping logic, see Secrets handling PR upbound/official-providers-ci#37

@ytsarev ytsarev added the bug Something isn't working label Jul 15, 2024
ytsarev added a commit to ytsarev/uptest that referenced this issue Jul 22, 2024
* Special skip of the Namespace object similar to Secret
* Fixes crossplane#18

Signed-off-by: Yury Tsarev <[email protected]>
ytsarev added a commit to ytsarev/uptest that referenced this issue Jul 22, 2024
* Special skip of the Namespace object similar to Secret
* Fixes crossplane#18

Signed-off-by: Yury Tsarev <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant