Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1649882 - [Container Admin Feature] It is possible to set docker tags whitelist for non-docker repository using hammer
Summary: [Container Admin Feature] It is possible to set docker tags whitelist for non...
Keywords:
Status: CLOSED DUPLICATE of bug 1649871
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer - Content
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Released
Assignee: satellite6-bugs
QA Contact: Mirek Długosz
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-14 17:04 UTC by Mirek Długosz
Modified: 2019-10-07 17:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-09 15:15:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mirek Długosz 2018-11-14 17:04:13 UTC
Docker tags whitelist is new feature in 6.5. It is relevant only for `docker` repositories. However, using hammer, it is possible to set it to non-docker repositories as well.


Version:
Satellite 6.5 snap 3
pulp-server-2.17.1-1.el7sat.noarch
katello-3.9.0-0.11.rc2.el7sat.noarch
foreman-1.20.0-0.17.RC2.el7sat.noarch
satellite-6.5.0-3.beta.el7sat.noarch
tfm-rubygem-hammer_cli-0.15.1-1.el7sat.noarch


Steps to reproduce:
1. Create new product - remember it's id
2. `hammer repository create --product-id :id --name test --content-type yum --docker-tags-whitelist 'one,two,three'`
3. `hammer repository create --product-id :id --name test-update --content-type yum` and `hammer repository update --id :repo_id --docker-tags-whitelist 'one,two,three'`


Actual results:
Docker tags whitelist field is set to provided value


Expected results:
Docker tags whitelist field is not set (repository is not created / updated and error message is displayed?)

Comment 5 Samir Jha 2019-01-09 15:15:30 UTC

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

Comment 6 Mirek Długosz 2019-01-15 13:36:35 UTC
Fix confirmed - when user attempts to set docker tags whitelist for non-docker repository, error message is displayed. Validation is run during both creation and update.

However, error message could be improved. Reported as https://bugzilla.redhat.com/show_bug.cgi?id=1666312


Version:
Satellite 6.5 snap 11
pulp-server-2.18.0-0.1.rc.el7sat.noarch
foreman-1.20.1.4-1.el7sat.noarch
satellite-6.5.0-5.beta.el7sat.noarch
katello-3.10.0-0.6.rc1.el7sat.noarch


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