# No bash fixes after an instance upgrade process, now what?

**URL:** <https://forums.suse.com/t/no-bash-fixes-after-an-instance-upgrade-process-now-what/26165>\
**Category:** Amazon-EC2\
**Created:** [October 2, 2014, 3:25am UTC](https://forums.suse.com/t/no-bash-fixes-after-an-instance-upgrade-process-now-what/26165 "2014-10-02T03:25:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\
**Post date:** [October 2, 2014, 3:25am UTC](https://forums.suse.com/t/no-bash-fixes-after-an-instance-upgrade-process-now-what/26165/1 "2014-10-02T03:25:18Z")

</div>

You followed the instance upgrade process posted in the blog [https://www.suse.com/communities/conversations/suse-linux-enterprise-server-aws-updates-shellshock/](https://www.suse.com/communities/conversations/suse-linux-enterprise-server-aws-updates-shellshock/) but running “zypper up” does not produce any bash patches.

There may be a couple of reasons:

1.) You are running a SLES 11 SP2 instance:  
Use:

```auto
grep "SUSE Linux Enterprise Server" /etc/products.d/SUSE_SLES.prod
```

to confirm

For SUSE Linux Enterprise Server 11 SP2 the bash patches are not generally available in the update repositories. SUSE Linux Enterprise Server 11 SP2 has been out of general support, i.e. receiving updates and security fixes since January 2014. However, this issue is obviously very critical and thus SUSE is making the bash fixes available for SP2 users. The update process is as follows (as root):

```auto
curl http://ec2-54-197-240-216.compute-1.amazonaws.com/shellshockPatchEC2_SLES11SP2.tgz | tar -zx
./install_shellshockPatchEC2_SLES11SP2.sh
```

2.) The update process failed

Verify that the guest properly registered with the new infrastructure:

```auto
zypper ls
```

should produce output that contains SMT-http\_smt-ec2\_susecloud\_net

If this is not the case the update script should have printed the register commend to be used to re-run the registration. This command can also be found in the registration log file /var/log/cloudregister. If the registration was successful, i.e. “zypper ls” contains the service indicated above but no repos are available, i.e. the output of “zypper lr” is empty, then “suse\_register -r” should do the trick to restore the repositories.