During and upgrade of our Aggregating Container Logging stack, we noticed that the
kibanarollout failed with the following error:
$ oc logs logging-kibana-xx-deploy --> Scaled older deployment logging-kibana-yy down --> Scaling up logging-kibana-xx from 0 to 1, scaling down logging-kibana-yy from 1 to 0 (keep 1 pods available, don't exceed 2 pods) Scaling logging-kibana-xx up to 1 --> FailedCreate: logging-kibana-xx Error creating: No API token found for service account "aggregated-logging-kibana", retry after the token is automatically created and added to the service account error: timed out waiting for "logging-kibana-xx" to be synced
- Red Hat OpenShift Container Platform (OCP) 3.11
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.