Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1039108 - Error message unclear when capsule fails to register to Satellite (Could not set 'present on ensure: 422 Unprocessable Entity)
Summary: Error message unclear when capsule fails to register to Satellite (Could not ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-06 16:35 UTC by Justin Sherrill
Modified: 2019-09-26 13:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 20:02:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14060 0 Normal Resolved Error message unclear when capsule fails to register (Could not set 'present on ensure: 422 Unprocessable Entity) 2021-01-06 02:19:43 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.