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

https://www.suse.com/c/suse-image-li...d-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..?