Bug 1498661

Summary:	Cannot remove proxy setting from the advanced tab
Product:	Red Hat CloudForms Management Engine	Reporter:	Saif Ali <saali>
Component:	UI - OPS	Assignee:	Dan Clarizio <dclarizi>
Status:	CLOSED DUPLICATE	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.8.0	CC:	hkataria, jfrey, jhardy, mpovolny, obarenbo
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-05 15:10:08 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:

Description Saif Ali 2017-10-04 21:31:39 UTC

Description of problem:
In CloudForms 4.5 we can add proxy setting per provider which is great but once you added the proxy you cannot removed or updated from the UI, The only way currently to remove or update the setting is to update the database table directly. 

Version-Release number of selected component (if applicable):
5.8.1.5

How reproducible:


Steps to Reproduce:
1. Navigate to the advanced tab under settings >> zones >> Select the appliance >> Advanced tab
2. under http_proxy:
   add proxy for ec2 and save.
3. everything should be good at this point.
4. try to update the proxy setting or remove the setting and save 


Actual results:
nothing has been change

Expected results:
to see the new setting.

Additional info:

Comment 3 Jason Frey 2017-10-05 15:02:34 UTC

Another workaround is to just set the value to an empty string in Advanced Settings

Comment 4 Jason Frey 2017-10-05 15:07:12 UTC

Sorry, I didn't mean empty string, I meant an empty value (aka nil)...you can do it as follows (that is, leave the key, but put nothing after it for a value.


:http_proxy:
  :ec2:
    :host:
    :port:
    :user:
    :password:

Comment 5 Jason Frey 2017-10-05 15:10:08 UTC


*** This bug has been marked as a duplicate of bug 1358433 ***