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
After implementing workarounds for #339 and #340 I hit the following issue:
litmus-upgrade-agent-cp-1-v7sqs upgrade-agent 2023-10-09T13:58:26.707181972+02:00 {"level":"fatal","ts":1696852706.706867,"caller":"upgrade-agent/main.go:54","msg":"failed to create upgrade manager","error":"failed to get previous version data from db, error=mongo: no documents in result","stacktrace":"main.main\n\t/upgrade-agent/main.go:54\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:225"}
The text was updated successfully, but these errors were encountered:
wrdls
changed the title
Fresh install of 3.0.0 fails on upgrade-agent
Fresh install of litmus 3.0.0 fails on upgrade-agent
Oct 9, 2023
wrdls
changed the title
Fresh install of litmus 3.0.0 fails on upgrade-agent
[litmus] Fresh install of litmus 3.0.0 fails on upgrade-agent
Oct 9, 2023
Hey @wrdls Thanks for pointing this out, We are removing upgrade-job from the templates for now to remove any confusion, as we are not supporting DB upgrade from 2.x.x to 3.x.x - #342
It will be added again once we support DB upgrade for upcoming versions!
After implementing workarounds for #339 and #340 I hit the following issue:
The text was updated successfully, but these errors were encountered: