Re: [Spacewalk-list] Unable to kickstart via spacewalk proxy

On 08.12.2014 08:14, Linder, Rolf wrote: Dear all Thanks for your suggestions. We too use spacewalk 2.2 on server and proxy. Right now we’re testing a behavior regarding our channel structure… We use a “special” channel structure as describe here:

Re: [Spacewalk-list] Unable to kickstart via spacewalk proxy

Hi again So, when using a channel structure like this: CentOS 6 --CentOS 6 updates --CentOS 6 approved updates --CentOS 6 internal packages With base channel having packages in it, it is working. But the channel structure (which is working smooth on the spacewalk-server

Re: [Spacewalk-list] Unable to kickstart via spacewalk proxy

On 08.12.2014 09:38, Linder, Rolf wrote: Hi again So, when using a channel structure like this: CentOS 6 --CentOS 6 updates --CentOS 6 approved updates --CentOS 6 internal packages With base channel having packages in it, it is working.

Re: [Spacewalk-list] Interesting OSAD Problem

Hi All, Can someone tell me why all my client server can not get packages from the SW server, this is the same case for all the machines I kickstart from the SW server and physical machine that I added as client to the SW server. When I run yum repolist, it list all the repos but no packages.

Re: [Spacewalk-list] Interesting OSAD Problem

Hi, On 08/12/2014 14:31, ezinne ibeagbazi wrote: Hi All, Can someone tell me why all my client server can not get packages from the SW server, this is the same case for all the machines I kickstart from the SW server and physical machine that I added as client to the SW server. There's

Re: [Spacewalk-list] Unable to kickstart via spacewalk proxy

On 08.12.2014 17:16, Paul Robert Marino wrote: did you by any chance include the updates channel during the kickstart? this is known to cause occasional conflicts. if the updates are in the base channel thats fine because it will actually use the repomd file from the installation disk instead

Re: [Spacewalk-list] Unable to kickstart via spacewalk proxy

I'd like to state that my problem is identical. We can successfully kickstart the same profile directly from our main Spacewalk server, it is only the proxy that fails. On Mon, Dec 8, 2014 at 8:25 AM, Patrick Hurrelmann patrick.hurrelm...@lobster.de wrote: On 08.12.2014 17:16, Paul Robert

Re: [Spacewalk-list] Unable to kickstart via spacewalk proxy

Additional info: Populating the base channel, rather than having a child channel with the base package set, fixes this issue. I would prefer to have the base channel empty, however, as we occasionally need to version lock a base package set and associated updates. It's much easier to go back

Re: [Spacewalk-list] Interesting OSAD Problem

yum repolist  (KEYword here is REPO, not packages) will not list packages but will list your repos which are in /etc/yum.repos.d First, remove all the default repos on all SW clients that came when you did the installation. You do not need this again. You need the repos that belong to the

Re: [Spacewalk-list] Interesting OSAD Problem

Zinny You can check the server logs, btw this problem may happen when you have name resolution problem. When you generate your certificate, the name of your server is using fqdn for example and in your system, only hostname is identified. Check in /var/log/rhn/* for error. __

Re: [Spacewalk-list] Interesting OSAD Problem

Wald, I think my clients were not well installed because non of them can list osad service in it. I don't know if just kickstarting a vm from the kickstart file I created will automatically add them to the server. Please can you send me sample of your kickstart file for client, let me use it and

[Spacewalk-list] Debian reposync fails on spacewalk

Hello, I was wondering if someone could point in the right direction? I created an empty debian channel and trying to sync the repo as follows below, however it keeps failing. https://github.com/stevemeier/spacewalk-debian-sync/blob/master/spacewalk-debian-sync.pl (this is the script I'm

Re: [Spacewalk-list] Interesting OSAD Problem

ATH, I have tried what you suggested and yet still getting the same error but unfortunately the clients I kickstarted from the SW server does not have osad service installed and there's no way to installed them since the packages are not showing unless alternatively I copy the package from SW

Re: [Spacewalk-list] Interesting OSAD Problem

Honestly, I found osad unreliable long term. It’s a lot more reliable to setup a cron that does an rhn_check every 5 mins on your rhn clients ☺ Nick Tailor http://www.nicktalor.com From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Zinny Sent:

Re: [Spacewalk-list] Interesting OSAD Problem

Also the osad package… I think is only available in the child channel (network-tools) If you don’t have that child channel available on the key, it wont pull the package down from spacewalk ☺ Did you add the child-channel to your activation key? Nick Tailor http://www.nicktailor.com From: