Canonical Juju

Klog Service Account Errors When Bootstrapping Juju

Bug #2038495 reported by Thomas Miller
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
In Progress
High
Simon Richardson
Canonical Juju 3.1.9

Bug Description

It looks like Kubernetes is changing some behaviour around how service accounts work in Kubernetes and will affect our usage. We are seeing the following in DEBUG output when bootstrapping:

11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:25 DEBUG juju.caas.kubernetes.provider.proxy setup.go:271 polling caas credential rbac secret, in 1 attempt, token for secret "controller-proxy" not found
11:40:26 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:26 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:26 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:26 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:26 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:26 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:26 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:26 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:27 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:27 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:27 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:27 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:27 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:28 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:28 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:28 DEBUG juju.kubernetes.provider configmap.go:31 updating configmap "controller-configmap"
11:40:28 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:28 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:28 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:28 DEBUG juju.kubernetes.provider configmap.go:31 updating configmap "controller-configmap"
11:40:29 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:29 DEBUG juju.kubernetes.provider secrets.go:60 secret "controller-application-config" created
11:40:29 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:29 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:29 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:29 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:29 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
11:40:29 INFO juju.kubernetes.klog klog.go:60 Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.

Thomas Miller (tlmiller)
Changed in juju:
importance: Undecided → High
Joseph Phillips (manadart)
Changed in juju:
status: New → Triaged
Revision history for this message
Nobuto Murata (nobuto) wrote :

It's spamming the log continuously fwiw.

juju 3.1.6
microk8s 1.28.2

2023-10-26 17:03:40
to
2023-10-30 03:05:59

$ juju debug-log -m controller --replay | grep -c 'Use tokens from the TokenRequest API'
83341

Simon Richardson (simonrichardson)
Changed in juju:
milestone: none → 3.1.8
assignee: nobody → Simon Richardson (simonrichardson)
status: Triaged → In Progress
Revision history for this message
Simon Richardson (simonrichardson) wrote :

See PR to suppress the message https://github.com/juju/juju/pull/16898

More work on getting rid of the origin of the message will be required, but just reducing this will remove load on the logging infrastructure.

Canonical Juju QA Bot (juju-qa-bot)
Changed in juju:
milestone: 3.1.8 → 3.1.9
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.