[Spacewalk-list] registerd system

[Frédéric SOSSON]

Hello,

I would like to know the best practice to register machine into
spacewalk.  Is it to make my own snippet or something else?

Manualy, when I try to register using rhn_register I got
Error Classe Code: 70
Error Class Info: Alla vailable subscriptions for the requested
channel have been exhausted. blablabla

someone know about that?


Frédéric

On 30 April 2010 13:06, Jonathan Scott <lists at xistenz.org> wrote:
> You've got the 0.8-client items installed, what about "python-dmidecode"
> from the EPEL distro?  A quick test on the newly built server, execute
> "rhnreg_ks" and see if it complains about that missing package.
>
> I added "python-dmidecode" in the Software -> Package Groups section of the
> kickstart once I made my locally sync'd copy of the EPEL channel available
> to my kickstart in order to get it to install prior to the snippet execution
> and have my server register to my Spacewalk.
>
> The kickstart its self should be automatically executing the kickstart
> snippet named "rhn_register" (look for the line that says something like
> "#begin Red Hat management server registration").
>
> - Jonathan
>
> 2010/4/30 Frédéric SOSSON <fsosson at gmail.com>
>>
>> I misunderstood you... so I've created a sub channel containing
>> http://spacewalk.redhat.com/yum/ client RPMs.
>>
>> My question is: How telling kickstart file to configure the target
>> machine to use my spacewalk?
>>
>> regards,
>>
>>
>>
>> Frédéric
>>
>> 2010/4/30 Frédéric SOSSON <fsosson at gmail.com>:
>> > Thanks for you help.  Should I include all the package from
>> > http://spacewalk.redhat.com/yum/0.8-client/RHEL/5/$basearch/ in my
>> > repos?
>> >
>> > On 30 April 2010 00:19, Jonathan Scott <lists at xistenz.org> wrote:
>> >> I'm not sure if this applies in your situation, but I just finished
>> >> doing an
>> >> 0.6 -> 0.7 -> 0.8 upgrade (just in time for 1.0 to release) and found
>> >> two
>> >> issues with my kickstarts and packages needed for them:
>> >>
>> >> 1) The packages in the appropriate client directory from
>> >> http://spacewalk.redhat.com/yum/ had to be available in a software
>> >> channel
>> >> for my builds or the rhn* packages wouldn't install.
>> >> 2 ) In order for the rhn_register kickstart snippet to work, I had to
>> >> make
>> >> sure the python-dmidecode package (from the EPEL repository) was also
>> >> available in a software channel so the rhnreg_ks script would execute
>> >> properly.
>> >>
>> >> Once I resolved those package dependencies, everything worked
>> >> perfectly.
>> >>
>> >> Good Luck!
>> >>
>> >> - Jonathan
>> >>
>> >>
>> >> 2010/4/29 Frédéric SOSSON <fsosson at gmail.com>
>> >>>
>> >>> Hello,
>> >>>
>> >>> I configured spacewalk (channels, distribution and kickstart), I
>> >>> installed a centos machine via kickstart, everything looks good but
>> >>> that machine is not configured to use spacewalk channel and I cannnot
>> >>> see the machine in the Systems are in my Spacewalk interface.
>> >>>
>> >>> Anybody could telle what is missing?
>> >>>
>> >>>
>> >>> regards,
>> >>>
>> >>>
>> >>> Frédéric
>> >>>