You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Pavan Kumar Bandarupally (JIRA)" <ji...@apache.org> on 2014/05/23 11:30:02 UTC

[jira] [Updated] (CLOUDSTACK-6754) SSVM not responding with S3 secondary sotre

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavan Kumar Bandarupally updated CLOUDSTACK-6754:
-------------------------------------------------

    Attachment: cloudoutfile.zip
                management-server.log
                cloud.log

cloud.out file is in the zipped folder

> SSVM not responding with S3 secondary sotre
> -------------------------------------------
>
>                 Key: CLOUDSTACK-6754
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6754
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller, SystemVM, Template
>    Affects Versions: 4.4.0
>         Environment: Host: Xenserver
> Secondary Store: Image store with S3 as provider
>            Reporter: Pavan Kumar Bandarupally
>            Priority: Blocker
>             Fix For: 4.4.0
>
>         Attachments: cloud.log, cloudoutfile.zip, management-server.log
>
>
> A new zone is created and systemVMs are up. The systemvm template is downloaded to S3 bucket. Once the SSVMs are up, the default BUILTIN centos template or any other template that we try to register manually are not getting downloaded to SSVM. There is no exception generated as well. 
> The registerTemplate API call is just listed in the MS traces and no further action happens. Attaching the MS logs and SSVM log. There is no trace of any exception in SSVM log as well. Attaching the /var/log/cloud/cloud.out , which is the only file that has some exception listed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)