Bug 1101545 - Add limitation in man page: spacewalk-clone-by-date doesn't work with RHEL3/RHEL4 channels.
Summary: Add limitation in man page: spacewalk-clone-by-date doesn't work with RHEL3/R...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Documentation
Version: 2.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2014-05-27 13:44 UTC by Neha
Modified: 2017-09-28 18:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1044898
Environment:
Last Closed: 2017-03-10 10:46:58 UTC
Embargoed:

Attachments (Terms of Use)

Description Neha 2014-05-27 13:44:04 UTC 
+++ This bug was initially created as a clone of Bug #1044898 +++

Description of problem:

spacewalk-clone-by-date doest work with RHEL3/RHEL4 channels. Its a limitation of this tool. rhel3/rhel4 channels use up2date to update/install packages and not yum. spacewalk-clone-by-date requires the yum meta-data to be available to do the dependency resolution. 

With RHEL3/RHEL4 spacewalk-clone-by-date fails with error:

~~~~~~~

spacewalk-clone-by-date --username=***** --password=***** --channels=rhel-i386-as-4 clone-rhel-i386-as-4 --to_date=2013-11-10
Reading repository information.

Unable to read repository information.
Please verify repodata has been generated in /var/cache/rhn/repodata/rhel-i386-as-4.

~~~~~~~

Refer also: to add limitation in documents BZ 1040374

--- Additional comment from Neha on 2013-12-19 03:28:56 EST ---
Comment 1 Neha 2014-05-29 12:10:16 UTC 
https://github.com/spacewalkproject/spacewalk/pull/89

~ Neha
Comment 3 Tomáš Kašpárek 2017-03-10 10:46:58 UTC 
PR from comment#1 was accepted in 2014 - closing as it's included in current release.
Comment 4 Eric Herget 2017-09-28 18:11:58 UTC 
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.
Note You need to log in before you can comment on or make changes to this bug.