Re: [Studio onsite + SLMS] Upgrade SP of rolled-out appliances

We had to add all needed SP3-Repositories to Studio. Now it is possible
to successful upgrade any appliance to SP3. After using the
upgrade-function, studio reports:
Upgraded from SLES 11 SP2 to SLES 11 SP3.
Upgraded from SLES 11 SP1 to SLES 11 SP2.

We then have a link to undo only the last upgrade (to SP3) and fallback
to SP2.


fhg_mko2

fhg_mko2’s Profile: http://forums.suse.com/member.php?userid=8498
View this thread: http://forums.suse.com/showthread.php?t=3390

On 17.10.2013 16:14, fhg mko2 wrote:
>
> We had to add all needed SP3-Repositories to Studio. Now it is possible
> to successful upgrade any appliance to SP3. After using the
> upgrade-function, studio reports:
> Upgraded from SLES 11 SP2 to SLES 11 SP3.
> Upgraded from SLES 11 SP1 to SLES 11 SP2.
>
> We then have a link to undo only the last upgrade (to SP3) and fallback
> to SP2.
>
>

Update:
We still have the problem, that our /etc/SuSE-release file will not be
updated with the new Patchlevel-String like mentioned in the first post
(I am fhg_mko2 and Yes, i have login-problems and support isnt able to
fix that, so i try nntp now, sorry for confusion).

The /etc/SuSE-release of an upgraded appliance still shows:

appliance:~ # cat /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 1

We made some investigation of this and think that this is because of the
adaption process before slms 1.3.

At that time the adaption process includes some automatic installation
of a ‘release-package’ which contained the files
/etc/SuSE-release
/etc/YaST2/control.xml
/etc/issue, /etc/issue.net and /etc/motd
/etc/products.d/<appliance_name>.prod
(See Chapter 5.1.2 Changes in Appliance Release Package, SLMS 1.2
documentation)

Now the adaption process changed and this file seems not to be used any
more. Can somebody confirm this? If so, how can we get rid of this package?

All of our appliances were built with studio 1.1 and adapted with slms
1.1, every appliance have this ‘release-package’ installed which takes
full control of /etc/SuSE-release.

Since removing of a package is not a supported scenario for slms,
anybody has an idea how we can solve this issue?

Btw. rebuilding the appliances and rolling out again is not an option
(we have about 12 kinds of different appliances with up to 60 productive
running instances of each of them).

Anybody help here?

Sincerely
Markus