Jayapal Reddy created CLOUDSTACK-8823: -----------------------------------------
Summary: Isolated network VR is failed to come up because of wrong interface order Key: CLOUDSTACK-8823 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8823 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.6.0 Reporter: Jayapal Reddy Priority: Blocker Fix For: 4.6.0 In the isolated network VR is failed to come up because it is failed to ssh to VR. Earlier the order of interfaces in the VR is as follows, which is fixed. eth0 - guest interface eth1 - link local eth2 - public . Now the order is changed due to which the sushi_configured to listen on eth1 which is public interface now on the VR. ip addr output: root@r-4-VM:~# ip a 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:01:e1 brd ff:ff:ff:ff:ff:ff inet 169.254.1.225/16 brd 169.254.255.255 scope global eth0 inet 169.254.2.106/16 brd 169.254.255.255 scope global secondary eth0 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:1b:6c:00:00:08 brd ff:ff:ff:ff:ff:ff inet 10.147.30.243/24 brd 10.147.30.255 scope global eth1 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 02:00:68:8a:00:02 brd ff:ff:ff:ff:ff:ff inet 10.1.1.1/24 brd 10.1.1.255 scope global eth2 root@r-4-VM:~# Recent interface order commit caused the regression. -- This message was sent by Atlassian JIRA (v6.3.4#6332)