[Spacewalk-list] systems not registered by default?

Tue Sep 14 17:32:07 UTC 2010

Can a client actually access the RPMs before being activated? I would have thought the tools would need to come from another non-spacewalk repo, installed and then activated.

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jason Welsh
Sent: Tuesday, September 14, 2010 9:24 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] systems not registered by default?

  anyone? i also noticed in my logs, that the "tools rpms" arent getting 
found for some reason.. im sure this is the main cause of the system not 
registering.
but whats the right way to set this up?

--2010-09-13 16:02:56--  
http://redhouse.mydomain.com/download/package/311a7f76de89f7771ca620b1d06d35aeea30bf14/0/1/2197/libxml2-python-2.6.26-2.1.2.8.x86_64.rpm
Resolving redhouse.mydomain.com... 172.18.184.50
Connecting to redhouse.mydomain.com|172.18.184.50|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2010-09-13 16:02:56 ERROR 404: Not Found.

--2010-09-13 16:02:56--  
http://redhouse.mydomain.com/download/package/ca96cbca538ffba541943902c1c742d16347fe3a/0/1/3249/pyOpenSSL-0.6-1.p24.7.2.2.x86_64.rpm
Reusing existing connection to redhouse.mydomain.com:80.
HTTP request sent, awaiting response... 404 Not Found
2010-09-13 16:02:56 ERROR 404: Not Found.

--2010-09-13 16:02:56--  
http://redhouse.mydomain.com/download/package/96cbf812c34191c95aa3a4566933b8eb2226bd64/0/1/6659/rhnlib-2.5.23-1.fc11.noarch.rpm
Reusing existing connection to redhouse.mydomain.com:80.
HTTP request sent, awaiting response... 404 Not Found
2010-09-13 16:02:56 ERROR 404: Not Found.

error: File not found by glob: /tmp/rhn_rpms/optional/pyOpenSSL*
error: File not found by glob: /tmp/rhn_rpms/optional/rhnlib*
error: File not found by glob: /tmp/rhn_rpms/optional/libxml2-python*
cp: cannot stat `/tmp/ks-tree-copy/*': No such file or directory

regards,
Jason

On 09/13/10 13:53, Jason Welsh wrote:
>
>
> On 09/13/10 11:51, Stroehmann, James wrote:
>> My clients auto-register when kickstarting, you might be missing the 
>> spacewalk client tools in your package list?
>>
>>
>> Also, one problem i was having originally was that new systems would 
>> not have the correct time on them, so i have a script in my kickstart 
>> to use rdate to update them.
>>
>>
>> look in the root's home directory for the installation log files, 
>> post them here ... they might provide some clues.
>>
>> _______________
>
> well, ive tried using the setup at 
> https://fedorahosted.org/spacewalk/wiki/HowToKickstartCobbler (please 
> correct me if this is not the right guide to follow)
> the doc says to set up the "tools" distro as a child of my mail 
> rhel-server directory, and someone else stated that it should be this 
> way.. i.e.
>
> rhel-server-5.5
>       |
>       |----VT
>       |----Cluster Server
>       |----Cluster Virtualization
>       |---- rhel-tools <-this has the 4 packages in it. (pyOpenSSL 
> rhnlib libxml2-python # spacewalk-koan)
>
> BUT, when I goto the step that says
> Select "Systems|Kickstart|Distributions" and select "+ create new 
> distribution"
>     "Base channel" should be "Fedora 9 with Tools"     (or rhel-tools 
> in my case)
>
> I cannot select this because its not a base channel.. its a child 
> channel..
>
> can someone please clear up how this is supposed to work?
>
>
> Jason
>
>
>
>
>> _________________________
>> From: spacewalk-list-bounces at redhat.com 
>> [spacewalk-list-bounces at redhat.com] On Behalf Of jason at monsterjam.org 
>> [jason at monsterjam.org]
>> Sent: Monday, September 13, 2010 11:34 AM
>> To: spacewalk-list at redhat.com
>> Subject: Re: [Spacewalk-list] systems not registered by default?
>>
>> ok thanks, I was thinking thats what I had to do, but I was was 
>> hoping there would be something more elegant and
>> built-in.
>>
>> Jason
>>
>> On Mon, Sep 13, 2010 at
>> 10:28:19AM -0500, Mike Hanby
>> wrote:
>>> This may not be the spacewalk way, but in my kickstart files I have 
>>> the clients register via:
>>>
>>> /usr/sbin/rhnreg_ks --serverUrl=http://spacewalk.some.domain/XMLRPC \
>>>   --activationkey=1-7777xxxxxxxxx
>>>
>>> Where the activation key is the appropriate one for whichever 
>>> channel the client needs to join.
>>>
>>> I don't use Spacewalk to handle the actual kickstarting, however.
>>>
>>>
>>> -----Original Message-----
>>> From: spacewalk-list-bounces at redhat.com 
>>> [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of 
>>> jason at monsterjam.org
>>> Sent: Monday, September 13, 2010 9:39 AM
>>> To: spacewalk-list at redhat.com
>>> Subject: [Spacewalk-list] systems not registered by default?
>>>
>>> I noticed that my clients after kickstarting are not
>>> registered with the spacewalk server by default, is there a way to 
>>> make kickstarted systems register with the
>>> spacewalk server by default so that after they're kickstarted, I can 
>>> just do a "yum install screen" or whatever?
>>>
>>> regards,
>>> Jason
>>>
>>>
>>> On Wed, Sep 08, 2010 at 01:32:50PM -0400, Jason Welsh wrote:
>>>>
>>>> On 09/06/10 09:54, James Hogarth wrote:
>>>>> Got your repos with the custom RPMs enabled in both the kickstart
>>>>> (under operating system) and the activation key (under child
>>>>> channels)?
>>>> well, under kickstart details->operating system, i have
>>>>
>>>> child channels:   which lists my 2 custom channels/repos and they 
>>>> have a
>>>> checkbox next to them.
>>>>
>>>> further below, I see
>>>>
>>>> Repositories:
>>>>
>>>> and i see the following :  Cluster, ClusterStorage, Workstation, VT
>>>>
>>>>
>>>> under the activation-keys, i click on my activation key, and click
>>>> "child channels",
>>>> I see my 2 repos under there..
>>>>
>>>> regards,
>>>> Jason
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>> _______________________________________________
>>> 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
>>
>>
>>
>> _______________________________________________
>> 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

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