Bug 755930

Summary: Test connection succeeds even if account number is invalid.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Imre Farkas <ifarkas>
Status: CLOSED WONTFIX QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, athomas, dajohnso, deltacloud-maint, dgao, ifarkas, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-29 11:58:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
test connection none

Description Aziza Karol 2011-11-22 12:46:54 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.configure ec2.
2.Add a provider account for ex:ec2-ap-southeast-1 with invalid account number and rest all credentials as valid.
3.Provider account get added.
4. click on test connection.


Test connection succeeds even if account number is invalid.
see attached screenshot.  

Account number should be validated.


Additional info:
[root@hp-bl490cg6-01 ~]# rpm -qa | grep aeolus
rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch
aeolus-conductor-doc-0.7.0-0.20111118205914git4c5036a.el6.noarch
rubygem-aeolus-cli-0.1.0-4.el6.noarch
rubygem-arel-2.0.10-0.aeolus.el6.noarch
rubygem-aeolus-image-0.1.0-6.el6.noarch
aeolus-configure-2.4.0-0.20111118150133gitde3c009.el6.noarch
aeolus-all-0.7.0-0.20111118205914git4c5036a.el6.noarch
aeolus-conductor-0.7.0-0.20111118205914git4c5036a.el6.noarch
rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch
aeolus-conductor-daemons-0.7.0-0.20111118205914git4c5036a.el6.noarch
Comment 1 Aziza Karol 2011-11-22 12:48:10 UTC 
Created attachment 535010 [details]
test connection
Comment 2 Aziza Karol 2011-11-22 12:52:35 UTC 
I just happened to push for this invalid account number.

imagefactory log displayed:
46e1-8481-e630b0350a09)
2011-11-22 07:10:23,963 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7372) Message: Exception caught in ImageFactory
2011-11-22 07:10:23,964 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7372) Message: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_ec2_Builder.py", line 443, in push_image
    credentials)
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_ec2_Builder.py", line 687, in push_image_snapshot_ec2
    ' '.join(command))
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_ec2_Builder.py", line 72, in guest_execute_command
    return super(FedoraRemoteGuest, self).guest_execute_command(guestaddr, command, timeout, tunnels)
  File "/usr/lib/python2.6/site-packages/oz/RedHat.py", line 476, in guest_execute_command
    command, timeout, tunnels)
  File "/usr/lib/python2.6/site-packages/oz/ozutil.py", line 355, in ssh_execute_command
    return subprocess_check_output(cmd)
  File "/usr/lib/python2.6/site-packages/oz/ozutil.py", line 323, in subprocess_check_output
    raise SubprocessException("'%s' failed(%d): %s" % (cmd, retcode, stderr), retcode)
SubprocessException: 'ssh -i /tmp/tmpT47yj4 -F /dev/null -o ServerAliveInterval=30 -o StrictHostKeyChecking=no -o ConnectTimeout=30 -o UserKnownHostsFile=/dev/null -o PasswordAuthentication=no root.amazonaws.com euca-register -U http://ec2.ap-southeast-1.amazonaws.com/ -A AKIAJRCPNVJYQBHCOBEA -S KQaCCub8PfyshHi7SvNOupRSbozSduObirlMUpvo imagefactory-ec2-ap-southeast-1-9/4eae5bf3-1da9-46e1-8481-e630b0350a09.manifest.xml' failed(1): Warning: Permanently added 'ec2-50-19-192-70.compute-1.amazonaws.com,50.19.192.70' (RSA) to the list of known hosts.^M

2011-11-22 07:10:23,965 DEBUG imgfac.BuildJob.BuildJob pid(7372) Message: Builder (4eae5bf3-1da9-46e1-8481-e630b0350a09) changed status from PUSHING to FAILED



Imagefactory log should also display an error message for an invalid account number.
Comment 3 Imre Farkas 2011-11-29 11:58:26 UTC 
Deltacloud is not capable of validating the account number.