Failed to list *v1.Secret: illegal base64 data at input byte 3

Solution Verified - Updated -

Issue

  • Error creating deployer pod: No API token found for service account "deployer", retry after the token is automatically created and added to the service account
E0612 13:54:26.356101  114495 reflector.go:201] github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/client/informers/informers_generated/externalversions/factory.go:70: Failed to list *v1.Secret: illegal base64 data at input byte 3
  • Error starting atomic-openshift-master-api service due to:
E0723 17:41:41.484909   94470 status.go:64] apiserver received an error that is not an metav1.Status: illegal base64 data at input byte 3
E0723 17:41:58.368637   94470 reflector.go:205] github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.Secret: illegal base64 data at input byte 3

Environment

  • Red Hat OpenShift Container Platform
    • 3.9
    • 3.7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content