Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1461804

Summary: Missing GPGkey field while creating new product via repo discovery
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: RepositoriesAssignee: Tom McKay <tomckay>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bkearney, ehelms, tomckay
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.4.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:54:17 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:
Attachments:
Description Flags
Missing GPGkey field while creating new product via repo discovery
none
in 6.2, gpgkey field was there none

Description Sachin Ghai 2017-06-15 11:13:55 UTC
Created attachment 1288009 [details]
Missing GPGkey field while creating new product via repo discovery

Description of problem:
In satellite6.2, when we create product during repo discovery, we see the GPG key field. Use can specify key. However in 6.3, its not there.

Is it expected behaviour for 6.3 ?

Please see the screen shots for more info

Version-Release number of selected component (if applicable):
satellite 6.3 snap2

How reproducible:


Steps to Reproduce:
1. go to product page
2. select repo discovery
3. specify URL to discover repos
4. select the discovered repo and click create
5. from dropdown, select 'New Product'

Actual results:
Missing GPGkey field while creating new product via repo discovery

Expected results:
it was there in 6.2

Additional info:

Comment 1 Sachin Ghai 2017-06-15 11:14:36 UTC
Created attachment 1288010 [details]
in 6.2, gpgkey field was there

Comment 4 Tom McKay 2017-06-15 12:31:55 UTC
Created redmine issue http://projects.theforeman.org/issues/20026 from this bug

Comment 5 Satellite Program 2017-06-26 22:00:32 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20026 has been resolved.

Comment 6 Satellite Program 2017-08-03 22:00:33 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20026 has been resolved.

Comment 7 Stanislav Tkachenko 2017-08-15 16:52:08 UTC
Verified on Satellite 6.3 Snap 11:
* satellite-6.3.0-16.0.beta.el7sat.noarch
* katello-3.4.4-2.el7sat.noarch
* foreman-1.15.3-1.el7sat.noarch

Comment 8 Satellite Program 2018-02-21 16:54:17 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://access.redhat.com/errata/RHSA-2018:0336