-
Notifications
You must be signed in to change notification settings - Fork 65
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
Panic in stable version #754
Comments
@bcrochet the stack trace seems to indicate that the
|
I noticed that. @jrsmroz Can you verify that you actually have a pyxis api token set up? It appears that's not being set. As in, I see no '***' after --pyxis-api-token. I'm assuming you'd have that stored in a secret. I will look to see if that would somehow trigger the noopSubmitter to be used. |
I was able to reproduce this locally by leaving off the pyxis api key. So, the command line finishes with:
So, without the pyxis api token, it will end up with the noopSubmitter, and panic. I will look to why it is panicing, but I will also make a fix that exits early if the flag is given, but no value is supplied. |
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
I used the correct pyxis token. Actually when I rerun the same pipeline it worked fine. So it's seems to be random. |
It definitely looks like the token wasn't present when it ran. If this happens again, after this PR is merged, it should at least give us an error with better info, and no panic. |
You're right the pyxis token was not set. |
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes redhat-openshift-ecosystem#754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Just setting the flags to required on submit doesn't test for whether the flags are actually provided. It only checks for their existence. This code checks that the data is actually provided, and that another flag isn't accidentally accepted as the value. Fixes #754 Signed-off-by: Brad P. Crochet <brad@redhat.com>
Bug Description
When running preflight stable image the panic can be seen during a submit
https://github.com/jrsmroz/gateway-operator/runs/7689619774?check_suite_focus=true
Version and Command Invocation
Extracted from the logs:
time="2022-08-05T10:44:59Z" level=info msg="certification library version 1.3.3 <commit: 6c30f7caae731ecc2faeaebd78c6d3981c708fe6>"
Steps to Reproduce:
(How can we reproduce this?)
Expected Result
I would expect the preflight not to panic.
Actual Result
Preflight have panicked
Additional Context
https://github.com/jrsmroz/gateway-operator/runs/7689619774?check_suite_focus=true
The text was updated successfully, but these errors were encountered: