Provide clearer Smart Proxy registration errors with as much context as possible based on the error
Handle the following:
* Apache can be down * Connection refused or connection timeout * Foreman can be down * HTTP 502 or 503 * Foreman can throw an error * Does not always return a proper error message * Need to check/fix Foreman to return a proper JSON structured error message * Typically a 500 * Authorization error * Show a proper invalid credentials error * Instruct users where to look for error messages * Include in error message to look in production.log when appropriate
#7 Updated by Ewoud Kohl van Wijngaarden about 1 year ago
Perhaps we can also use the #28384 to provide better debug instructions. I've asked @ https://github.com/theforeman/foreman/pull/7220#issuecomment-665141626 if it does.
#11 Updated by William Clark 9 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman|d0bfd990b3e84d096e621987b39542369394fe5e.