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

Bug 1051577

Summary: Provider failure errors are not specific enough.
Product: Red Hat Enterprise Virtualization Manager Reporter: Stephen Gordon <sgordon>
Component: ovirt-engineAssignee: Ravi Nori <rnori>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 3.3.0CC: abaron, acathrow, bazulay, gklein, iheim, lpeer, mkolesni, pstehlik, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-27 05:00:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stephen Gordon 2014-01-10 15:45:51 UTC 
Description of problem:

When adding a provider and it fails "PROVIDER FAILURE and code 5050" is returned in the logs:

2014-01-10 10:24:23,154 ERROR [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] (ajp-/127.0.0.1:8702-15) [55b6f83d] Command org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand throw Vdc Bll exception. With error message VdcBLLException: (Failed with error PROVIDER_FAILURE and code 5050)
2014-01-10 10:24:23,156 ERROR [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] (ajp-/127.0.0.1:8702-15) [55b6f83d] Transaction rolled-back for command: org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand

It seems like this can be for a number of reasons (firewall issues, keystone url not set or doesn't contain API value, keystone user/tenant/pass incorrect). 

I think we need to make the effort to break these down and return a more accurate error instead of this catch all. Setting this functionality up is kind of tricky as is (in part because of documentation issues I have already filed) without non-specific error reporting.
Comment 1 Mike Kolesnik 2014-02-27 05:00:42 UTC 

*** This bug has been marked as a duplicate of bug 1048777 ***
Comment 2 Mike Kolesnik 2014-02-27 05:15:09 UTC 
There is no feasible way to fix a "all providers" bug as each provider type provides different resources and so has entirely different error codes (Foreman is not even an OpenStack provider), so a bug for each provider type has to exist.