Red Hat Bugzilla – Bug 1321354
Red Hat Access insight api changed. CF appliance can't connect to it anymore
Last modified: 2016-07-27 02:29:09 EDT
Description of problem: CloudForms is not able to connect to the Access insights portal because of api change? Version-Release number of selected component (if applicable): 5.5.2.4.20160127105142_395c086 How reproducible: 1. My EVM is registered via subscription manager (not satellite6) and has the status Subscribed / Last Message Registered 2. The default profile for the smart state analysis has /etc/redhat-access-insights/machine-id -> true 3. Provider refresh for RHEV so that it discovers the 2 vm's 5. I yum removed the redhat-access-insights package and rm -rf /etc/redhat/access-insights on the vm's 4. I installed redhat-access-insights on the RHEL7 vm's and registered with redhat-access-insights --force-reregister (the vm's are registered with the same rhn user as the cfme appliance) 5. The ID of look like this 1d1d6d48-1250-4b1e-8b20-0362140ee4b3 and abdab4e5-b992-4b7e-92bb-6f9ce8e549f3 (looks like the right format to me) 6. Run a smart state analysis on the machine successfully and see that the file was indexed. 7. Click on the Insight tab in CFME. still no data Actual results: No systems show up in the Red Hat insights portal Expected results: Systems should show up in the insights portal Additional info: This bug was verified already by Lindani Phiri 2016-03-23 20:47:05 EDT with the following comment. bugzilla (1290744) I did not see a seperate bugzilla for it The issue seen by Laurent is unrelated to this bug, even though the symptoms are similar. A change in the external Insights API was made that broke backwards compatibility. Once the API is fixed Laurent's issue should disappear without any changes to the CFME appliance.
Laurent, Insights API has been updated on the customer portal to be backwards compatible. You should now be able to view insights data in your appliance. Lindani
The VM is listed in Red Hat Insights Portal. Verified Version: 5.6.0.7-beta2.6.20160516171555_b1be31f
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:1348