ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-08-31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This must be fixed on the 9.0 branch

      Timeline:

      • 9.0 branch cut
      • adding new parameters on master
      • putting r9.0.0-rc1019 tag on master
      • running any patch on v9.0-staging

      During 9.0 release after cutting the 9.0 branch the tag r9.0.0-rc1019 was put on master after adding some new parameters into the codebase.
      The stable API test tests if there was parameter removal (breaking the API) compared to the previous version.
      When running a patch on v9.0-staging, evergreen checks the v9.0-staging head against r8.3.X, v9.0 (branch) head and r9.0.0-rc1019 (latest DSC RC tag).
      Since the r9.0.0-rc1019 logically fresher as the v9.0-staging (as r9.0.0-rc1019 is on master) it really should be r9.1.0-rc1019, but because of some mistake, it got the 9.0 prefix.
      Because of this constellation the stable_api task fails, causing a hot BF.
      The linked ticket (SERVER-133664) fixes the BF by putting the parameters added in r9.0.0-rc1019 on an exception list in v9.0-staging.
      After finalizing the 9.0 release the DSC builds on master will get the 9.1 prefix too, making the whole constellation go away.
      The task here is to revert the changes of SERVER-133664 after 9.0 release.

            Assignee:
            Wolfee Farkas
            Reporter:
            Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: