If a zone has two public IPs range in different VLANs, ACS doesn't create a second northbound NIC if needed

[msinhore]

ISSUE TYPE

VR

CLOUDSTACK VERSION

4.11.3

CONFIGURATION

• 2 public IPs ranges configured in the same zone using different VLANs.

SUMMARY

ACS is configured with 2 public IPs ranges in different VLANs.
If a user creates a network (where the snat IP is from one of the public IP ranges) and request a new public IP address (ACS deliver from the another IP range), this second IP will be in the same VLAN of the first one, since the ACS doesn't create a second northbound (public) NIC in the VR.

EXPECTED RESULTS

2 northbound NICs each connected in the right VLAN 

ACTUAL RESULTS

The second IP is configured on the same primary public IP NIC and doesn't have network access.

[weizhouapache]

@msinhore
cloudstack will plug a new nic in virtual routers when the ip is in use.
For example, enable static nat, create load balancer rule or port forwarding rule.
If ip is Allocated but not in use, there is no nic for the ip/vlan in virtual routers.

This is not an issue I think.

[msinhore]

@weizhouapache
When was added a new NIC, it was configured a static NAT too and looking inside the VR, the second NIC wasn't created. Considering this behavior, I presume it is a bug.

[weizhouapache]

@msinhore
which hypervisor ?
isolated network or vpc ?
if kvm, linux bridge or openvswitch ?
is vm running ?

[msinhore]

@weizhouapache

• XenServer 7.2
• VPC
• with VMs running.

[weizhouapache]

@msinhore
I cannot reproduce the issue on kvm (linux bridge or ovs)
it might be caused by some code in xenserver plugin.

It might be related to issue #3179
I have uploaded some commits to https://github.com/ustcweizhou/cloudstack/commits/4.14.0-vpc-vr-issues
not sure if it fixes your issue

[andrijapanicsb]

This works fine in 4.13 per my memory (from a few days ago). Can you test @msinhore ?

[andrijapanicsb]

I couldn't reproduce this on master:
ACS 4.14 (master)
XS 7.1

Configured Static NAT from 1.1.1.4 to the internal VM:

@msinhore let me know if it's possible to test master or 4.13 - otherwise, I would close this issue as not applicable any more (I assume it was fixed in the meantime from 4.11 until now)

[msinhore]

@andrijapanicsb
I am closing this issue, as you applied the needed tests and it isn't reproduced anymore.