Bug #3083
closed
Proxy registration happens before Apache is started
Added by Dominic Cleal over 10 years ago.
Updated over 10 years ago.
Description
There's a dependency issue in the installer modules - the proxy registration can happen before Apache's started.
[ERROR 2013-09-13 10:10:07 puppet] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[quickstart.fm.example.net]: Could not evaluate: Connection refused - connect(2)
[ WARN 2013-09-13 10:10:16 puppet] /Stage[main]/Apache::Service/Service[httpd]/ensure: ensure changed 'stopped' to 'running'
Full log file attached.
Tested with nightlies, foreman-installer-1.3.9999-3.201309112032git52e349a.el6.noarch
Files
- Priority changed from Normal to Immediate
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
- Related to Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final added
- Priority changed from Immediate to Normal
- Related to deleted (Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final)
- Target version changed from 1.3.0 to 1.4.0
This has become somewhat involved and affects a few modules, bumping to 1.4. As far as I can see, there's nothing 1.3-specific here, so it's always been a possibility and hasn't cropped up during more recent tests. Workaround is to run the installer twice.
- Target version deleted (
1.4.0)
- Status changed from Assigned to Rejected
#3972 will fix this properly.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by