Red Hat Network Satellite 4.2.0 Notice

RHN Satellite Customers, 

We wanted to make available some notes about the upcoming
Red Hat
Enterprise Linux 5.0 (official date not announced yet) and
RHN Satellite
4.2 releases (available now). With Red Hat Enterprise Linux
5.0, we are
moving to yum as the standard client by which to communicate
with the
Red Hat Network Satellite. The yum on Red Hat Enterprise
Linux 5.0 will
be packaged with a plug-in to achieve this capability. We
have also made
changes in the rhn_register command to support changes in
the Red Hat
Enterprise Linux 5.0 registration process.   

As a result of these changes, only Red Hat Network Satellite
4.2, Proxy
4.2 and beyond will be compatible with Red Hat Enterprise
Linux 5.0.
Any customer using the new OS in their environment in
combination with
Red Hat Network Satellite will need to upgrade to version
4.2 or newer.

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

Thanks Richard.

Where do we find information on upgrading our RHN Proxy
server?  We are 
currently running RHN Proxy 4.0.

$ rpm -qa | grep -i proxy
rhns-proxy-docs-4.0.6-11.rhel4
rhns-proxy-redirect-4.0.6-11.rhel4
rhns-proxy-management-4.0.6-11.rhel4
rhns-proxy-tools-4.0.6-11.rhel4
rhns-proxy-broker-4.0.6-11.rhel4
rhns-proxy-package-manager-4.0.6-11.rhel4


Alfred Hovdestad, RHCE
University of Saskatchewan



Richard Friedman wrote:
> RHN Satellite Customers, 
> 
> We wanted to make available some notes about the
upcoming Red Hat
> Enterprise Linux 5.0 (official date not announced yet)
and RHN Satellite
> 4.2 releases (available now). With Red Hat Enterprise
Linux 5.0, we are
> moving to yum as the standard client by which to
communicate with the
> Red Hat Network Satellite. The yum on Red Hat
Enterprise Linux 5.0 will
> be packaged with a plug-in to achieve this capability.
We have also made
> changes in the rhn_register command to support changes
in the Red Hat
> Enterprise Linux 5.0 registration process.   
> 
> As a result of these changes, only Red Hat Network
Satellite 4.2, Proxy
> 4.2 and beyond will be compatible with Red Hat
Enterprise Linux 5.0.
> Any customer using the new OS in their environment in
combination with
> Red Hat Network Satellite will need to upgrade to
version 4.2 or newer.
> 
> _______________________________________________
> rhn-users mailing list
> rhn-usersredhat.com
> htt
ps://www.redhat.com/mailman/listinfo/rhn-users

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

Hi there,
The upgrade process for RHN Proxy is outlined within the
following 
knowledge base article:

How do I upgrade my Red Hat Network (RHN) Proxy to the
latest version?
http://k
base.redhat.com/faq/FAQ_48_8542.shtm


For anyone interested for RHN Satellite, see:

How is Red Hat Network (RHN) Satellite upgraded to the most
current version?
http://k
base.redhat.com/faq/FAQ_49_8610.shtm

Regards,
Clifford.


Alfred Hovdestad wrote:
> Thanks Richard.
> 
> Where do we find information on upgrading our RHN Proxy
server?  We are 
> currently running RHN Proxy 4.0.
> 

-- 
Clifford Perry
Team Lead, RHN Sustaining Engineering
Red Hat, Inc.
http://www.redhat.com/
+1 919 754 4403
RHCE# 803004507210710

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

Hi,

Can you give some idea of the timescale involved?

Thanks Nick

--On 28 February 2007 15:28 -0500 Richard Friedman
<rfriedmaredhat.com> 
wrote:

> RHN Satellite Customers,
>
> We wanted to make available some notes about the
upcoming Red Hat
> Enterprise Linux 5.0 (official date not announced yet)
and RHN Satellite
> 4.2 releases (available now). With Red Hat Enterprise
Linux 5.0, we are
> moving to yum as the standard client by which to
communicate with the
> Red Hat Network Satellite. The yum on Red Hat
Enterprise Linux 5.0 will
> be packaged with a plug-in to achieve this capability.
We have also made
> changes in the rhn_register command to support changes
in the Red Hat
> Enterprise Linux 5.0 registration process.
>
> As a result of these changes, only Red Hat Network
Satellite 4.2, Proxy
> 4.2 and beyond will be compatible with Red Hat
Enterprise Linux 5.0.
> Any customer using the new OS in their environment in
combination with
> Red Hat Network Satellite will need to upgrade to
version 4.2 or newer.
>
> _______________________________________________
> rhn-users mailing list
> rhn-usersredhat.com
> htt
ps://www.redhat.com/mailman/listinfo/rhn-users



