[SERVER-64974] OpsManager upgrade not working (from-4-2-24-to-4-4-10) Created: 26/Mar/22  Updated: 01/May/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Venkata Sivasankar Assignee: Cloud Ops Manager Escalation
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi,
Good morning.

Can I request your suggestions on MongoDB OpsManager upgrade error? I have current setup Ops Manager 4.2.24 version installed. Doing Ops Manager upgrade to 4.4.10 version. I used rpm upgrade process (rpm -Uvh). During upgrade process I hit following error and Ops Manager not upgraded due to this error.

I tried 4.2.24 to 4.2.26, it was working without any issues. but from 4.2.26 to 4.4.10 same issue received.

I crated issue in forums. Please find link below

https://www.mongodb.com/community/forums/t/ops-manager-upgrade-issue-from-4-2-24-to-4-4-10/152739

 

Error Details

2022-03-04T04:54:57.287+0000 [main] ERROR com.xgen.svc.common.migration.MigrationRunner [MigrationRunner.java.run:310] - Failed to apply migration(s) com.xgen.svc.common.migration.exception.NoMigrationPathException: There is no migration path from the existing application version (7c47919fa03b89ec66bb769d7d6ead4246cfa231) to the current one (80727814dc078a9ff9beb24f914729602dc059d0). Exiting. at com.xgen.svc.common.migration.MigrationSvc.verifyMigrationPath(MigrationSvc.java:300) at com.xgen.svc.common.migration.MigrationSvc.areWePerformingASystemUpgrade(MigrationSvc.java:202) at com.xgen.svc.common.migration.MigrationRunner.ensureLiveMigrationsState(MigrationRunner.java:353) at com.xgen.svc.common.migration.MigrationRunner.run(MigrationRunner.java:305)



 Comments   
Comment by Peter Vertenten [ 01/May/23 ]

This just came to my attention, it is incorrectly filed, so didn't land on our work board.

You cannot just upgrade from any 4.2 version to any 4.4 version. The general migration path would be to first upgrade to the latest 4.2.x then upgrade to the latest 4.4.x.

4.2.26 was released 2021-07-29, 4.2.24 was released 2021-05-05
4.4.10 was release 2021-03-04

So essentially you are trying to do an unsupported downgradeish path.

Comment by Venkata Sivasankar [ 27/Mar/22 ]

we tried upgrade process in Red Hat Enterprise Linux 8 

Generated at Thu Feb 08 06:01:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.