-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.19.0
-
False
-
sat-proton
-
None
-
None
-
None
-
None
Description:
While the Configure\Reconfigure Cloud Connector job runs and completes fine, at the end of each attempt, we see a "400 Bad Request (RestClient::BadRequest)" error with a long traceback and that is unexpected. I have confirmed that the Satellite source remains online\active in console.redhat.com side despite this happening.
Environment:
Satellite 6.19.0 ( Snap 2.0 )
Steps to reproduce and Actual Behavior:
- Install the mentioned satellite version
- Run "satellite-installer --foreman-proxy-plugin-remote-execution-script-install-key true"
- Connect the OS of satellite with console.redhat.com using `rhc connect`
- Go to WebUI --> Red Hat Lightspeed --> Inventory Upload and click on the "Configure Cloud Connector" button
- Once that is complete, click on the "Reconfigure Cloud Connector" button
While monitoring logs , We see the job is actually completed for both step 4 and 5, but at the very end of that job, we see
2026-03-05T20:54:44 [I|bac|7259cb42] Task {label: Actions::RemoteExecution::RunHostJob, id: 57e4c338-1a87-4c45-b5a8-899679624a6c, execution_plan_id: ef807e3f-9cc5-4d18-9010-ead1ce957baa} state changed: stopped result: success
2026-03-05T20:54:44 [I|app|7259cb42] ForemanWebhooks::EventSubscriber: actions.remote_execution.run_host_job_ansible_configure_cloud_connector_succeeded.event.foreman event received
2026-03-05T20:54:44 [I|app|7259cb42] ForemanWebhooks::EventSubscriber: actions.remote_execution.run_host_job_succeeded.event.foreman event received
2026-03-05T20:55:00 [W|bac|7259cb42] 400 Bad Request (RestClient::BadRequest)
7259cb42 | /usr/share/gems/gems/rest-client-2.1.0/lib/restclient/abstract_response.rb:249:in `exception_with_response'
7259cb42 | /usr/share/gems/gems/rest-client-2.1.0/lib/restclient/abstract_response.rb:129:in `return!'
7259cb42 | /usr/share/gems/gems/rest-client-2.1.0/lib/restclient/request.rb:836:in `process_result'
7259cb42 | /usr/share/gems/gems/rest-client-2.1.0/lib/restclient/request.rb:743:in `block in transmit'
7259cb42 | /usr/share/ruby/net/http.rb:960:in `start'
7259cb42 | /usr/share/gems/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
7259cb42 | /usr/share/gems/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
7259cb42 | /usr/share/gems/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
7259cb42 | /usr/share/gems/gems/foreman_rh_cloud-13.2.0/app/services/foreman_rh_cloud/cloud_request.rb:15:in `execute_cloud_request'
7259cb42 | /usr/share/gems/gems/foreman_rh_cloud-13.2.0/app/services/foreman_rh_cloud/cloud_presence.rb:80:in `register_rhc_instance'
7259cb42 | /usr/share/gems/gems/foreman_rh_cloud-13.2.0/app/services/foreman_rh_cloud/cloud_presence.rb:14:in `announce_to_sources'
7259cb42 | /usr/share/gems/gems/foreman_rh_cloud-13.2.0/lib/insights_cloud/async/cloud_connector_announce_task.rb:21:in `block in finalize'
7259cb42 | /usr/share/gems/gems/activerecord-7.0.10/lib/active_record/relation/delegation.rb:88:in `each'
{+}Expected Results:
{+}No such errors if the job is completed or else if any errors, then it needs to be meaningful enough to understand what the 400 bad request is happening.