[ https://issues.apache.org/jira/browse/CLOUDSTACK-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012036#comment-14012036 ]
Jayapal Reddy commented on CLOUDSTACK-6801: ------------------------------------------- MS logs: http://pastebin.com/s77nu5Ei >From the logs it seems the public vlan is untagged. I think the problem might >be coming incase of untagged. Can you please try the same thing with the tagged vlan ? {"com.cloud.agent.api.PlugNicCommand":{"nic":{"deviceId":1,"networkRateMbps":99999,"defaultNic":true,"uuid":"e6b734d4-3302-4113-8ec7-5c205c90959a","ip":"46.232.180.248","netmask":"255.255.255.0","gateway":"46.232.180.1","mac":"06:5e:e8:00:00:27","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://untagged","isolationUri":"vlan://untagged","isSecurityGroupEnabled":false,"name":"breth1-500"}, "instanceName":"r-779-VM","vmType":"DomainRouter","wait":0}},{"com.cloud.agent.api.routing.IpAssocVpcCommand":{"ipAddresses":[{"accountId":2,"publicIp":"46.232.180.248","sourceNat":true,"add":true,"oneToOneNat":false,"firstIP":false,"broadcastUri":"untagged","vlanGateway":"46.232.180.1","vlanNetmask":"255.255.255.0","vifMacAddress":"06:5e:e8:00:00:27","networkRate":99999,"trafficType":"Public","networkName":"breth1-500"}],"accessDetails": > Public IP not assigned to eth1 on VR in VPC > ------------------------------------------- > > Key: CLOUDSTACK-6801 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6801 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router > Affects Versions: 4.3.0 > Environment: CentOS, KVM. > Reporter: Andrija Panic > Priority: Blocker > Labels: publicip, virtualrouter, vpc > > Hi, > after upgrade from 4.2.1 to 4.3.0, Public IP on eth1 is missing on VR when > creating new (and on existing) VPCs, although eth1 seems present per > /proc/net/dev. > Mangement logs are fine, eth1 plugged in correct bridge, etc. > Manually adding IP on eth1 and starting eth1 does work. > From /var/log/messages inside VR: > May 28 18:27:36 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 0 seconds > May 28 18:27:37 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 1 seconds > May 28 18:27:38 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 2 seconds > May 28 18:27:39 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 3 seconds > May 28 18:27:40 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 4 seconds > May 28 18:27:41 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 5 seconds > May 28 18:27:42 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 6 seconds > May 28 18:27:43 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 7 seconds > May 28 18:27:44 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 8 seconds > May 28 18:27:45 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 9 seconds > May 28 18:27:46 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 10 seconds > May 28 18:27:47 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 11 seconds > May 28 18:27:48 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 12 seconds > May 28 18:27:49 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 13 seconds > May 28 18:27:50 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 14 seconds > May 28 18:27:51 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 15 seconds > May 28 18:27:52 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 16 seconds > May 28 18:27:53 r-799-VM cloud: vpc_ipassoc.sh:interface ethnull never > appeared > May 28 18:27:53 r-799-VM cloud: vpc_ipassoc.sh:Adding ip 46.232.x.246 on > interface ethnull > May 28 18:27:53 r-799-VM cloud: vpc_ipassoc.sh:Add routing 46.232.x.246 on > interface ethnull > May 28 18:27:53 r-799-VM cloud: vpc_privateGateway.sh:Added SourceNAT > 46.232.x.246 on interface ethnull > May 28 18:27:53 r-799-VM cloud: vpc_snat.sh:Added SourceNAT 46.232.x.246 on > interface eth1 > May 28 18:27:54 r-799-VM cloud: vpc_guestnw.sh: Create network on interface > eth2, gateway 10.0.1.1, network 10.0.1.1/24 > May 28 18:27:59 r-799-VM cloud: Setting up apache web server for eth2 > May 28 18:27:59 r-799-VM cloud: Setting up password service for network > 10.0.1.1/24, eth eth2 > May 28 18:27:59 r-799-VM cloud: vpc_guestnw.sh: Create network on interface > eth3, gateway 10.0.3.1, network 10.0.3.1/24 > May 28 18:28:04 r-799-VM cloud: Setting up apache web server for eth3 > May 28 18:28:06 r-799-VM cloud: Setting up password service for network > 10.0.3.1/24, eth eth3 > May 28 18:28:06 r-799-VM cloud: vpc_guestnw.sh: Create network on interface > eth4, gateway 10.0.4.1, network 10.0.4.1/24 > May 28 18:28:11 r-799-VM cloud: Setting up apache web server for eth4 > May 28 18:28:12 r-799-VM cloud: Setting up password service for network > 10.0.4.1/24, eth eth4 > May 28 18:28:13 r-799-VM cloud: vpc_guestnw.sh: Create network on interface > eth5, gateway 10.0.6.1, network 10.0.6.1/24 > May 28 18:28:18 r-799-VM cloud: Setting up apache web server for eth5 > May 28 18:28:19 r-799-VM cloud: Setting up password service for network > 10.0.6.1/24, eth eth5 > Nothing else usefull in other logs... -- This message was sent by Atlassian JIRA (v6.2#6252)