https://github.com/ManageIQ/manageiq/pull/13459
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/9763bc3d0d5b59f5f2165f4f41c89c6e3393ca76 commit 9763bc3d0d5b59f5f2165f4f41c89c6e3393ca76 Author: Adam Grare <agrare> AuthorDate: Thu Jan 12 16:39:34 2017 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Mon Jan 16 14:32:51 2017 -0500 Merge pull request #13459 from selmanj/pass_proxy_uri_to_fog-google Pass through google proxy options to fog-google (cherry picked from commit 9a90292339eea01d438b1d40d603c3c81ddff792) https://bugzilla.redhat.com/show_bug.cgi?id=1412825 Gemfile | 2 +- app/models/manageiq/providers/google/manager_mixin.rb | 6 ++++-- config/settings.yml | 5 +++++ .../manageiq/providers/google/cloud_manager_spec.rb | 16 ++++++++++++++++ 4 files changed, 26 insertions(+), 3 deletions(-)
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/863512627fe807ddfa9ca54b5735e1695d3e6394 commit 863512627fe807ddfa9ca54b5735e1695d3e6394 Author: Oleg Barenboim <chessbyte> AuthorDate: Mon Jan 16 11:44:49 2017 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Mon Jan 16 14:37:30 2017 -0500 Merge pull request #13486 from agrare/bump_fog_google_gem_version Increase fog-google version to v0.5.2 (cherry picked from commit 9ae9ff92c9fcffde75ef94108453cb872e0ad9b8) https://bugzilla.redhat.com/show_bug.cgi?id=1412825 Gemfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Hi, could you give us an update please?
It's in the UI on upstream builds and appears to be working. Won't be able to officially close it until we get a proper 5.7.1 build.
The UI is implemented, but it seem to be using the proxy values. I know it is working because if I change to bogus values it stops working. And when I correct the values it starts working again. Moving to Verified using 57100 on 10.16.7.73 I also add the positive/negative test cases to Polarion and marked qetestcoverage to +
Hi, do you know when this BZ/RFE will be release for CF?
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://rhn.redhat.com/errata/RHSA-2017-0320.html