[
https://issues.apache.org/jira/browse/CLOUDSTACK-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652928#comment-13652928
]
Kishan Kavala commented on CLOUDSTACK-2309:
-------------------------------------------
Nicolas,
Destroy SSVM is not required. Just stop start of SSVM is sufficient. It'll
pick up the new template during the start.
You should see below sequence of commands for SSVM to work properly. Can you
check SecStorageVMSetupCommand in the logs when SSVM was started after upgrade?
2013-05-09 23:43:44,898 DEBUG [agent.transport.Request]
(AgentConnectTaskPool-2:null) Seq 5-1922891777: Sending { Cmd , MgmtId:
7683327393908, via: 5, Ver: v1, Flags: 100111,
[{"SecStorageSetupCommand":{"secUrl":"nfs://10.147.28.7/export/home/kishan/secondary22","certs":{},"wait":0}}]
}
2013-05-09 23:43:46,367 DEBUG [agent.transport.Request]
(AgentManager-Handler-11:null) Seq 5-1922891777: Processing: { Ans: , MgmtId:
7683327393908, via: 5, Ver: v1, Flags: 110,
[{"SecStorageSetupAnswer":{"_dir":"52274c13-dd76-3c46-90d6-b329419eab4f","result":true,"details":"success","wait":0}}]
}
2013-05-09 23:43:46,368 DEBUG [agent.transport.Request]
(AgentConnectTaskPool-2:null) Seq 5-1922891777: Received: { Ans: , MgmtId:
7683327393908, via: 5, Ver: v1, Flags: 110, { SecStorageSetupAnswer } }
2013-05-09 23:43:46,368 DEBUG [agent.manager.AgentManagerImpl]
(AgentConnectTaskPool-2:null) Details from executing class
com.cloud.agent.api.SecStorageSetupCommand: success
2013-05-09 23:43:46,374 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(AgentConnectTaskPool-2:null) Successfully programmed secondary storage
nfs://10.147.28.7/export/home/kishan/secondary22 in secondary storage VM s-1-VM
2013-05-09 23:43:46,393 DEBUG [agent.transport.Request]
(AgentConnectTaskPool-2:null) Seq 5-1922891778: Sending { Cmd , MgmtId:
7683327393908, via: 5, Ver: v1, Flags: 100011,
[{"SecStorageFirewallCfgCommand":{"isAppendAIp":false,"wait":0}}] }
2013-05-09 23:43:46,461 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(AgentConnectTaskPool-2:null) Successfully programmed firewall rules into s-1-VM
2013-05-09 23:43:46,483 DEBUG [agent.transport.Request]
(AgentConnectTaskPool-2:null) Seq 5-1922891779: Sending { Cmd , MgmtId:
7683327393908, via: 5, Ver: v1, Flags: 100111,
[{"SecStorageVMSetupCommand":{"allowedInternalSites":["10.0.0.0/0"],"copyUserName":"cloud","copyPassword":"xB5rzvrbqhxizif","wait":0}}]
}
2013-05-09 23:43:46,611 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 5-1922891779: Processing: { Ans: , MgmtId:
7683327393908, via: 5, Ver: v1, Flags: 110,
[{"Answer":{"result":true,"details":"","wait":0}}] }
2013-05-09 23:43:46,612 DEBUG [agent.manager.AgentManagerImpl]
(AgentConnectTaskPool-2:null) Details from executing class
com.cloud.agent.api.SecStorageVMSetupCommand:
2013-05-09 23:43:46,612 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(AgentConnectTaskPool-2:null) Successfully programmed http auth into s-1-VM
> Upgrade from 2.2.14 to 4.1.0 : network static routes deleted on SSVM
> --------------------------------------------------------------------
>
> Key: CLOUDSTACK-2309
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2309
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.1.0
> Reporter: Nicolas Lamirault
> Assignee: Kishan Kavala
> Priority: Blocker
> Fix For: 4.1.0
>
>
> After upgrading from 2.2.14 to 4.1.0, we have rebooted the SSVM. After that,
> all network static routes disapeared.
> This static routes was added by CS on 2.2.14 dynamically.
--
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
