Project

General

Profile

Feature #1966

Improve UI errors when smart proxy returns 400 bad request

Added by Dominic Cleal over 6 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Category:
Orchestration
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

The smart proxy can return 400 bad request HTTP responses for a large number of configuration problems, which are all logged in the smart proxy's proxy.log file. The Foreman UI though only reports the 400 bad request error, but doesn't indicate that this originated from a call to a smart proxy, or which proxy it was.

The UI should be improved to indicate the origin of the HTTP error and preferably a hint to look in the proxy's log files. If possible (and if it doesn't expose confidential data) then the proxy could return a more meaningful error in the body of the HTTP error to be displayed.


Related issues

Related to Foreman - Feature #4772: Display better error messages for DHCP errorsFeedback2014-03-21
Related to Foreman - Feature #7916: Foreman WebUI should give clearer error message when foreman-proxy cannot be contactedNew2014-10-13
Related to Foreman - Feature #11154: Print error message from Smart-Proxy in addition to the error codeNew2015-07-20

Associated revisions

Revision c83e29ac (diff)
Added by Lukas Zapletal about 5 years ago

fixes #1966 - improved UI errors for proxy

History

#1 Updated by Lukas Zapletal over 5 years ago

  • Description updated (diff)
  • Status changed from New to Assigned
  • Assignee set to Lukas Zapletal
  • Target version set to 1.10.0
  • Legacy Backlogs Release (now unused) set to 2
  • Difficulty set to easy

Oh, I have a fix already locally, forgot to push it! Lemme just teardown that patch.

#2 Updated by Lukas Zapletal over 5 years ago

  • Status changed from Assigned to Ready For Testing

#3 Updated by Dominic Cleal over 5 years ago

  • Target version changed from 1.10.0 to 1.9.3

#4 Updated by Dmitri Dolguikh over 5 years ago

  • Target version changed from 1.9.3 to 1.9.2

#5 Updated by Dominic Cleal about 5 years ago

  • Legacy Backlogs Release (now unused) deleted (2)

#6 Updated by Dmitri Dolguikh about 5 years ago

  • Target version changed from 1.9.2 to 1.9.1

#7 Updated by Dmitri Dolguikh about 5 years ago

  • Target version changed from 1.9.1 to 1.9.0

#8 Updated by Dominic Cleal about 5 years ago

  • Related to Feature #4772: Display better error messages for DHCP errors added

#9 Updated by Dmitri Dolguikh about 5 years ago

  • Target version changed from 1.9.0 to 1.8.4

#10 Updated by Dominic Cleal about 5 years ago

  • Legacy Backlogs Release (now unused) set to 4
  • Difficulty deleted (easy)

#11 Updated by Lukas Zapletal about 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#12 Updated by Dominic Cleal over 4 years ago

  • Related to Feature #7916: Foreman WebUI should give clearer error message when foreman-proxy cannot be contacted added

#13 Updated by Dominic Cleal over 3 years ago

  • Related to Feature #11154: Print error message from Smart-Proxy in addition to the error code added

Also available in: Atom PDF