You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sanjeev N (JIRA)" <ji...@apache.org> on 2013/05/24 09:09:22 UTC
[jira] [Created] (CLOUDSTACK-2665) [Object_Store_Refactor] UI:
Default cent OS template Ready field shows "NO" in UI whereas it shows YES
in DB
Sanjeev N created CLOUDSTACK-2665:
-------------------------------------
Summary: [Object_Store_Refactor] UI: Default cent OS template Ready field shows "NO" in UI whereas it shows YES in DB
Key: CLOUDSTACK-2665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2665
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: UI
Affects Versions: 4.2.0
Environment: Latest build from object_store branch
Reporter: Sanjeev N
Fix For: 4.2.0
Default cent OS template Ready field shows "NO" in UI whereas it shows YES in DB
Steps to Reproduce:
=================
1.Bring up CS in advanced zone with s3 as the secondary storage provider
2.Wait for the SSVM to come up
3.After SSVM is up, it downloads the default cent os template to S3 image store and once the download is successful template state will be marked Ready.
mysql> select * from vm_template where id=5\G;
*************************** 1. row ***************************
id: 5
unique_name: centos56-x86_64-xen
name: CentOS 5.6(64-bit) no GUI (XenServer)
uuid: 162ea93c-c469-11e2-9096-06ab4600005f
public: 1
featured: 1
type: BUILTIN
hvm: 0
bits: 64
url: http://10.147.28.7/templates/builtin/centos56-x86_64.vhd.bz2
format: VHD
created: 2013-05-24 07:57:19
removed: NULL
account_id: 1
checksum: 905cec879afd9c9d22ecc8036131a180
display_text: CentOS 5.6(64-bit) no GUI (XenServer)
enable_password: 0
enable_sshkey: 0
guest_os_id: 12
bootable: 1
prepopulate: 0
cross_zones: 1
extractable: 1
hypervisor_type: XenServer
source_template_id: NULL
template_tag: NULL
sort_key: 0
size: 374730926
state: Ready
update_count: 3
updated: 2013-05-24 12:18:52
1 row in set (0.00 sec)
ERROR:
No query specified
Attached screen shot to describe the bug.
--
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