Bug 1367915 - spacewalk-clone-by-date may not clone all packages correctly
Summary: spacewalk-clone-by-date may not clone all packages correctly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-17 19:14 UTC by Grant Gainey
Modified: 2016-11-07 13:38 UTC (History)
3 users (show)

Fixed In Version: spacewalk-java-2.3.8-154-sat
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 13:38:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2662 0 normal SHIPPED_LIVE Satellite 5.7 bug fix update 2016-11-07 18:37:17 UTC

Comment 1 Grant Gainey 2016-08-17 19:42:08 UTC
Description of problem:

Using spacewalk-clone-by-date to clone a content's entire channel:

[#c0 had internal machine names - repeating w/cleansed data]

# spacewalk-clone-by-date --login -l rhel-i386-server-6 cbd-rhel-i386-server-6 -y -d 2016-08-15

should result in the same number of packages and errata as the originating channel. In some cases, alas, it does not.

Actual results:

https://<SAT5.7>/rhn/software/channels/All.do:

 cbd-rhel-i386-server-6	RED HAT SATELLITE ENGINEERING	9057	3555
	
Expected results:

https://<SAT5.7>/rhn/software/channels/All.do:

 cbd-rhel-i386-server-6	RED HAT SATELLITE ENGINEERING  13806	3555

Additional info:

The issue is a suboptimal query introduced by SW commit 

2be48080365ed26f12de18818c3327e84af0dcf9

that causes the query 'find all errata whose packages need to be cloned into a destination channel' to return an empty set.

Comment 2 Grant Gainey 2016-08-22 19:30:55 UTC
spacewalk.github:
c9584cbb4d30c36c0c5ec31c50fa03691954f74e

Comment 7 errata-xmlrpc 2016-11-07 13:38:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2662.html


Note You need to log in before you can comment on or make changes to this bug.