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:
No notifications are raised for success or failure of taks related to gpg-keys.
Version-Release number of selected component (if applicable):
sat6.1-Beta-snap2
How reproducible:
always
Steps to Reproduce:
1. create valid gpg-key
2. create invalid gpg-key
3. Neither success nor error notifications are raised.
Actual results:
Neither success nor error notifications are raised.
Expected results:
Proper success and error notifications are raised.
Additional info:
Important Note:
This bug is raised after testing with Satellite6.1 Beta Snap2 build, please check for this bug against the mentioned build to re-produce.
It works fine with
a) Nightly
b) zstream
NOTE: Issue is with sat6.1 Beta-snap2 builds only.
In rc7 with
` gpg_strict_validation: true` appended to /etc/foreman/plugins/katello.yaml,
validations appear to be working correctly (http://i.imgur.com/hCaKcXKl.jpg).
Do we want to turn that particular option on by default?
No not that, I am referring to notification not validation of the gpg_key.
Success or Failed notification doesn't work for gpg_key after we try creating one.
Moving to POST since upstream bug http://projects.theforeman.org/issues/10440 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|43b95c67f1071ef00d49f2ea81e146fa5c06dbab.
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/RHBA-2016:1501
