Bug 706100

Summary: Conductor displays incorrect error message on image import
Product: [Retired] CloudForms Cloud Engine Reporter: Martyn Taylor <mtaylor>
Component: aeolus-conductorAssignee: Ian McLeod <imcleod>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 0.3.1CC: dajohnso, deltacloud-maint, ssachdev
Target Milestone: alpha   
Target Release: ---   
Hardware: All   
OS: All   
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:

Description Martyn Taylor 2011-05-19 13:44:20 UTC 
Description of problem:

When trying to import an image, for a provider that is not reachable an incorrect error message is shown:  

Could not import image: undefined method `image' for nil:NilClass

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


How reproducible:


Steps to Reproduce:
1.Add provider+account to conductor
2.Stop core server running
3.Run image import via UI
  
Actual results:
Could not import image: undefined method `image' for nil:NilClass

Expected results:
Error: Could not contact provider on: http://localhost:3001/api

Additional info:
Comment 1 wes hayutin 2011-06-15 12:12:58 UTC 
moving bugs to cloud engine project
Comment 2 wes hayutin 2011-06-16 18:50:36 UTC 
Could not import image: InvalidAMIID.Malformed: Invalid id: "ami-6a897e033"

[root@ibm-x3650-03 ~]# rpm -qa | grep aeolus
aeolus-conductor-devel-0.3.0-0.el6.20110616154040gited9b37c.noarch
aeolus-configure-2.0.1-0.el6.20110602110128git5cb9257.noarch
aeolus-conductor-0.3.0-0.el6.20110616154040gited9b37c.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110616154040gited9b37c.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110616154040gited9b37c.noarch
aeolus-all-0.3.0-0.el6.20110616154040gited9b37c.noarch


seems like a decent error to me.. not great.. but ok
Comment 3 wes hayutin 2011-08-01 20:02:37 UTC 
release pending...
Comment 4 wes hayutin 2011-08-01 20:02:54 UTC 
release pending 3
Comment 5 wes hayutin 2011-08-01 20:02:56 UTC 
release pending...
Comment 6 wes hayutin 2011-08-01 20:03:00 UTC 
release pending.. 2
Comment 8 wes hayutin 2011-12-08 14:02:40 UTC 
perm close
Comment 9 wes hayutin 2011-12-08 14:05:15 UTC 
closing out old bugs