[Spacewalk-list] Need help with registration problems.

[Paul Robert Marino]

On Thu, Jan 31, 2013 at 5:24 PM, Edward Drummond
<spacewalkList-iscool at snkmail.com> wrote:
>
>
> That's a very interesting idea and I will try it. The implication is
> there are things needed during install that are not available in the
> "proper" channels, such as:
> fedora16-x86_64
> fedora16-x86_64-updates
> spacewalk18-client-fedora16-x86_64

>
> Is this true? Or is it the case that for me, the channels themselves
> are not available?
>
The spacewalk18-client-fedora16-x86_64 channel is the one you need to
include in the kickstart

> Also, to be clear, you suggest I put the children on the ks file
> directly. Right now I have no child channels on the file, but I do
> have them on an activation key on the ks file. Are you making a
> distinction between these two things? The spacewalk interface
> (I believe) says either of these schemes will work, but they are
> mutually exclusive.
thats not what it means
let me clarify
you need to specify any channels you want to use during the kickstart
process in the kickstart
any channels in the activation key will be included after the
registration which happens at the end of the kickstart but they will
not be visible to the anaconda installer unless you specify them in
the kickstart itself
in other words set the channels in both
>
> Is it possible putting the child channels on a key creates a
> timing issue? Is the client first registered, then activation
> keys are applied?
>
>
>
>
>
> On Thu, Jan 31, 2013 at 4:18 PM, Jon Miller jonebird-at-gmail.com
> |spacewalkList-iscool| <45ka6oedht at sneakemail.com> wrote:
>>
>> I had to setup a child channel, populate it with packages I was missing,
>> and then explicitly select it in your kickstart profile under Kickstart
>> Details -> Operating System. If you have a working client, with good yum
>> repos, you can try the command "yum install  --downloadonly
>> --downloaddir=/tmp rhn-setup rhn-check" (and any others to that list) which
>> will download not only those packages but also their dependencies. Finally,
>> use "rhnpush" to upload those packages to the child channel. At that point
>> you should be able to put those packages in your package list and have them
>> successfully installed. Repeat the process for any other packages you need
>> during install.
>>
>> -- Jon Miller
>>
>>
>> On Thu, Jan 31, 2013 at 1:07 PM, Edward Drummond
>> <spacewalkList-iscool at snkmail.com> wrote:
>>>
>>> I have tried this. If I make it:
>>>
>>> %packages
>>> @ Base
>>> rhn-setup
>>> rhn-check
>>>
>>> %end
>>>
>>> the installer tells me these packages don't exist.
>>>
>>>
>>>
>>>
>>> On Thu, Jan 31, 2013 at 11:47 AM, Jon Miller jonebird-at-gmail.com
>>> |spacewalkList-iscool| <45ka6oedht at sneakemail.com> wrote:
>>>>
>>>> I've seen a similar error during some of my initial kickstarts. The
>>>> error that sticks out to me is your:
>>>>    /tmp/ks-script-QpNRzX: line 207: rhnreg_ks: command not found
>>>>    /tmp/ks-script-QpNRzX: line 213: rhn_check: command not found
>>>>
>>>> What I did was explicitly include "rhn-setup" and "rhn-check" in my
>>>> packages list for my kickstart profile. Try including those packages and see
>>>> if your registration works.
>>>>
>>>> -- Jon Miller
>>>>
>>>>
>>>> On Thu, Jan 31, 2013 at 8:14 AM, key 1
>>>> <spacewalkList-iscool at snkmail.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Can anyone help me. I'm new to spacewalk and a little bit stuck......
>>>>>
>>>>>
>>>>> I have installed spacewalk1.8-postgres on a f17 box. I have
>>>>> repo-sync'ed
>>>>> channels for fedora 16 & 17, as well as CentOS 5 & 6.. (all x86_64).
>>>>>
>>>>> ...
>>>
>>>
>>> -snip
>>>
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list