Environment:

• This issue affects all released versions of Yugabyte.

Issue:

when a customer wants the particular version(application) of a yugabyte at that time, it won't be available to upgrade the version, also if support make changes from the vendor portal then also (it takes the Latest (recommended)as shown in the below screenshot

Resolution:

To solve this issue pin the release sequence of a vendor application by creating or updating the file /etc/replicated.conf with property "ReleaseSequence" set to the numerical identifier of a release of the vendor application. This sequence number must correspond to a release that has been promoted to the channel to which the license is set.

For example:

{

"ReleaseSequence": 123

}

After the modification/making of /etc/replicated.conf file we need to restart replicated container at least or perform a sudo systemctl restart docker so that it can read the file and initiate update checks from there.

Note - A support engineer will tell you ReleaseSequence value to set.