Description of problem:
- 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):
Steps to Reproduce:
1. navigate to content -> gpg keys
2. hit create new key
3. watch browser console
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 firstname.lastname@example.org
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:
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
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.