Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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 1566540 - javascript error on new gpg key page
Summary: javascript error on new gpg key page
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Credentials
Version: 6.3.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: 6.5.0
Assignee: Samir Jha
QA Contact: Roman Plevka
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-12 13:36 UTC by Roman Plevka
Modified: 2019-11-05 22:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-14 12:37:13 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23381 0 None None None 2018-11-08 21:55:58 UTC
Foreman Issue Tracker 23716 0 None None None 2018-11-08 22:00:53 UTC
Red Hat Product Errata RHSA-2019:1222 0 None None None 2019-05-14 12:37:20 UTC

Description Roman Plevka 2018-04-12 13:36:38 UTC
Description of problem:
There is a javascript traceback logged in the browser console on navigating to "new gpg key"
- anyway, the new gpg key form seems to be functional and user is able to create a new record:

Error: t.path(...).match(...) is null

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

How reproducible:

Steps to Reproduce:
1. navigate to content -> gpg keys
2. hit create new key
3. watch browser console

Actual results:
javascript traceback

Comment 4 Nikhil Kathole 2018-04-12 13:52:16 UTC
Adding to above description,

This is common issue while creating each new entity in satellite like creating activation key, host collection, product, etc.

Comment 7 Walden Raines 2018-05-29 02:34:54 UTC
Created redmine issue from this bug

Comment 8 Satellite Program 2018-07-11 20:17:59 UTC
Upstream bug assigned to tomckay

Comment 9 Satellite Program 2018-11-08 21:55:57 UTC
Connecting redmine issue from this bug

Comment 10 Brad Buckingham 2018-11-12 19:15:25 UTC
The fix for this was introduced in the upstream with the following PRs:

I have confirmed that the code changes for both were in the internal Satellite 6.5 SNAP 1 builds; therefore, moving this one to ON_DEV

Comment 12 Roman Plevka 2018-12-10 14:11:51 UTC
on satellite-6.5.0-5.beta.el7sat.noarch

the new content credentials form raises no errors and i am able to create a gpg key successfully

Comment 15 errata-xmlrpc 2019-05-14 12:37:13 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.

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