This FAQ is to describe the steps necessary to prevent a CSN on CentOS 6.7 (or before) from upgrading to 6.9, which is the latest release as of April, 2017.
CSN 8.2 and 8.3 require CentOS/ RHEL 6.8. Only those versions have been tested. If the CSN is accidentally updated to CentOS/ RHEL 6.9, we can't guarantee all of the CSN's functions will work properly.
If you are upgrading from CSN 8.1 or before, the CSN's OS will be CentOS/ RHEL 6.7 or earlier.
The below steps have been tested with CentOS. If you need assistance updating your CSN to 6.8 on Redhat (not CentOS), please contact Redhat support.
If during the OS upgrade, you simply do a "yum update" after removing the yum lock, per our instructions in the documentation, the CSN will upgrade to CentOS 6.9 which is NOT a supported CSN OS version.
To prevent this from happening, please download the support scripts bundle from https://support.cloud.caringo.com/tools/caringo-support-tools.tgz (if you don't already have it) and transfer it to your CSN. If you already have the support scripts, please run the updateBundle.sh script so that you have the latest tools.
During the CSN upgrade, AFTER removing the yum lock according to the existing documentation, but BEFORE running "yum update", please run the script called csn-yum-68-upgrade.sh as root user.
This will bundle up your existing yum repos and replace them with a single repo file locked to 6.8. After running this script, you will do the yum update as usual.
After the yum update is complete, the usual yum repos associated with 6.8 will be placed by the update process back into /etc/yum.repos.d/
You can then remove the temporary repo used by the csn-yum-68-upgrade.sh script:
rm /etc/yum.repos.d/CentOS-Base-68.repo;yum clean all
After the yum update, you may proceed with the CSN upgrade by running the caringo-csn-bundle-install.sh script in your code bundle.
If you have any questions, please create a ticket with Caringo Tech Support.