You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rajesh Battala (JIRA)" <ji...@apache.org> on 2014/07/02 10:00:47 UTC

[jira] [Created] (CLOUDSTACK-7037) Unable to add new vm/service to existing LB rule of SSL protocol

Rajesh Battala created CLOUDSTACK-7037:
------------------------------------------

             Summary: Unable to add new vm/service to existing LB rule of SSL protocol
                 Key: CLOUDSTACK-7037
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7037
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Network Controller
    Affects Versions: 4.5.0
            Reporter: Rajesh Battala
            Assignee: Rajesh Battala
            Priority: Blocker
             Fix For: 4.5.0


Exception is thrown from nitro api when try to add new vm to LB rule.
INFO  [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-20:ctx-eb12ce6b job-82) Add job-82 into job monitoring
ERROR [c.c.n.r.NetscalerResource] (DirectAgent-418:ctx-6caefe76) Failed to execute LoadBalancerConfigCommand due to
com.citrix.netscaler.nitro.exception.nitro_exception: Operation not permitted
        at com.citrix.netscaler.nitro.resource.base.base_resource.put_data(base_resource.java:693)
        at com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:196)
        at com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:180)
        at com.citrix.netscaler.nitro.resource.config.lb.lbvserver_service_binding.add(lbvserver_service_binding.java:256)
        at com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:650)
        at com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:427)
        at com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:416)
        at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293)
        at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
        at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)




--
This message was sent by Atlassian JIRA
(v6.2#6252)