Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1101545

Summary: Add limitation in man page: spacewalk-clone-by-date doesn't work with RHEL3/RHEL4 channels.
Product: [Community] Spacewalk Reporter: Neha <nerawat>
Component: DocumentationAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.2CC: mzywusko, xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1044898 Environment:
Last Closed: 2017-03-10 10:46:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1484117    

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 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.