Bug 1623550

Summary: Invalid proxy doesn't cause any error in log while refreshing a provider.
Product: Red Hat CloudForms Management Engine Reporter: Jaroslav Henner <jhenner>
Component: ProvidersAssignee: Loic Avenel <lavenel>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: high    
Version: 5.10.0CC: dmetzger, gblomqui, jfrey, jhardy, mfeifer, obarenbo
Target Milestone: GA   
Target Release: 5.10.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-18 11:28:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: GCE Target Upstream Version:
Embargoed:
Attachments:
Description Flags
evm.tail.log none

Description Jaroslav Henner 2018-08-29 15:21:56 UTC
Created attachment 1479521 [details]
evm.tail.log

Description of problem:
When proxy is set to invalid IP, no error appears in the evm.log so it looks like some fall-back was used to connect to the provider, or setting the new proxy values is ignored.

Proxy settings:
  :default:
    :host: 192.0.2.1
    :password: 
    :port: '1234'
    :user: 
    :scheme: 
  :gce:
    :host: 192.0.2.1
    :password: 
    :port: '1234'
    :user: 
    :scheme: 
 

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

How reproducible:
3/3

Steps to Reproduce:
1. Add a GCE provider
2. set proxy to invalid values
3.

Actual results:
Provider refresh works

Expected results:
Fail to refresh the provider because of the invalid proxy settings

Additional info:

Comment 3 Jaroslav Henner 2018-12-18 11:28:57 UTC

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