[CLOUDSTACK-6041] [Automation] Creating port forwarding rule for secondary IP (ranges - 172.16.x.x and 192.168.x.x) in Shared Network fails with "Invalid vm ip address"

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 4.4.0
• Fix Version/s: 4.4.0
• Component/s: Network Controller
• Security Level: Public (Anyone can view this level - this is the default.)
• Labels: automation
• Environment: Observed on VMware. Not yet verified on Xen and KVM.
• Assignee: Unassigned
• Reporter: Gaurav Aradhye
• Created: 06/Feb/14 12:58
• Updated: 06/Feb/14 13:03
• Resolved: 06/Feb/14 13:03

Description

This works for 10.x.x.x

Steps to reproduce:

1) Create a shared network (PF enabled) with range in 172.16.x.x or 192.168.x.x
2) Deploy a VM in this and add secondary IP to the default NIC of VM
3) Acquire a public IP in the shared network and try to create a NAT rule using this public ip to the secondary IP of VM

Operation fails.

Issue Links

• is duplicated by: CLOUDSTACK-6040 Failed to configure PF on vm secondary ip for shared network