Re: [kubernetes/kubernetes] failure when attempting to delete secret: invalid padding on input (#60345)
Jordan Liggitt
How did you create the secret? If you go directly to etcd, do you see the secret there?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Jeffrey Forman
@liggitt I think this happened when I was testing k8s 1.10-beta.0 with a 1.9.3 kubectl
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
/remove-lifecycle stale
David Dyball
I've also been bitten by this issue. I'm running 1.9.3 and can't delete a secret that was created via Helm (chart was kubernetes-dashboard, but I doubt the chart was the issue).
Resolved by manually jumping into one of the etcd containers running on a master and doing
ETCDCTL_API=3 etcdctl --endpoints=[127.0.0.1:2380] del /registry/secrets/kube-system/kubernetes-dashboard
Annoying, but now resolved :-/
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
Closed #60345.
Prabhakar Palanivel
/remove-lifecycle stale
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Prabhakar Palanivel
We do see this issue even with 1.19.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Prabhakar Palanivel
/reopen
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Kubernetes Prow Robot
@prabhakar-oracle: You can't reopen an issue/PR unless you authored it or you are a collaborator.
In response to this:
/reopen
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.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.