[
https://issues.apache.org/jira/browse/CLOUDSTACK-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751072#comment-13751072
]
Jayapal Reddy commented on CLOUDSTACK-4303:
-------------------------------------------
There is problem in python script in calling create network offering API.
If you found some test case failing, please try manually to cross verify the
behaviour.
Observed in DB the network offering set default egress policy to 1.
In API egressdefaultpolicy=false is not passed.
2013-08-27 12:49:24,309 DEBUG [cloud.api.ApiServlet]
(1493260295@qtp-1633857122-5:null) ===END=== 10.252.192.18 -- GET
apiKey=b6DmUS4LbUoltaGuprax050KWP2Hy4Ggm-LpTNjqV0SJxTi0Eb9wtDnlwAkHMkQ5BB3
aNWfjXYFgI1sxhQsh4g&serviceProviderList%5B2%5D.provider=VirtualRouter&serviceProviderList%5B5%5D.service=Dhcp&displaytext=Network+offering-VR+services-PUKGUM&serviceProviderList%5B0%5D.service=Us
erData&serviceProviderList%5B4%5D.provider=VirtualRouter&serviceProviderList%5B1%5D.provider=VirtualRouter&availability=Optional&conservemode=True&serviceProviderList%5B3%5D.service=Dns&servicePr
oviderList%5B5%5D.provider=VirtualRouter&response=json&serviceProviderList%5B0%5D.provider=VirtualRouter&serviceProviderList%5B8%5D.provider=VirtualRouter&serviceProviderList%5B1%5D.service=Lb&se
rviceProviderList%5B4%5D.service=Firewall&supportedservices=Dhcp%2CDns%2CSourceNat%2CPortForwarding%2CVpn%2CFirewall%2CLb%2CUserData%2CStaticNat&traffictype=GUEST&serviceProviderList%5B6%5D.provi
der=VirtualRouter&serviceProviderList%5B8%5D.service=StaticNat&serviceProviderList%5B3%5D.provider=VirtualRouter&name=Network+offering-VR+services-34DXO9&guestiptype=Isolated&serviceProviderList%
5B7%5D.provider=VirtualRouter&serviceProviderList%5B7%5D.service=SourceNat&serviceProviderList%5B2%5D.service=PortForwarding&serviceProviderList%5B6%5D.service=Vpn&command=createNetworkOffering&s
ignature=iZVfLOqMCnqqjdh2njj88omyIhw%3D&specifyVlan=False
> [Automation] test_egress_fw_rules test cases failed to except script and
> tests failed
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4303
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4303
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Infra, Network Controller
> Reporter: Rayees Namathponnan
> Assignee: Jayapal Reddy
> Priority: Critical
>
> Test cases from integration.component.test_egress_fw_rules.TestEgressFWRules
> fails
> test cases expecting script @ /tmp/expect_scrip, this should be handled in
> test case,
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_egress_fw_rules.py",
> line 51, in test_wrap_exception_log
> raise e
> Script result is ['bash: /tmp/expect_script.exp: /usr/bin/expect: bad
> interpreter: No such file or directory'] is not matching with ['100']
> -------------------- >> begin captured logging << --------------------
> testclient.testcase.TestEgressFWRules: DEBUG: Creating network with network
> offering: 0bd6212f-b34c-4f7a-a84f-0c172bee6ac8
> testclient.testcase.TestEgressFWRules: DEBUG: Created network with ID:
> ef2626c2-6849-43e7-8418-0c89ed528d62
> testclient.testcase.TestEgressFWRules: DEBUG: Deploying instance in the
> account: test-SSFX20
> testclient.testcase.TestEgressFWRules: DEBUG: Deployed instance in account:
> test-SSFX20
> testclient.testcase.TestEgressFWRules: DEBUG: expect_script>>
> #!/usr/bin/expect
> spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o
> LogLevel=quiet -i /root/.ssh/id_rsa.cloud -p 3922 root@169.254.3.141
> expect "root@r-342-QA:~#"
> send "ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o
> LogLevel=quiet root@10.1.1.215 ping -c 1 www.google.com; exit $?
> "
> expect "root@10.1.1.215's password: "
> send "password
> "
> interact
> <<expect_script
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
