Sangeetha Hariharan created CLOUDSTACK-1794:
-----------------------------------------------
Summary: We are allowed to create Egress rules for Shared networks.
Key: CLOUDSTACK-1794
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1794
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.1.0
Environment: Build from 4.1
Reporter: Sangeetha Hariharan
Assignee: Jayapal Reddy
Fix For: 4.1.0
We are allowed to create Egress rules for Shared networks.
Steps to reproduce the problem:
Set up - Advanced Zone
Create a shared network.
>From Network tab , select this shared network and go to Egress tab and create
>a egress rule.
Creation of egress rule succeed.
Expected Behavior:
There is no support for egress rule in shared network. API should error out.
apilog.log
2013-03-22 16:56:54,839 INFO [cloud.api.ApiServer] (catalina-exec-16:null)
(userId=2 accountId=2 sessionId=FB9EC7CB6FF657012432A2067C3414B9)
10.217.252.128 -- GET
command=createEgressFirewallRule&response=json&sessionkey=H%2Ffj8xnB4it%2BUnoyU6Q%2FM3uT4gA%3D&protocol=tcp&cidrlist=0.0.0.0%2F0&networkid=41305c7c-4206-4b3d-a5a3-b8c64d29d1b1&startport=22&endport=22&_=1364000015912
200 { "createegressfirewallruleresponse" :
{"id":"3","jobid":"ba51e1c7-e6fc-48cf-8210-191e35a42a48"} }
2013-03-22 16:56:57,913 INFO [cloud.api.ApiServer] (catalina-exec-17:null)
(userId=2 accountId=2 sessionId=FB9EC7CB6FF657012432A2067C3414B9)
10.217.252.128 -- GET
command=queryAsyncJobResult&jobId=ba51e1c7-e6fc-48cf-8210-191e35a42a48&response=json&sessionkey=H%2Ffj8xnB4it%2BUnoyU6Q%2FM3uT4gA%3D&_=1364000019143
200 { "queryasyncjobresultresponse" :
{"accountid":"b1b53b7e-8fed-11e2-89d9-06d4460004b1","userid":"b1b5e920-8fed-11e2-89d9-06d4460004b1","cmd":"org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd","jobstatus":1,"jobprocstatus":0,"jobresultcode":0,"jobresulttype":"object","jobresult":{"firewallrule":{"id":"f4aacb15-20e1-4ea1-af3f-e600c2373527","protocol":"tcp","startport":"22","endport":"22","networkid":212,"state":"Active","cidrlist":"0.0.0.0/0","tags":[]}},"created":"2013-03-22T16:56:54-0700","jobid":"ba51e1c7-e6fc-48cf-8210-191e35a42a48"}
}
management server log:
2013-03-22 16:56:54,835 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-16:null) submit async job-56, details: AsyncJobVO {id:56,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId: 3,
cmd:
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd,
cmdOriginator: null, cmdInfo:
{"id":"3","response":"json","sessionkey":"H/fj8xnB4it+UnoyU6Q/M3uT4gA\u003d","protocol":"tcp","ctxUserId":"2","cidrlist":"0.0.0.0/0","startport":"22","_":"1364000015912","ctxAccountId":"2","networkid":"41305c7c-4206-4b3d-a5a3-b8c64d29d1b1","ctxStartEventId":"140","endport":"22"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 206915885079359,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-03-22 16:56:54,836 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) Executing
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd for
job-56
2013-03-22 16:56:54,839 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===END=== 10.217.252.128 -- GET
command=createEgressFirewallRule&response=json&sessionkey=H%2Ffj8xnB4it%2BUnoyU6Q%2FM3uT4gA%3D&protocol=tcp&cidrlist=0.0.0.0%2F0&networkid=41305c7c-4206-4b3d-a5a3-b8c64d29d1b1&startport=22&endport=22&_=1364000015912
2013-03-22 16:56:54,843 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) Sync job-56 execution on object network.212
2013-03-22 16:56:54,860 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) job
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd for
job-56 was queued, processing the queue.
2013-03-22 16:56:54,876 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) Executing sync queue item: SyncQueueItemVO {id:9,
queueId: 9, contentType: AsyncJob, contentId: 56, lastProcessMsid:
206915885079359, lastprocessNumber: 1, lastProcessTime: Fri Mar 22 16:56:54 PDT
2013, created: Fri Mar 22 16:56:54 PDT 2013}
2013-03-22 16:56:54,878 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) Schedule queued job-56
2013-03-22 16:56:54,887 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-9:job-56) Executing
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd for
job-56
2013-03-22 16:56:54,887 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-8:job-56) There is a pending process in sync queue(id: 9)
2013-03-22 16:56:54,914 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-9:job-56) Complete async job-56, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.FirewallResponse@4c3e3f94
2013-03-22 16:56:54,928 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-9:job-56) Sync queue (9) is currently empty
2013-03-22 16:56:54,930 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-9:job-56) Done executing
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd for
job-56
2013-03-22 16:56:54,930 WARN [cloud.async.AsyncJobManagerImpl]
(Job-Executor-9:job-56) Unable to unregister active job 56 from JMX monitoring
2013-03-22 16:56:55,696 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-14:null) Seq 1-2011239461: Response Received:
2013-03-22 16:56:55,697 DEBUG [agent.transport.Request] (StatsCollector-3:null)
Seq 1-2011239461: Received: { Ans: , MgmtId: 206915885079359, via: 1, Ver: v1,
Flags: 10, { GetStorageStatsAnswer } }
2013-03-22 16:56:57,902 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===START=== 10.217.252.128 -- GET
command=queryAsyncJobResult&jobId=ba51e1c7-e6fc-48cf-8210-191e35a42a48&response=json&sessionkey=H%2Ffj8xnB4it%2BUnoyU6Q%2FM3uT4gA%3D&_=1364000019143
2013-03-22 16:56:57,908 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-17:null) Async job-56 completed
--
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
