Hide Forgot
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.
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.
Node install isn't a thing anymore.
Created redmine issue http://projects.theforeman.org/issues/14060 from this bug
Upstream bug assigned to stbenjam
Upstream bug component is Uncategorized
Upstream bug component is Installer
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."
The fix to this bug will be delivered with release 6.3 of Satellite.