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 1436045 [details]
screenshot of UI

Description of problem: Trying to copy activation key showed error as no implicit conversion of nil into String and production.log showed 500 internal server error.


Version-Release number of selected component (if applicable): Satellite 6.4.0 snap 3


How reproducible: always


Steps to Reproduce:
1. create activation key
2. copy activation key

Actual results:
no implicit conversion of nil into String error while copying activation keys.


Expected results: No error while copying activation keys.


Additional info: Though error is shown, Activation key got copied.

Created attachment 1436046 [details]
log in production.log file

*** This bug has been marked as a duplicate of bug 1553338 ***

Nikhil: the BZ was marked as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1553338, which should mean that this actually doesn't work in 6.3, while you claim it was working fine for you.

Could you re-verify this with latest snap. Similar BZ has been already verified https://bugzilla.redhat.com/show_bug.cgi?id=1553338, but I wonder if there is something different in your reproducer.

Hi ivan,

Thanks for looking into it. But yes I verified it with latest 6.4 snap 16,
it is working fine now.