Bug 1328223 - spacewalk-clone-by-date recursion failure using --blacklist option
Summary: spacewalk-clone-by-date recursion failure using --blacklist option
Keywords:
Status: CLOSED DUPLICATE of bug 1331023
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: 570
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On: 1222906
Blocks: 465198 sat570-triage
TreeView+ depends on / blocked
 
Reported: 2016-04-18 18:49 UTC by Shannon Hughes
Modified: 2020-05-14 15:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-17 18:34:21 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1331023 1 None None None 2021-08-30 10:40:41 UTC

Internal Links: 1331023

Description Shannon Hughes 2016-04-18 18:49:55 UTC 
Description of problem:

When running spacewalk-clone-by-date on a 32bit rhel6 channel using the blacklist flag we see a recursion issue and seems to be masked by python traceback: 

> 
> spacewalk-clone-by-date -u myid --blacklist="kernel*"  --to_date="2016-03-31" --assumeyes --channels=rhel-i386-server-6 lonestar-prod-rhel-i386-server-6 --channels=rhn-tools-rhel-i386-server-6 lonestar-prod-rhn-tools-rhel-i386-server-6
> 
> ....
> File "/usr/lib64/python2.6/httplib.py", line 710, in _set_hostport
>     if host and host[0] == '[' and host[-1] == ']':
> RuntimeError: maximum recursion depth exceeded in cmp

This seems to be an edge case of the following bugzilla: 

https://bugzilla.redhat.com/show_bug.cgi?id=1222906

spacewalk-utils-2.3.2-23.el6sat.noarch
Comment 2 Grant Gainey 2016-08-17 18:34:21 UTC 
Closing this as a dup of 1331023 - testing this scenario with a potential fix for '023 shows it working. Watch '023 for continued investigation/details.

*** This bug has been marked as a duplicate of bug 1331023 ***
Note You need to log in before you can comment on or make changes to this bug.