-
Notifications
You must be signed in to change notification settings - Fork 133
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
playbook in error when using openshift lib 0.12 #12
Comments
@nergalex What version of this collection are you using? Is it the latest stable, v1.2? |
Sorry, please find attached error ouput with community.kubernetes version: 1.2.0 (and not 1.1.1 in the previous message)
|
@nergalex I am unable to reproduce this. Specifying the path to the kubeconfig file works for me. |
I have this issue too.
I don't know how to watch version, and have not time for this anymore. |
thx @belenot . I would not prefer to modify kubernetes ansible collection because it's loaded for each job by Tower (collections/requirements.yml is used). @gravesm
Did you reproduced this behavior? |
I know @nergalex , that's why I just specified previous version of package for pip3 installation on remote host, namely openshift==0.11.0. This fixed my issue. |
thx @belenot, same workaround :) |
SUMMARY
Error encounter when using openshift 0.12 package and community.kubernetes.k8s. See attached file: error_with_openshift_0.12.json.txt
community.kubernetes.k8s works well with openshift 0.11.2 pakage. See attached file: ok_with_openshift_0.11.2.json.txt
error_with_openshift_0.12.json.txt
ok_with_openshift_0.11.2.json.txt
ISSUE TYPE
COMPONENT NAME
community.kubernetes.k8s
ANSIBLE VERSION
Virtual Env with openshift 0.11.2 and 0.12.0 run both:
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
https://github.com/nergalex/f5-aks-nginx_ingress_app_protect/blob/master/playbooks/roles/poc-k8s/tasks/create_nap_log_format.yaml
EXPECTED RESULTS
See attached file: ok_with_openshift_0.11.2.json.txt
ACTUAL RESULTS
See attached file: ok_with_openshift_0.11.2.json.txt
The text was updated successfully, but these errors were encountered: