Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

cluster breaks if skipping major upgrades

Description

I had 3.6 cluster with sharding running and tried to upgrade directly to 4.2 and cluster broke.
Correct upgrade path is 3.6->4.0->4.2->4.4 (without skipping).
Second issue is that we should not allow major upgrade at all if current FCV is not the same as current mongo version (in this case only major downgrade should be allowed) (example of this is running 4.0 cluster while FCV is still 3.6 from previous upgrade and we try to upgrade to 4.2 - it will not work from mongo side).

Error:

Pods:

Environment

None

Smart Checklist

Activity

Show:

Tomislav Plavcic April 29, 2021 at 9:44 AM

Closing as my mistake, tried to do major upgrade with patching the image, which should not be supported.

Not a Bug

Details

Assignee

Reporter

Labels

Time tracking

30m logged

Affects versions

Priority

Smart Checklist

Created April 28, 2021 at 12:31 PM
Updated March 5, 2024 at 4:55 PM
Resolved April 29, 2021 at 9:44 AM