Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 517468 - [RFE] spacewalk-repo-sync needs --with-childs
Summary: [RFE] spacewalk-repo-sync needs --with-childs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 0.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Stephen Herr
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: spacewalk-rfe space22
TreeView+ depends on / blocked
 
Reported: 2009-08-14 08:29 UTC by Sandro Mathys
Modified: 2014-07-17 08:40 UTC (History)
5 users (show)

Fixed In Version: spacewalk-backend-2.2.31-1
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-17 08:40:56 UTC
Embargoed:

Attachments (Terms of Use)

Description Sandro Mathys 2009-08-14 08:29:08 UTC 
Right now, one has to sync the base channel and each child channel one by one. It should be possible to specify --with-childs together with the base channel (i.e. either --channel=<base> --with childs or --with-childs=<base>) to sync them all together.

Since in future spacewalk releases, it should be possible to have >1 repo per channel, all repos of base+childs should be synced with this option.

As for '--label is mandatory', which obviously doesn't work well with this new feature, see:
https://bugzilla.redhat.com/show_bug.cgi?id=517467
Comment 1 Jan Hutař 2010-08-24 09:19:53 UTC 
Hello, just tested on SWnightly and there is no --with-childs option or providing more --channel options do not work and accepts only last one.
Comment 2 Jan Hutař 2010-08-24 10:47:25 UTC 
Oh, for issue in comment #1 reported separate bug, so please ignore it as it is different use-case.
Comment 4 Jan Pazdziora 2010-11-19 16:02:44 UTC 
Mass-moving to space13.
Comment 5 Miroslav Suchý 2011-04-11 07:31:16 UTC 
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Comment 6 Miroslav Suchý 2011-04-11 07:36:21 UTC 
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Comment 7 Jan Pazdziora 2011-07-20 11:48:45 UTC 
Aligning under space16.
Comment 8 Dimitar Yordanov 2014-04-24 15:24:28 UTC 
I would like to add to this RFE two more useful option.

[-l|--list] List the Custom channels available on the Satellite server with the associated repositories.

[-d|--dry-run] Do a test run. No sync takes place. Useful when the repositories are set in the Satellite database and the user want to check the channel->repository configuration beforehand.
Comment 9 Stephen Herr 2014-04-24 18:20:45 UTC 
Accepting pull request https://github.com/spacewalkproject/spacewalk/pull/41 which adds the --list option mentioned in comment 8. I expect patches for the other options mentioned in this bug to be following shortly.

Committing to Spacewalk master:
5775e76647587f545ebc4d71ec8ec91ba1c98b00
Comment 10 Stephen Herr 2014-05-23 16:11:14 UTC 
Accepting pull request https://github.com/spacewalkproject/spacewalk/pull/51 which adds the --dry-run option. Now we are just waiting for a --with-children option or similar.

Committing to Spacewalk master:
bbcafcfc77476e2189ffeff11202158a658b8262
83a9d85aa964940028166fcb65a22ef3c804fb2a
50f6cf185925e9bb6f4bd6471d08227e02fa3f6e
Comment 11 Stephen Herr 2014-05-30 15:12:13 UTC 
Accepting pull request https://github.com/spacewalkproject/spacewalk/pull/86 which adds the --parent option. If you supply a channel label with --parent then the specified channel and all of its children will be synced. This resolves the request in comment 0.

Committing to Spacewalk master:
39b64b5e6235c1b4b8d674610e1f4f82b3fe90dc
Comment 12 Milan Zázrivec 2014-07-17 08:40:56 UTC 
Spacewalk 2.2 has been released:

    https://fedorahosted.org/spacewalk/wiki/ReleaseNotes22
Note You need to log in before you can comment on or make changes to this bug.