-
Notifications
You must be signed in to change notification settings - Fork 23
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
Selecting Kubernetes resources with "do not match" label selector causes an error #84
Comments
@mwohlmutherebc: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
The label is suggested in the template for the bug report - now changed it to a "normal" string - because it's indeed an ansible operator. |
Bug Report
What did you do?
Trying to get specific resources from an OpenShift cluster using an Ansible Operator with the following ansible code:
What did you expect to see?
The expectation is to get all objects in "mynamespace" with kind "VirtualServer" which do match the label app=application AND do NOT MATCH the label my-value=value_variable.
What did you see instead? Under which circumstances?
An error occured in the operator, which can be seen in the logs:
Environment
Operator type:
ansible
Kubernetes cluster type:
OpenShift
$ operator-sdk version
1.34.1
$ kubectl version
1.23.0
Additional context
The same ansible code can be executed without any error on a linux machine targeting the same cluster to manage the cluster resources on.
Further tries to mitigate the issue (but did not solve it):
Changing quotes to single / double quotes
Not quoting the label name but only the value doesn't solve the issue.
Conclusion
Since no ansible syntax changes seem to change the behavior and the stacktrace in the error message states that the error happens in some ansible-operator-plugin library it is likely that the error has to do with the operator framework but not the ansible code.
The text was updated successfully, but these errors were encountered: