[
https://issues.apache.org/jira/browse/CLOUDSTACK-8759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725430#comment-14725430
]
Wilder Rodrigues commented on CLOUDSTACK-8759:
----------------------------------------------
It has been fixed. I'm adding a Marvin test and will create a PR by tomorrow.
The problem was on the NetworkHelperImpl class, in configureDefaultNics()
method - line 614.
The method was adding the guest nic in front of the control nic, when
deploying a router via the creation of the instance VM. When just restarting
the VPC, the guest nic was not present, which made the control nic to be at the
right place.
Steps to cover it were:
* create a VCP
* add 2 Tiers
* add 2 IPs
* add 1 ACL and open the port 22 to 0.0.0.0/0
* add 2 VMs - 1 per tier
* associate IPs with VMs
* add 2 PF rules - 1 per VM
* stop and destroy the VPC router
* add 1 new instance to 1 of the tiers
* control nic created successfully and VPC router nics fully configured!
root@r-56-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
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 0e:00:a9:fe:02:95 brd ff:ff:ff:ff:ff:ff
inet 169.254.2.149/16 brd 169.254.255.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 06:d0:e6:00:00:18 brd ff:ff:ff:ff:ff:ff
inet 192.168.23.24/24 brd 192.168.23.255 scope global eth1
inet 10.0.1.65/26 brd 10.0.1.127 scope global eth1
inet 192.168.23.28/24 brd 192.168.23.255 scope global secondary eth1
inet 192.168.23.27/24 brd 192.168.23.255 scope global secondary eth1
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 02:00:2a:e1:00:18 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 02:00:79:8d:00:10 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.1/26 brd 10.0.1.63 scope global eth3
root@r-56-VM:~#
[root@kvm2 ~]#
> Destroying VPC router results in a new unusable VPC router
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-8759
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8759
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.6.0
> Environment: ACS master/4.6 with XenServer and KVM tested
> Reporter: Remi Bergsma
> Assignee: Wilder Rodrigues
> Priority: Critical
> Fix For: 4.6.0
>
>
> Deploy VPC
> Deploy VM
> This all works fine
> Shutdown, then destroy VPC
> Expected result:
> A new VPC router is deployed that has the same functionality than before, but
> with a new router instance ID.
> Experienced result:
> VPC router is unaccessible for CloudStack due to missing link-local interface:
> root@r-7-VM:~# ifconfig -a
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:1 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:93 (93.0 B) TX bytes:93 (93.0 B)
> From a first look, the command line info seems OK.
> root@r-7-VM:/etc/cloudstack# cat cmdline.json
> {
> "config": {
> "baremetalnotificationapikey":
> "pPgegDQwez17eCbRj4Wx8IwFs543rcPpF7Gavvtys_D7w1jnAoyJ4A-21H9Bf58s1ZjC4DTVrD0BHxNA3y7agA",
>
> "baremetalnotificationsecuritykey":
> "Sxv0QbIgRTH-PkeDWBsY-GYsKz2WIz9JIyWTK16mNnIPPZ-Ozo940_8d8bSEx5pHZ4rEdxG5HQMRRcchANHuHg",
>
> "disable_rp_filter": "true",
> "dns1": "8.8.8.8",
> "domain": "cs2cloud",
> "eth1ip": "169.254.0.249",
> "eth1mask": "255.255.0.0",
> "host": "192.168.22.61",
> "name": "r-7-VM",
> "port": "8080",
> "redundant_router": "false",
> "template": "domP",
> "type": "vpcrouter",
> "vpccidr": "10.0.1.0/24"
> },
> "id": "cmdline"
> [~wilder.rodrigues] Let's have a look when you're back!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
