Comment 0 for bug 1881353

Revision history for this message
Ghada Khalil (gkhalil) wrote :

Brief Description
-----------------
Application apply failed at waiting for ingress pods due to fetch token failure

Severity
--------
Major

Steps to Reproduce
------------------
- Install and configure system with openstack
- Lock/unlock both controllers were performed
- Configure additional applications or attempt to re-apply openstack

Expected Behavior
------------------
The new apply works

Actual Behavior
----------------
The apply fails with this error in the logs:
Warning FailedCreatePodSandBox 4m37s (x70 over 19m) kubelet, controller-0 Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "registry.local:9001/k8s.gcr.io/pause:3.2": failed to pull image "registry.local:9001/k8s.gcr.io/pause:3.2": failed to pull and unpack image "registry.local:9001/k8s.gcr.io/pause:3.2": failed to resolve reference "registry.local:9001/k8s.gcr.io/pause:3.2": failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized

Reproducibility
---------------
Intermittent - but seen frequently

System Configuration
--------------------
any

Branch/Pull Time/Commit
-----------------------
2020-05-13_20-00-00

Last Pass
---------
Unknown - this seems to be an issue with the # of

Timestamp/Logs
--------------
The logs show an image pull failure as follows:
Warning FailedCreatePodSandBox 4m37s (x70 over 19m) kubelet, controller-0 Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "registry.local:9001/k8s.gcr.io/pause:3.2": failed to pull image "registry.local:9001/k8s.gcr.io/pause:3.2": failed to pull and unpack image "registry.local:9001/k8s.gcr.io/pause:3.2": failed to resolve reference "registry.local:9001/k8s.gcr.io/pause:3.2": failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized

Test Activity
-------------
Testing

Workaround
----------
None