Hey there, anyone recently experiencing the issue ...
# fleet
a
Hey there, anyone recently experiencing the issue of "update metadata: tuf: failed to decode root.json: expired at 2024-10-06 174749 +0000 UTC"? This error causing all of my agent fail to start and even unable to generate a new agent with fleetctl, when executing "fleetctl package" same error will pop-up and terminate the process
Copy code
2024-10-07T14:24:09+08:00 INF found enroll secret in keystore: Credential Manager
2024-10-07T14:24:09+08:00 INF update metadata. using saved metadata error="update metadata: tuf: failed to decode root.json: expired at 2024-10-06 17:47:49 +0000 UTC"
2024-10-07T14:24:09+08:00 ERR run orbit failed error="target orbit lookup: lookup orbit: expired at 2024-10-06 17:47:49 +0000 UTC"
2024-10-07T14:24:10+08:00 INF found enroll secret in keystore: Credential Manager
2024-10-07T14:24:11+08:00 INF update metadata. using saved metadata error="update metadata: tuf: failed to decode root.json: expired at 2024-10-06 17:47:49 +0000 UTC"
2024-10-07T14:24:11+08:00 ERR run orbit failed error="target orbit lookup: lookup orbit: expired at 2024-10-06 17:47:49 +0000 UTC"
2024-10-07T14:24:12+08:00 INF found enroll secret in keystore: Credential Manager
2024-10-07T14:24:12+08:00 INF update metadata. using saved metadata error="update metadata: tuf: failed to decode root.json: expired at 2024-10-06 17:47:49 +0000 UTC"
2024-10-07T14:24:12+08:00 ERR run orbit failed error="target orbit lookup: lookup orbit: expired at 2024-10-06 17:47:49 +0000 UTC"
j
Same issue here
a
My guess is somehow the root.json is expired, and orbit / fleetctl will raise error whenever this root.json have any issue.
j
yeah, that's what it looks like
Fleet support is aware and is on it
a
good to hear this
z
Thanks @Jacob Burley ! @Alan Chu we will post an update here upon resolution
e
same issue here, commenting to follow thread
t
o
Same issue for me. Waiting for a fix
l
Hi folks! We are working to fix this ASAP. (#22687)
z
hey folks - providing another quick update here that we're still actively working on this as our highest priority and hope to have a resolution shortly.