You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/05/20 09:19:15 UTC
[jira] [Created] (CLOUDSTACK-2573) [Zone-Wide-PrimaryStorage]
SystemVMs are not coming up using zone wide primary storage
venkata swamybabu budumuru created CLOUDSTACK-2573:
------------------------------------------------------
Summary: [Zone-Wide-PrimaryStorage] SystemVMs are not coming up using zone wide primary storage
Key: CLOUDSTACK-2573
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2573
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller
Affects Versions: 4.2.0
Environment: commit # 85d54cd1c088997dd08f0328984bee1a55703636
Reporter: venkata swamybabu budumuru
Fix For: 4.2.0
Steps to reproduce :
1. Have a CloudStack setup with at least 1 advanced zone.
2. Deploy advanced zone with default which brings up the primary storage with scope set to "Cluster"
3. Disable the zone
4. Remove the primary storage.
5. add primary storage with scope set to Zone.
6. Enable Zone
Observations:
(i) CloudStack didnt kick in for system vm bring up.
Here is the snippet from mgmt server log.
2013-05-20 08:45:58,347 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-05-20 08:45:58,372 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Primary storage is not ready, wait until it is ready to launch secondary storage vm. dcId: 2 system.vm.use.local.storage: falseIf you want to use local storage to start ssvm, need to set system.vm.use.local.storage to true
2013-05-20 08:45:58,372 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2 is not ready to launch secondary storage VM yet
2013-05-20 08:45:58,807 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-05-20 08:45:58,817 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Primary storage is not ready, wait until it is ready to launch console proxy
2013-05-20 08:45:58,817 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 2 is not ready to launch console proxy yet
2013-05-20 08:46:02,447 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-21:null) Ping from 1
Here is the db snippet for the same
*************************** 4. row ***************************
id: 5
name: primaryZone2
uuid: b5671f5d-c64c-36e7-9249-6d87010c7bac
pool_type: NetworkFilesystem
port: 2049
data_center_id: 2
pod_id: NULL
cluster_id: NULL
available_bytes: 0
capacity_bytes: 0
host_address: 10.147.28.7
user_info: NULL
path: /export/home/swamy/primary.campo.vmw.1
created: 2013-05-20 12:21:08
removed: NULL
update_time: NULL
status: Up
storage_provider_name: ancient primary data store provider
scope: ZONE
4 rows in set (0.00 sec)
Attaching all the required logs to the bug along with db dump
--
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