Bug 1308895

Summary: [RFE] Support remove-old option on hammer level in Satellite 6.2
Product: Red Hat Satellite Reporter: Jindrich Novy <jindrich.novy>
Component: HammerAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1.6CC: bbuckingham, fhirtz, xdmoon
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-19 19:53:15 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: 260381, 1115190    

Description Jindrich Novy 2016-02-16 11:54:08 UTC
Description of problem:
There will be a new Pulp in Satellite 6.2 supporting 'remove-old' flag for repositories which allows to publish only packages which are present in the upstream repository. So once they are deleted upstream they will also vanish from published content.

Since this feature is new to Satellite's Pulp it would be nice if hammer understands this option as well so that hammer created repositories needn't to be amended via pulp-admin afterwards.

Nice feature would be to have an UI element in Satellite whether this option is enabled or disabled for a particular repository.

Version-Release number of selected component (if applicable):
6.2

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Brad Buckingham 2016-04-19 19:53:15 UTC
Thanks for creating the bugzilla request.

Satellite 6.2 will introduce a feature referred to as 'mirror on sync'.  It will ensure that the repository synced to Satellite will mirror the remote repository.  The solution for this one is covered by bug 1215672; therefore, I am going to mark this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1215672 ***