[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231265#comment-14231265 ]
ASF subversion and git services commented on CLOUDSTACK-7994: ------------------------------------------------------------- Commit 291a34aac17ef0c61727379fca0094dfff22c1ee in cloudstack's branch refs/heads/4.4 from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=291a34a ] CLOUDSTACK-7994: Network rules are not configured in VR after out-of-band movement due to host crash Ensure that VR is re-booted when it is moved to another host out-of-band. This is necessary to re-program all network rules (cherry picked from commit 513adab51b53ba1acdea908225cfffab90ca1595) Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com> Conflicts: server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java > 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)