------------------------------------------------------------
----------------
Nick Bruton                                          PADI
Divemaster #624215
University of Bristol                                TDM LC4
640 SuperMoto
Computing Service
Tyndall Avenue
Bristol BS8 1UD
Tel: 0117 9288193

Team email: isys-srctbris.ac.uk

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

Given the announcement below, we would like to upgrade our
RHN Proxy
server from 4.0 to 4.2. What is the process to do this? Does
it require
a complete reinstall or is it as simple as modifying the
channel
subscription and running up2date on the proxy server? We are
also
running the proxy server over SSL. Will this upgrade require
us to
generate new certs? Our proxy server is running on RHEL AS
4.

TIA,

Gregg Phillips
NOAA/OAR/ESRL/GSD

Richard Friedman wrote:
> RHN Satellite Customers, 
>
> We wanted to make available some notes about the
upcoming Red Hat
> Enterprise Linux 5.0 (official date not announced yet)
and RHN Satellite
> 4.2 releases (available now). With Red Hat Enterprise
Linux 5.0, we are
> moving to yum as the standard client by which to
communicate with the
> Red Hat Network Satellite. The yum on Red Hat
Enterprise Linux 5.0 will
> be packaged with a plug-in to achieve this capability.
We have also made
> changes in the rhn_register command to support changes
in the Red Hat
> Enterprise Linux 5.0 registration process.   
>
> As a result of these changes, only Red Hat Network
Satellite 4.2, Proxy
> 4.2 and beyond will be compatible with Red Hat
Enterprise Linux 5.0.
> Any customer using the new OS in their environment in
combination with
> Red Hat Network Satellite will need to upgrade to
version 4.2 or newer.
>
> _______________________________________________
> rhn-users mailing list
> rhn-usersredhat.com
> htt
ps://www.redhat.com/mailman/listinfo/rhn-users
>
>   

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

Hi there,
I had previously replied to a similar question. The upgrade
process for 
RHN Proxy is outlined within the following knowledge base
article:

How do I upgrade my Red Hat Network (RHN) Proxy to the
latest version?
http://k
base.redhat.com/faq/FAQ_48_8542.shtm

More comments below.

Cliff.

Gregg Phillips wrote:
> Given the announcement below, we would like to upgrade
our RHN Proxy
> server from 4.0 to 4.2. What is the process to do this?
Does it require
> a complete reinstall or is it as simple as modifying
the channel
> subscription and running up2date on the proxy server? 
Reinstall, see link.
> We are also
> running the proxy server over SSL. Will this upgrade
require us to
> generate new certs? 
Should not, no.
> Our proxy server is running on RHEL AS 4.
>
> TIA,
>
> Gregg Phillips
> NOAA/OAR/ESRL/GSD
>   

-- 
Clifford Perry
Team Lead, RHN Sustaining Engineering
Red Hat, Inc. 
http://www.redhat.com/
+1 919 754 4403
RHCE# 803004507210710

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

Yes, I did look at this document as I processed through the
thread.
However, it appears to be concerned with upgrading from 3.X
to 4.X. My
question has to do with upgrading from 4.0 to 4.2 a minor
revision
update. The kbase doc listed below talks about upgrading
OSes and SSL to
4.X standards and since I am already there is there a need
to redo these
steps or can I just change to the most recent channel, 4.2,
and run up2date?

Thanks,

Gregg.

Clifford Perry wrote:
> Hi there,
> I had previously replied to a similar question. The
upgrade process
> for RHN Proxy is outlined within the following
knowledge base article:
>
> How do I upgrade my Red Hat Network (RHN) Proxy to the
latest version?
> http://k
base.redhat.com/faq/FAQ_48_8542.shtm
>
> More comments below.
>
> Cliff.
>
> Gregg Phillips wrote:
>> Given the announcement below, we would like to
upgrade our RHN Proxy
>> server from 4.0 to 4.2. What is the process to do
this? Does it require
>> a complete reinstall or is it as simple as
modifying the channel
>> subscription and running up2date on the proxy
server? 
> Reinstall, see link.
>> We are also
>> running the proxy server over SSL. Will this
upgrade require us to
>> generate new certs? 
> Should not, no.
>> Our proxy server is running on RHEL AS 4.
>>
>> TIA,
>>
>> Gregg Phillips
>> NOAA/OAR/ESRL/GSD
>>   
>

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

Gregg Phillips wrote:
> Yes, I did look at this document as I processed through
the thread.
> However, it appears to be concerned with upgrading from
3.X to 4.X. My
> question has to do with upgrading from 4.0 to 4.2 a
minor revision
> update. The kbase doc listed below talks about
upgrading OSes and SSL to
> 4.X standards and since I am already there is there a
need to redo these
> steps or can I just change to the most recent channel,
4.2, and run up2date?
>   
Reviewing the article I do see how it is not clear in this
respect (and 
have already asked a member of my team to review and update
the article 
on this). A 4.0 -> 4.2 RHN Proxy change is still
considered a major 
upgrade, and cannot just flip channels and run up2date -u on
it. The 
process is as outlined within the kbase article - backup,
reinstall, 
install 4.2, restore.

Regards,
Cliff
> Thanks,
>
> Gregg.
>
> Clifford Perry wrote:
>   


-- 
Clifford Perry
Team Lead, RHN Sustaining Engineering
Red Hat, Inc. 
http://www.redhat.com/
+1 919 754 4403
RHCE# 803004507210710

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

On 3/1/07, Nick Bruton <nick.brutonbristol.ac.uk> wrote:
> Hi,
>
> Can you give some idea of the timescale involved?

And if you can't give us any idea of the timescale involved
can you
give us some idea of what will happen if RHEL5 is released
before
these upgrades are completed?

Thanks,
John

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

On 3/1/07, Clifford Perry <cperryredhat.com> wrote:
> As I am sure you are aware, if you monitor the
rhelv5-beta-list, and
> thread
> (https://www.redhat.com/archives/rhel
v5-beta-list/2007-February/msg00106.html)
> that a date is not freely available to give out.

I am very well aware and did not ask you to give me a date.

I find it disappointing that Red Hat is treating its
customers this
way. Do you think we have nothing else to do and can drop
everything
whenever Red Hat decides to say "upgrade your
infrastructure now or
stuff is going to break." And not even get the courtesy
of a "you have
X days to complete these upgrades before stuff breaks"
timeframe to
work in. I'm assuming we have 10-14 days from the
announcement based
on a previous comment. But Red Hat doesn't stick by the
dates they do
leak either, as the evidence you provide below demonstrates,
so who
knows?

Unbelievable.

> The last public press release from Red Hat giving a
rough date that I
> know off is:
> http://www.redhat.com/about/news/prarchive/2006/r
hel5beta2.html
> "Red Hat Enterprise Linux 5, to be released in
early 2007".
>
> I felt that Rich's email was fairly clear, but to
restate in another way
> for you  ...
>
>   If you plan to use/deploy Red Hat Enterprise Linux 5
with any current
> RHN Satellite or RHN Proxy systems you have deployed,
then those systems
> will need to be upgraded to at least RHN 4.2 Satellite
or RHN 4.2 Proxy
> prior to being able to use them with the yum based
client in Enterprise
> Linux 5 and code changes for rhn_register.
>
> So, for example, if you have a 4.1 RHN Proxy which was
pointing to RHN
> (rhn.redhat.com, xmlrpc.rhn.redhat.com) you could
register a Enterprise
> Linux 5 system through it, but when you tried to use
yum to try and
> download packages, it would fail. While for a 4.1
Satellite, both would
> fail.

If some nut in a hat decides tomorrow to release RHEL5 I
would like to
know that all our current processes will continue working.
At least
the processes that aren't already broken by unresolved bugs.
That was
implied by Rich's email I think but I'd feel better hearing
it in a
more direct fashion. I think it is implied by your
restatement too.

At this point I don't really care. I'll just go with the
flow like the
other cool kids.

John

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users