-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
[k8s] Surface resource discovery errors properly #55388
Comments
Files identified in the description:
If these files are inaccurate, please update the |
@fabianvf: Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information. Here are the items we could not find in your description:
Please set the description of this issue with this template: |
Files identified in the description: If these files are inaccurate, please update the |
I'm not sure this issue properly captures the whole problem with DeploymentConfig, but that only really affects Openshift 3.6 and earlier. |
I think i just ran into this with
I tried both
but was originally inserted using |
@fabianvf , i monkey-patched my
It works, though you may want to just provide different messages for each exception type. In any case, surfacing the true error would have eliminated hours of digging through source to figure out i am running into this issue where there are 2 distinct types for |
Thank you very much for your interest in Ansible. Ansible has migrated much of the content into separate repositories to allow for more rapid, independent development. We are closing this issue/PR because this content has been moved to one or more collection repositories.
For further information, please see: |
SUMMARY
Follow up on #55221
When we aren't able to find a specific resource, we fail cryptically. We should report the results of our search in our failure message so that users don't need to dig around in the python code manually.
ISSUE TYPE
COMPONENT NAME
k8s
ANSIBLE VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
Fails, with a message that explains that a
v1beta1.Deployment
resource was found in bothextensions
andapps
api groupsACTUAL RESULTS
The text was updated successfully, but these errors were encountered: