[Spacewalk-list] spacewalk-clone-by-date [SEC=UNCLASSIFIED]

[Andrew Bergman]

Hi List,

We have a Channel structure whereby we have a Parent channel, say centos7-x86_64, which contains no packages or errata but within it has child channels such as centos7-updates-x86_64.  We also have cloned frozen channels of these childs within the parent channels so that we can easily subscribe systems to the frozen channels without having to delete and re-register using a new activation key.  Instead rather than being subscribed to centos7-updates it is instead subscribed to frozen-201704-updates-x86_64 for example.  The main thing is that the parent channel is unchanged.

This works great, except that it appears we cannot use spacewalk-clone-by-date in this structure:

# spacewalk-clone-by-date -y -j --username <username> --channels=centos7-updates-x86_64 frozen-201709-centos7-updates-x86_64 --to_date=`date +%F` --parents centos7-x86_64
Password:
Reading repository information.
Using issue_date.
Channel centos7-x86_64 is not a cloned channel.

Is there any way around this?  Why must the parent also be a clone?!?

In the past the organisation created frozen channels manually by doing them on the day via the Web UI.  Whereas now, with an updated spacewalk running 2.6, we want to be able to draw our line in the sand, to a date which may be in the past,  quickly and easily from command line which can be automated later by using the spacewalk-clone-by-date script.

Cheers

Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20170914/83c66a47/attachment.htm>