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.

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
link/o<@https://sat6.host.fqdn/assets/bastion/bastion-2b28df80b56d107b087fea1305695eaa138231f98bbfee66debf6cd5fc820246.js:75:12982
$digest@https://sat6.host.fqdn/assets/bastion/bastion-2b28df80b56d107b087fea1305695eaa138231f98bbfee66debf6cd5fc820246.js:3:9274
$apply@https://sat6.host.fqdn/assets/bastion/bastion-2b28df80b56d107b087fea1305695eaa138231f98bbfee66debf6cd5fc820246.js:3:10763
s@https://sat6.host.fqdn/assets/bastion/bastion-2b28df80b56d107b087fea1305695eaa138231f98bbfee66debf6cd5fc820246.js:2:18080
y@https://sat6.host.fqdn/assets/bastion/bastion-2b28df80b56d107b087fea1305695eaa138231f98bbfee66debf6cd5fc820246.js:2:19983
Fn/</x.onload@https://sat6.host.fqdn/assets/bastion/bastion-2b28df80b56d107b087fea1305695eaa138231f98bbfee66debf6cd5fc820246.js:2:20526

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

How reproducible:
always

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

Actual results:
javascript traceback

Adding to above description,

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

Created redmine issue http://projects.theforeman.org/issues/23716 from this bug

Upstream bug assigned to tomckay

Connecting redmine issue https://projects.theforeman.org/issues/23381 from this bug

The fix for this was introduced in the upstream with the following PRs:
- https://github.com/Katello/katello/pull/7370
- https://github.com/Katello/bastion/pull/228

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

VERIFIED
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

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-2019:1222