Project

General

Profile

Actions

Bug #14060

closed

Error message unclear when capsule fails to register (Could not set 'present on ensure: 422 Unprocessable Entity)

Added by Stephen Benjamin over 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1039108
Description of problem:

If doing a node-install the satellite cannot connect to the node either because of firewall or networking issues, the node install will fail but will give no indication of why.

How reproducible:
always

Steps to Reproduce:
1. Install a satellite server
2. Attempt to install a node with the firewall still running

Actual results:

Node install fails with an unhelpful error:

/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[smart.proxy.example.com]/ensure: change from absent to 
present failed: Could not set 'present on ensure: 422 Unprocessable Entity at
/usr/share/node-installer/modules/foreman_proxy/manifests/register.pp:12

Expected results:
Should show some type of error that would help the user understand what is wrong

Additional info:

Errors seen in /var/log/foreman/production.log:

Unprocessable entity SmartProxy (id: new):
Unable to communicate with the proxy: No route to host - connect(2)
Please check the proxy is configured and running on the host.


Related issues 1 (0 open1 closed)

Related to Installer - Bug #10466: Proxy registration puppet error is not clearClosedLukas Zapletal05/11/2015Actions
Actions #1

Updated by Stephen Benjamin over 8 years ago

  • Project changed from Foreman to Installer
  • Subject changed from Error message unclear when capsule fails to register to Satellite (Could not set 'present on ensure: 422 Unprocessable Entity) to Error message unclear when capsule fails to register (Could not set 'present on ensure: 422 Unprocessable Entity)
  • Category set to Foreman modules
  • Assignee set to Stephen Benjamin
Actions #2

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #10466: Proxy registration puppet error is not clear added
Actions #3

Updated by Stephen Benjamin almost 8 years ago

  • Status changed from New to Closed

The new RESTv3 provider delivers the full_messages from the active record errors, so this isn't needed anymore.

Actions #4

Updated by Dominic Cleal almost 8 years ago

  • Status changed from Closed to Resolved

Fixed #14455 for 1.12.0.

Actions

Also available in: Atom PDF