Environment

• Yugabyte Platform - All

Issue

Yugabyte Anywhere upgrade fails with below error on Replicated installation's based environment. The below snippet is from the platform host after running the below command. 

$sudo docker logs -f replicated

WARN 2022-11-12T11:15:31+00:00 daemon/daemon.go:1234 Cannot pin to release sequence 124, sequence is less than current sequence 125 

NOTE: The digit 124 and 125 is just an example, it can be changed according to the release running in the environment.

Overview

Yugabyte Anywhere upgrade will fail with above error if you are running a version which coincidently running a release which is having high Sequence Number than current release.

Cause

Replicated software (Replicated Portal) checks for the Sequence Number with respect to the Yugabyte Anywhere software release. Replicated ignores the actual release version of software i.e 2.12.x. Since the Sequence Number is always incremental, the availability/order of Yugabyte Anywhere Software may be affected in certain edge cases. 

Example

Let’s assume we have two versions of Yugabyte Anywhere available, one is 2.12.1 having Sequence Number 123, and another is 2.14.1 with Sequence Number 124 and the customer is running 2.12.1. Now at some point we delivered a patch or maintenance for 2.12.1, the next Sequence Number becomes 125 for 2.12.1.p1 (patched) version.

In this situation, the user can install the patched 2.12.1.p1 (125) but not the newer software 2.14.1 since that Sequence Number is now lower after the release of the patch for the older version of Yugabyte Anywhere software, and will face errors described above. 

Resolution

1. If this is not urgent, wait for the latest software release which will be added as a higher Sequence Number.
2. If this is urgent, the Yugabyte Team can create a placeholder version with higher Sequence Number which can workaround the situation. Please open a case with Yugabyte Support for this option.