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

Bug 641948

Summary:

[UI]: No error information is presented to the user on a failed "Provider Account"

Product:

[Retired] CloudForms Cloud Engine

Reporter:

Chris Lalancette <clalance>

Component:

aeolus-conductor

Assignee:

Dave Johnson <dajohnso>

Status:

CLOSED CURRENTRELEASE

QA Contact:

wes hayutin <whayutin>

Severity:

medium

Docs Contact:

Priority:

low

Version:

0.3.1

CC:

cpelland, dajohnso, deltacloud-maint, mtaylor

Target Milestone:

alpha

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Bug Depends On:

Bug Blocks:

651514

Attachments:

Description	Flags
good to go	none

Description Chris Lalancette 2010-10-11 15:27:36 UTC

Description of problem:
If you try to enter in the data for a provider account and it doesn't work, there is no information presented as to why it failed.  The only error message is:

The entered credential information is incorrect

Which doesn't give the user much information to work off of to try and correct the problem.  We should expose more detailed error information to the user so that they have a fighting chance of rectifying the error.

Comment 1 Martyn Taylor 2010-11-18 12:29:28 UTC

This may not be feasible, as it depends on whether the particular provider returns the needed information in their response to the failed connection attempt.  Even if each Provider did return this information, we would then need to add support for this to Core and the Client.

It would even be difficult to add something simple like checking fields are not blank or format etc... since different providers expect different credentials.

Comment 2 Dave Johnson 2011-01-26 17:32:47 UTC

this looks good now, moving to ON_QA for verification against official build

Comment 3 Dave Johnson 2011-04-18 14:08:04 UTC

Created attachment 492903 [details]
good to go

This looks good to go in the 2011-04-15 AMI (ami-18fa0671)

[root@ip-10-118-26-86 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.0.3-6.el6.x86_64
aeolus-conductor-0.0.3-6.el6.x86_64
aeolus-conductor-daemons-0.0.3-6.el6.x86_64
aeolus-configure-2.0.0-8.el6.noarch

Comment 4 wes hayutin 2011-08-01 19:53:01 UTC

release pending...

Comment 5 wes hayutin 2011-08-01 19:55:25 UTC

release pending...

Comment 7 wes hayutin 2011-12-08 13:50:49 UTC

closing out old bugs

Comment 8 wes hayutin 2011-12-08 14:03:26 UTC

perm close