Description of problem: Running insights-client with the latest egg 3.0.97 fails at the step to set the display name. Also the display name is not changed, so that it wants to change it is a second bug. ---------- 2019-05-10 15:13:06,133 DEBUG insights.client.connection HTTP Response Reason: OK 2019-05-10 15:13:06,134 DEBUG insights.client.connection HTTP Response Content: {"total":1,"count":1,"pag ... lti.com"],"infrastructure.ipv4_addresses":null,"system_properties.memory_in_gb":"1.9 GB"}}],"created":"2019-03-12T01:21:13.679506Z","updated":"2019-05-10T14:40:08.140931Z"}]} 2019-05-10 15:13:06,134 DEBUG insights.client.connection No HTTP Response message present. 2019-05-10 15:13:06,135 INFO network PATCH https://fibssat6sb.hag.hilti.com:443/redhat_access/r/insights/platform/inventory/v1/hosts/4fc26dc4-826e-4549-85cb-ce3bca62f485 2019-05-10 15:13:06,147 DEBUG insights.client.connection HTTP Status Code: 404 2019-05-10 15:13:06,147 DEBUG insights.client.connection HTTP Response Text: {"status":404,"error":"Not Found"} 2019-05-10 15:13:06,147 DEBUG insights.client.connection HTTP Response Reason: Not Found 2019-05-10 15:13:06,147 DEBUG insights.client.connection HTTP Response Content: {"status":404,"error":"Not Found"} 2019-05-10 15:13:06,148 DEBUG insights.client.connection No HTTP Response message present. 2019-05-10 15:13:06,148 INFO insights.client.connection Debug Information: HTTP Status Code: 404 2019-05-10 15:13:06,148 INFO insights.client.connection HTTP Status Text: Not Found 2019-05-10 15:13:06,148 ERROR insights.client.connection Could not update display name. ------------- With egg 3.0.87 this was all working and the display name was also not tried to to be changed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Connect client to Sat6 2. Set displayname to dummy-$fqdn 3. Run insights-client with egg 3.0.97 Actual results: Step 3 fails with a 404 Expected results: Success Additional info:
This one is reported here as well: https://bugzilla.redhat.com/show_bug.cgi?id=1708295 - we have a patch and are working with the satellite team to ship it.
I have a display name set in the config. The other BZ did not mention that situation. If that is also covered then this BZ can be closed as a duplicate
Should be the same bug but we'll definitely test both. I set this to depend on the other BZ for now until we are sure.
We do have a hot fix for satellite that we can share if you would like.
Jeff, The patch for Sat6.x is the long term solution that will take a long time before cusotmers have it in place. As the insights client is the frequent changing part it shall keep the backwards compatible mode when connected through Sat6. At least with egg 3.0.87 it was still working. If new features (e.g. like the compliance payload upload) really needing the 'PATCH and payload' features of the sat6 fix a check if it is supported on Sat6 shall be done and the user shall be notified accordingly. Peter
This is fixed in Insights Core version 3.0.102
This is now fixed. Note that the fix is independent of