[
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.
- 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 sent by Atlassian JIRA
(v6.3.15#6346)
