Bug 1309477

Summary:	[RFE] add proxy support to azure-armrest
Product:	Red Hat CloudForms Management Engine	Reporter:	Colin Arnott <carnott>
Component:	Providers	Assignee:	Daniel Berger <dberger>
Status:	CLOSED ERRATA	QA Contact:	Jeff Teehan <jteehan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.5.0	CC:	bascar, benglish, cpelland, jfrey, jhardy, jprause, jteehan, mfeifer, obarenbo, ptavares
Target Milestone:	GA	Keywords:	FutureFeature, ZStream
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	azure:proxy
Fixed In Version:	5.6.0.0	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1314835 (view as bug list)		Environment:
Last Closed:	2016-06-29 15:38:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1314835

Description Colin Arnott 2016-02-17 22:41:15 UTC

Description of problem:
At the moment there's no way to specify a proxy for http requests in the azure-armrest gem.

Version-Release number of selected component (if applicable):
cfme-5.5.2.4-1.el7cf.x86_64

Additional info:
This RFE is mirrored on the upstream manageiq github site:
https://github.com/ManageIQ/azure-armrest/issues/125

Comment 2 Greg Blomquist 2016-02-18 15:08:56 UTC

Looks like an update to the armrest gem is in order.

Comment 4 Daniel Berger 2016-02-26 16:43:55 UTC

This was added by https://github.com/ManageIQ/azure-armrest/pull/126 and https://github.com/ManageIQ/azure-armrest/pull/128.

It was pushed out as part of release 0.1.1 of the azure-armrest gem.

Now we just need to bump the Gemfile in MIQ to use it.

Comment 5 Colin Arnott 2016-02-26 17:15:44 UTC

This support is for http proxies only, not socks proxies?

Comment 8 Daniel Berger 2016-03-03 11:55:54 UTC

Colin, the underlying rest-client library should support a socks proxy as well.

Comment 10 Daniel Berger 2016-03-11 18:56:45 UTC

This was added in 0.1.1, and ssl configuration support was added in 0.2.0.

Comment 11 Jeff Teehan 2016-04-20 19:31:24 UTC

I configured the http_proxy server fields with the info from our QE proxy server and refreshed all cloud providers.  Worked as expected.  Moving to verified using 5.6.0.1 Beta 2 on https://10.16.7.174/ems_cloud/415000000000002

Comment 13 errata-xmlrpc 2016-06-29 15:38:17 UTC

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/RHBA-2016:1348