Bug 1039108

Summary:	Error message unclear when capsule fails to register to Satellite (Could not set 'present on ensure: 422 Unprocessable Entity)
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	Installer	Assignee:	Stephen Benjamin <stbenjam>
Status:	CLOSED NEXTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.2	CC:	bbuckingham, bkearney, mmccune, stbenjam
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14060
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 20:02:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Justin Sherrill 2013-12-06 16:35:51 UTC

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.

Comment 2 Mike McCune 2014-07-30 17:04:34 UTC

This is still an issue in Sat6 Beta.  if the Satellite can't talk back to the Proxy during the self-registration you get this error.

Ideally we would indicate this in a clearer error message.

Comment 3 Stephen Benjamin 2016-03-04 19:45:11 UTC

Node install isn't a thing anymore.

Comment 4 Stephen Benjamin 2016-03-04 19:55:24 UTC

Created redmine issue http://projects.theforeman.org/issues/14060 from this bug

Comment 5 Bryan Kearney 2016-03-04 21:04:32 UTC

Upstream bug assigned to stbenjam

Comment 6 Bryan Kearney 2016-08-10 18:14:37 UTC

Upstream bug component is Uncategorized

Comment 7 Bryan Kearney 2016-08-10 18:59:43 UTC

Upstream bug component is Installer

Comment 8 Stephen Benjamin 2016-10-17 19:51:25 UTC

This should be in 6.3 already - the new RESTv3 provider automatically shows a detailed error message.

So you end up with an error message like:


"Unable to communicate with the Capsule: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([SocketError]: getaddrinfo: Name or service not known) for Capsule https://asdf.example.com:9191/features. Please check the Capsule is configured and running on the host."

Comment 9 Bryan Kearney 2017-08-01 20:02:26 UTC

The fix to this bug will be delivered with release 6.3 of Satellite.