Thomas O'Dowd created CLOUDSTACK-3224: -----------------------------------------
Summary: Object_Store_Refactor - Cannot launch instances from templates uploaded to S3 object storage Key: CLOUDSTACK-3224 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3224 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Environment: chrome on linux devcloud Cloudian or Amazon S3 Object store Reporter: Thomas O'Dowd Priority: Critical Assuming initial devcloud state... I added a cache for the S3 storage like this. on devcloud machine as root: # mkdir /opt/storage/cache # vi /etc/exports (and append this line) /opt/storage/cache *(rw,no_subtree_check,no_root_squash,fsid=9999) # exportfs -a On Mgmt server gui: 1. navigate to infrastructure -> secondary storage 2. delete the NFS SS. 3. add S3 storage for Cloudian (I used 60000 as the timeouts - assuming millis). 4. nav to templates 5. register a new template (I uploaded tinyLinux again as "mytiny"). 6. confirm with s3cmd that 2 objects are now on S3. --------- s3 objects ------- template/tmpl/1/1/routing-1/acton-systemvm-02062012.vhd.bz2 2013-06-27T03:01:46.203Z None 140616708 "b533e7b65219439ee7fca0146ddd7ffa-27" template/tmpl/2/201/201-2-ae9e9409-4c8e-3ad8-a62f-abec7a35fe26/tinylinux.vhd 2013-06-27T03:04:06.730Z None 50430464 "4afac316e865adf74ca1a8039fae7399-10" --------- s3 objects ------- 7. I restarted the management server at this point which actually resulted in another object on S3. --------- the new s3 object ------- template/tmpl/1/5/tiny Linux/ttylinux_pv.vhd 2013-06-27T03:43:26.494Z None 50430464 "4afac316e865adf74ca1a8039fae7399-10" --------- the new s3 object ------- 8. Go to instance and create a new choosing the "mytiny" template which we registered. 9. launch it after selecting all defaults. 10. At this point it takes a while but fails with an error (see below). 11. Then try create a new instance using "tiny linux" which was actually added in step 7. 12. Launch it using all defaults. 13. It works! 14. try 8 and 9 again but same outcome. In step 12, if I sniff the S3 port, I can see the template being downloaded from S3. However in step 9, no S3 commands are received by the server. The terminal has a lot of exceptions and logs for step 9 and again in step 14. I'll see if I can attach the log entries separately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira