config.load_kube_config fails with Exception TypeError: "'NoneType' object is not callable"

[Jainbrt]

Hi Team,
I have tried simple code to load kube config but it is failing saying "'NoneType' object is not callable" .

[root@node1 ~]# cat list.py
import os
from kubernetes import client, config
config.load_kube_config()

[root@node1 ~]# python list.py
Exception TypeError: "'NoneType' object is not callable" in <function _removeHandlerRef at 0x7fc213b85c80> ignored

[eagle9527]

@Jainbrt config.load_kube_config("/root/.kube/config")

[eagle9527]

@Jainbrt You need to put the configuration file here.

[Jainbrt]

Thanks for your response. Still the same Exception error.

Snippet:

[root@node1 ~]# cat list.py
import os
from kubernetes import client, config
config.load_kube_config("/root/.kube/config")

[root@node1 ~]# python list.py
Exception TypeError: "'NoneType' object is not callable" in <function _removeHandlerRef at 0x7f70def6ec80> ignored

[root@node1 ~]# ls -ltr "/root/.kube/config"
-rw------- 1 root root 5454 Sep 11 14:34 /root/.kube/config
[root@node1 ~]#

[cliffburdick]

I'm seeing the same error. I have the config in the place suggested above.

[gangadhars]

I'm also getting the same problem.

How to reproduce:

>>> import kubernetes
>>> exit()
Exception TypeError: "'NoneType' object is not callable" in <function _removeHandlerRef at 0x7f3b0bccd938> ignored

Environment

Client version:  8.0.0a1

kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

OS: Ubuntu 16.04.5 LTS

EDIT:
In python3 it is working fine. This bug is occuring only in python2

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.