Red Hat Bugzilla – Bug 621166
RFE: add options like timeout for spacewalk-repo-sync
Last modified: 2011-12-23 05:02:10 EST
Description of problem:
I am using Spacewalk behind proxies. I want to syncronize a channel in my Spacewalk by running spacewalk-repo-sync but this command does not care about /etc/yum.conf "timeout" setting.
To reproduct the problem, you can run this command: /usr/bin/spacewalk-repo-sync --channel myChannel --url http://aWebServer/mirror/centos.org/5/updates/i386/ --type yum
Downloading problematic file from the same source using wget on the same machine works well.
The actual result is no way to syncronize because of timeout.
Mass-aligning under space12, so that we don't lose track of this bugzilla. This however does not mean that we plan (will be able to) address this bug in Spacewalk 1.2.
Mass-moving to space13.
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
Michael, is spacewalk-repo-sync supposed to use /etc/yum.conf content? Do we have an alternative way of specifying timeouts for spacewalk-repo-sync?
Well definitely not, /etc/yum.conf is server's yum configuration file, i.e. what's matter when you do 'yum update'.
While spacewalk-repo-sync is spacewalk's (the application) stuff. We'd better introduce our own configuration file e.g. /etc/rhn/spacewalk-repo-sync/yum_src.conf or something like that if there's need for it. And better not mix up server's and application's stuff, they might have very different needs for the same option.
(In reply to comment #7)
> Well definitely not, /etc/yum.conf is server's yum configuration file, i.e.
> what's matter when you do 'yum update'.
> While spacewalk-repo-sync is spacewalk's (the application) stuff. We'd better
> introduce our own configuration file e.g.
> /etc/rhn/spacewalk-repo-sync/yum_src.conf or something like that if there's
> need for it. And better not mix up server's and application's stuff, they might
> have very different needs for the same option.
In any case, spacewalk-repo-sync not caring about /etc/yum.conf is expected and correct thing to do.
While the initial description is NOTABUG, let's keep this bugzilla open as an RFE, to add the possibility to configure similar things. I might prefer to have this configured in the database rather than in the config file -- you might want to have different timeout/proxy/whatever values for different repositories, so it's best kept close to those repositories data-wise.
I did report this bug because spacewalk-repo-sync man page tells that the only current supported type is yum. see --type=yum
(In reply to comment #9)
> I did report this bug because spacewalk-repo-sync man page tells that the only
> current supported type is yum. see --type=yum
That's correct. But as Michael explained in comment 7, while both yum the system updater and spacewalk-repo-sync might use the same libraries from the yum package, the /etc/yum.conf is only meant to configure yum (the system updater). We currently don't have the equivalent of /etc/yum.conf for spacewalk-repo-sync.
I'm OK with what you said. Maybe just add proxy and timeout parameters to spacewalk-repo-sync command. ex.: --proxy= and --timeout=
This feature has been implemented in Spacewalk nightly.
You can put yum related options for spacewalk-repo-sync to /etc/rhn/spacewalk-repo-sync/yum.conf.
Spacewalk master commits
621166 - reuse YumBase instance from __init__
621166 - notice config file in man page
621166 - let's enable yum_src tuning (via config file)
anyway yum options for spacewalk-repo-sync should not interfere with
machine's yum i.e. /etc/yum.conf; thus separate config file
Spacewalk 1.6 has been released.