Bug 1577798

Summary: no implicit conversion of nil into String while copying activation keys
Product: Red Hat Satellite Reporter: Nikhil Kathole <nkathole>
Component: Activation KeysAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: inecas, nkathole
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-16 17:36:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of UI
none
log in production.log file none

Description Nikhil Kathole 2018-05-14 07:17:36 UTC
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.

Comment 1 Nikhil Kathole 2018-05-14 07:18:06 UTC
Created attachment 1436046 [details]
log in production.log file

Comment 5 Brad Buckingham 2018-05-16 17:36:43 UTC

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

Comment 6 Ivan Necas 2018-08-08 09:11:32 UTC
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.

Comment 7 Nikhil Kathole 2018-08-08 10:11:57 UTC
Hi ivan,

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