You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During CI end-to-end lanes, it happens a node stuck with an InProgress SriovNetworkNodeState and its logs contain a list of
E0625 14:40:06.172663 5508 token_source.go:185] Unable to rotate token: failed to read token file "/var/run/secrets/kubernetes.io/serviceaccount/token": open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
E0625 14:40:11.177478 5508 token_source.go:185] Unable to rotate token: failed to read token file "/var/run/secrets/kubernetes.io/serviceaccount/token": open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
E0625 14:40:16.179337 5508 token_source.go:185] Unable to rotate token: failed to read token file "/var/run/secrets/kubernetes.io/serviceaccount/token": open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
E0625 14:40:21.183166 5508 token_source.go:185] Unable to rotate token: failed to read token file "/var/run/secrets/kubernetes.io/serviceaccount/token": open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
The cause might be the config-daemon uses chroot and never goes back to the regular filesystem root, making the Token rotator fail to work.
During CI end-to-end lanes, it happens a node stuck with an
InProgress
SriovNetworkNodeState and its logs contain a list ofThe cause might be the config-daemon uses chroot and never goes back to the regular filesystem root, making the Token rotator fail to work.
Attaching a report archive
ocp-artifacts (15).zip
The text was updated successfully, but these errors were encountered: