playbook in error when using openshift lib 0.12 about kubernetes.core HOT 7 OPEN

@nergalex What version of this collection are you using? Is it the latest stable, v1.2?

from kubernetes.core.

Sorry, please find attached error ouput with community.kubernetes version: 1.2.0 (and not 1.1.1 in the previous message)

"msg": "Failed to load kubeconfig due to Invalid kube-config file. No configuration found."

error_with_openshift_0.12_and_collection_1.2.0.json.txt

from kubernetes.core.

@nergalex I am unable to reproduce this. Specifying the path to the kubeconfig file works for me.

from kubernetes.core.

I have this issue too.
It's solved when I patched common.py in /usr/local/lib/python3.8/dist-packages/ansible_collections/community/kubernetes/plugins/module_utils/common.py on line 263.

            #return DynamicClient(kubernetes.client.ApiClient(configuration))
            return DynamicClient(kubernetes.config.new_client_from_config())

I don't know how to watch version, and have not time for this anymore.
I can give more info, if needed and if someone tell me how to obtain it )

from kubernetes.core.

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
using a config.yaml file located in a AWX project, the module invocation differs:

• kubernetes collection 1.2.0 : invocation.module_args.kubeconfig: "config.yaml" --> error_with_openshift_0.12_and_collection_1.2.0.json.txt line 12
• kubernetes collection 1.1.1 : invocation.module_args.kubeconfig: "/tmp/bwrap_24858_brzydgui/awx_24858_bs7aho2c/project/playbooks/roles/poc-k8s/files/config.yaml" --> ok_with_openshift_0.11.2.json.txt line 63

Did you reproduced this behavior?

from kubernetes.core.

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).

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.

from kubernetes.core.

thx @belenot, same workaround :)

from kubernetes.core.