Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2025-08-04, CAR Team 2025-08-18, CAR Team 2025-09-01
CAR Domain/s:

🟩 Routing and Topology

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

We need to add a new permitted transition in the FCVTransitions class in order to allow downgrading back to the original FCV in case an upgrade fails due to incompatible features. More specifically, we need to allow transition isUpgrading -> isDowngrading -> isDowngraded.

is duplicated by

SERVER-103518 Add support to a feasibility phase on setFCV upgrade

Closed

related to

SERVER-109008 Support "upgrading to downgrading" transition for 8.2 to 9.0 upgrade

Open

SERVER-109377 topologyVersion gets incremented more often than expected on FCV changes

In Code Review

SERVER-109474 Disallow lastLTS to lastContinuous FCV upgrade on addShard containing user data

Closed

Assignee:: Virginia Chacón Pérez (Inactive)
Reporter:: Virginia Chacón Pérez (Inactive)
Participants:: Githook User, Virginia Chacón Pérez
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 21 2025 12:59:17 PM UTC
Updated:: Sep 17 2025 03:46:43 PM UTC
Resolved:: Aug 18 2025 02:28:24 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates