[Spacewalk-list] How to properly setup Solaris Channels

Thu Nov 13 17:13:26 UTC 2014

You shouldn’t have to do that. I have mine set up as separate channels on
CentOS and they work independently. I would try out the Solaris if I had
the time, but I don’t. I also don’t know Solaris really all that much,
hopefully someone else can chime in.

Regards,

[image:
https://lh3.googleusercontent.com/pPQYWyEgd3U9tfRSLCOfyEAjztZRe-j4nPYRdMYrN6FGIZFJEo-O3D-nQ5mhhJA1aetmO-GtoGO7U3mYiw2fDUZIGYNtR5ifQ4hOE_g1rRE0sUqsJlk]

*Ethan Bonick** | Information Technology *
*TruQua*
Mobile 630.445.9313
Office 312.525.8790

*CONFIDENTIAL:  *This e-mail and any attachments are confidential and may
be protected by legal privilege. If you are not the intended recipient, be
aware that any disclosure, copying, distribution or use of this e-mail or
any attachment is prohibited. If you have received this e-mail in error,
please reply and notify the sender and delete this copy from your system.

*From:* spacewalk-list-bounces at redhat.com [mailto:
spacewalk-list-bounces at redhat.com] *On Behalf Of *Daryl Rose
*Sent:* Thursday, November 13, 2014 10:56 AM
*To:* spacewalk-list at redhat.com
*Subject:* Re: [Spacewalk-list] How to properly setup Solaris Channels

Ethan,

To answer your questions, yes. Yes, I ran the rhn_check -vv on the client
server, and yes the server had checked in.  So, the updates channel was a
child of the base, so when I re-registered the client, it should have known
about the child because it was part of the activation key.

I've since blown away the base channel and the child channel and combined
everything into a single channel. I know see that there are over 900
updates available, which should be pretty accurate, however, I don't like
all of patches and packages intermixed.  It makes it difficult to figure
out whats what.  however, that is how the CentOS channel is, all three
repositories combined into a single large list, so maybe I just have to get
used to it.

Thanks

Daryl

On Thu, Nov 13, 2014 at 9:58 AM, Ethan Bonick <ethan.bonick at truqua.com>
wrote:

Have you run an rhn_check or has the server checked in get to get the new
channel config? My guess would be it doesn't know about the channel yet.
When you re-registered did you make sure the child channel is subscribed to
by the base channel? I know some of it is low level and you might have
checked already, but never hurts to ask. Also did you remove the repo or
just the channel?

*Ethan Bonick | *Information Technology
*TruQua*

*CONFIDENTIAL:  *This e-mail and any attachments are confidential and may
be protected by legal privilege. If you are not the intended recipient, be
aware that any disclosure, copying, distribution or use of this e-mail or
any attachment is prohibited. If you have received this e-mail in error,
please reply and notify the sender and delete this copy from your system.

On Thu, Nov 13, 2014 at 8:21 AM, Daryl Rose <rosede12 at gmail.com> wrote:

When I initially setup Solaris, I did just a single channel just for
patches.  However, I decided that I want to also have a base channel as
well.  Currently, if I want to add a new package to a Solaris server, I
have to either pop a dvd into the drive, or NFS an ISO image.  However,
this is what SW is for.  A repository of all of the packages, plus updates
that may need to be applied.

I made a new base channel and imported all of the installation packages
into it.   However, I already had an update channel with a system assigned
to it.  What I am trying to figure out is; what is the correct way to set
up the two channels?

I removed the updates channel, and recreated it as a child of the base
channel.  I had previously removed the subscribed system, so I resubscribed
to the base channel.  There are over 2000 packages in the base channel, and
381 in the updates channel.  I thought that once I resubscribed the server
to the base/child updates channel, I would see needed updates. I know that
there should be 80 updates needed on this server, however, SW tells me that
the system is up to date.

When I setup the CentOS Channel, I created three repositories:  Base,
Updates and Extra's.   All three are then assigned to the CentOS channel.
There are now over 8000 packages available for the CentOS server.  Is best
practice to put *ALL *base packages and updates together in a single
channel so that way the Solaris server can see everything?  Why doesn't the
client server see the child channel and SW tell me that it needs updates?

Thank you.

Daryl

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141113/5d13d6e4/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2038 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141113/5d13d6e4/attachment.gif>