Project

General

Profile

Actions
Copy link

Feature #30284

closed

Provide clearer Smart Proxy registration errors with as much context as possible based on the error

Added by Eric Helms almost 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
William Clark
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/theforeman/puppet-foreman/pull/865, https://github.com/theforeman/puppet-foreman/pull/912
Fixed in Releases:
Foreman - 2.4.0
Found in Releases:
Red Hat JIRA:

Description

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

Related issues 1 (1 open — 0 closed)

Related to Foreman - Bug #30285: Smart proxy registration API does not always return a structured JSON error responseNewActions
Actions
Copy link

Also available in: Atom PDF