cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjeev N (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4395) [Object_store_refactor] Default template is not available for use to deploy vm in case of multi zone environment
Date Mon, 19 Aug 2013 09:29:50 GMT

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

Sanjeev N updated CLOUDSTACK-4395:
----------------------------------

    Attachment: cloud.dmp
                management-server.rar
    
> [Object_store_refactor] Default template is not available for use to deploy vm in case
of multi zone environment
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4395
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4395
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Storage Controller, Template
>    Affects Versions: 4.2.0
>         Environment: Latest build from ACS 4.2
> Multi-zone environment
>            Reporter: Sanjeev N
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: cloud.dmp, management-server.rar
>
>
> Default template is not available for use to deploy vm in case of multi zone environment
> Steps to Reproduce:
> ================
> 1.Bring up CS initially with one zone say zone1 using xen cluster
> 2.Wait for the system vms to come up and let the default xen cent os template to download
> 3.Add second zone say zone2 using vmware cluster
> At this state SSVM in zone1 will initiate the centos system template and default template
download process.
> 4.After SSVM is up in zone2 try to deploy guest vm in zone2 using default centos template

> Result:
> =======
> VM deployment failed with error "The template 7 is not available for use"
> Observations:
> ===========
> Entries in template_zone_ref table are as follows:
> mysql> select * from template_zone_ref where template_id<9;
> +----+---------+-------------+---------------------+---------------------+---------+
> | id | zone_id | template_id | created             | last_updated        | removed |
> +----+---------+-------------+---------------------+---------------------+---------+
> |  1 |       1 |           1 | 2013-08-16 11:31:50 | 2013-08-16 11:31:50 | NULL    |
> |  2 |       1 |           2 | 2013-08-16 11:31:50 | 2013-08-16 11:31:50 | NULL    |
> |  3 |       1 |           3 | 2013-08-16 11:31:50 | 2013-08-16 11:31:50 | NULL    |
> |  4 |       1 |           4 | 2013-08-16 11:31:50 | 2013-08-16 11:31:50 | NULL    |
> |  5 |       1 |           5 | 2013-08-16 11:31:50 | 2013-08-16 12:00:18 | NULL    |
> |  6 |       1 |           7 | 2013-08-16 11:31:50 | 2013-08-16 11:31:50 | NULL    |
> |  7 |       1 |           8 | 2013-08-16 11:31:50 | 2013-08-16 11:31:50 | NULL    |
> +----+---------+-------------+---------------------+---------------------+---------+
> All the templates have zone_id set to 1 even though cross-zones is set to 1for all of
these templates.
> Attaching management server log file and cloud DB.

--
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

Mime
View raw message