Bug 1623550 - Invalid proxy doesn't cause any error in log while refreshing a provider.
Summary: Invalid proxy doesn't cause any error in log while refreshing a provider.
Keywords:
Status: CLOSED DUPLICATE of bug 1623862
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.10.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: GA
: 5.10.0
Assignee: Loic Avenel
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-29 15:21 UTC by Jaroslav Henner
Modified: 2018-12-18 15:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-18 11:28:57 UTC
Category: ---
Cloudforms Team: GCE
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
evm.tail.log (100.94 KB, application/x-xz)
2018-08-29 15:21 UTC, Jaroslav Henner
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.