You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/12/14 01:03:07 UTC
[jira] [Created] (CLOUDSTACK-5505) [Automation] Private gateway not
getting programmed in VPC router
Rayees Namathponnan created CLOUDSTACK-5505:
-----------------------------------------------
Summary: [Automation] Private gateway not getting programmed in VPC router
Key: CLOUDSTACK-5505
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5505
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Network Controller
Affects Versions: 4.3.0
Environment: KVM
Branch : 4.3
Reporter: Rayees Namathponnan
Priority: Critical
Fix For: 4.3.0
This issue found as part of regression automation
integration.component.test_vpc_vms_deployment.TestVMDeployVPC.test_07_delete_network_with_rules
Test cases performing below steps
1726 # Validate the following
1727 # 1. Create a VPC with cidr - 10.1.1.1/16
1728 # 2. Add network1(10.1.1.1/24) and network2(10.1.2.1/24) to this VPC.
1729 # 3. Deploy vm1 and vm2 in network1 and vm3 and vm4 in network2.
1730 # 4. Create a PF /Static Nat/LB rule for vms in network1.
1731 # 5. Create a PF /Static Nat/LB rule for vms in network2.
1732 # 6. Create ingress network ACL for allowing all the above rules from
1733 # public ip range on network1 and network2.
1734 # 7. Create egress network ACL for network1 and network2 to access
1735 # google.com.
1736 # 8. Create a private gateway for this VPC and add a static route to
1737 # this gateway
1738 # 9. Create a VPN gateway for this VPC and add a static route to this
1739 # gateway.
1740 # 10. Make sure that all the PF,LB, Static NAT rules work as expected
1741 # 11. Make sure that we are able to access google from all user Vms
1742 # 12. Make sure that the newly added private gateway's and VPN
1743 # gateway's static routes work as expected.
1744 # Steps:
1745 # 1. Delete the 1st network.
1746 # 2. Delete account
1747 # Validations:
1748 # 1. As part of network deletion all the resources attached with
1749 # network should get deleted. All other VMs and rules shall work as
1750 # expected
1751 # 2. All the resources associated with account should be deleted
Steps to reproduce
Step 1 : Create advanced zone in KVM
Step 2 : Create VPC
Step 3 : create 2 network inside
Step 4 : Create Private Gateway
Step 5 : Add static route
Result
Failed to add static route; if you look the message.log in side the VPC router, you can see Private Gateway itself not programmed (attaching all log, please check router log r-706-QA)
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160401] pci 0000:00:0b.0: BAR 6: assigned [mem 0x08040000-0x0804ffff pref]
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160406] pci 0000:00:0b.0: BAR 1: assigned [mem 0x08013000-0x08013fff]
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160443] pci 0000:00:0b.0: BAR 0: assigned [io 0x1060-0x107f]
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160483] pci 0000:00:00.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160486] pci 0000:00:00.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160536] pci 0000:00:01.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160539] pci 0000:00:01.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160584] ata_piix 0000:00:01.1: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160587] ata_piix 0000:00:01.1: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160637] uhci_hcd 0000:00:01.2: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160641] uhci_hcd 0000:00:01.2: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160818] piix4_smbus 0000:00:01.3: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160822] piix4_smbus 0000:00:01.3: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160872] pci 0000:00:02.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.160875] pci 0000:00:02.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163389] virtio-pci 0000:00:03.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163393] virtio-pci 0000:00:03.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163430] virtio-pci 0000:00:04.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163433] virtio-pci 0000:00:04.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163488] virtio-pci 0000:00:05.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163491] virtio-pci 0000:00:05.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163532] virtio-pci 0000:00:06.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163535] virtio-pci 0000:00:06.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163581] virtio-pci 0000:00:07.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163584] virtio-pci 0000:00:07.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163640] virtio-pci 0000:00:08.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163644] virtio-pci 0000:00:08.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163795] virtio-pci 0000:00:09.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163798] virtio-pci 0000:00:09.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163855] pci 0000:00:0b.0: no hotplug settings from platform
Dec 13 23:45:39 r-706-QA kernel: [ 2365.163858] pci 0000:00:0b.0: using default PCI settings
Dec 13 23:45:39 r-706-QA kernel: [ 2365.166368] virtio-pci 0000:00:0b.0: enabling device (0000 -> 0003)
Dec 13 23:45:39 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 0 seconds
Dec 13 23:45:40 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 1 seconds
Dec 13 23:45:41 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 2 seconds
Dec 13 23:45:42 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 3 seconds
Dec 13 23:45:43 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 4 seconds
Dec 13 23:45:44 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 5 seconds
Dec 13 23:45:45 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 6 seconds
Dec 13 23:45:46 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 7 seconds
Dec 13 23:45:47 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 8 seconds
Dec 13 23:45:48 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 9 seconds
Dec 13 23:45:49 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 10 seconds
Dec 13 23:45:50 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 11 seconds
Dec 13 23:45:51 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 12 seconds
Dec 13 23:45:52 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 13 seconds
Dec 13 23:45:53 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 14 seconds
Dec 13 23:45:54 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 15 seconds
Dec 13 23:45:55 r-706-QA cloud: vpc_ipassoc.sh:Waiting for interface ethnull to appear, 16 seconds
Dec 13 23:45:56 r-706-QA cloud: vpc_ipassoc.sh:interface ethnull never appeared
Dec 13 23:45:56 r-706-QA cloud: vpc_ipassoc.sh:Adding ip 10.2.3.2 on interface ethnull
Dec 13 23:45:56 r-706-QA cloud: vpc_ipassoc.sh:Add routing 10.2.3.2 on interface ethnull
Dec 13 23:45:57 r-706-QA cloud: vpc_privategw_acl.sh: enter apply acl rules on private gateway interface : eth4, inbound::all:0:0:0.0.0.0/0
Dec 13 23:45:57 r-706-QA cloud: vpc_privategw_acl.sh: exit apply acl rules for private gw interface : eth4
Dec 13 23:45:57 r-706-QA cloud: vpc_privategw_acl.sh: successful in applying acl rules on private gateway interface : eth4
Dec 13 23:45:57 r-706-QA cloud: vpc_privategw_acl.sh: enter apply acl rules on private gateway interface : eth4, inbound::all:0:0:0.0.0.0/0
Dec 13 23:45:57 r-706-QA cloud: vpc_privategw_acl.sh: exit apply acl rules for private gw interface : eth4
Dec 13 23:45:57 r-706-QA cloud: vpc_privategw_acl.sh: successful in applying acl rules on private gateway interface : eth4
Dec 13 23:45:57 r-706-QA cloud: vpc_privategw_acl.sh: deleting backup on private gateway interface : eth4
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)