Bug 695661

Summary: Image Import should be able to truncate space in front of ami's if any
Product: [Retired] CloudForms Cloud Engine Reporter: Shveta <ssachdev>
Component: aeolus-conductorAssignee: Jason Guiditta <jguiditt>
Status: CLOSED NOTABUG QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: cpelland, deltacloud-maint, morazi
Target Milestone: beta   
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-03 00:45:04 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
err none

Description Shveta 2011-04-12 10:54:18 UTC 
Created attachment 491456 [details]
err

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Image Imports 
2. If imported an image with space in front ( ami-d3025196 ) gives error 
3. bad URI(is not URI?): http://localhost:3003/api/images/ ami-d3025196
  
Actual results:


Expected results:


Additional info:
Comment 1 Shveta 2011-04-12 11:09:10 UTC 
 rpm -qa|grep aeolus
aeolus-conductor-0.0.3-0.fc14.20110401225256git6800ed8.x86_64
aeolus-configure-2.0.0-5.fc14.20110401173241git4d62feb.noarch
aeolus-conductor-debuginfo-0.0.3-0.fc14.20110401225256git6800ed8.x86_64
aeolus-conductor-doc-0.0.3-0.fc14.20110401225256git6800ed8.x86_64
aeolus-conductor-daemons-0.0.3-0.fc14.20110401225256git6800ed8.x86_64
Comment 2 Shveta 2011-04-18 11:11:58 UTC 
Same bug recreated in ami-18fa0671

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 3 Jason Guiditta 2011-09-19 20:21:34 UTC 
This is no longer in the UI, is it a valid issue still?  I would vote not.
Comment 4 wes hayutin 2011-09-28 16:40:51 UTC 
making sure all the bugs are at the right version for future queries
Comment 6 Jason Guiditta 2011-10-11 17:48:44 UTC 
please validate this is a current bug, as noted by my question in september, otherwise, I will request this be closed.  If is it still valid, please give a more detailed example of how to recreate with current release.  Thanks