Upgrade issues for 1.20.0-RC1

paulcalabro · October 26, 2018, 9:01am

Problem:

I can’t execute Ansible roles after the upgrade

Expected outcome:

Selecting “Run Ansible Roles” executes job to apply Ansible roles successfully

Foreman and Proxy versions:

1.20.0-RC1

Foreman and Proxy plugin versions:

foreman-tasks: 0.14.1
foreman_ansible: 2.2.9
foreman_hooks: 0.3.14
foreman_memcache: 0.1.1
foreman_remote_execution: 1.6.4

Other relevant data:

Debug log info:

gist.github.com

https://gist.github.com/paulcalabro/aa169624d663df2ba27f206d5f79f62a

Debug log

Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: 2018-10-26 08:54:04 - Errno::ECONNREFUSED - Connection refused - connect(2):
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/ruby/net/http.rb:878:in `initialize'
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/ruby/net/http.rb:878:in `open'
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/ruby/net/http.rb:878:in `block in connect'
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/ruby/timeout.rb:52:in `timeout'
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/ruby/net/http.rb:877:in `connect'
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/ruby/net/http.rb:862:in `do_start'
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/ruby/net/http.rb:851:in `start'
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/ruby/net/http.rb:1373:in `request'
Oct 26 08:54:04 ip-10-242-30-7 smart-proxy: /usr/share/foreman-proxy/lib/proxy/request.rb:46:in `send_request'

This file has been truncated. show original

ekohl · October 26, 2018, 9:11am

I’m guessing this is on CentOS 7 from the file paths, but could you confirm this?

paulcalabro · October 26, 2018, 9:14am

That’s correct. It’s CentOS Linux release 7.5.1804 (Core).

paulcalabro · October 26, 2018, 9:17am

The error message I’m seeing in the web UI is:

Failed to initialize: RuntimeError - The only applicable proxy localhost is down

I tried starting foreman-proxy and smart_proxy_dynflow_core, but that didn’t seem to work.

paulcalabro · October 26, 2018, 9:29am

Cool, I resolved the issue by running foreman-installer again. Is there any info. I can provide to you guys to help identity the source of the issue?

ekohl · October 29, 2018, 12:02pm

Did you run the installer after the first upgrade or was that only a yum update? Also wondering if you have the installer log to see what changed to fixed it.

paulcalabro · October 29, 2018, 7:21pm

Hmmm… I might have missed Step 3 C.
Is there a way to redact hostnames with foreman-debug?