[
https://issues.apache.org/jira/browse/CLOUDSTACK-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nawawit Kessaraphong updated CLOUDSTACK-2203:
---------------------------------------------
Description:
I had cloudstack 3.0.2 upgraded to 4.0.1. After upgraded, I try to restart
Secondary Storage VM by destroying it from web console.
Normally, the management server will notifies its missing and redeploy new SSVM
automatically (I can confirmed its work before upgraded)
However, after the upgrade, the system did not automatically redeploy SSVM
anymore. This also happened to console proxy VM as well.
Is there anyway to manually create SSVM ?
------------------------
013-04-26 13:10:08,403 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) StorageCollector is running...
2013-04-26 13:10:08,405 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) There is no secondary storage VM for secondary storage
host nfs://172.16.0.4/export/secondary
2013-04-26 13:10:08,696 DEBUG [agent.transport.Request] (StatsCollector-3:null)
Seq 6-1025253660: Received: { Ans: , MgmtId: 57452528196556, via: 6, Ver: v1,
Flags: 10, { GetStorageStatsAnswer } }
2013-04-26 13:10:24,314 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is not ready to launch console proxy yet
was:
I had cloudstack 3.0.2 upgraded to 4.0.1. After the upgraded, i try to restart
Secondary Storage VM by destroying it from web console.
Normally, the management server will notify its missing and redeploy new SSVM
automatically (I can confirmed its work before upgraded)
However, after the upgrade, the system did not automatically redeploy SSVM
anymore.
This happend on console proxy VM as well.
Is there anyway to manually create SSVM ?
------------------------
013-04-26 13:10:08,403 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) StorageCollector is running...
2013-04-26 13:10:08,405 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) There is no secondary storage VM for secondary storage
host nfs://172.16.0.4/export/secondary
2013-04-26 13:10:08,696 DEBUG [agent.transport.Request] (StatsCollector-3:null)
Seq 6-1025253660: Received: { Ans: , MgmtId: 57452528196556, via: 6, Ver: v1,
Flags: 10, { GetStorageStatsAnswer } }
2013-04-26 13:10:24,314 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is not ready to launch console proxy yet
> SSVM does not redeploy after destroyed
> --------------------------------------
>
> Key: CLOUDSTACK-2203
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2203
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.0.1
> Environment: Cloudstack 3.0.3 upgraded to 4.0.1, CentOS 6.3, KVM
> Hypervisor,
> Reporter: Nawawit Kessaraphong
> Labels: server,, ssvm,, upgrade,
>
> I had cloudstack 3.0.2 upgraded to 4.0.1. After upgraded, I try to restart
> Secondary Storage VM by destroying it from web console.
> Normally, the management server will notifies its missing and redeploy new
> SSVM automatically (I can confirmed its work before upgraded)
> However, after the upgrade, the system did not automatically redeploy SSVM
> anymore. This also happened to console proxy VM as well.
> Is there anyway to manually create SSVM ?
> ------------------------
> 013-04-26 13:10:08,403 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-3:null) StorageCollector is running...
> 2013-04-26 13:10:08,405 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-3:null) There is no secondary storage VM for secondary
> storage host nfs://172.16.0.4/export/secondary
> 2013-04-26 13:10:08,696 DEBUG [agent.transport.Request]
> (StatsCollector-3:null) Seq 6-1025253660: Received: { Ans: , MgmtId:
> 57452528196556, via: 6, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-04-26 13:10:24,314 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null) Zone 1 is not ready to launch console proxy yet
--
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
