[Spacewalk-list] RHEL 6.x repository not syncing from parentchannel

Tue Dec 20 21:39:58 UTC 2016

Like Jeremy said,

The URLs used within yum or subscription-manager may not be the same as within spacewalk. I know, yum uses variables within its config. Spacewalk cannot use these... This is why we asked for the URL (with authentication token and/or credentials removed).

If I remember right, one of your directory names had variables in it. This might be one part of the problem. 

Currently, I have no further tips for you. If the SSL certificate and key are correct (and valid) and the URL (without variables) is correct and firewall is not blocking and you don't have a proxy that might interfer in a strange way... Then... You are very unlucky and would suggest to really start from the beginning. Completely re-setup the server.

Robert 

Am 20. Dezember 2016 17:29:18 MEZ, schrieb jma at schaubroeck.be:
>Hi Daryl
>
>
>At the risk of repeating something someone else has already said,
>here's 
>my thoughts:
>
>Spacewalk-repo-sync and the subscription manager registration are two 
>separate things. I don't think anyone doubts that your server is 
>registered all fine with RedHat and that all the relevant yum commands 
>work. But as far as I know the two are unrelated.
>
>If you want to sync directly with Spacewalk itself (spacewalk-repo-sync
>
>is that, and it uses the repo config you set within spacewalk) then you
>
>will have to use the way Paul described:
>>
>> 2) using a the same URL and keys as subscription manager, the URLs
>for
>> the repos and the SSL keys can be retrieved from subscritpion manager
>> on a registered host or through access.redhat.com by drilling into
>the
>> subscriptions.
>>
>> the scheduling and exact options like the URL and if a SSL cert is
>> used are configured on each repository through the spacewalk web
>> interface. by the way this is the url you were being asked about.
>>
>Aka: in your repository configuration in spacewalk you have to enter
>the 
>correct URL, along with an SSL CA Certificate, SSL Client Certificate 
>and SSL Client Key. The info where to get these and how to use them has
>
>been posted on the list a few times.
>
>Now the URL should be fine from what I read, but did you check the SSL 
>cert/key? Are they the ones for your current registered server or for 
>the old one? Are they still valid? (I had mine expire earlier this
>year, 
>took me a while to figure out that was the issue) If there is an issue 
>with these the sync will just outright fail without much useful info. 
>Example:
>
>> Sync started: Sun Nov 20 20:30:00 2016
>> ['/usr/bin/spacewalk-repo-sync', '--channel', 'rhel-6-server-x86_64',
>
>> '--type', 'yum', '']
>> Repo URL: <whatever correct URL for whatever repo you want>
>> ERROR: Cannot retrieve repository metadata (repomd.xml) for 
>> repository: rhel-6-server-x86_64. Please verify its path and try
>again
>> Sync completed.
>> Total time: 0:00:00
>
>Regards,
>Jeremy
>
>On 20/12/2016 16:44, Daryl Rose wrote:
>>
>> Robert,
>>
>>
>> Thank you for the reply, and I apologize if I came off angry in my 
>> reply to you before.
>>
>>
>> In your comments you kept asking about the URL.  As I've stated many 
>> times previously, the server is registered, and entitled properly. 
>>  I've been able to prove this many different ways.  By running the
>yum 
>> command, by using the subscription-manager command to verify my 
>> entitlement etc....  I even opened a ticket with Red Hat to verify 
>> the entitlement, but because I mentioned Spacewalk in the ticket they
>
>> told me to go pound sand because I don't have a Satellite 
>> subscription.    But that was just a feel good ticket anyway.  I know
>
>> that the URL that I am using is accurate, because I can run the "yum 
>> repolist", "yum update" and "reposync" command and they all work. 
>>  There is something else that is broke.
>>
>>
>> You and others tell me to look at the logs, however, there is nothing
>
>> in the logs to point me in the direction on what the issue is. I've 
>> posted the only error that I receive.  Oh, one thing that I have 
>> failed to mention is that I disabled the schedule a couple of weeks 
>> ago when this issue first started.  So that takes taskomatic out of 
>> the picture.  I have been using the "spacewalk-repo-sync" command
>from 
>> the command line trying to troubleshoot this issue. That is why in
>all 
>> of my previous updates I kept specifying spacewalk-repo-sync.  But 
>> that is my fault for not mentioning that before.
>>
>>
>> With that said, I don't care how many verbose v's I put at the end of
>
>> the command, the only error that I get is the error that I've been 
>> posting.
>>
>>
>> Here is what I get in the channel log:
>>
>> 2016/12/20 09:12:22 -05:00 Sync of channel started.
>>
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.channel_info('rhel-6-server-rpms',)
>> 2016/12/20 09:12:22 -05:00 Repo URL: <RHEL URL HERE>
>> 2016/12/20 09:12:22 -05:00 Sync of channel completed in 0:00:00.
>>
>> Here is what I get in the reposync.log:
>> 2016/12/20 09:12:22 -05:00 Command: ['/usr/bin/spacewalk-repo-sync', 
>> '--channel', 'rhel-6-server-rpms', '-vvv']
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(136,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(136, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(133,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(133, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(103,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(103, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(122,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(122, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(129,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(129, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(120,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(120, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(121,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(121, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(131,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(131, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(124,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(124, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(138,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(138, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(134,)
>> 2016/12/20 09:12:22 -05:00 2595 0.0.0.0: 
>> server/rhnChannel.isCustomChannel(134, 'is a custom channel')
>> 2016/12/20 09:12:22 -05:00 ======================================
>> 2016/12/20 09:12:22 -05:00 | Channel: rhel-6-server-rpms
>> 2016/12/20 09:12:22 -05:00 ======================================
>> 2016/12/20 09:12:22 -05:00 Sync of channel started.
>>                            Please check 
>> 'reposync/rhel-6-server-rpms.log' for sync log of this channel.
>> 2016/12/20 09:12:22 -05:00 Sync of channel completed.
>> 2016/12/20 09:12:22 -05:00 Total time: 0:00:00
>>
>> Not much information to go on.
>>
>> Thanks
>>
>> Daryl
>>
>>
>------------------------------------------------------------------------
>>
>> *From:* spacewalk-list-bounces at redhat.com 
>> <spacewalk-list-bounces at redhat.com> on behalf of Robert Paschedag 
>> <robert.paschedag at web.de>
>> *Sent:* Tuesday, December 20, 2016 9:02 AM
>> *To:* spacewalk-list at redhat.com
>> *Cc:* spacewalk-list at redhat.com
>> *Subject:* Re: [Spacewalk-list] RHEL 6.x repository not syncing from 
>> parentchannel
>> Hi Daryl,
>> I'm not angry....also frustrated because we all seem to talk about 
>> different things and you seem to focus on an problem, that - in my 
>> opinion - is not of interest yet.
>> The first is to get the synchronisation from RHEL done!
>> Now....in your first post, you wrote, that you did not get updates 
>> from RHEL since several month. This makes me think....aha....you are 
>> downloading "directly" from RHEL. Hence, this is your "master" 
>> spacewalk server. So the "creation" of the metadata of the 
>> "downloaded" packages (that does not work right now) is currently
>useless.
>> The main problem is....why can't you download the packages?
>> One problem might be...that you are "not" entitlet to download. But 
>> you wrote, you are. So I take this for granted.
>> So....when I look into one of my sync logs, it looks like 
>> this...(these are stored in /var/log/rhn/reposync/...)
>> ...
>> Sync started: Tue Mar 22 11:43:43 2016
>> ['/usr/bin/spacewalk-repo-sync', '--channel', 
>> 'sles12-sp1-updates-x86_64', '--type', 'yum']
>> Repo URL: 
>>
>http://<MY-INTERNAL-SMT-Server>/repo/SUSE/Updates/SLE-SERVER/12-SP1/x86_64/update/
>
>>
><http://s0002120.swr.ard/repo/SUSE/Updates/SLE-SERVER/12-SP1/x86_64/update/>
>> Packages in repo:               893
>> Packages already synced:          0
>> Packages to sync:               689
>> 1/689 : openssh-fips-6.6p1-33.1-0.x86_64
>> 2/689 : libxml2-tools-2.9.1-17.1-0.x86_64
>> 3/689 : ceph-common-0.80.11-8.1-0.x86_64
>> 4/689 : desktop-data-SLE-12-3.1-0.noarch
>> 5/689 : postgresql94-docs-9.4.6-7.2-0.noarch
>> 6/689 : gnome-shell-3.10.4-54.1-0.x86_64
>> 7/689 : typelib-1_0-Polkit-1_0-0.113-5.6.1-0.x86_64
>> 8/689 : xorg-x11-server-extra-7.6_1.15.2-46.1
>> ...
>> So here the "Repo URL" the script tries to connect to, is listed. And
>
>> this is the URL we want you to show us. Please also remove any 
>> possible authentication tokens and credentials.
>> What I also think is that you - maybe - run a spacewalk proxy! that 
>> tries to download his packages from an "upstream" spacewalk server. 
>> But you did not mention this (or maybe a didn't read it).
>> Regards,
>> Robert
>> *Gesendet:* Dienstag, 20. Dezember 2016 um 15:16 Uhr
>> *Von:* "Daryl Rose" <darylrose at outlook.com>
>> *An:* "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
>> *Betreff:* Re: [Spacewalk-list] RHEL 6.x repository not syncing from 
>> parentchannel
>>
>> Hello Paul,
>>
>> Thank you for the information.
>>
>> In response to your statement about angry reply.  No, I am not angry.
>
>> Frustrated yes, angry no.  Comments made by Robert, and then you do 
>> frustrate me. I've been trying to figure this out now for several 
>> weeks, posting questions with no answer.  In more than one reply I 
>> had specifically said where I had obtained the URL.    I've tried to 
>> be as specific as I could about what I am seeing and what specific 
>> steps I've taken to resolve this issue. I've asked multiple times, 
>> where does the data 