Bug #16028
closed
Upgrades fail if a proxy is set on the system
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1365542
Description of problem:
We're seeing 6.2 systems where tomcat fails to start if $https_proxy is set.
Version-Release number of selected component (if applicable):
6.2.0
How reproducible:
100%
Steps to Reproduce:
1. On a 6.1 system, set $https_proxy
2. Perform upgrade
Actual results:
Installer fails with:
[ INFO 2016-08-03 23:18:08 main] Upgrade Step: start_tomcat...
[ERROR 2016-08-03 23:20:10 main] Redirecting to /bin/systemctl start tomcat.service
Some services failed to start: tomcat
Expected results:
Upgrade ignores proxy and succeeds.
Additional info:
I found this commit:
https://github.com/Katello/puppet-service_wait/commit/c641a1112aea1e4ffd01a5d39aff0f4c5d32fb4f
Looks like we need to make the same change here:
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello-packaging/pull/267 added
Updated by Anonymous over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello-packaging|19b8979311a57f6131db472238f3aeb04ff47e63.
Updated by Justin Sherrill over 7 years ago
- translation missing: en.field_release set to 143
- Difficulty set to easy