Project

General

Profile

Actions
Copy link

Feature #1966

closed

Improve UI errors when smart proxy returns 400 bad request

Added by Dominic Cleal about 12 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Orchestration
Target version:
1.5.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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 3 (2 open — 1 closed)

Related to Foreman - Feature #4772: Display better error messages for DHCP errorsFeedback03/21/2014Actions
Related to Foreman - Feature #7916: Foreman WebUI should give clearer error message when foreman-proxy cannot be contactedNew10/13/2014Actions
Related to Foreman - Feature #11154: Print error message from Smart-Proxy in addition to the error codeNew07/20/2015Actions
Actions
Copy link
 #1

Updated by Lukas Zapletal about 11 years ago

  • Description updated (diff)
  • Status changed from New to Assigned
  • Assignee set to Lukas Zapletal
  • Target version set to 1.10.0
  • Translation missing: en.field_release set to 2
  • Difficulty set to easy

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

Actions
Copy link
 #2

Updated by Lukas Zapletal about 11 years ago

  • Status changed from Assigned to Ready For Testing
Actions
Copy link
 #3

Updated by Dominic Cleal almost 11 years ago

  • Target version changed from 1.10.0 to 1.9.3
Actions
Copy link
 #4

Updated by Anonymous almost 11 years ago

  • Target version changed from 1.9.3 to 1.9.2
Actions
Copy link
 #5

Updated by Dominic Cleal almost 11 years ago

  • Translation missing: en.field_release deleted (2)
Actions
Copy link
 #6

Updated by Anonymous almost 11 years ago

  • Target version changed from 1.9.2 to 1.9.1
Actions
Copy link
 #7

Updated by Anonymous almost 11 years ago

  • Target version changed from 1.9.1 to 1.9.0
Actions
Copy link
 #8

Updated by Dominic Cleal over 10 years ago

  • Related to Feature #4772: Display better error messages for DHCP errors added
Actions
Copy link
 #9

Updated by Anonymous over 10 years ago

  • Target version changed from 1.9.0 to 1.8.4
Actions
Copy link
 #10

Updated by Dominic Cleal over 10 years ago

  • Translation missing: en.field_release set to 4
  • Difficulty deleted (easy)
Actions
Copy link
 #11

Updated by Lukas Zapletal over 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #12

Updated by Dominic Cleal about 10 years ago

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

Updated by Dominic Cleal over 9 years ago

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

Also available in: Atom PDF