[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696668#comment-14696668 ] Rohit Yadav commented on CLOUDSTACK-7994: - Ping, looks like this has been resolved and ported to other branches. Should we close this, cc [~koushikd] [~dahn] ? 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696676#comment-14696676 ] Daan Hoogland commented on CLOUDSTACK-7994: --- There was a follow up because alarms were sent for regular VMs. a mistake in the second if statement. Remi, wrote some fix for it. I think it can still do with some improvement but that seems out of scope for this ticket. closing... 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14570715#comment-14570715 ] Rohit Yadav commented on CLOUDSTACK-7994: - [~koushikd] - Sudhanshu shared on the users ML that since ACS 4.4+ has VR aggregated cmd execution, this may be not necessary. Can you suggest a suitable fix in that case? 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239187#comment-14239187 ] ASF subversion and git services commented on CLOUDSTACK-7994: - Commit 016d009adfa7e12b7d5c2c43b946fc93ad07aa9d in cloudstack's branch refs/heads/master 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231262#comment-14231262 ] Rohit Yadav commented on CLOUDSTACK-7994: - [~koushikd] The idea is to encourage committers to fix bugs on all the branches the issue is applicable. We cannot get there without everyone participating and doing their own bits. I'm backporting this to 4.3 and 4.4 branches now. 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231267#comment-14231267 ] ASF subversion and git services commented on CLOUDSTACK-7994: - Commit 8a91aa9afa8f58266393c7c9949893ca4ce18fb7 in cloudstack's branch refs/heads/4.3 from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8a91aa9 ] 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229730#comment-14229730 ] ASF subversion and git services commented on CLOUDSTACK-7994: - Commit 513adab51b53ba1acdea908225cfffab90ca1595 in cloudstack's branch refs/heads/4.5 from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=513adab ] 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 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.5.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.5.0 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229751#comment-14229751 ] Rohit Yadav commented on CLOUDSTACK-7994: - Is this related to https://issues.apache.org/jira/browse/CLOUDSTACK-5685 ? [~koushikd] can you help port this to 4.3/4.4? As this clearly affects both of those branches. 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.5.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.5.0 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229774#comment-14229774 ] ASF subversion and git services commented on CLOUDSTACK-7994: - Commit c3515c9ff98c8447d16dc9cc294aab3496f045a4 in cloudstack's branch refs/heads/master from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c3515c9 ] 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 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.5.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.5.0 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)
[jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230934#comment-14230934 ] Koushik Das commented on CLOUDSTACK-7994: - [~rohit.ya...@shapeblue.com] You can cherry-pick it to the required branches. I currently don't have a 4.3/4.4 setup to verify the changes. 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.5.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.5.0 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)
