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
The relation data still shows the previously configured bucket name in the data field. I think this is causing Tempo worker applications to remain in a restart (tenacity) loop with the pebble logs providing:
"error running Tempo" err="failed to init module services: error initialising module: store: failed to create store: unexpected error from ListObjects on tempo: The specified bucket does not exist"
As you can see, the 3 applications do not behave the same (Mimir vs. Loki & Tempo). We need to ensure that the same functionality exists for all 3.
After deploying cos with TF, with the manual steps of:
The relation data still shows the previously configured bucket name in the
data
field. I think this is causing Tempo worker applications to remain in a restart (tenacity) loop with the pebble logs providing:As you can see, the 3 applications do not behave the same (Mimir vs. Loki & Tempo). We need to ensure that the same functionality exists for all 3.
Tempo
Loki
Mimir
The text was updated successfully, but these errors were encountered: