Python: Python3.7 binascii.Error: Incorrect padding on configuration loading

Created on 28 Jun 2019  路  6Comments  路  Source: kubernetes-client/python

  File "<...>/venv3.7/lib/python3.7/site-packages/kubernetes-10.0.0_snapshot-py3.7.egg/kubernetes/config/kube_config.py", line 636, in load_kube_config
  File "<...>/venv3.7/lib/python3.7/site-packages/kubernetes-10.0.0_snapshot-py3.7.egg/kubernetes/config/kube_config.py", line 448, in load_and_set
  File "<...>/venv3.7/lib/python3.7/site-packages/kubernetes-10.0.0_snapshot-py3.7.egg/kubernetes/config/kube_config.py", line 203, in _load_authentication
  File "<...>/venv3.7/lib/python3.7/site-packages/kubernetes-10.0.0_snapshot-py3.7.egg/kubernetes/config/kube_config.py", line 222, in _load_auth_provider_token
  File "<...>/venv3.7/lib/python3.7/site-packages/kubernetes-10.0.0_snapshot-py3.7.egg/kubernetes/config/kube_config.py", line 287, in _load_oid_token
  File "<...>/venv3.7/lib/python3.7/base64.py", line 87, in b64decode
    return binascii.a2b_base64(s)
binascii.Error: Incorrect padding

Could someone apply fix for this and release?

lifecyclrotten

Most helpful comment

The fix should have been released in v10.

All 6 comments

I'm having the same problem, it comes from the python-client submodule.
i believe if should be updated and create a release of this module.
related to: https://github.com/kubernetes-client/python/issues/525

@ltagliamonte-dd Fix is something like:

cd venv3.6/lib/python3.6/site-packages/kubernetes/config/
curl -sL https://github.com/kubernetes-client/python-base/pull/79.diff | patch -p2

However would be great to release this fix.

The fix should have been released in v10.

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

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

Fix confirmed.

Was this page helpful?
0 / 5 - 0 ratings