I have an SMT box (sles11sp2) that my production boxes use for updates.
All my servers are sles11sp2 (with or without oes11sp1).
I have not seen any updates for sles11sp2 or oes11sp1 in the past few
weeks.
Is that just how it’s been (no updates) or is my SMT box missing
something?
I’m mirroring these:
OES11-SP1-Pool sle-11-x86_64
OES11-SP1-Updates sle-11-x86_64
SLE11-SMT-Updates sle-11-x86_64
SLES11-SP2-Core sle-11-x86_64
SLES11-SP2-Updates sle-11-x86_64
–
Stevo
“Stevo” Wrote in message:
[color=blue]
I have an SMT box (sles11sp2) that my production boxes use for updates.
All my servers are sles11sp2 (with or without oes11sp1).I have not seen any updates for sles11sp2 or oes11sp1 in the past few
weeks.Is that just how it’s been (no updates) or is my SMT box missing
something?I’m mirroring these:
OES11-SP1-Pool sle-11-x86_64
OES11-SP1-Updates sle-11-x86_64
SLE11-SMT-Updates sle-11-x86_64
SLES11-SP2-Core sle-11-x86_64
SLES11-SP2-Updates sle-11-x86_64[/color]
Since there have been updates for both SLES11 SP2 and OES11 SP1 I
would check that your registration codes are still valid and
haven’t expired.
Note also that SLES11 SP2 uses a couple of SLES11 SP1 repositories
HTH.
Simon
SUSE Knowledge Partner
----Android NewsGroup Reader----
http://www.piaohong.tk/newsgroup
Simon Flood sounds like they ‘said’:
[color=blue]
Since there have been updates for both SLES11 SP2 and OES11 SP1 I
would check that your registration codes are still valid and
haven’t expired.Note also that SLES11 SP2 uses a couple of SLES11 SP1 repositories
- see TID 7010225.
HTH.
[1] https://www.suse.com/support/kb/doc.php?id=7010225[/color]
So my response to Simon’s comment is…
Weird thing is, my SMT server does not update from itself, it updates
from Novell.
I re-registered it with an activation code that is not expired, and
there still are no updates for this box.
It’s SLES11sp2 with no OES installed on it.
Anything else to check?
–
Stevo
On 29/04/2014 17:25, Stevo wrote:
[color=blue]
Weird thing is, my SMT server does not update from itself, it updates
from Novell.I re-registered it with an activation code that is not expired, and
there still are no updates for this box.It’s SLES11sp2 with no OES installed on it.
Anything else to check?[/color]
Checking a local SLES11 SP2 server and our updates server I now don’t
think that there have been any updates for SLES11 SP2 since the
beginning of February. This would seem to tie in with General Support
for SLES11 SP2 ending on 31 January[1], more than 6 months after SLES11
SP3 was released on 01 July 2013[2].
Time to upgrade to SLES11 SP3!
HTH.
Simon
SUSE Knowledge Partner
Simon Flood sounds like they ‘said’:
[color=blue]
Time to upgrade to SLES11 SP3!
[/color]
So my response to Simon’s comment is…
Ok, so is this a PITA? I’m guessing this can be done to an existing
server? Can you point me to documentation on the steps needed?
–
Stevo
On 30/04/2014 14:50, Stevo wrote:
[color=blue]
Ok, so is this a PITA? I’m guessing this can be done to an existing
server? Can you point me to documentation on the steps needed?[/color]
There are several ways of upgrading SLES11 SP2 to SP3, offline using
physical (or virtual) media or online via YaST (wagon) or zypper - see
https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec_update_sle11sp2.html
Whilst I had issues with online upgrades during beta process those were
resolved once SP3 was released.
Simon
SUSE Knowledge Partner
Simon Flood sounds like they ‘said’:
[color=blue]
There are several ways of upgrading SLES11 SP2 to SP3, offline using
physical (or virtual) media or online via YaST (wagon) or zypper -
see
https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec
_update_sle11sp2.htmlWhilst I had issues with online upgrades during beta process those
were resolved once SP3 was released.HTH.[/color]
So my response to Simon’s comment is…
Thanks for the info Simon.
–
Stevo
Simon Flood sounds like they ‘said’:
[color=blue]
There are several ways of upgrading SLES11 SP2 to SP3, offline using
physical (or virtual) media or online via YaST (wagon) or zypper -
see
https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec
_update_sle11sp2.htmlWhilst I had issues with online upgrades during beta process those
were resolved once SP3 was released.HTH.[/color]
So my response to Simon’s comment is…
So is a person required to go to OES11sp2 as part of this update, or
afterwards even?
Or can that be done later at your convenience?
–
Stevo
On 01/05/2014 16:00, Stevo wrote:
[color=blue]
So is a person required to go to OES11sp2 as part of this update, or
afterwards even?Or can that be done later at your convenience?[/color]
If you’re wanting to upgrade an OES11 SP1 (on SLES11 SP2) to OES11 SP2
(SLES11 SP3) then you need to upgrade both SLES11 SP2 and OES11 SP1 to
SLES11 SP3 and OES11 SP2 at the same time. Otherwise you’ll end up
uninstalling the OES components thus breaking OES. See
https://www.novell.com/documentation/oes11/inst_oes_lx/data/b11mrzf5.html
Simon
SUSE Knowledge Partner
Simon Flood sounds like they ‘said’:
[color=blue]
There are several ways of upgrading SLES11 SP2 to SP3, offline using
physical (or virtual) media or online via YaST (wagon) or zypper -
see
https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec
_update_sle11sp2.htmlWhilst I had issues with online upgrades during beta process those
were resolved once SP3 was released.HTH.[/color]
So my response to Simon’s comment is…
Ok, so I tried a couple test servers, results follow:
via yast wagon, all seems fine, still no updates available and this
server is sles11sp3 now.
via booting from media (just for sles update), oes is broken on
this server, doesn’t even show Open Enterprise Server in yast
anymore…sigh
–
Stevo
Simon Flood sounds like they ‘said’:
[color=blue]
If you’re wanting to upgrade an OES11 SP1 (on SLES11 SP2) to OES11
SP2 (SLES11 SP3) then you need to upgrade both SLES11 SP2 and OES11
SP1 to SLES11 SP3 and OES11 SP2 at the same time. Otherwise you’ll
end up uninstalling the OES components thus breaking OES. See
https://www.novell.com/documentation/oes11/inst_oes_lx/data/b11mrzf5.h
tmlHTH,
Simon[/color]
So my response to Simon’s comment is…
D’oh! Found this out the hard way on one of my test boxes. Now, to
get it back on there.
–
Stevo