Updating old SLES 11 SP1 EC2 instance, glibc failure

I was trying to update my SLES 11 SP1 ec2 instance by following this blog guide:

https://www.suse.com/c/suse-image-life-cycle-public-cloud-deployments/

I keyed in the commands suggested:

1.) zypper up
2.) cd /etc/zypp/repos.d
3.) for i in SP1; do newname=${i/SP1/SP2}; cp $i $newname; done
4.) sed -i s/SP1/SP2/ SP2.repo
5.) sed -i s/enabled=0/enabled=1/ SP2.repo
6.) zypper refresh
7.) zypper in zypper
8.) zypper dup

Halfway through the install process I kept getting numerous GLIBC not found errors and aborted. On checking the progress I found this:
Installing: glibc-2.9-2.3 [done]

after which I kept getting repeated “version `GLIBC_2.11’ not found” errors.
Now,
zypper throws the same error
yast2 throws the same error
rpm throws the same error

Looking farther back I noticed something very worrying:

The following NEW product is going to be installed:
openSUSE

Did the steps in the blog invariably lead me to installing the wrong version of SuSe and breaking my instance…?

mashakos Wrote in message:
[color=blue]

I was trying to update my SLES 11 SP1 ec2 instance by following this
blog guide:

https://www.suse.com/c/suse-image-life-cycle-public-cloud-deployments/

I keyed in the commands suggested:

1.) zypper up
2.) cd /etc/zypp/repos.d
3.) for i in SP1; do newname=${i/SP1/SP2}; cp $i $newname; done
4.) sed -i s/SP1/SP2/ SP2.repo
5.) sed -i s/enabled=0/enabled=1/ SP2.repo
6.) zypper refresh
7.) zypper in zypper
8.) zypper dup

Halfway through the install process I kept getting numerous GLIBC not
found errors and aborted. On checking the progress I found this:
Installing: glibc-2.9-2.3 [done]

after which I kept getting repeated “version `GLIBC_2.11’ not found”
errors.
Now,
zypper throws the same error
yast2 throws the same error
rpm throws the same error

Looking farther back I noticed something very worrying:

The following NEW product is going to be installed:
openSUSE

Did the steps in the blog invariably lead me to installing the wrong
version of SuSe and breaking my instance…?[/color]

As the article you referenced hints to, SLES11 SP2 is slightly
different when it comes to repositories in that it has oddly
named SP2 repositories plus borrows from SLES11 SP1 - see TID
7010225[1].

However what is concerning is your note about an openSUSE product
being installed. Which repositories do you currently have
configured? Please can you post the output from “zypper lr
-u”.

HTH.

[1] https://www.suse.com/support/kb/doc/?id=7010225

Simon Flood
SUSE Knowledge Partner

----Android NewsGroup Reader----
http://usenet.sinaapp.com/

unfortunately zypper, yast2 and rpm throw the same error:

zypper: /lib/libc.so.6: version GLIBC_2.11' not found (required by /lib/libreadline.so.5) zypper: /lib/libc.so.6: version GLIBC_2.11’ not found (required by /usr/lib/librpm-4.4.so)
zypper: /lib/libc.so.6: version `GLIBC_2.11’ not found (required by /usr/lib/librpmio-4.4.so)

I have restored an older snapshot and am in the process of moving my folders and configs to the restored instance.

I am still back to square one though. How can I upgrade my instance to a more recent version since the blog instructions cannot really be used? Any repository out there that has an upgrade path…?