Bug 800292 - Should display appropriate error message when user tried to import an image with empty fields
Summary: Should display appropriate error message when user tried to import an image w...
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-06 08:54 UTC by Rehana
Modified: 2020-03-27 18:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
import (200.01 KB, image/png)
2012-03-06 08:54 UTC, Rehana
no flags Details
Error (206.41 KB, image/png)
2012-03-06 08:55 UTC, Rehana
no flags Details

Description Rehana 2012-03-06 08:54:53 UTC
Created attachment 567870 [details]
import

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Login to conductor
2.Go to Cloud
3.click on "import Comp. outline" button
4. Select a provider account
5.leave other fields blank (PFA: import.png)
6.click continue
  
Actual results:
The user is allowed to continue with out entering the  "Component Outline ID" and a wrong error message gets displayed "The record you tried to access does not exist, it may have been deleted"(PFA:Error.png)


Expected results:
The user should not be allowed to continue with out  entering the details in the fields, "Component Outline ID"  and "Component Outline Name"

Additional info:

[root@ibm-ls22-03 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.8.0-39.el6.noarch
aeolus-configure-2.5.0-16.el6.noarch
rubygem-aeolus-cli-0.3.0-12.el6.noarch
aeolus-all-0.8.0-39.el6.noarch
rubygem-aeolus-image-0.3.0-11.el6.noarch
aeolus-conductor-0.8.0-39.el6.noarch
aeolus-conductor-daemons-0.8.0-39.el6.noarch

Comment 1 Rehana 2012-03-06 08:55:43 UTC
Created attachment 567871 [details]
Error


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