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

Bonfire does not detect wrong Clowdapp on deploying iqe-cji pod #214

Open
Victoremepunto opened this issue May 12, 2022 · 1 comment
Open

Comments

@Victoremepunto
Copy link
Collaborator

Victoremepunto commented May 12, 2022

Not sure if related to #190 .

If you try to deploy-iqe-cji and provide a non-deployed clowdapp, bonfire keeps trying to deploy but no apparent resource is created and the process keeps waiting in there:

bonfire deploy-iqe-cji foobar -n cool-namespace
2022-05-12 11:06:44 [    INFO] [          MainThread] processing IQE ClowdJobInvocation
2022-05-12 11:06:44 [    INFO] [          MainThread] running (pid 3064951): oc apply -f - -n ephemeral-ztt1av 
2022-05-12 11:06:47 [    INFO] [         pid-3064951]  |stdout| clowdjobinvocation.cloud.redhat.com/iqe-2eac8781 created
2022-05-12 11:06:47 [    INFO] [          MainThread] waiting on CJI 'iqe-2eac8781' for max of 600sec...
2022-05-12 11:06:47 [    INFO] [          MainThread] waiting for Job to appear owned by CJI 'iqe-2eac8781'

How to reproduce
Deploy a CJI using a non deployed clowdapp
bonfire deploy-iqe-cji foobar

@bsquizz
Copy link
Collaborator

bsquizz commented May 16, 2022

We could start to do a check when running that command to verify that the ClowdApp is present in the namespace first.

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

2 participants