[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938049#comment-15938049 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit 9bf428162df6d2a91a3405d636247faa9f7b6167 in cloudstack's branch refs/heads/4.9 from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9bf4281 ] Merge pull request #2011 from ustcweizhou/fix-issue-p55p1 CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp * pr/2011: CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp Signed-off-by: Rajani Karuturi > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938047#comment-15938047 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit 9bf428162df6d2a91a3405d636247faa9f7b6167 in cloudstack's branch refs/heads/4.9 from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9bf4281 ] Merge pull request #2011 from ustcweizhou/fix-issue-p55p1 CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp * pr/2011: CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp Signed-off-by: Rajani Karuturi > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938045#comment-15938045 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit bf93b6313e537a56b27f61fdaaf7319fc04a8058 in cloudstack's branch refs/heads/4.9 from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bf93b63 ] CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938040#comment-15938040 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit ec2d4dd42205b5a51ef1755e66c6051a5c588280 in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ec2d4dd ] Merge release branch 4.9 to master * 4.9: CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938035#comment-15938035 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit 9bf428162df6d2a91a3405d636247faa9f7b6167 in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9bf4281 ] Merge pull request #2011 from ustcweizhou/fix-issue-p55p1 CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp * pr/2011: CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp Signed-off-by: Rajani Karuturi > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938030#comment-15938030 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit 9bf428162df6d2a91a3405d636247faa9f7b6167 in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9bf4281 ] Merge pull request #2011 from ustcweizhou/fix-issue-p55p1 CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp * pr/2011: CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp Signed-off-by: Rajani Karuturi > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938025#comment-15938025 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit bf93b6313e537a56b27f61fdaaf7319fc04a8058 in cloudstack's branch refs/heads/master from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bf93b63 ] CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938023#comment-15938023 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit 2b0a5ae4b288b3d9e3892fc1e144ba42cbf79f8f in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2b0a5ae ] Merge pull request #2003 from swill/cs_ip_fix CLOUDSTACK-9811: fixed an issue if the dev is not in the databagDefend against the specified dev not being in the databag. * pr/2003: changed the order fix to be closer to the original code CLOUDSTACK-9811: fixed an issue if the dev is not in the databag Signed-off-by: Rajani Karuturi > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938020#comment-15938020 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/2011 > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938018#comment-15938018 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit 2b0a5ae4b288b3d9e3892fc1e144ba42cbf79f8f in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2b0a5ae ] Merge pull request #2003 from swill/cs_ip_fix CLOUDSTACK-9811: fixed an issue if the dev is not in the databagDefend against the specified dev not being in the databag. * pr/2003: changed the order fix to be closer to the original code CLOUDSTACK-9811: fixed an issue if the dev is not in the databag Signed-off-by: Rajani Karuturi > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938013#comment-15938013 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/2003 > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938010#comment-15938010 ] ASF subversion and git services commented on CLOUDSTACK-9811: - Commit 8d4855b4ebff91a0d9fed12c17b8b123d2463ca6 in cloudstack's branch refs/heads/master from [~williamstev...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8d4855b ] CLOUDSTACK-9811: fixed an issue if the dev is not in the databag > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938004#comment-15938004 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user karuturi commented on the issue: https://github.com/apache/cloudstack/pull/2011 ok. Thanks everyone. I am merging this. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938003#comment-15938003 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user karuturi commented on the issue: https://github.com/apache/cloudstack/pull/2003 ok. Thanks everyone. I am merging this. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937860#comment-15937860 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user DaanHoogland commented on the issue: https://github.com/apache/cloudstack/pull/2011 thanks @ustcweizhou @karuturi can we merge this? and merge forward? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937100#comment-15937100 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2011 @DaanHoogland @karuturi @borisstoyanov Here is a short explanation why the issue happened: Normally getBroadcastUriFromBridge method in KVM plugin will get the URI from a bridge name. for example, breth1-100 -> vlan://100, brem1-200 -> vlan://200. However, for the bridge like brp55p1-100, it will return vlan://1 which is obviously wrong. The method getBroadcastUriFromBridge is used in prepareNetworkElementCommand for command IpAssocCommand in VR. Each time when a new ip is associated, it will check the existing nics by getting the URIs from bridge name of nics. If the URIs do not contain the uri of te new ip, then a new nic will be plugged and new ip will be associated to the new nic. The issue happened when cloudstack try to set more information of eth2 (public nic) of a VR, as for the error described in part 1 , the URI of eth2 return wrong result (vlan://1) which is different from uri of ip (it is vlan://7 from StartCommand), so eth3 is added. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936749#comment-15936749 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2011 thank you guys, tests are looking good as well. I think we have enough LGTM to merge this now cc: @karuturi tag:mergeready > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936578#comment-15936578 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2011 Trillian test result (tid-962) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 28290 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2011-t962-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py Test completed. 46 look ok, 2 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_04_rvpc_privategw_static_routes | `Failure` | 359.28 | test_privategw_acl.py test_02_list_snapshots_with_removed_data_store | `Error` | 0.03 | test_snapshots.py test_01_vpc_site2site_vpn | Success | 164.78 | test_vpc_vpn.py test_01_vpc_remote_access_vpn | Success | 66.08 | test_vpc_vpn.py test_01_redundant_vpc_site2site_vpn | Success | 255.18 | test_vpc_vpn.py test_02_VPC_default_routes | Success | 265.84 | test_vpc_router_nics.py test_01_VPC_nics_after_destroy | Success | 527.08 | test_vpc_router_nics.py test_05_rvpc_multi_tiers | Success | 504.56 | test_vpc_redundant.py test_04_rvpc_network_garbage_collector_nics | Success | 1403.26 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Success | 557.21 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | Success | 752.65 | test_vpc_redundant.py test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1300.22 | test_vpc_redundant.py test_09_delete_detached_volume | Success | 156.34 | test_volumes.py test_08_resize_volume | Success | 156.52 | test_volumes.py test_07_resize_fail | Success | 161.15 | test_volumes.py test_06_download_detached_volume | Success | 156.03 | test_volumes.py test_05_detach_volume | Success | 155.78 | test_volumes.py test_04_delete_attached_volume | Success | 150.94 | test_volumes.py test_03_download_attached_volume | Success | 156.59 | test_volumes.py test_02_attach_volume | Success | 89.67 | test_volumes.py test_01_create_volume | Success | 711.12 | test_volumes.py test_deploy_vm_multiple | Success | 277.07 | test_vm_life_cycle.py test_deploy_vm | Success | 0.02 | test_vm_life_cycle.py test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py test_10_attachAndDetach_iso | Success | 26.52 | test_vm_life_cycle.py test_09_expunge_vm | Success | 125.20 | test_vm_life_cycle.py test_08_migrate_vm | Success | 40.67 | test_vm_life_cycle.py test_07_restore_vm | Success | 0.07 | test_vm_life_cycle.py test_06_destroy_vm | Success | 125.63 | test_vm_life_cycle.py test_03_reboot_vm | Success | 125.67 | test_vm_life_cycle.py test_02_start_vm | Success | 10.12 | test_vm_life_cycle.py test_01_stop_vm | Success | 40.25 | test_vm_life_cycle.py test_CreateTemplateWithDuplicateName | Success | 50.40 | test_templates.py test_08_list_system_templates | Success | 0.02 | test_templates.py test_07_list_public_templates | Success | 0.02 | test_templates.py test_05_template_permissions | Success | 0.04 | test_templates.py test_04_extract_template | Success | 5.12 | test_templates.py test_03_delete_template | Success | 5.08 | test_templates.py test_02_edit_template | Success | 90.17 | test_templates.py test_01_create_template | Success | 50.36 | test_templates.py test_10_destroy_cpvm | Success | 161.58 | test_ssvm.py test_09_destroy_ssvm | Success | 163.45 | test_ssvm.py test_08_reboot_cpvm | Success | 131.54 | test_ssvm.py test_07_reboot_ssvm | Success | 163.49 | test_ssvm.py test_06_stop_cpvm | Success | 131.59 | test_ssvm.py test_05_stop_ssvm | Success | 138.58 | test_ssvm.py test_04_cpvm_internals | Success | 1.26 | test_ssvm.py test_03_ssvm_internals | Success | 3.83 | test_ssvm.py test_02_list_cpvm_vm | Success | 0.09 | test_ssvm.py test_01_list_sec_storage_vm | Success | 0.10 | test_ssvm.py test_01_snapshot_root_disk | Success | 10.95 | test_snapshots.py test_04_change_offering_small | Success | 239.49 | test_service_offerings.py test_03_delete_service_offering | Success | 0.03 | test_service_offerings.py test_02_edit_service_offering | Success | 0.04 | test_service_offerings.py test_01_create_service_offering | Success | 0.08 | test_service_offerings.py test_02_sys_template_ready | Success | 0.09 | test_secondary_storage.py test_01_sys_vm_start | Success | 0.13 | test_secondary_storage.py test_09_reboot_router | Success | 40.25 | test_routers.py test_
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936264#comment-15936264 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user DaanHoogland commented on the issue: https://github.com/apache/cloudstack/pull/2011 @ustcweizhou this enables looking for a nic by a name like a1b2c3 (\D+\d+\D*\d*\D*\d*) it will also allow all shorter as long as they start with which makes sense. But to satisfy @karuturi's question in 2003, could you *briefly* describe how this prevents extra nics from being created? otherwise LGTM > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936245#comment-15936245 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @karuturi we have 3 LGTMs, I think we're good to merge this. tag:mergeready > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936236#comment-15936236 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 I think #2011 fixes the observed issue, but this PR improves the IP ordering fix originally added to the strongswan pr. This implementation ensures (again) that duplicate public ips will not be saved to the data bag while ensuring the source nature ip is primary on its nic. In short, I think both PRs are worth merging. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932351#comment-15932351 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2011 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932349#comment-15932349 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2011 @blueorangutan test > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932348#comment-15932348 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @DaanHoogland you could review it as well it addressed in https://github.com/apache/cloudstack/pull/2011/files > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932343#comment-15932343 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user DaanHoogland commented on the issue: https://github.com/apache/cloudstack/pull/2003 code LGTM but @ustcweizhou 's patch still makes sense to me. Maybe you can add that separately? travis still fails! > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932342#comment-15932342 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2011 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-597 > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932316#comment-15932316 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2011 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932315#comment-15932315 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2011 @blueorangutan package > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932314#comment-15932314 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2011 Packaging result: ✖centos6 ✔centos7 ✔debian. JID-596 > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932291#comment-15932291 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2011 @borisstoyanov first 4.9, then merge into master. this patch can also be applied to master. ``` wget --no-check-certificate https://github.com/apache/cloudstack/pull/2011.patch git am 2011.patch (or patch -p1 <2011.patch) ``` > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932285#comment-15932285 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 ping @rhtyd @DaanHoogland @abhinandanprateek @PaulAngus for review. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932281#comment-15932281 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2011 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932282#comment-15932282 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2011 Hi @ustcweizhou, out of curiosity why 4.9 instead of master? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932280#comment-15932280 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2011 @blueorangutan package > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932212#comment-15932212 ] ASF GitHub Bot commented on CLOUDSTACK-9811: GitHub user ustcweizhou opened a pull request: https://github.com/apache/cloudstack/pull/2011 CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp You can merge this pull request into a Git repository by running: $ git pull https://github.com/ustcweizhou/cloudstack fix-issue-p55p1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/2011.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2011 commit cf442b459ae79ff7828c0ae868c4e1af9c078f01 Author: Wei Zhou Date: 2017-03-16T10:48:35Z CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name pp > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931289#comment-15931289 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2003 Trillian test result (tid-958) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 31840 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2003-t958-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Test completed. 46 look ok, 3 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | `Failure` | 369.05 | test_vpc_redundant.py test_04_rvpc_privategw_static_routes | `Failure` | 335.61 | test_privategw_acl.py test_02_list_snapshots_with_removed_data_store | `Error` | 0.04 | test_snapshots.py test_01_vpc_site2site_vpn | Success | 145.03 | test_vpc_vpn.py test_01_vpc_remote_access_vpn | Success | 66.12 | test_vpc_vpn.py test_01_redundant_vpc_site2site_vpn | Success | 250.53 | test_vpc_vpn.py test_02_VPC_default_routes | Success | 275.54 | test_vpc_router_nics.py test_01_VPC_nics_after_destroy | Success | 547.92 | test_vpc_router_nics.py test_05_rvpc_multi_tiers | Success | 508.38 | test_vpc_redundant.py test_04_rvpc_network_garbage_collector_nics | Success | 1403.12 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Success | 543.21 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | Success | 750.68 | test_vpc_redundant.py test_09_delete_detached_volume | Success | 156.45 | test_volumes.py test_08_resize_volume | Success | 156.39 | test_volumes.py test_07_resize_fail | Success | 161.50 | test_volumes.py test_06_download_detached_volume | Success | 156.27 | test_volumes.py test_05_detach_volume | Success | 150.72 | test_volumes.py test_04_delete_attached_volume | Success | 151.19 | test_volumes.py test_03_download_attached_volume | Success | 156.32 | test_volumes.py test_02_attach_volume | Success | 94.54 | test_volumes.py test_01_create_volume | Success | 711.06 | test_volumes.py test_03_delete_vm_snapshots | Success | 275.20 | test_vm_snapshots.py test_02_revert_vm_snapshots | Success | 95.66 | test_vm_snapshots.py test_01_create_vm_snapshots | Success | 163.76 | test_vm_snapshots.py test_deploy_vm_multiple | Success | 247.58 | test_vm_life_cycle.py test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py test_10_attachAndDetach_iso | Success | 26.64 | test_vm_life_cycle.py test_09_expunge_vm | Success | 125.24 | test_vm_life_cycle.py test_08_migrate_vm | Success | 45.95 | test_vm_life_cycle.py test_07_restore_vm | Success | 0.15 | test_vm_life_cycle.py test_06_destroy_vm | Success | 125.83 | test_vm_life_cycle.py test_03_reboot_vm | Success | 125.85 | test_vm_life_cycle.py test_02_start_vm | Success | 10.16 | test_vm_life_cycle.py test_01_stop_vm | Success | 40.31 | test_vm_life_cycle.py test_CreateTemplateWithDuplicateName | Success | 30.38 | test_templates.py test_08_list_system_templates | Success | 0.03 | test_templates.py test_07_list_public_templates | Success | 0.04 | test_templates.py test_05_template_permissions | Success | 0.06 | test_templates.py test_04_extract_template | Success | 5.13 | test_templates.py test_03_delete_template | Success | 5.13 | test_templates.py test_02_edit_template | Success | 90.17 | test_templates.py test_01_create_template | Success | 25.33 | test_templates.py test_10_destroy_cpvm | Success | 161.59 | test_ssvm.py test_09_destroy_ssvm | Success | 163.56 | test_ssvm.py test_08_reboot_cpvm | Success | 101.50 | test_ssvm.py test_07_reboot_ssvm | Success | 133.54 | test_ssvm.py test_06_stop_cpvm | Success | 131.72 | test_ssvm.py test_05_stop_ssvm | Success | 193.66 | test_ssvm.py test_04_cpvm_internals | Success | 1.22 | test_ssvm.py test_03_ssvm_internals | Success | 3.25 | test_ssvm.py test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py test_01_snapshot_root_disk | Success | 11.12 | test_snapshots.py test_04_change_offering_small | Success | 239.60 | test_service_offerings.py test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py test_02_edit_service_offering | Success | 0.05 | test_service_offerings.py
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931121#comment-15931121 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931120#comment-15931120 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @blueorangutan test > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930835#comment-15930835 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 thank you sir. :) > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930815#comment-15930815 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930814#comment-15930814 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @blueorangutan test > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930806#comment-15930806 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2003 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-594 > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930771#comment-15930771 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930770#comment-15930770 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 not sure about the CI tests @swill, I think the easiest way to kick Travis tests is the close/reopen the PR. I'll pick it up as soon as possible. I'll rebuild and run the smoketests. @blueorangutan package > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930537#comment-15930537 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov alright, this is ready for you to start testing. Can you kick off CI on this as well? I will be doing testing of this locally as well. This implementation is very similar to how it was implemented before my original change. See: https://github.com/apache/cloudstack/pull/1741/files#diff-a7d6f7150cca74029f23c19b72ad0622L19 The only change from the original was that if the IP is a `source_nat` IP and there are already IPs associated with that dev, it will `prepend` instead of `append` so the source nat ip is set as the primary ip on the nic (required for VPN). > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930504#comment-15930504 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 Thanks @remibergsma. I am going to use `source_nat` as it better represents what it is I am trying to establish and it seems to always be in the object where `first_i_p` does not always seem to be present (look at @borisstoyanov's output above for example). @borisstoyanov I will work on getting you the new implementation today. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930485#comment-15930485 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user remibergsma commented on the issue: https://github.com/apache/cloudstack/pull/2003 @swill FYI if you look for `first_i_p` as seen in the json on the Python side, then on the Java side it's called `firstIP`, as the gson lib replaces every capital with an underscore and then the lowercase letter. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930313#comment-15930313 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov could you please test with my suggestion? I think it should fix the duplicated nics in VR. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930025#comment-15930025 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 Hi @swill, could you please let us know when do you expect to address the changes you have mentioned, so I could schedule the testing accordingly. Thanks. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928329#comment-15928329 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 I am considering changing my implementation to be the same as the old implementation (which removed the IP from the dbag in the initial loop of the merge), but if `source_nat` is present and it is `true` and the `len(dbag[ip['device']]) > 0` (with all the checking required), then prepend else append. This should ensure that the source nat ip is the primary ip on the nic which the StrongSwan feature depends on. If I do this and there is a bug elsewhere that will duplicate the IPs in the databag, then this will clean that up (as I assume it was doing before). Not sure this will fix @borisstoyanov's current problem, but I think it is probably a safer implementation to keep the source nat IP as the first IP. I will update this PR with that change later today... > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927781#comment-15927781 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov I suspect this is caused by the name of your public interface (p55p1). can you please try the following change ``` diff --git a/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java b/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingReso index d925297..706f7d9 100755 --- a/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java +++ b/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java @@ -1481,7 +1481,7 @@ public class LibvirtComputingResource extends ServerResourceBase implements Serv private String getBroadcastUriFromBridge(final String brName) { final String pif = matchPifFileInDirectory(brName); -final Pattern pattern = Pattern.compile("(\\D+)(\\d+)(\\D*)(\\d*)"); +final Pattern pattern = Pattern.compile("(\\D+)(\\d+)(\\D*)(\\d*)(\\D*)(\\d*)"); final Matcher matcher = pattern.matcher(pif); s_logger.debug("getting broadcast uri for pif " + pif + " and bridge " + brName); if(matcher.find()) { @@ -1489,7 +1489,9 @@ public class LibvirtComputingResource extends ServerResourceBase implements Serv return BroadcastDomainType.Vxlan.toUri(matcher.group(2)).toString(); } else{ -if (!matcher.group(4).isEmpty()) { +if (!matcher.group(6).isEmpty()) { +return BroadcastDomainType.Vlan.toUri(matcher.group(6)).toString(); +} else if (!matcher.group(4).isEmpty()) { return BroadcastDomainType.Vlan.toUri(matcher.group(4)).toString(); } else { //untagged or not matching (eth|bond|team)#.# ``` > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927680#comment-15927680 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 Thanks @ustcweizhou here's the StartCommand log ``` 2017-03-16 08:48:46,068 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) (logid:be1f1987) Request:Seq 1-2088825802169778189: { Cmd , MgmtId: 6629449860900, via: 1, Ver: v1, Flags: 100011, [{"com.cloud.agent.api.StartCommand":{"vm":{"id":5,"name":"r-5-VM","type":"DomainRouter","cpus":1,"minSpeed":250,"maxSpeed":500,"minRam":268435456,"maxRam":268435456,"arch":"x86_64","os":"Debian GNU/Linux 5.0 (64-bit)","platformEmulator":"Debian GNU/Linux 5","bootArgs":" template=domP name=r-5-VM eth2ip=10.1.35.83 eth2mask=255.255.224.0 gateway=10.1.63.254 eth0ip=10.1.1.1 eth0mask=255.255.255.0 domain=cs2cloud.internal cidrsize=24 dhcprange=10.1.1.1 eth1ip=169.254.2.157 eth1mask=255.255.0.0 type=router disable_rp_filter=true dns1=8.8.8.8 dns2=8.8.4.4 baremetalnotificationsecuritykey=QtUSkBDvXbuIN02ekUDrlpkmPzc5XXTVAOV1_L3Nvozwp46Xyq7PnGvYYiPWctsrMj2cgIIxFIUzXOXLntsomA baremetalnotificationapikey=3cvNCQ5aBbRVT2a1vjuO0WKF3cELdiS86t_J_5GJnpPTobkyHZPjmxIKuDNHZHRpzfWooLi6pms0QPiEhpiq5A host=10.2.2.44 port=8080","enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"aFTlD_W3vJCMrO9fjc_GFA","params":{"cpuOvercommitRatio":"2.0","memoryOvercommitRatio":"1.0"},"uuid":"469106c8-107d-46b9-9bd0-237221c97ffe","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"2844d31e-edd9-40a1-8e2d-0394df1b2d1d","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"a86067db-e2df-3c95-819c-254d6d60f4bd","id":2,"poolType":"NetworkFilesystem","host":"10.2.0.16","path":"/acs/primary/ref-trl-106-k-cs410-bstoyanov/ref-trl-106-k-cs410-bstoyanov-kvm-pri2","port":2049,"url":"NetworkFilesystem://10.2.0.16/acs/primary/ref-trl-106-k-cs410-bstoyanov/ref-trl-106-k-cs410-bstoyanov-kvm-pri2/?ROLE=Primary&STOREUUID=a86067db-e2df-3c95-819c-254d6d60f4bd","isManaged":false}},"name":"ROOT-5","size":348984320,"path":"2844d31e-edd9-40a1-8e2d-0394df1b2d1d","volumeId":5,"vmName":"r-5-VM","accountId":2,"format":"QCOW2","provisioningType":"THIN","id":5,"deviceId":0,"bytesReadRate":0,"bytesWriteRate":0,"iopsReadRate":0,"iopsWriteRate":0,"hypervisorType":"KVM"}},"diskSeq":0,"path":"2844d31e-edd9-40a1-8e2d-0394df1b2d1d","type":"ROOT","_details":{"storageHost":"10.2.0.16","managed":"false","storagePort":"2049","volumeSize":"348984320"}}],"nics":[{"deviceId":2,"networkRateMbps":200,"defaultNic":true,"pxeDisable":true,"nicUuid":"8bc36a5d-e51a-4f93-b764-89d452a89617","uuid":"268a2858-a1ac-4aec-aa3f-365c4ea97d18","ip":"10.1.35.83","netmask":"255.255.224.0","gateway":"10.1.63.254","mac":"06:17:c6:00:00:03","dns1":"8.8.8.8","dns2":"8.8.4.4","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://7","isolationUri":"vlan://7","isSecurityGroupEnabled":false,"name":"cloudbr1"},{"deviceId":0,"networkRateMbps":200,"defaultNic":false,"pxeDisable":true,"nicUuid":"cf5bcb72-96e2-47a2-a5b2-9187d8922ae5","uuid":"9046a22a-ac92-45c9-9757-107ca10e38d4","ip":"10.1.1.1","netmask":"255.255.255.0","mac":"02:00:46:fd:00:03","dns1":"8.8.8.8","dns2":"8.8.4.4","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://884","isolationUri":"vlan://884","isSecurityGroupEnabled":false,"name":"cloudbr1"},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"pxeDisable":true,"nicUuid":"8cc9d552-6238-4add-9497-9b3d61ca938a","uuid":"9a24aaa5-e041-460c-9954-660fb4a41404","ip":"169.254.2.157","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:02:9d","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false}]},"hostIp":"10.2.5.1","executeInSequence":false,"wait":0}},{"com.cloud.agent.api.check.CheckSshCommand":{"ip":"169.254.2.157","port":3922,"interval":6,"retries":100,"name":"r-5-VM","wait":0}},{"com.cloud.agent.api.GetDomRVersionCmd":{"accessDetails":{"router.ip":"169.254.2.157","router.name":"r-5-VM"},"wait":0}},{},{"com.cloud.agent.api.routing.AggregationControlCommand":{"action":"Start","accessDetails":{"router.guest.ip":"10.1.1.1","router.ip":"169.254.2.157","router.name":"r-5-VM"},"wait":0}},{"com.cloud.agent.api.routing.IpAssocCommand":{"ipAddresses":[{"accountId":2,"publicIp":"10.1.35.83","sourceNat":true,"add":true,"oneToOneNat":false,"firstIP":true,"broadcastUri":"vlan://7","vlanGateway":"10.1.63.254","vlanNetmask":"255.255.224.0","vifMacAddress":"06:b5:28:00:00:03","networkRate":200,"trafficType":"Public","networkName":"cloudbr1","newNic":false}],"accessDetails":{"router.guest.ip":"10.1.1.1","router.ip":"169.254.2.157","zone.network.type":"Advanced","router.name":"r-5-VM"},"wait":0}},{"com.cloud.agent.api.routin
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927653#comment-15927653 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov I think this is caused by KVM plugin. can you please perform the following on KVM host ? (1) change INFO to DEBUG in /etc/cloudstack/agent/log4j-cloud.xml, and restart cloudstack-agent (2) restart the VR (on UI), and post the StartCommand in /var/log/cloudstack/agent/agent.log (3) post the xml definition of VR (virsh dumpxml r--VM) (4) post bridge information (brctl show) (5) post /etc/cloudstack/agent/agent.properties > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927017#comment-15927017 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 @swill first_i_p in json -> firstIP in java. This is formatted by google.gson it is defined in api/src/com/cloud/agent/api/to/IpAddressTO.java, and used in server/src/com/cloud/network/router/CommandSetupHelper.java so, the issue might be caused by commit baac747089ef48ea6627a6aacf27156222862352 not sure. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927006#comment-15927006 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 Does anyone know what `first_i_p` represents in the `ips.json` dbag? I am assuming it is the Source NAT IP, but I can't find it represented anywhere in the code (other than in a test). If it does represent the Source NAT, then we can use it to maintain the order and keep the Source NAT IP as the primary IP on the Nic. That was the bug I was trying to fix in my #1741 PR. Example with: 1) source nat 2) port forwarding 3) static nat 4) load balancer ``` "eth2": [ { "add": true, "broadcast": "192.168.80.255", "cidr": "192.168.80.8/24", "device": "eth2", "first_i_p": true, "gateway": "192.168.80.5", "netmask": "255.255.255.0", "network": "192.168.80.0/24", "new_nic": false, "nic_dev_id": 2, "nw_type": "public", "one_to_one_nat": false, "public_ip": "192.168.80.8", "size": "24", "source_nat": true, "vif_mac_address": "06:00:44:00:00:23" }, { "add": true, "broadcast": "192.168.80.255", "cidr": "192.168.80.9/24", "device": "eth2", "first_i_p": false, "gateway": "192.168.80.5", "netmask": "255.255.255.0", "network": "192.168.80.0/24", "new_nic": false, "nic_dev_id": 2, "nw_type": "public", "one_to_one_nat": false, "public_ip": "192.168.80.9", "size": "24", "source_nat": false, "vif_mac_address": "06:34:d1:00:00:23" }, { "add": true, "broadcast": "192.168.80.255", "cidr": "192.168.80.10/24", "device": "eth2", "first_i_p": false, "gateway": "192.168.80.5", "netmask": "255.255.255.0", "network": "192.168.80.0/24", "new_nic": false, "nic_dev_id": 2, "nw_type": "public", "one_to_one_nat": true, "public_ip": "192.168.80.10", "size": "24", "source_nat": false, "vif_mac_address": "06:34:d1:00:00:23" }, { "add": true, "broadcast": "192.168.80.255", "cidr": "192.168.80.11/24", "device": "eth2", "first_i_p": false, "gateway": "192.168.80.5", "netmask": "255.255.255.0", "network": "192.168.80.0/24", "new_nic": false, "nic_dev_id": 2, "nw_type": "public", "one_to_one_nat": false, "public_ip": "192.168.80.11", "size": "24", "source_nat": false, "vif_mac_address": "06:34:d1:00:00:23" } ], ``` @ustcweizhou @murali-reddy @remibergsma > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926125#comment-15926125 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 nics in database seems ok, so it looks some issue in creating ip_associations.json > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925692#comment-15925692 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @ustcweizhou - I was able to restart the network with cleanup. New VR came up with duplicated eth2 and eth3. ![screen shot 2017-03-15 at 9 48 33 am](https://cloud.githubusercontent.com/assets/13551960/23938354/b2cb8398-0964-11e7-8690-4cb0d635ec9c.png) - Not sure what you mean by what is my last commit, currently this PR has been built and deployed on the physical hosts. - There are 3 nics in the DB for that router. ``` *** 8. row *** id: 8 uuid: 9a2d5343-fbff-487e-a48d-509ae0503687 instance_id: 4 mac_address: 02:00:19:89:00:02 ip4_address: 10.1.1.1 netmask: 255.255.255.0 gateway: NULL ip_type: NULL broadcast_uri: vlan://884 network_id: 204 mode: Dhcp state: Reserved strategy: Start reserver_name: ExternalGuestNetworkGuru reservation_id: 2f428f23-afae-4916-a423-4a7452a33138 device_id: 0 update_time: 2017-03-14 13:41:23 isolation_uri: vlan://884 ip6_address: NULL default_nic: 0 vm_type: DomainRouter created: 2017-03-14 09:31:29 removed: NULL ip6_gateway: NULL ip6_cidr: NULL secondary_ip: 0 display_nic: 1 *** 9. row *** id: 9 uuid: bb36a0a5-ac45-45ac-976f-341e2d2c72be instance_id: 4 mac_address: 0e:00:a9:fe:00:44 ip4_address: 169.254.0.68 netmask: 255.255.0.0 gateway: 169.254.0.1 ip_type: Ip4 broadcast_uri: NULL network_id: 202 mode: Static state: Reserved strategy: Start reserver_name: ControlNetworkGuru reservation_id: 2f428f23-afae-4916-a423-4a7452a33138 device_id: 1 update_time: 2017-03-14 13:41:23 isolation_uri: NULL ip6_address: NULL default_nic: 0 vm_type: DomainRouter created: 2017-03-14 09:31:29 removed: NULL ip6_gateway: NULL ip6_cidr: NULL secondary_ip: 0 display_nic: 1 *** 10. row *** id: 10 uuid: a4e7691b-b290-4bfe-905e-ddb3c5b1c466 instance_id: 4 mac_address: 06:bb:c8:00:00:03 ip4_address: 10.1.35.83 netmask: 255.255.224.0 gateway: 10.1.63.254 ip_type: NULL broadcast_uri: vlan://7 network_id: 200 mode: Static state: Reserved strategy: Managed reserver_name: PublicNetworkGuru reservation_id: NULL device_id: 2 update_time: 2017-03-14 13:41:23 isolation_uri: vlan://7 ip6_address: NULL default_nic: 1 vm_type: DomainRouter created: 2017-03-14 09:31:29 removed: NULL ip6_gateway: NULL ip6_cidr: NULL secondary_ip: 0 display_nic: 1 ``` > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sen
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925657#comment-15925657 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov moreover, can you please restart the network with cleanup, to see if the new VRs can start ? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925025#comment-15925025 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 Ya, I am not sure where the problem is stemming from. The fact that my code is not defensive around this problem is a problem. That is for sure. But given my understanding of the moving parts here, I feel like there is something else going on as well. I will see if I can get an environment up and running tomorrow so I can do some more testing on this. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925015#comment-15925015 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov what's the last commit in your code ? could you check how many nics attached to the VR in database, select * from nics where instance_id= ? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925010#comment-15925010 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 it seems nicDevId is not set correctly in java code. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924950#comment-15924950 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 yes, agree with you @swill, it seems eth3 is duplicated eth2. The VR we're trying to bring up isn't supposed to have eth3 at all... > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924943#comment-15924943 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 the ips.json is very very weird > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924813#comment-15924813 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 So... Looking at this with a different perspective. If there is a bug elsewhere which would cause an IP to be duplicated in the `dbag`, the old implementation would have cleaned up this bug and would have removed all the duplicates (including the real one) and then would have only added back the real one. My implementation did not assume that I was having to clean up duplicates in the `dbag` variable and only focused on adding if it didn't exist or updating the existing entry if it did exist. I will have to think about this more... > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924788#comment-15924788 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 This `ips.json` file confuses the hell out of me. From what I can tell both `eth2` and `eth3` both have the ip `10.1.35.83` twice for each (for a total of the IP being configured 4 times over two interfaces). How was this IP configured? ``` "eth2": [ { "add": true, "broadcast": "10.1.63.255", "cidr": "10.1.35.83/19", "device": "eth2", "gateway": "10.1.63.254", "netmask": "255.255.224.0", "network": "10.1.32.0/19", "nic_dev_id": "2", "nw_type": "public", "one_to_one_nat": false, "public_ip": "10.1.35.83", "size": "19", "source_nat": false }, { "add": true, "broadcast": "10.1.63.255", "cidr": "10.1.35.83/19", "device": "eth2", "gateway": "10.1.63.254", "netmask": "255.255.224.0", "network": "10.1.32.0/19", "nic_dev_id": "2", "nw_type": "public", "one_to_one_nat": false, "public_ip": "10.1.35.83", "size": "19", "source_nat": false } ], "eth3": [ { "add": true, "broadcast": "10.1.63.255", "cidr": "10.1.35.83/19", "device": "eth3", "first_i_p": true, "gateway": "10.1.63.254", "netmask": "255.255.224.0", "network": "10.1.32.0/19", "new_nic": true, "nic_dev_id": 3, "nw_type": "public", "one_to_one_nat": false, "public_ip": "10.1.35.83", "size": "19", "source_nat": true, "vif_mac_address": "06:ee:46:00:00:03" }, { "add": true, "broadcast": "10.1.63.255", "cidr": "10.1.35.83/19", "device": "eth3", "first_i_p": true, "gateway": "10.1.63.254", "netmask": "255.255.224.0", "network": "10.1.32.0/19", "new_nic": true, "nic_dev_id": 3, "nw_type": "public", "one_to_one_nat": false, "public_ip": "10.1.35.83", "size": "19", "source_nat": true, "vif_mac_address": "06:a4:80:00:00:03" } ], ``` I will see if I can get to the bottom of this, but this is pretty confusing. Do you have a sequence of events which produced this configuration? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924683#comment-15924683 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov I have a suspicion that the ip_association.json is a transient file which may be short lived. I am not sure because I have not seen it either, but it was the file being processed when you had your original error. I will review your ips.json and see what I can find. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924675#comment-15924675 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @ustcweizhou no VPC > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924672#comment-15924672 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @swill thanks, I found the ips.json, but I couldn't find the ip_association.json on the VR. I guess it's not processed yet. Can you advise how to force it to generate? Hope this helps. [ips.txt](https://github.com/apache/cloudstack/files/842199/ips.txt) > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924424#comment-15924424 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov we are still trying to understand how the IP was found when looping through the `dbag` but it is not associated with the expected dev when we try to update the index which it was found on. The only way I can see this could happen is if the dev requested it be configured on is different from the dev it is actually configured on. I still have not figured out how that case exists. @ustcweizhou has some good ideas on this front, but I don't think we have gotten to a point where we understand how this problem is happening. @borisstoyanov is there a chance you can post the `ips.json` and `ip_association.json` files in your environment so we can start to understand what the config is that is causing this? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924341#comment-15924341 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 @borisstoyanov are you using vpc ? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924334#comment-15924334 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @swill we're using one IP range for the physical guest public network. I think we could set this up if required? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924306#comment-15924306 ] Will Stevens commented on CLOUDSTACK-9811: -- [~weizhou] ya ok, that could make sense to me given my understanding. I am still not sure why the dbag variable does not have it since it just looped through the dbag variable and found it. so to me it looks like the dev got changed from where it is to a new dev in the same dbag. if that happens, we will have a problem because we didn't remove it from the original dev but we added it to the new dev. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924300#comment-15924300 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 On the Jira ticket, Wei Zhou mentioned that this could potentially happen if you have two different public IP ranges. So if you associate a public IP which is in a different range than the source nat, a new nic will be created. If you disassociate it, that nic will be removed. I guess my question is. Why is it not on the`dbag`variable then associated with that dev? I think Wei is probably right in terms of context, but I am not sure how exactly to solve this yet. @borisstoyanov can you confirm that you have two different public IP ranges in your setup? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924295#comment-15924295 ] Wei Zhou commented on CLOUDSTACK-9811: -- [~wstevens] I think so. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924257#comment-15924257 ] Will Stevens commented on CLOUDSTACK-9811: -- [~weizhou] so this can happen when you have two different public IP ranges? Is that the case? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924244#comment-15924244 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 I have to admit, I am not sure how the IP was found when looping through the list initially, but then when trying to update the index for the IP that was found, it is not there. The only way I can think of that would cause this is if the IP <-> dev mapping is broken somehow. It found the matching IP, but apparently that IP is not on the dev defined by the `nic_dev_id` (which comes from either: `nic_dev_id = address['nic_dev_id']` (from the databag), which can then be overridden by `nic_dev_id = ip['nic_dev_id']` (from the passed in IP) ). Yes, I think you are right that the `else` case does not work right now. This is because we are appending the IP to this dev, but we never removed it from the other dev it was apparently found in. This logic is SUPPOSED to find the existing IP's index and then if found, update that index with the updated info. The old logic which just removed all "found" IPs and then re-added them, did not preserve the order, so the source nat IP could get reconfigured as a secondary IP on a nic instead of it being primary. This reordering of the IPs on VR reboot caused the VPN to fail because the source nat IP was no longer the primary IP. So we know that removing all found IPs and then adding them does not work because it changes the order of the IPs causing the source nat IP to become a secondary IP on the nic. The error described in CLOUDSTACK-9811 seems to be a situation where the IP is found on one nic, but then for some reason the dev which the IP is associated with is changed (I don't know why this would be happening), causing the index where the IP was found to not be valid because the IP is actually on a different dev. To know how to fix this correctly, we need to understand why/how an IP can be associated with one dev (index found) and then get changed to be associated with a different dev. We need to find a way to preserve IP order while being able to update the IP configurations. @remibergsma do you have any ideas on this? Anyone else have ideas here? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924241#comment-15924241 ] Wei Zhou commented on CLOUDSTACK-9811: -- If you associate an IP in different subnet as source nat IP, then the new nic will be added. After deassociate it, the nic will be gone, but ... it still exists in /etc/cloudstack/ips.json > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924197#comment-15924197 ] Will Stevens commented on CLOUDSTACK-9811: -- [~bstoyanov] can you post the `ips.json` and `ip_associations.json` files so we can see what the config is that is attempting to be applied? I would like to understand what IPs are being configured and why `eth3` is referenced by the code and does not exist. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924193#comment-15924193 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user ustcweizhou commented on the issue: https://github.com/apache/cloudstack/pull/2003 @swill what I mean is , if you do not want to change the logic, do you need to change 'else:' to 'elif index == -1:' ? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924179#comment-15924179 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/2003 @ustcweizhou the `else` case did not change from the original code: https://github.com/apache/cloudstack/pull/1741/files#diff-a7d6f7150cca74029f23c19b72ad0622L49 @karuturi I have updated the PR title and I updated the commit message to include the jira ticket. @borisstoyanov do we have a run of these tests just against master recently to review the difference in output? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923531#comment-15923531 ] ASF GitHub Bot commented on CLOUDSTACK-9811: Github user karuturi commented on the issue: https://github.com/apache/cloudstack/pull/2003 Thanks Will. Can you please add bug id(CLOUDSTACK-9811) to the PR and commit message? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922827#comment-15922827 ] Will Stevens commented on CLOUDSTACK-9811: -- [~bstoyanov] here is a PR to fix this issue: https://github.com/apache/cloudstack/pull/2003 I still think there is a different problem in play which is getting us to this condition without a valid dev, but that is a different story. This will fix the problem of the code breaking if the dev does not exist while keeping the bug fix this change was introduced to fix. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922738#comment-15922738 ] Boris Stoyanov commented on CLOUDSTACK-9811: That is it [~wstevens], I've reverted the changes to https://github.com/swill/cloudstack/blob/8b4c36ef501a96742c52b4d532cc3adda25aa71b/systemvm/patches/debian/config/opt/cloud/bin/cs_ip.py which is the previous version before StrongSwan. VR did came up and the instance got deployed. I guess we need to create a separate PR to address this issue and restructure the StronSwan changes, I'll be really happy to help with testing. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907527#comment-15907527 ] Will Stevens commented on CLOUDSTACK-9811: -- I will admit that I am a bit confused that the IP was matched by looping through the databag and an index was found, but then when it tries to set the IP, it is not found. Is `eth3` supposed to exist? Can you post the ips.json and ip_associations.json databags so we understand what the config is there? We can easily 'get rid' of the error by changing this line of code: https://github.com/apache/cloudstack/blob/master/systemvm/patches/debian/config/opt/cloud/bin/cs_ip.py#L48 from: if index != -1: to: if index != -1 and ip['device'] in dbag and index in dbag[ip['device']]: I am curious if the `nic_dev_id` variable is correct. It was introduced here (it looks to be relatively consistent with the functionality before): https://github.com/apache/cloudstack/commit/6749785caba78a9379e94bf3aaf0c1fbc44c5445#diff-a7d6f7150cca74029f23c19b72ad0622R24 Looking at the logs, I am unclear how the `nic_dev_id` is getting set to `3`. Let me know if the code change I suggested in this comment works to fix your issue. If it does, I will create a PR with that change for you. Cheers... > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907463#comment-15907463 ] Will Stevens commented on CLOUDSTACK-9811: -- I really doubt my change in https://github.com/apache/cloudstack/pull/1741 is causing this. The change to `cs_ip.py` in that PR fixes a bug that cause the IP addresses to be reordered on reboot. If there are secondary IPs on that nic, then the source nat IP will no longer be the primary IP on that nic and instead one of the other secondary IPs will be the primary IP after reboot. The change I made results in the same network config after a reboot by recording the index and modifying that index rather than removing it and re-adding it at the end. I know Murali made a LOT of VR changes that got merged into 4.10 as well. I have not reviewed all of them, but he made a lot of changes. I will review the logs and see if anything pops up. [~boriss], let me know if reverting that change to cs_ip.py makes any difference. > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907466#comment-15907466 ] Will Stevens commented on CLOUDSTACK-9811: -- I just checked the logs. I see the key error. I will review further... > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907149#comment-15907149 ] Boris Stoyanov commented on CLOUDSTACK-9811: ok will try, thanks [~remibergsma] and [~ustcweiz...@gmail.com] > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906941#comment-15906941 ] Wei Zhou commented on CLOUDSTACK-9811: -- Hi [~bstoyanov], can you please revert the commit on cs_ip.py which mentioned by [~remibergsma] and test it ? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906139#comment-15906139 ] Remi Bergsma commented on CLOUDSTACK-9811: -- [~bstoyanov] [~ustcweiz...@gmail.com] This is due to a change introduced here: https://github.com/apache/cloudstack/pull/1741 (the cs_ip.py file is changed https://github.com/apache/cloudstack/pull/1741/files#diff-a7d6f7150cca74029f23c19b72ad0622R49) > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: agent.log, cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899224#comment-15899224 ] Wei Zhou commented on CLOUDSTACK-9811: -- can you post the agent.log ? > VR will not start, looking to configure eth3 while no such device exists on > the VR. On KVM-CentOS6.8 physical host > -- > > Key: CLOUDSTACK-9811 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.10.0.0 >Reporter: Boris Stoyanov >Priority: Blocker > Attachments: cloud.log, management.log > > > This issue appears only on 4.10. When you add an instance with a new network > the VR starts and fails at the configuration point. Looks like it is looking > to configure eth3 adapter while no such device should be available on the VR. > The VR does not start and aborts the deployment of the VM. > Pease note that this issue was reproduced on physical KVM hosts in our lab. > Hardware Hosts details: > - 4x Dell C6100 > - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant) > OS: > CentOS 6.8. > Management: > VM, running CentOS 6.8 > ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67 > In a nested virtualization environment it was working fine with CentOS6.8. > Attached are the management log and the cloud.log form the VR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)