Red Hat Bugzilla – Bug 1563268
CloudForms appliance is ignoring azure proxy settings in advanced tab.
Last modified: 2018-09-17 10:12:38 EDT
New commit detected on ManageIQ/manageiq/gaprindashvili: https://github.com/ManageIQ/manageiq/commit/f368a10d5f63e6343b7e84e169c6c51dc1344c26 commit f368a10d5f63e6343b7e84e169c6c51dc1344c26 Author: Adam Grare <agrare@redhat.com> AuthorDate: Wed Mar 28 08:36:06 2018 -0400 Commit: Adam Grare <agrare@redhat.com> CommitDate: Wed Mar 28 08:36:06 2018 -0400 Merge pull request #17218 from slemrmartin/validate-new-provider-with-proxy Makes http_proxy_uri class method (cherry picked from commit 1c45ec38851f0b11a83641acb6d778ee30877a23) https://bugzilla.redhat.com/show_bug.cgi?id=1563267 https://bugzilla.redhat.com/show_bug.cgi?id=1563268 app/models/manageiq/providers/base_manager.rb | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)
New commit detected on ManageIQ/manageiq-ui-classic/gaprindashvili: https://github.com/ManageIQ/manageiq-ui-classic/commit/24b2f2be8f0b94b88fff9a10ecad00742b52b8ce commit 24b2f2be8f0b94b88fff9a10ecad00742b52b8ce Author: Harpreet Kataria <hkataria@redhat.com> AuthorDate: Mon Apr 2 11:00:56 2018 -0400 Commit: Harpreet Kataria <hkataria@redhat.com> CommitDate: Mon Apr 2 11:00:56 2018 -0400 Merge pull request #3693 from slemrmartin/validate-new-provider-with-proxy Validation of new provider with http_proxy settings (cherry picked from commit a0ff186c3fef26bd5e8ea6d141fe5406e8e0d78d) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1563267 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1563268 app/controllers/mixins/ems_common_angular.rb | 6 +- 1 file changed, 3 insertions(+), 3 deletions(-)
Verified on 5.9.2.4.20180501195858_35dc609 Set up mitmproxy, ensured CFME->azure traffic is being routed through the proxy for these configurations: 1) azure proxy defined, no default proxy defined 2) azure proxy defined, default proxy defined w/ a bogus IP 3) no azure proxy defined, only default proxy defined Works for all 3 cases.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1328