-
Bug
-
Resolution: Done
-
Normal
-
openshift-4.12
-
None
-
None
Description of problem:
With recent builds (I am on microshift-4.12.0_20221206093532_239202f3-1.el8.x86_64), restarting microshift gives a variable number (usually 100+) copies of the following E level message which does not seem to be hurting anything. I've seen up to 173 copies of the message for a restart in limited testing.
Dec 06 14:00:59 dhcp-1-235-119.arm.eng.rdu2.redhat.com microshift[171667]: kube-apiserver E1206 14:00:59.677158 171667 authentication.go:63] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
Dec 06 14:01:00 dhcp-1-235-119.arm.eng.rdu2.redhat.com microshift[171667]: kube-apiserver E1206 14:01:00.378280 171667 authentication.go:63] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
Dec 06 14:01:00 dhcp-1-235-119.arm.eng.rdu2.redhat.com microshift[171667]: kube-apiserver E1206 14:01:00.831107 171667 authentication.go:63] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
Dec 06 14:01:00 dhcp-1-235-119.arm.eng.rdu2.redhat.com microshift[171667]: kube-apiserver E1206 14:01:00.973586 171667 authentication.go:63] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
Dec 06 14:01:01 dhcp-1-235-119.arm.eng.rdu2.redhat.com microshift[171667]: kube-apiserver E1206 14:01:01.359375 171667 authentication.go:63] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
Version-Release number of selected component (if applicable):
microshift-4.12.0_20221206093532_239202f3-1.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. systemctl restart microshift 2. watch the journal for this message. e.g. journalctl --since "<timestamp>" | grep E1206 | wc -l Modify as appropriate for date/time 3.
Actual results:
100+ E level messages as described above
Expected results:
Minimal error messages for a clean restart
Additional info: