Bug 1017538 - [TEXT] Tell user to let engine know where keystone auth endpoint lives
[TEXT] Tell user to let engine know where keystone auth endpoint lives
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal (Show other bugs)
Unspecified Unspecified
high Severity medium
: ---
: 3.5.0
Assigned To: Lior Vernia
Depends On:
Blocks: rhev3.5beta 1156165
  Show dependency treegraph
Reported: 2013-10-10 02:46 EDT by Tim Hildred
Modified: 2016-02-10 14:47 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: While configuring an external provider in RHEV, a non-trivial process, it is possible for users to skip the step where the Keystone authentication server URL is configured via the engine-config utility. Consequence: If the Keystone server URL is not configured, and the external provider requires authentication, then nearly all operations involving the provider will subsequently fail. Fix: When a user tests connectivity via the "Test" button in the Add/Edit Provider dialog, while the provider is marked to require authentication, a fair warning will be displayed in case no Keystone server URL is found to be configured. Result: It is relatively easy for users to figure out that connectivity to a provider is failing due to a missing Keystone server URL.
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 12:11:51 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 25720 master MERGED webadmin: Warn user if KeystoneAuthUrl wasn't configured Never
oVirt gerrit 27517 ovirt-engine-3.4 ABANDONED webadmin: Warn user if KeystoneAuthUrl wasn't configured Never

  None (edit)
Description Tim Hildred 2013-10-10 02:46:19 EDT
Description of problem:
When adding external providers, it isn't clear that before you can do that, you have to use the rhevm-config / engine-config tool to let engine know where the keystone auth endpoint is. 

This came up in a thread on the ovirt[1] users mailing list, and Itamar suggested[2] this bug be raised. 

Maybe when you hit the "Test" button, instead of just saying "Failed to communicate with service provider"

the engine could say:
"Failed to communicate with service provider. Have you used the configuration utility to set the KeystoneAuthUrl value?"

Comment 1 Lior Vernia 2013-10-15 03:40:40 EDT
In the current tech preview form of the Neutron integration feature, this is not feasible; there's no way of knowing what went wrong with the connection to the provider. I don't think this should be part of 3.3.
Comment 3 Nir Yechiel 2014-02-19 07:47:44 EST
Verify that a url was entered for keystone and if not, report it in the UI. This is a limited solution and the issue will be fully addressed in 3.5.
Comment 5 Meni Yakove 2014-07-17 08:34:23 EDT
Comment 7 Eyal Edri 2015-02-17 12:11:51 EST
rhev 3.5.0 was released. closing.

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