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

[BUG] crane does not return an non-zero exit code when plugins are not found #127

Closed
jmontleon opened this issue Jul 6, 2022 · 6 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/minor Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@jmontleon
Copy link
Contributor

What version of crane are you running, and what are your clutsters+platform

crane:
	Version: v0.0.3
crane-lib:
	Version: v0.0.6

What did you expect to happen?
Crane should have returned an exit code other than 0 and the container should have failed to build.

What actually happened?
The build proceeded and pushed without the plugins

Please include any relevant logs or errors

[3/3] STEP 9/12: RUN crane plugin-manager add OpenShiftPlugin --version v0.0.3
Run "crane plugin-manager list" to list all the available plugins 

time="2022-07-06T20:21:48Z" level=error msg="The plugin OpenShiftPlugin is not found"
--> 525f12999ed
[3/3] STEP 10/12: RUN crane plugin-manager add ImagestreamPlugin
Run "crane plugin-manager list" to list all the available plugins 

time="2022-07-06T20:21:49Z" level=error msg="The plugin ImagestreamPlugin is not found"
@jmontleon jmontleon added the kind/bug Categorizes issue or PR as related to a bug. label Jul 6, 2022
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 6, 2022
@github-actions
Copy link

github-actions bot commented Jul 6, 2022

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

jmontleon added a commit to jmontleon/crane that referenced this issue Jul 7, 2022
@openshift-ci openshift-ci bot closed this as completed in 1909826 Jul 7, 2022
@eriknelson
Copy link
Contributor

/triage accepted
/priority minor

@openshift-ci openshift-ci bot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/minor Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Jul 8, 2022
@eriknelson eriknelson removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Jul 8, 2022
@eriknelson eriknelson reopened this Jul 8, 2022
@eriknelson
Copy link
Contributor

@djzager might have exposed a hole in the sync. I think we would have wanted this to show up in jira but I triaged after it was closed. If we still want this to be verified by QE, we need to make sure that it gets an associated triage.. I'll set a TODO to see what we can do about it.

@jmontleon I'm just opening to see if I can trigger the sync.

@eriknelson
Copy link
Contributor

Sorry about this @jmontleon, we need to figure out how to enable you to work this way without getting in your way while also makinng sure some kind of a proxy Jira makes its way into that system so it's on QE team's radar for verification, ortherwise they would never see this. I'll thin a bit on this.
CC: @djzager

@jmontleon
Copy link
Contributor Author

No worries! Test away!

@eriknelson eriknelson reopened this Jul 8, 2022
@github-actions
Copy link

github-actions bot commented Jul 8, 2022

This issue synced with: https://issues.redhat.com/browse/MTRHO-88

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/minor Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants