Red Hat Bugzilla – 1254252 – Fields 'Customer Portal Username/Password' under Access Insights > Manage(Sat 6.1.1) should not be mandatory to use Insights service
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 1063863[details]
UI authentication error
Description of problem:
The Access insights Service is not available to the user in Satellite 6.1.1 until he mentions 'Customer Portal Username/passowrd under RHAI> Manage tab.
Version-Release number of selected component (if applicable):
ruby193-rubygem-foreman-redhat_access-0.2.2-1.el7sat.noarch
How reproducible:
Steps to Reproduce:
1. Setup a Satellite 6.1.1 instance.
2. Register a client machine to the Satelite instance using:
subscription-manager register --activationkey <ak> --org <org name>
3.redhat-access-insights --register
Actual results:
[root@abc ~]# redhat-access-insights --register
ERROR: Upload failed!
Debug Information:
HTTP Status Code: 502
HTTP Status Text: Bad Gateway
[root@abc ~]# redhat-access-insights --test-connection
Connection test config:
Proxy config: None
Certificate Verification: /etc/rhsm/ca/katello-server-ca.pem
Testing upload_url connection:
Testing: https://hp-dl320g6-01.rhts.eng.bos.redhat.com:443/redhat_access/r/insights/uploads/
HTTP Status Code: 502
HTTP Status Text: Bad Gateway
Connection failed
Testing: https://hp-dl320g6-01.rhts.eng.bos.redhat.com:443
HTTP Status Code: 500
HTTP Status Text: Internal Server Error
Connection failed
Testing: https://hp-dl320g6-01.rhts.eng.bos.redhat.com:443/r
HTTP Status Code: 404
HTTP Status Text: Not Found
Connection failed
Testing: https://hp-dl320g6-01.rhts.eng.bos.redhat.com:443/r/insights
HTTP Status Code: 404
HTTP Status Text: Not Found
Connection failed
upload_url test success
Testing api_url connection:
Testing: https://hp-dl320g6-01.rhts.eng.bos.redhat.com:443/redhat_access/r/insights/
HTTP Status Code: 401
HTTP Status Text: Unauthorized
Connection failed
Testing: https://hp-dl320g6-01.rhts.eng.bos.redhat.com:443
HTTP Status Code: 401
HTTP Status Text: Unauthorized
Connection failed
Testing: https://hp-dl320g6-01.rhts.eng.bos.redhat.com:443/r
HTTP Status Code: 404
HTTP Status Text: Not Found
Connection failed
Testing: https://hp-dl320g6-01.rhts.eng.bos.redhat.com:443/r/insights
HTTP Status Code: 404
HTTP Status Text: Not Found
Connection failed
api_url test success
Connectivity tests completed successfully
refer screenshots for the UI.
Expected results:
Registration should have been successful, no mandatory Portal username/password should be there.
Additional info:
A test config file was inadvertently included in the build.
To workaround this issue for these steps on satellite server:
(1) rm /opt/rh/ruby193/root/usr/share/gems/gems/redhat_access-0.2.2/config/config.yml
(2) service httpd restart
Verified on SNAP 17.
rpm version: ruby193-rubygem-foreman-redhat_access-0.2.3-1
The client system can register to the RHAI service without adding a Customer Portal Username/Password in the RHAI > Manage tab.
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-2015:1688