Description of problem:

Registering a host with satellite server is always successful and never shows any failures even when the built request did not complete successfully. 

Steps to reproduce: 

• Block port 80 incoming access to satellite
• generate a global reg curl command and execute it on a client host to register it
• once registered , check the Build status for the host

Actual and Expected Behavior:

This is what the relevant part looks like: 

Refreshing subscription data
+ subscription-manager refresh
All local data refreshed
+ trap - ERR
+ '[' -x /usr/bin/curl ']'
+ /usr/bin/curl -o /dev/null --noproxy '*' -H 'Content-Type: text/plain' --silent 'http://satellite.example.com/unattended/built?token=fa252db8-ac61-4110-86bf-43771f7f0141'
++ command -v subscription-manager
+ '[' -x /usr/sbin/subscription-manager ']'
+ subscription-manager facts --update
Successfully updated the system facts.
+ [[ 0 == 0 ]]
+ echo 'Host [rhel9.example.com] successfully configured.'
Host [rhel9.example.com] successfully configured.
+ subscription-manager facts --update
Successfully updated the system facts.
+ exit 0
+ cleanup_and_exit
+ rm -f /tmp/tmp.yjFppwrBDJ
+ exit

whether successful or failed. 

If you see https://access.redhat.com/solutions/7083637 , then in the past, the error message would be raised by curl even if --silent was being used but that is not happening anymore. So maybe something at RHEL level has changed recently for curl and hence the issue. 

Additional Info:

There are two sets of effort being done via two redmines:

Bug #38569: Fix error handling for global registration while submitting built status - Foreman
https://projects.theforeman.org/issues/38569

Bug #38458: Host Registration - use --fail-with-body for curl - Foreman
https://projects.theforeman.org/issues/38458