[
https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239042#comment-14239042
]
ASF subversion and git services commented on CLOUDSTACK-7994:
-------------------------------------------------------------
Commit 016d009adfa7e12b7d5c2c43b946fc93ad07aa9d in cloudstack's branch
refs/heads/4.5 from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=016d009 ]
CLOUDSTACK-7994: Network rules are not configured in VR after out-of-band
movement due to host crash
The last commit 513adab51b53ba1acdea908225cfffab90ca1595 didn't fully fix it.
Scenario #1 was not handled, only #2 was handled.
Fixed #1 as part of this commit.
1. If VM is in stopped state in CS due to 'PowerMissing' report from old host
(hostId is null) and then there is a 'PowerOn' report from new host
2. If VM is in running state in CS and there is a 'PowerOn' report from new host
> Network rules are not configured in VR after out-of-band movement due to host
> crash
> -----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7994
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7994
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, VMware
> Affects Versions: 4.4.0, 4.5.0, 4.3.1, 4.4.1, 4.4.2, 4.3.2
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.5.0, 4.4.3, 4.3.2
>
>
> This is specific to Vmware. If VR is moved out-of-band from one host to
> another then the configured network rules are lost.
> In order to re-configure VR with the rules it needs to be rebooted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
