Hello!
I'm using discovery image
"discovery_version": "3.0.5",
"discovery_release": "20151113.1",
I can't reboot the server with discovery image on it through Foreman web UI
(via autoprovision)
foreman says
> ProxyAPI::ProxyException: ERF12-1772 [ProxyAPI::ProxyException]: Unable
to perform power BMC operation ([Errno::ECONNREFUSED]: Connection refused -
connect(2)) for proxy http://10.68.21.78:8448/bmc
I've enabled ssh on the discovery image
when I ssh into it and check smart-proxy status
[root@fdi ~]# systemctl status foreman-proxy
foreman-proxy.service - Foreman Proxy
Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled)
Active: failed (Result: exit-code) since Tue 2016-05-17 14:40:19 UTC;
10min ago
Process: 1473 ExecStartPre=/usr/bin/generate-proxy-cert (code=exited,
status=1/FAILURE)
May 17 14:40:19 fdi generate-proxy-cert[1473]: Generating a 2048 bit RSA
private key
May 17 14:40:19 fdi generate-proxy-cert[1473]:
…+++
May 17 14:40:19 fdi generate-proxy-cert[1473]:
…+++
May 17 14:40:19 fdi generate-proxy-cert[1473]: writing new private key to
'/etc/foreman-proxy/key.pem'
May 17 14:40:19 fdi generate-proxy-cert[1473]: -----
May 17 14:40:19 fdi generate-proxy-cert[1473]: end of string encountered
while processing type of subject name element #0
May 17 14:40:19 fdi generate-proxy-cert[1473]: problems making Certificate
Request
May 17 14:40:19 fdi systemd[1]: foreman-proxy.service: control process
exited, code=exited status=1
May 17 14:40:19 fdi systemd[1]: Failed to start Foreman Proxy.
May 17 14:40:19 fdi systemd[1]: Unit foreman-proxy.service entered failed
state.
in /usr/bin/generate-proxy-cert I see
IP=$(nmcli -t -f IP4.ADDRESS con show primary 2>/dev/null | cut -f2 -d: |
cut -f1 -d/)
but the problem is that my network cards are kinda slow
and this generate-proxy-cer gets executed BEFORE my nic gets its IP via DHCP
How can I work around this problem?
discovery-debug is in http://pastebin.com/mVgPww0n