Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1552578

Summary: Log details of error messages on external network provider errors
Product: [oVirt] ovirt-engine Reporter: Dominik Holler <dholler>
Component: BLL.NetworkAssignee: Dominik Holler <dholler>
Status: CLOSED CURRENTRELEASE QA Contact: Mor <mkalfon>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.1.7CC: bugs, lveyde, mkalfon
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:11:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dominik Holler 2018-03-07 11:32:56 UTC 
Description of problem: On many errors during communicating with external networks provider, webadmin shows "Failed to communicate with the external provider, see log for additional details.", but the log does not contain any additional details, just the generic "EngineException: (Failed with error PROVIDER_FAILURE and code 5050)". This is not helpful to identify the reason for the error.




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


How reproducible:
Use a wrong TCP port number in the authentication URL, or
add a network on an external network provider with a name which already exists on the provider, but not in the engine.

Steps to Reproduce:
1. Use a wrong TCP port number in the authentication URL for the external network provider
2. Click the "Test" button in the "Edit Provider" dialog. 
3.

Actual results:
engine.log contains only "EngineException: (Failed with error PROVIDER_FAILURE and code 5050)" without any additional information.

Expected results:
engine.log contains a log entry which contains "Connection refused"

(or an OpenStack response error code for the flow with adding a network on an external network provider with a name which already exists on the provider, but not in the engine)

Additional info:
Comment 1 Mor 2018-03-18 14:19:34 UTC 
Verified on: RHV 4.2.2.4-0.1.el7 with a scenario where ovirt-provider-ovn is down and not responding to requests.
Comment 2 Sandro Bonazzola 2018-03-29 11:11:40 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.