[
https://issues.apache.org/jira/browse/CLOUDSTACK-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923403#comment-13923403
]
angeline shen commented on CLOUDSTACK-6198:
-------------------------------------------
Verify fix MS 10.223.130.59 CloudPlatform-QA-4.3-0.349-rhel6.3
Host xen 6.2 10.223.51.4
Subnet 1: vlan: 1230 GW: 10.223.123.1 subnet 2: vlan:
1232 GW: 10.223.123.129
Advance zone network using subnet 1 . Create a VPC . Deploy 2 Vms.
Acquire & exhaust Ip addresses from Public range of subnet 1.
2 VMs public IP from subnet 1. Create PF, Static NAT ,LB rules , ingress and
egress rules.
Add subnet 2 public range .
Acquire Ip addresses from subnet 2 Public range.
Create 2 VMs public IP {from subnet 2. Create PF, Static NAT ,LB rules ,
ingress and egress rules
Make sure all the rules (PF, Static NAT ,LB rules , ingress and egress )
created from both the public ip ranges work as expected.
In MS UI: VPC VR has 4 NICs . VPC VR > Ifconfig has 4 NICs eth0
eth1 eth2 eth3
Iptables-save
Test case1:
Restart VPC
Test result after VPC restart:
No changes to VPC VR NIC entries, ifconfig entries, iptables content
PF, Static NAT ,LB rules , ingress and egress rules from both the public ip
ranges All still work
Create VPC 2 and repeat same test. Restart VPC 2.
Test result after VPC 2 restart: successful
> VPC: secondary public ip address (from diff Vlan range) doesn't get
> reprogrammed on the VR upon VPC/Network/VR resetart
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6198
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6198
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.3.0
> Reporter: Alena Prokharchyk
> Assignee: Alena Prokharchyk
> Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: management-server.log.2014-03-05.gz,
> management-server.log.gz, v1.png, v2.png, v3.png
>
>
> Regression bug.
> Steps to reproduce:
> 1. Create vpc and launch a vm in one tear.
> 2. vpc source ip address is from one subnet (ex: 10.147.52.1)
> 3. Acquire another public ip address from new public subnet.
> 4. create static nat on it to plug the nic on VR.
> 5. Now the VR has link local nic, guest nic, source nat ip nic and second
> public range nic.
> 6. Restart the vpc.
> 7. After restart there is no source nat nic.
> 8. If we restart vpc again observed that more nics are missed.
> I do observe the HUGE problem in 4.3 in
> VpcVirtualNetworkApplianceManager.java createVpcRouterNetworks() method. In
> 4.2 we used to store vm's nics in the ArrayList datastructure:
> List<Pair<NetworkVO, NicProfile>> networks = new ArrayList<Pair<NetworkVO,
> NicProfile>>(4);
> ArrayList does allow duplicates.
> Then in 4.3 the datastructure was changed to LinkedHashMap that doesn't allow
> duplicates:
> LinkedHashMap<Network, NicProfile> networks = new LinkedHashMap<Network,
> NicProfile>(4);
> To fix the problem, the datastructure has to be changed to
> LinkedHashMap<Network, List<NicProfile>>. It has to be changed all the way up
> to VirtualMachienManagerImpl where the nics are being passed to.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
