Hide Forgot
Description of problem: Error happened when auto attach by subscription-manager-gui Version-Release number of selected component (if applicable): Satellite-6.2.0-RHEL-6-20160420.1 subscription-manager: 1.16.8-8.el6 python-rhsm: 1.16.6-1.el6 How reproducible: 2/3 Steps to Reproduce: 1. Open subscription-manager-gui, and register system to Satellite6.2. 2. Click Auto-attach button: Failed to auto-attach and an error msg prompted. Please see attachment 'error_with_subscribing_in_GUI.png' Actual results: As step 2. Expected results: auto-attach should succeed. Additional info:
Created attachment 1149652 [details] error_with_subscribing_in_GUI.png
Created attachment 1149654 [details] rhsm.log
Also failed by CLI: [root@dhcp-128-71 ~]# subscription-manager attach --servicelevel=standard undefined method `[]=' for nil:NilClass
Also failed in firstboot. Please see attachment "subscribing_failed_in_firstboot.png"
Created attachment 1149663 [details] subscribing_failed_in_firstboot.png
This appears to be an issue in the katello proxy as evidenced by the 'nil' in the error message.
Hi Tom, as this already been fixed or perhaps a duplicate?
Myself and another dev are having trouble reproducing this bug. It most likely has been fixed with recent changes. I am moving to ON_QA in case QA wants to verify.
Verified. Version-Release number of selected component (if applicable): Satellite-6.2.0-20160620.0 subscription-manager: 1.16.8-8.el6 python-rhsm: 1.16.6-1.el6 Register the client to satellite6.2 and auto-attach in GUI, CLI and firstboot. All auto-attachings are successful. Please see attachment 'successful_auto_attach_in_GUI', 'successful_auto_attach_in_CLI' and 'successful_auto_attach_in_firstboot'. Moving this bug from ON_QA to VERIFIED.
Created attachment 1172757 [details] successful_auto_attach_in_GUI
Created attachment 1172758 [details] successful_auto_attach_in_CLI
Created attachment 1172759 [details] successful_auto_attach_in_firstboot
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