[
https://issues.apache.org/jira/browse/CLOUDSTACK-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815516#comment-13815516
]
Yoshikazu Nojima commented on CLOUDSTACK-5067:
----------------------------------------------
It seems it is caused by wrong handling of IpAssocCommand.
{
"com.cloud.agent.api.routing.IpAssocCommand": {
"accessDetails": {
"router.guest.ip": "172.16.0.1",
"router.ip": "169.254.0.193",
"router.name": "r-7-VM",
"zone.network.type": "Advanced"
},
"ipAddresses": [
{
"accountId": 2,
"add": true,
"broadcastUri": "vlan://untagged",
"firstIP": true,
"networkName": "cloudbr1",
"networkRate": 200,
"oneToOneNat": false,
"publicIp": "198.172.17.243",
"sourceNat": true,
"trafficType": "Public",
"vifMacAddress": "06:96:7a:00:00:0d",
"vlanGateway": "198.172.17.1",
"vlanNetmask": "255.255.255.0"
}
],
"wait": 0
}
},
LibvirtComputingResource#execute(IpAssocCommand) method hotplugs vNIC by
mistake.
https://github.com/apache/cloudstack/blob/master/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L2049
It is caused by isolation method notation mismatch in this line.
https://github.com/apache/cloudstack/blob/master/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L2047
It expects isolation method is expressed in broadcast uri style like
"vlan://1234", "vlan://untagged", but "untagged" is passed.
https://github.com/apache/cloudstack/blob/master/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L2033
> two NICs connected to Public network exist in VR
> ------------------------------------------------
>
> Key: CLOUDSTACK-5067
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5067
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: 4.3.0
> Reporter: Yoshikazu Nojima
> Assignee: Yoshikazu Nojima
>
> * "ip addr" output of VR
> root@r-7-VM:~# ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
> qlen 1000
> link/ether 02:00:05:6c:00:04 brd ff:ff:ff:ff:ff:ff
> inet 172.16.0.1/24 brd 172.16.0.255 scope global eth0
> inet6 fe80::5ff:fe6c:4/64 scope link
> valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
> qlen 1000
> link/ether 0e:00:a9:fe:00:c1 brd ff:ff:ff:ff:ff:ff
> inet 169.254.0.193/16 brd 169.254.255.255 scope global eth1
> inet6 fe80::c00:a9ff:fefe:c1/64 scope link
> valid_lft forever preferred_lft forever
> 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
> qlen 1000
> link/ether 06:6a:92:00:00:0d brd ff:ff:ff:ff:ff:ff
> inet 198.172.17.243/24 brd 198.172.17.255 scope global eth2
> inet6 fe80::46a:92ff:fe00:d/64 scope link
> valid_lft forever preferred_lft forever
> 5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
> qlen 1000
> link/ether 06:96:7a:00:00:0d brd ff:ff:ff:ff:ff:ff
> inet 198.172.17.243/24 brd 198.172.17.255 scope global eth3
> inet6 fe80::496:7aff:fe00:d/64 scope link
> valid_lft forever preferred_lft forever
> Two NICs connected to Public network exist in VR.
> It seems eth3 is unnecessary NIC.
> It has same MAC addr as eth2 has. It's weird.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
