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

Assert Deletion phase calls kubectl instead of ${KUBECTL} #34

Open
nekr0z opened this issue Oct 11, 2024 · 0 comments · May be fixed by #36
Open

Assert Deletion phase calls kubectl instead of ${KUBECTL} #34

nekr0z opened this issue Oct 11, 2024 · 0 comments · May be fixed by #36
Labels
bug Something isn't working

Comments

@nekr0z
Copy link

nekr0z commented Oct 11, 2024

What happened?

All the test steps call ${KUBECTL} whenever kubectl commands are executed. However, when asserting deletion, kubectl is used instead, which leads to failures if kubectl is not in $PATH.

How can we reproduce it?

Examine logs closely; observe lines like

kubectl wait <something> --for=delete <etc>

during the Delete step.

What environment did it happen in?

  • Uptest Version: 1.1.2
  • Chainsaw Version: 0.2.0

Reasons for the undesired behavior:

Everywhere in templates, ${KUBECTL} is called explicitly, except for the assertion step in the Delete template, where Chainsaw's wait directive is used.

Chainsaw, unfortunately, has kubectl hardcoded.

@nekr0z nekr0z added the bug Something isn't working label Oct 11, 2024
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