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.
Created attachment 888976[details]
Screenshot
Description of problem:
Firebug shows the following error when I associated a GPG key to my existing custom product
Error: [$compile:nonassign] Expression 'undefined' used with directive 'alchEditSelect' is non-assignable!
So far it doesn't seem to be fatal...
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a custom product using the UI
2. Create a repository
3. Create a new gpg key
4. Associate the new gpg key to the existing custom product
Actual results:
Firebug shows the error message afore mentioned
Expected results:
Additional info:
I am not seeing the error above; therefore, going to move this BZ to ON_QA for verification.
In my test scenario, I did the following:
- created product/repo (zoo)
- created gpg key (using http://inecas.fedorapeople.org/fakerepos/cds/RPM-GPG-KEY-dummy-packages-generator)
- associated the key with the zoo product
- no error observed
Created attachment 888976 [details] Screenshot Description of problem: Firebug shows the following error when I associated a GPG key to my existing custom product Error: [$compile:nonassign] Expression 'undefined' used with directive 'alchEditSelect' is non-assignable! So far it doesn't seem to be fatal... Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a custom product using the UI 2. Create a repository 3. Create a new gpg key 4. Associate the new gpg key to the existing custom product Actual results: Firebug shows the error message afore mentioned Expected results: Additional info: