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

Bug 1455075

Summary: I'm unable to make blacklist in spacewalk-clone-by-date to work
Product: Red Hat Satellite 5 Reporter: Jan Hutař <jhutar>
Component: OtherAssignee: Jan Dobes <jdobes>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 580CC: tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 08:40:55 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: 1450940    

Description Jan Hutař 2017-05-24 08:42:53 UTC
Description of problem:
I'm unable to make blacklist in spacewalk-clone-by-date to work


Version-Release number of selected component (if applicable):
spacewalk-utils-2.5.1-23.el6sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Create channel bz1103960 and attach repo to it which have:
     Repository URL*: http://<some_download_host>/released/RHEL-5-Server/U0/i386/os/Server/
     Filters: +ImageMagic*,compat*
2. Sync that channel. It gave me channel with 61 packages
3. # spacewalk-remove-channel -c bz1103960-2008-01-01; spacewalk-clone-by-date --assumeyes -u admin -p nimda --channels=bz1103960 bz1103960-2008-01-01 --to_date=2008-01-01 --blacklist='bash'


Actual results:
Resulting channel contains bash package. When I use "--removelist", it works.


Expected results:
bash should not be there


Additional info:
This is not a regression in 5.8.0.

From man page:

[...]
       -b PKG1,PKG2,PKG3, --blacklist=PKG1,PKG2,PKG3
              Comma  separated list of Perl-style regular expressions used to match package names to be removed after cloning. Only newly added packages will removed if they are on the blacklist. Dependency resolu-
              tion is not ensured on resulting repository.

              Note: This option is global across all destination channels. To specify per channel blacklists, you must use a configuration file. See --sample-config for an example.
[...]
       -r PKG1,PKG2,PKG3, --removelist=PKG1,PKG2,PKG3
              Comma separated list of Perl-style regular expressions used to match package names to be removed after cloning. All packages are considered for removal, even those not added by errata/channel cloning.
              Dependency resolution is not ensured on resulting repository.

              Note: This option is global across all destination channels. To specify per channel removelists, you must use a configuration file. See --sample-config for an example.
[...]

Comment 1 Tomas Lestach 2018-04-10 08:40:55 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED.