Upgrade SUSE

SUSE Life Cycle Announcement and Steps for Upgrade From: Amazon Web Services, Inc.Add to Contacts

Sent: Fri, Feb 19, 2016 at 2:04 pm

Based on our records we believe you are currently running or have launched in the past twelve months an instance of a SUSE Linux Enterprise Server (SLES) AMI that SUSE has marked for deprecation as part of SUSE’s standard image lifecycle. The SLES AMI(s) we believe you have used that are marked for deprecation are:

ami-c7144c82

SUSE is deprecating these AMIs either because they are older versions of SLES that are now out of the SUSE support life cycle, or because they use an older update infrastructure that SUSE is retiring. SUSE has indicated it is necessary for you to migrate to a newer SLES version per the instructions below so that you will continue to receive software updates from SUSE as part of their standard support cycle.

As part of SUSE’s deprecation process, AWS will take these SLES AMI(s) out of the Amazon EC2 AMI catalog on May 18, 2016. You will not be able to launch any further instances from the AMI after that date. Although running instances will not be interrupted at that time, they will not be able to restart from a reboot or stop/start. To avoid interruption of service, you must migrate/update your running instances by following the instructions below.

In connection with the SUSE deprecation, AWS took steps to minimize new usage of the deprecated AMIs by removing them from the search function of the console and API/CLI on May 28, 2015. However, with the AMI ID you will still be able to launch new instances via the API or CLI from the AMIs until the deprecation date of May 18, 2016.

Should you require assistance identifying and updating your instances, please contact AWS Support.

Full details from SUSE can be found in the AWS section of the following SUSE post:

SUSE Image Life Cycle for Public Cloud Deployments

Update/upgrade applies only to 64bit SLES. All 32bit SLES AMIs and update infrastructure is being deprecated on May 18 2016. SLES has all required package to run 32bit software on the 64bit kernel and you should migrate to a 64bit SLES.

Run the following command to determine which patch level of SUSE Linux Enterprise Server (SLES) you are running:

1) cat /etc/SuSE-release | grep PATCHLEVEL

If you are running SLES 11 SP1 you need to first upgrade to SLES 11 SP2. Due to the way the repositories were set up in the old update infrastructure you will get some warnings during the “zypper refresh” step in the procedure below. Ignore these warnings by entering “i.”

1) zypper up

2) cd /etc/zypp/repos.d

3) for i in *SP1*; do newname=${i/SP1/SP3}; cp $i $newname; done

4) sed -i s/SP1/SP3/ *SP3*.repo

5) sed -i s/enabled=0/enabled=1/ *SP3*.repo

6) zypper refresh

7) zypper in zypper

8) zypper dup

9) wget http://54.197.240.216/instanceInfraUpgrade.noarch.rpm

10) zypper –non-interactive in instanceInfraUpgrade.noarch.rpm

11) instanceInfraUpgrade

12) rm instanceInfraUpgrade.noarch.rpm

If you are running instances based on SUSE Linux Enterprise Server 11 SP2 you need to follow the upgrade procedure below to SUSE Linux Enterprise Server 11 SP3.

1) zypper up

2) cd /etc/zypp/repos.d

3) for i in *SP1*; do newname=${i/SP1/SP3}; cp $i $newname; done

4) sed -i s/SP1/SP3/ *SP3*.repo

5) sed -i s/enabled=0/enabled=1/ *SP3*.repo

6) zypper refresh

7) zypper in zypper

8) zypper dup

If you are running an instance based on SLES 11 SP3 run:

1) grep smt-ec2 /etc/hosts

If this returns empty you will need to migrate your instance to the new update infrastructure. This process will introduce changes to the instance including introducing cloud-init. root remains the default user (ec2-user is the default user for new images) and the hostname and hostkeys are preserved.

1) wget http://54.197.240.216/instanceInfraUpgrade.noarch.rpm

2) zypper –non-interactive in instanceInfraUpgrade.noarch.rpm

3) instanceInfraUpgrade

4) rm instanceInfraUpgrade.noarch.rpm