date:20130802


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727642#comment-13727642
 ] 

Gaurav Aradhye commented on CLOUDSTACK-4028:


[~nitinme] Are you working on this?

 [Automation] Null Pointer Exception observed while creating template
 

 Key: CLOUDSTACK-4028
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4028
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: Rayees Namathponnan
Assignee: Nitin Mehta
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


  This issue observed during regression test resource_limits 
 Below null pointer exception observed in MS log
 9b-483c-902f-167fb01cd2f1,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,id:1,poolTy
 pe:NetworkFilesystem,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049}},name:ROOT-453,size:147456,path:d57149f0-9932-49dd-b4f0-
 4dc286c95283,volumeId:509,vmName:i-251-453-QA,accountId:251,format:QCOW2,id:509,hypervisorType:KVM}},destTO:{org.apache.cloudstack.storage.to.TemplateObj
 ectTO:{path:template/tmpl/251/226,uuid:b884ddac-ba48-4946-8266-ce10fe40ab7d,id:226,format:RAW,accountId:251,hvm:true,displayText:Cent
  OS Template,image
 DataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary,_role:Image}},name:2ac0ba622-e789-354d-b69b-d3b40de4
 5701,hypervisorType:KVM}},executeInSequence:false,wait:10800}}] }
 2013-07-05 03:29:45,456 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-6:null) Seq 4-297077579: Processing:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10
 , 
 [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:java.lang.NullPointerException,wait:0}}]
  }
 2013-07-05 03:29:45,456 DEBUG [agent.transport.Request] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) Seq 
 4-297077579: Received:  { Ans: , MgmtId: 2906
 6118877352, via: 4, Ver: v1, Flags: 10, { CopyCmdAnswer } }
 2013-07-05 03:29:45,464 DEBUG [cloud.template.TemplateManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) Failed 
 to create templatejava.lang.NullPointerException
 2013-07-05 03:29:45,560 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to create 
 templatejava.lang.NullPointerException
 at 
 com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1372)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-05 03:29:45,561 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) 
 Complete async job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ], 
 jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to 
 create templatejava.lang.NullPointerException
 2013-07-05 03:29:46,044 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===START===  10.223.240.194 -- GET  
 signature=d5oNqmtHPLw0QTpehRKp0O0OhPo%3DapiKey=p4VwLP4mhd90QBeBxwJ39YurvbLtOuGc-qgcm4pN2B58bSZJZgGJezD5V1GR6vx38YPDGF4-h7_R0WqxvUkGEAcommand=queryAsyncJobResultresponse=jsonjobid=f7075411-b89e-4fd0-804d-e9af80b856ce
 2013-07-05 03:29:46,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===END===  10.223.240.194 -- GET

[jira] [Updated] (CLOUDSTACK-4046) Can't edit global settings

2013-08-02 Thread Nicolas Lamirault (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Lamirault updated CLOUDSTACK-4046:
--

Attachment: CloudStack_GlobalSettingsOK3.png
CloudStack_GlobalSettingsOK2.png
CloudStack_GlobalSettingsOK.png

 Can't edit global settings
 --

 Key: CLOUDSTACK-4046
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.1.0
Reporter: Nicolas Lamirault
Priority: Minor
 Attachments: CloudStack_GlobalSettingsOK2.png, 
 CloudStack_GlobalSettingsOK3.png, CloudStack_GlobalSettingsOK.png


 Hi,
 in our Cloudstack, we've got a strange behavior.
 gradually as one moves down the settings, the Edit box disappears.
 See screenshots.
 Regards

--
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

[jira] [Resolved] (CLOUDSTACK-3926) portable public ip range test is failing because it is not able to disassociate the public IP.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam resolved CLOUDSTACK-3926.


Resolution: Fixed

 portable public ip range test is failing because it is not able to 
 disassociate the public IP.
 --

 Key: CLOUDSTACK-3926
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3926
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Prasanna Santhanam
Priority: Blocker
 Fix For: 4.2.0


 Steps to reproduce:
 ==
 1. create portable public ip range
 2. acquire ip.
 3. disassociate the ip.
 Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'ip 
 address is used for source nat purposes and can not be disassociated.'}
   begin captured stdout  -
 marvin.integration.lib.base.PublicIPAddress instance at 0x3834e18
 -  end captured stdout  --
 Stacktrace
 Traceback (most recent call last):
   File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
 testMethod()
   File /root/cloudstack/test/integration/smoke/test_portable_publicip.py, 
 line 235, in test_createPortablePublicIPAcquire
 ip_address.delete(self.api_client)
   File 
 /usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py, line 
 1110, in delete
 apiclient.disassociateIpAddress(cmd)
   File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 879, in disassociateIpAddress
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py, line 
 230, in marvin_request
 response = self.poll(asyncJobId, response_type)
   File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py, line 
 91, in poll
 asyncquery, asyncResonse.jobresult)
 cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode : 
 530, errortext : u'ip address is used for source nat purposes and can not be 
 disassociated.'}
   begin captured stdout  -
 marvin.integration.lib.base.PublicIPAddress instance at 0x3834e18
 -  end captured stdout  --
 I'll provide detailed log in a while

--
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

[jira] [Created] (CLOUDSTACK-4046) Can't edit global settings

2013-08-02 Thread Nicolas Lamirault (JIRA)

Nicolas Lamirault created CLOUDSTACK-4046:
-

 Summary: Can't edit global settings
 Key: CLOUDSTACK-4046
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.1.0
Reporter: Nicolas Lamirault
Priority: Minor
 Attachments: CloudStack_GlobalSettingsOK2.png, 
CloudStack_GlobalSettingsOK3.png, CloudStack_GlobalSettingsOK.png

Hi,
in our Cloudstack, we've got a strange behavior.
gradually as one moves down the settings, the Edit box disappears.
See screenshots.
Regards

--
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

[jira] [Updated] (CLOUDSTACK-4025) [Automation] NullPointer Exception observed while destroying the VM during starting state

2013-08-02 Thread Ram Ganesh (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ram Ganesh updated CLOUDSTACK-4025:
---

Assignee: Likitha Shetty  (was: Rajesh Battala)

 [Automation] NullPointer Exception observed while destroying the VM during 
 starting state
 -

 Key: CLOUDSTACK-4025
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4025
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Management Server
Affects Versions: 4.2.0
 Environment: 4.2 build
 KVM 
Reporter: Rayees Namathponnan
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 Below null pointer observed in MS log during regression automation run,  i 
 dont know which test case cause this; from the log, looks like its happening 
 destroying account while vm is in  that account is in start state 
 2013-07-05 10:03:07,296 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Lock 
 is released for network id 755 as
 a part of network implement
 2013-07-05 10:03:07,296 ERROR [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Failed 
 to start instance VM[User|3384
 7e84-b811-4132-aa30-12b65385d397]
 java.lang.NullPointerException
 at 
 com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2081)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:932)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:624)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3408)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1954)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-05 10:03:07,299 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) 
 Cleaning up resources for the vm 
 VM[User|33847e84-b811-4132-aa30-12b65385d397] in Starting state
 2013-07-05 10:03:07,300 DEBUG [agent.transport.Request] 
 (Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Seq 
 4-1845366559: Sending  { Cmd , MgmtId: 29066118877352, via: 4, Ver: v1, 
 Flags: 100011, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:false,vmName:i-735-1074-QA,wait:0}}]
  }
 2013-07-05 10:03:07,534 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-8:null) Seq 4-1845366559: Processing:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.StopAnswer:{vncPort:0,result:true,wait:0}}] }
 2013-07-05 10:03:07,535 DEBUG [agent.transport.Request] 
 (Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Seq 
 4-1845366559: Received:  { Ans: , MgmtId: 29066118877352, via: 4, Ver: v1, 
 Flags: 10, { StopAnswer } }

--
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

[jira] [Commented] (CLOUDSTACK-3865) [Automation] Test cases failed due miss match in template size


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727646#comment-13727646
 ] 

Prasanna Santhanam commented on CLOUDSTACK-3865:


Ok -  I've changed the infra to enable kvm snapshotting in the KVM setup. If 
you could show us the new logs for the tests I can debug this before the infra 
picks this up.

https://github.com/vogxn/cloud-autodeploy/commit/c734c0a9450f9a66c8eabe9fd570f6234a875a71

 [Automation] Test cases failed due miss match in template size 
 ---

 Key: CLOUDSTACK-3865
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3865
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.2.0
 Environment: Automation
Reporter: Rayees Namathponnan
Assignee: Rayees Namathponnan
Priority: Critical
 Fix For: 4.2.0


 Test cases failed to miss match in template size
 integration.component.test_blocker_bugs.TestTemplates.test_02_check_size_snapshotTemplate
  and 
 integration.component.test_blocker_bugs.TestTemplates.test_02_check_size_snapshotTemplate
 Observed below error 
 Check if size of snapshot and template matches
   begin captured logging  
 testclient.testcase.TestTemplates: DEBUG: Created snapshot with ID: 
 91340fe1-8697-42ec-a548-542365c9831f
 testclient.testcase.TestTemplates: DEBUG: Created template from snapshot with 
 ID: fd7402db-038c-4b0f-ad09-461a0c17096f
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
 testMethod()
   File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_blocker_bugs.py, 
 line 884, in test_02_check_size_snapshotTemplate
 Check if size of snapshot and template matches
   File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual
 assertion_func(first, second, msg=msg)
   File /usr/local/lib/python2.7/unittest/case.py, line 487, in 
 _baseAssertEqual
 raise self.failureException(msg)
 Check if size of snapshot and template matches
   begin captured logging  
 testclient.testcase.TestTemplates: DEBUG: Created snapshot with ID: 
 91340fe1-8697-42ec-a548-542365c9831f
 testclient.testcase.TestTemplates: DEBUG: Created template from snapshot with 
 ID: fd7402db-038c-4b0f-ad09-461a0c17096f
 -  end captured logging  -

--
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

[jira] [Commented] (CLOUDSTACK-4005) snapshot create on a volume created on cluster scoped primary storage is failing


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727645#comment-13727645
 ] 

Prasanna Santhanam commented on CLOUDSTACK-4005:


Thanks - The test infra will pick up this change in the next run
https://github.com/vogxn/cloud-autodeploy/commit/c734c0a9450f9a66c8eabe9fd570f6234a875a71

 snapshot create on a volume created on cluster scoped primary storage is 
 failing
 

 Key: CLOUDSTACK-4005
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4005
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Snapshot
Affects Versions: 4.2.0
 Environment: KVM
Reporter: Srikanteswararao Talluri
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.2.0


 Steps to reproduce:
 ==
 1. create a snapshot of a data/root volume on a KVM deployment.
  ===START===  10.101.255.7 -- GET  
 command=createSnapshotvolumeid=72667eaf-859e-4639-b0c3-29cf5fa4bb6aresponse=jsonsessionkey=%2Ffgph8eXl%2BeIzsdyOBQZp9jAEBQ%3D_=1375349453994
 2013-08-01 20:25:25,065 ERROR [cloud.api.ApiServer] (catalina-exec-22:null) 
 unhandled exception executing api command: createSnapshot
 com.cloud.utils.exception.CloudRuntimeException: KVM Snapshot is not 
 supported on cluster: 1
   at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.supportedByHypervisor(SnapshotManagerImpl.java:943)
   at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.allocSnapshot(SnapshotManagerImpl.java:1112)
   at 
 com.cloud.storage.VolumeManagerImpl.allocSnapshot(VolumeManagerImpl.java:2696)
   at 
 org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.create(CreateSnapshotCmd.java:155)
   at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:104)
   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:460)
   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
   at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
   at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
   at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
   at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
   at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
   at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
   at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
   at 
 org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
   at 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:679)
 2013-08-01 20:25:25,068 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===END===  10.101.255.7 -- GET  
 command=createSnapshotvolumeid=72667eaf-859e-4639-b0c3-29cf5fa4bb6aresponse=jsonsessionkey=%2Ffgph8eXl%2BeIzsdyOBQZp9jAEBQ%3D_=1375349453994

--
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

[jira] [Comment Edited] (CLOUDSTACK-3954) HA with Security Groups and ping disabled will cause split-brian

2013-08-02 Thread Lennert den Teuling (JIRA)

[
https://issues.apache.org/jira/browse/CLOUDSTACK-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727573#comment-13727573
]

Lennert den Teuling edited comment on CLOUDSTACK-3954 at 8/2/13 12:56 PM:
--

I would like to add, that over a period of time a split-brain will eventually
occur, even if one of the VMs allows ping. The VMs which allow ping will not be
started on another host, VMs who don't will be restarted even when they are
running.

was (Author: lennert):
I would like to add, that over a period of time a split-brain will
eventually occur, even if one of the VMs allows ping. The VMs which allow ping
will not be started on another host, VMs who don't will be restarted even when
they are running.

So if you use security groups under KVM i would recommend, turning on ping for
_every_ VM as soon as possible.

HA with Security Groups and ping disabled will cause split-brian

Key: CLOUDSTACK-3954
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3954
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM
Affects Versions: 4.1.0
Environment: Tested this with CS 4.1 on Ubuntu, but will probably
exist in other versions
Reporter: Lennert den Teuling
Priority: Critical

We found out that when running CS 4.1 on KVM with Security Groups enabled +
ping disabled (default) will cause a split-brain when agent crashes.
How to reproduce:
1. Setup a Basic Zone with SG enabled
2. Create one or multiple HA-enabled VMs with a security group which does
not allow ping (by default).
3. Kill the agent on one of the hosts
When you do this, the HA component on the management server will restart all
VMs on another node, even when they are running and the VM host is still
pingable. This will likely corrupt all VMs on the host where the agent was
stopped/killed.
We had some issues with libvirt causing the agent to disconnect. Luckily some
VMs allowed ping so nothing bad happened.
Temporary fix:
Ensure at least one of the running VMs on each hosts allows ping, so the HA
manager will be able to ping it and will not HA the host.
I'm not sure yet why this happens, but wanted to file this bug so people can
take necessary preparations.

--
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

[jira] [Commented] (CLOUDSTACK-4028) [Automation] Null Pointer Exception observed while creating template

2013-08-02 Thread Nitin Mehta (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727647#comment-13727647
 ] 

Nitin Mehta commented on CLOUDSTACK-4028:
-

4.2 setup is not coming up so I am not able to make any progress on this. Why 
do you ask ?

 [Automation] Null Pointer Exception observed while creating template
 

 Key: CLOUDSTACK-4028
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4028
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: Rayees Namathponnan
Assignee: Nitin Mehta
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


  This issue observed during regression test resource_limits 
 Below null pointer exception observed in MS log
 9b-483c-902f-167fb01cd2f1,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,id:1,poolTy
 pe:NetworkFilesystem,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049}},name:ROOT-453,size:147456,path:d57149f0-9932-49dd-b4f0-
 4dc286c95283,volumeId:509,vmName:i-251-453-QA,accountId:251,format:QCOW2,id:509,hypervisorType:KVM}},destTO:{org.apache.cloudstack.storage.to.TemplateObj
 ectTO:{path:template/tmpl/251/226,uuid:b884ddac-ba48-4946-8266-ce10fe40ab7d,id:226,format:RAW,accountId:251,hvm:true,displayText:Cent
  OS Template,image
 DataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary,_role:Image}},name:2ac0ba622-e789-354d-b69b-d3b40de4
 5701,hypervisorType:KVM}},executeInSequence:false,wait:10800}}] }
 2013-07-05 03:29:45,456 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-6:null) Seq 4-297077579: Processing:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10
 , 
 [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:java.lang.NullPointerException,wait:0}}]
  }
 2013-07-05 03:29:45,456 DEBUG [agent.transport.Request] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) Seq 
 4-297077579: Received:  { Ans: , MgmtId: 2906
 6118877352, via: 4, Ver: v1, Flags: 10, { CopyCmdAnswer } }
 2013-07-05 03:29:45,464 DEBUG [cloud.template.TemplateManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) Failed 
 to create templatejava.lang.NullPointerException
 2013-07-05 03:29:45,560 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to create 
 templatejava.lang.NullPointerException
 at 
 com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1372)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-05 03:29:45,561 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) 
 Complete async job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ], 
 jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to 
 create templatejava.lang.NullPointerException
 2013-07-05 03:29:46,044 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===START===  10.223.240.194 -- GET  
 signature=d5oNqmtHPLw0QTpehRKp0O0OhPo%3DapiKey=p4VwLP4mhd90QBeBxwJ39YurvbLtOuGc-qgcm4pN2B58bSZJZgGJezD5V1GR6vx38YPDGF4-h7_R0WqxvUkGEAcommand=queryAsyncJobResultresponse=jsonjobid=f7075411-b89e-4fd0-804d-e9af80b856ce
 2013-07-05 03:29:46,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===END===  10.223.240.194 -- GET

[jira] [Resolved] (CLOUDSTACK-2921) Fix stopped_vm testcases


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam resolved CLOUDSTACK-2921.


Resolution: Fixed

 Fix stopped_vm testcases 
 -

 Key: CLOUDSTACK-2921
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2921
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Reporter: Girish Shilamkar
Assignee: Prasanna Santhanam

 Fix test_stopped_vm testcases failures
 http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/23/suite=test_stopped_vm/testReport/?

--
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

[jira] [Created] (CLOUDSTACK-4047) [sM][VMWare][ZWPS]: no need of storage migration while migrating VM when the root volume is on zone wide primary storage

2013-08-02 Thread Srikanteswararao Talluri (JIRA)

Srikanteswararao Talluri created CLOUDSTACK-4047:


 Summary: [sM][VMWare][ZWPS]: no need of storage migration while 
migrating VM when the root volume is on zone wide primary storage 
 Key: CLOUDSTACK-4047
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4047
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Storage Controller
Affects Versions: 4.2.0
 Environment: VMWARE, zone wide primary storage
Reporter: Srikanteswararao Talluri
Priority: Critical
 Fix For: 4.2.0


Steps to reproduce:
==
1. On a VMWare deployment with only zone wide primary storage, Issue 
findhostsformigration API
It marks the isstoragemotionrequired=true in the findHostsForMigration API 
response thought storagemigration is not required. when you actually use UI to 
migrate VM it 

{ findhostsformigrationresponse : { count:1 ,host : [  
{id:668f9bcc-a645-4a64-96d2-b19c885448b9,name:10.147.40.21,state:Up,type:Routing,ipaddress:10.147.40.21,zoneid:c78cbdfb-d138-4950-9af8-db478b60a3fb,zonename:sm,podid:0d491fa6-cb78-4964-bd22-de0793a47029,podname:pod,version:4.2.0-SNAPSHOT,hypervisor:VMware,cpunumber:4,cpuspeed:2394,cpuallocated:0%,cpuused:0.23%,cpuwithoverprovisioning:9576.0,networkkbsread:0,networkkbswrite:0,memorytotal:17169539072,memoryallocated:0,memoryused:1099928,capabilities:hvm,lastpinged:1970-01-16T18:37:03+0530,managementserverid:7363452993625,clusterid:ab7f3e99-f3e3-4c27-ac24-39f20f8fa262,clustername:10.147.60.13/sm/smclus1,clustertype:ExternalManaged,islocalstorageactive:false,created:2013-08-02T21:57:07+0530,events:HostDown;
 Remove; ManagementServerDown; ShutdownRequested; AgentDisconnected; Ping; 
PingTimeout; AgentConnected; 
StartAgentRebalance,suitableformigration:true,requiresStorageMotion:true,resourcestate:Enabled,hypervisorversion:5.1,hahost:false,jobstatus:0}
 ] } 

--
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

[jira] [Updated] (CLOUDSTACK-3828) [Automation ]test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated failed to delete network


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye updated CLOUDSTACK-3828:
---

Assignee: (was: Gaurav Aradhye)

 [Automation ]test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated failed to 
 delete network 
 

 Key: CLOUDSTACK-3828
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3828
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.2.0
 Environment: Automation 
Reporter: Rayees Namathponnan
 Fix For: 4.2.0


 Test case component/test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated 
 failed,  test case failed to delete network, observed below error in log
 Error Message
 Warning: Exception during cleanup : Execute cmd: deletenetworkoffering 
 failed, due to: errorCode: 431, errorText:Can't delete network offering 51 as 
 its used by 1 networks. To make the network offering unavaiable, disable it
 Stacktrace
 Traceback (most recent call last):
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 227, in 
 run
 self.tearDown()
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 350, in 
 tearDown
 self.teardownContext(ancestor)
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 366, in 
 teardownContext
 try_run(context, names)
   File /usr/local/lib/python2.7/site-packages/nose/util.py, line 469, in 
 try_run
 return func()
   File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_vpc_vm_life_cycle.py,
  line 1790, in tearDownClass
 raise Exception(Warning: Exception during cleanup : %s % e)
 Exception: Warning: Exception during cleanup : Execute cmd: 
 deletenetworkoffering failed, due to: errorCode: 431, errorText:Can't delete 
 network offering 51 as its used by 1 networks. To make the network offering 
 unavaiable, disable it

--
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

[jira] [Commented] (CLOUDSTACK-3828) [Automation ]test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated failed to delete network


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727650#comment-13727650
 ] 

Gaurav Aradhye commented on CLOUDSTACK-3828:


Fixed by Sheng

 [Automation ]test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated failed to 
 delete network 
 

 Key: CLOUDSTACK-3828
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3828
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.2.0
 Environment: Automation 
Reporter: Rayees Namathponnan
 Fix For: 4.2.0


 Test case component/test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated 
 failed,  test case failed to delete network, observed below error in log
 Error Message
 Warning: Exception during cleanup : Execute cmd: deletenetworkoffering 
 failed, due to: errorCode: 431, errorText:Can't delete network offering 51 as 
 its used by 1 networks. To make the network offering unavaiable, disable it
 Stacktrace
 Traceback (most recent call last):
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 227, in 
 run
 self.tearDown()
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 350, in 
 tearDown
 self.teardownContext(ancestor)
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 366, in 
 teardownContext
 try_run(context, names)
   File /usr/local/lib/python2.7/site-packages/nose/util.py, line 469, in 
 try_run
 return func()
   File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_vpc_vm_life_cycle.py,
  line 1790, in tearDownClass
 raise Exception(Warning: Exception during cleanup : %s % e)
 Exception: Warning: Exception during cleanup : Execute cmd: 
 deletenetworkoffering failed, due to: errorCode: 431, errorText:Can't delete 
 network offering 51 as its used by 1 networks. To make the network offering 
 unavaiable, disable it

--
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

[jira] [Commented] (CLOUDSTACK-4048) [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created with gslbmethod=leastconn

2013-08-02 Thread venkata swamybabu budumuru (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727651#comment-13727651
 ] 

venkata swamybabu budumuru commented on CLOUDSTACK-4048:


2013-08-02 14:33:56,094 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-440:null) Seq 9-788267021: Executing request
2013-08-02 14:33:56,164 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,320 WARN  [network.resource.NetscalerResource] 
(DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
retries remaining: 1
2013-08-02 14:33:56,382 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,433 WARN  [network.resource.NetscalerResource] 
(DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
retries remaining: 0
2013-08-02 14:33:56,436 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-6:null) SeqA 3-11845: Processing Seq 3-11845:  { Cmd , 
MgmtId: -1, via: 3, Ver: v1, Flags: 11, 
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
  \connections\: []\n},wait:0}}] }
2013-08-02 14:33:56,447 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-6:null) SeqA 3-11845: Sending Seq 3-11845:  { Ans: , 
MgmtId: 7280707764394, via: 3, Ver: v1, Flags: 100010, 
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-02 14:33:56,479 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,479 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-440:null) Seq 9-788267021: Response Received:
2013-08-02 14:33:56,480 DEBUG [agent.transport.Request] (DirectAgent-440:null) 
Seq 9-788267021: Processing:  { Ans: , MgmtId: 7280707764394, via: 9, Ver: v1, 
Flags: 10, 
[{com.cloud.agent.api.routing.GlobalLoadBalancerConfigAnswer:{result:false,details:Failed
 to apply GSLB configuration due to Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION],wait:0}}] }
2013-08-02 14:33:56,480 DEBUG [agent.transport.Request] 
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Seq 
9-788267021: Received:  { Ans: , MgmtId: 7280707764394, via: 9, Ver: v1, Flags: 
10, { GlobalLoadBalancerConfigAnswer } }
2013-08-02 14:33:56,480 DEBUG [agent.manager.AgentManagerImpl] 
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Details 
from executing class 
com.cloud.agent.api.routing.GlobalLoadBalancerConfigCommand: Failed to apply 
GSLB configuration due to Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,480 DEBUG [network.element.NetscalerElement] 
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Unable to 
apply global load balancer rule to the gslb service provid
er in zone 

 [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created 
 with gslbmethod=leastconn
 --

 Key: CLOUDSTACK-4048
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4048
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.2.0
 Environment: commit id # 9cd4e089a5798f422961940efbf8ae33ed906b87
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.2.0


 Steps to reproduce:
 1. Have latest CloudStack setup with at least 2 zones which are GSLB enabled.
 2. create LB1Zone1, LB1Zone2 rules in each zone.
 3. Create a GSLB rule with gslbmethod=leastconn
 2013-08-02 14:32:54,633 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===START===  10.252.192.25 -- GET  
 command=createGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Dname=test1regionid=1gslblbmethod=leastconngslbstickysessionmethodname=sourceipgslbdomainname=test1gslbservicetype=udpdescription=test1_=1375434184015
 4. Assign LB1Zone1 to the above GSLB rule

[jira] [Created] (CLOUDSTACK-4048) [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created with gslbmethod=leastconn

2013-08-02 Thread venkata swamybabu budumuru (JIRA)

venkata swamybabu budumuru created CLOUDSTACK-4048:
--

 Summary: [GSLB] Failed to assign more than one LB rule to a GSLB 
rule that is created with gslbmethod=leastconn
 Key: CLOUDSTACK-4048
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4048
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Controller
Affects Versions: 4.2.0
 Environment: commit id # 9cd4e089a5798f422961940efbf8ae33ed906b87
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.2.0


Steps to reproduce:

1. Have latest CloudStack setup with at least 2 zones which are GSLB enabled.
2. create LB1Zone1, LB1Zone2 rules in each zone.
3. Create a GSLB rule with gslbmethod=leastconn

2013-08-02 14:32:54,633 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
===START===  10.252.192.25 -- GET  
command=createGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Dname=test1regionid=1gslblbmethod=leastconngslbstickysessionmethodname=sourceipgslbdomainname=test1gslbservicetype=udpdescription=test1_=1375434184015

4. Assign LB1Zone1 to the above GSLB rule

command=assignToGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Did=44be9c74-40b8-49ea-af7f-3e95fdf18230loadbalancerrulelist=06dae3f7-b65f-4f14-ae75-c2c22cbdaa40_=1375434216924

2013-08-02 14:33:27,796 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-126:null) Successfully added GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com
2013-08-02 14:33:27,883 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-126:null) Successfully created GSLB site: cloudsite1
2013-08-02 14:33:28,048 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-126:null) Successfully created service: 
cloud-gslb-service-cloudsite1-10.147.44.68-22 at site: cloudsite1
2013-08-02 14:33:28,079 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-11:null) Ping from 1
2013-08-02 14:33:28,080 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-126:null) Successfully created service: 
cloud-gslb-service-cloudsite1-10.147.44.68-22 and virtual server: 
cloud-gslb-vserver-test1.xyztelco.com binding
2013-08-02 14:33:28,178 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-126:null) Successfully added virtual server: 
cloud-gslb-vserver-test1.xyztelco.com domain name: test1.xyztelco.com binding


5. assign another LB1Zone2 rule to the above GSLB rule

command=assignToGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Did=44be9c74-40b8-49ea-af7f-3e95fdf18230loadbalancerrulelist=ae92ca25-7c33-4545-a329-01602fb80daa_=1375434245185


Observations:

(i) Seen the following error in mgmt server logs.

2013-08-02 14:33:56,094 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-440:null) Seq 9-788267021: Executing request
2013-08-02 14:33:56,164 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,320 WARN  [network.resource.NetscalerResource] 
(DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
retries remaining: 1
2013-08-02 14:33:56,382 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,433 WARN  [network.resource.NetscalerResource] 
(DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
retries remaining: 0
2013-08-02 14:33:56,436 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-6:null) SeqA 3-11845: Processing Seq 3-11845:  { Cmd , 
MgmtId: -1, via: 3, Ver: v1, Flags: 11, 
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
  \connections\: []\n},wait:0}}] }
2013-08-02 14:33:56,447 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-6:null) SeqA 3-11845: Sending Seq 3-11845:  { Ans: , 
MgmtId: 7280707764394, via: 3, Ver: v1, Flags: 100010, 
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-02 14:33:56,479 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,479 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-440:null) Seq 9-788267021: Response Received:
2013-08-02 14:33:56,480 DEBUG [agent.transport.Request] (DirectAgent-440:null) 
Seq 9-788267021: Processing:  { Ans: , MgmtId: 7280707764394, via: 9, Ver: v1, 
Flags: 10,

[jira] [Issue Comment Deleted] (CLOUDSTACK-4028) [Automation] Null Pointer Exception observed while creating template


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye updated CLOUDSTACK-4028:
---

Comment: was deleted

(was: [~nitinme] Are you working on this?)

 [Automation] Null Pointer Exception observed while creating template
 

 Key: CLOUDSTACK-4028
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4028
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: Rayees Namathponnan
Assignee: Nitin Mehta
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


  This issue observed during regression test resource_limits 
 Below null pointer exception observed in MS log
 9b-483c-902f-167fb01cd2f1,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,id:1,poolTy
 pe:NetworkFilesystem,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049}},name:ROOT-453,size:147456,path:d57149f0-9932-49dd-b4f0-
 4dc286c95283,volumeId:509,vmName:i-251-453-QA,accountId:251,format:QCOW2,id:509,hypervisorType:KVM}},destTO:{org.apache.cloudstack.storage.to.TemplateObj
 ectTO:{path:template/tmpl/251/226,uuid:b884ddac-ba48-4946-8266-ce10fe40ab7d,id:226,format:RAW,accountId:251,hvm:true,displayText:Cent
  OS Template,image
 DataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary,_role:Image}},name:2ac0ba622-e789-354d-b69b-d3b40de4
 5701,hypervisorType:KVM}},executeInSequence:false,wait:10800}}] }
 2013-07-05 03:29:45,456 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-6:null) Seq 4-297077579: Processing:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10
 , 
 [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:java.lang.NullPointerException,wait:0}}]
  }
 2013-07-05 03:29:45,456 DEBUG [agent.transport.Request] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) Seq 
 4-297077579: Received:  { Ans: , MgmtId: 2906
 6118877352, via: 4, Ver: v1, Flags: 10, { CopyCmdAnswer } }
 2013-07-05 03:29:45,464 DEBUG [cloud.template.TemplateManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) Failed 
 to create templatejava.lang.NullPointerException
 2013-07-05 03:29:45,560 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to create 
 templatejava.lang.NullPointerException
 at 
 com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1372)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-05 03:29:45,561 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) 
 Complete async job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ], 
 jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to 
 create templatejava.lang.NullPointerException
 2013-07-05 03:29:46,044 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===START===  10.223.240.194 -- GET  
 signature=d5oNqmtHPLw0QTpehRKp0O0OhPo%3DapiKey=p4VwLP4mhd90QBeBxwJ39YurvbLtOuGc-qgcm4pN2B58bSZJZgGJezD5V1GR6vx38YPDGF4-h7_R0WqxvUkGEAcommand=queryAsyncJobResultresponse=jsonjobid=f7075411-b89e-4fd0-804d-e9af80b856ce
 2013-07-05 03:29:46,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===END===  10.223.240.194 -- GET  
 signature=d5oNqmtHPLw0QTpehRKp0O0OhPo%3DapiKey=p4VwLP4mhd90QBeBxwJ39YurvbLtOuGc-qgcm4pN2B58bSZJZgGJezD5V1GR6vx38YPDGF4-h7_R0WqxvUkGEAcommand=queryAsyncJobResultresponse=jsonjobid=f7075411-b89e-4fd0-804d-e9af80b856ce

[jira] [Commented] (CLOUDSTACK-4048) [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created with gslbmethod=leastconn

2013-08-02 Thread venkata swamybabu budumuru (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727652#comment-13727652
 ] 

venkata swamybabu budumuru commented on CLOUDSTACK-4048:


2013-08-02 14:33:56,481 ERROR [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Unexpected 
exception while executing 
org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to configure GSLB rule 
in the zone 1 due to Resource [DataCenter:1] is unreachable: Unable to apply 
global load balancer rule to the gslb service provider in zone 1
at 
org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.applyGlobalLoadBalancerRuleConfig(GlobalLoadBalancingRulesServiceImpl.java:679)
at 
org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:274)
at 
org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:151)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at 
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)


 [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created 
 with gslbmethod=leastconn
 --

 Key: CLOUDSTACK-4048
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4048
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.2.0
 Environment: commit id # 9cd4e089a5798f422961940efbf8ae33ed906b87
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.2.0


 Steps to reproduce:
 1. Have latest CloudStack setup with at least 2 zones which are GSLB enabled.
 2. create LB1Zone1, LB1Zone2 rules in each zone.
 3. Create a GSLB rule with gslbmethod=leastconn
 2013-08-02 14:32:54,633 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===START===  10.252.192.25 -- GET  
 command=createGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Dname=test1regionid=1gslblbmethod=leastconngslbstickysessionmethodname=sourceipgslbdomainname=test1gslbservicetype=udpdescription=test1_=1375434184015
 4. Assign LB1Zone1 to the above GSLB rule
 command=assignToGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Did=44be9c74-40b8-49ea-af7f-3e95fdf18230loadbalancerrulelist=06dae3f7-b65f-4f14-ae75-c2c22cbdaa40_=1375434216924
 2013-08-02 14:33:27,796 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully added GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com
 2013-08-02 14:33:27,883 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created GSLB site: cloudsite1
 2013-08-02 14:33:28,048 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created service: 
 cloud-gslb-service-cloudsite1-10.147.44.68-22 at site: cloudsite1
 2013-08-02 14:33:28,079 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-11:null) Ping from 1
 2013-08-02 14:33:28,080 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created service: 
 cloud-gslb-service-cloudsite1-10.147.44.68-22 and virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com binding
 2013-08-02 14:33:28,178 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully added virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com domain name: test1.xyztelco.com binding
 5. assign another LB1Zone2 rule to the above GSLB rule
 command=assignToGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Did=44be9c74-40b8-49ea-af7f-3e95fdf18230loadbalancerrulelist=ae92ca25-7c33-4545-a329-01602fb80daa_=1375434245185
 Observations:
 (i) Seen the following error in mgmt server logs.
 2013-08-02 14:33:56,094 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-440:null) Seq 9-788267021: Executing request
 2013-08-02 14:33:56,164 DEBUG

[jira] [Commented] (CLOUDSTACK-4028) [Automation] Null Pointer Exception observed while creating template


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727653#comment-13727653
 ] 

Gaurav Aradhye commented on CLOUDSTACK-4028:


Just to confirm, there was some confusion who is working on this.
No problem.

 [Automation] Null Pointer Exception observed while creating template
 

 Key: CLOUDSTACK-4028
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4028
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: Rayees Namathponnan
Assignee: Nitin Mehta
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


  This issue observed during regression test resource_limits 
 Below null pointer exception observed in MS log
 9b-483c-902f-167fb01cd2f1,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,id:1,poolTy
 pe:NetworkFilesystem,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049}},name:ROOT-453,size:147456,path:d57149f0-9932-49dd-b4f0-
 4dc286c95283,volumeId:509,vmName:i-251-453-QA,accountId:251,format:QCOW2,id:509,hypervisorType:KVM}},destTO:{org.apache.cloudstack.storage.to.TemplateObj
 ectTO:{path:template/tmpl/251/226,uuid:b884ddac-ba48-4946-8266-ce10fe40ab7d,id:226,format:RAW,accountId:251,hvm:true,displayText:Cent
  OS Template,image
 DataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary,_role:Image}},name:2ac0ba622-e789-354d-b69b-d3b40de4
 5701,hypervisorType:KVM}},executeInSequence:false,wait:10800}}] }
 2013-07-05 03:29:45,456 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-6:null) Seq 4-297077579: Processing:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10
 , 
 [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:java.lang.NullPointerException,wait:0}}]
  }
 2013-07-05 03:29:45,456 DEBUG [agent.transport.Request] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) Seq 
 4-297077579: Received:  { Ans: , MgmtId: 2906
 6118877352, via: 4, Ver: v1, Flags: 10, { CopyCmdAnswer } }
 2013-07-05 03:29:45,464 DEBUG [cloud.template.TemplateManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) Failed 
 to create templatejava.lang.NullPointerException
 2013-07-05 03:29:45,560 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to create 
 templatejava.lang.NullPointerException
 at 
 com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1372)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-05 03:29:45,561 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-14:job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ]) 
 Complete async job-1314 = [ bad71aec-8f24-4964-b510-e30b4ef1a999 ], 
 jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to 
 create templatejava.lang.NullPointerException
 2013-07-05 03:29:46,044 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===START===  10.223.240.194 -- GET  
 signature=d5oNqmtHPLw0QTpehRKp0O0OhPo%3DapiKey=p4VwLP4mhd90QBeBxwJ39YurvbLtOuGc-qgcm4pN2B58bSZJZgGJezD5V1GR6vx38YPDGF4-h7_R0WqxvUkGEAcommand=queryAsyncJobResultresponse=jsonjobid=f7075411-b89e-4fd0-804d-e9af80b856ce
 2013-07-05 03:29:46,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
 ===END===  10.223.240.194 -- GET

[jira] [Issue Comment Deleted] (CLOUDSTACK-4048) [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created with gslbmethod=leastconn

2013-08-02 Thread venkata swamybabu budumuru (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

venkata swamybabu budumuru updated CLOUDSTACK-4048:
---

Comment: was deleted

(was: 2013-08-02 14:33:56,094 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-440:null) Seq 9-788267021: Executing request
2013-08-02 14:33:56,164 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,320 WARN  [network.resource.NetscalerResource] 
(DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
retries remaining: 1
2013-08-02 14:33:56,382 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,433 WARN  [network.resource.NetscalerResource] 
(DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
retries remaining: 0
2013-08-02 14:33:56,436 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-6:null) SeqA 3-11845: Processing Seq 3-11845:  { Cmd , 
MgmtId: -1, via: 3, Ver: v1, Flags: 11, 
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
  \connections\: []\n},wait:0}}] }
2013-08-02 14:33:56,447 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-6:null) SeqA 3-11845: Sending Seq 3-11845:  { Ans: , 
MgmtId: 7280707764394, via: 3, Ver: v1, Flags: 100010, 
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-02 14:33:56,479 DEBUG [network.resource.NetscalerResource] 
(DirectAgent-440:null) Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,479 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-440:null) Seq 9-788267021: Response Received:
2013-08-02 14:33:56,480 DEBUG [agent.transport.Request] (DirectAgent-440:null) 
Seq 9-788267021: Processing:  { Ans: , MgmtId: 7280707764394, via: 9, Ver: v1, 
Flags: 10, 
[{com.cloud.agent.api.routing.GlobalLoadBalancerConfigAnswer:{result:false,details:Failed
 to apply GSLB configuration due to Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION],wait:0}}] }
2013-08-02 14:33:56,480 DEBUG [agent.transport.Request] 
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Seq 
9-788267021: Received:  { Ans: , MgmtId: 7280707764394, via: 9, Ver: v1, Flags: 
10, { GlobalLoadBalancerConfigAnswer } }
2013-08-02 14:33:56,480 DEBUG [agent.manager.AgentManagerImpl] 
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Details 
from executing class 
com.cloud.agent.api.routing.GlobalLoadBalancerConfigCommand: Failed to apply 
GSLB configuration due to Failed to add GSLB virtual server: 
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified 
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,480 DEBUG [network.element.NetscalerElement] 
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Unable to 
apply global load balancer rule to the gslb service provid
er in zone )

 [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created 
 with gslbmethod=leastconn
 --

 Key: CLOUDSTACK-4048
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4048
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.2.0
 Environment: commit id # 9cd4e089a5798f422961940efbf8ae33ed906b87
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.2.0


 Steps to reproduce:
 1. Have latest CloudStack setup with at least 2 zones which are GSLB enabled.
 2. create LB1Zone1, LB1Zone2 rules in each zone.
 3. Create a GSLB rule with gslbmethod=leastconn
 2013-08-02 14:32:54,633 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===START===  10.252.192.25 -- GET  
 command=createGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Dname=test1regionid=1gslblbmethod=leastconngslbstickysessionmethodname=sourceipgslbdomainname=test1gslbservicetype=udpdescription=test1_=1375434184015
 4. Assign LB1Zone1 to the above GSLB rule

[jira] [Updated] (CLOUDSTACK-4048) [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created with gslbmethod=leastconn

2013-08-02 Thread venkata swamybabu budumuru (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

venkata swamybabu budumuru updated CLOUDSTACK-4048:
---

Attachment: logs.tgz

 [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created 
 with gslbmethod=leastconn
 --

 Key: CLOUDSTACK-4048
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4048
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.2.0
 Environment: commit id # 9cd4e089a5798f422961940efbf8ae33ed906b87
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.2.0

 Attachments: cloud.sql, logs.tgz


 Steps to reproduce:
 1. Have latest CloudStack setup with at least 2 zones which are GSLB enabled.
 2. create LB1Zone1, LB1Zone2 rules in each zone.
 3. Create a GSLB rule with gslbmethod=leastconn
 2013-08-02 14:32:54,633 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===START===  10.252.192.25 -- GET  
 command=createGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Dname=test1regionid=1gslblbmethod=leastconngslbstickysessionmethodname=sourceipgslbdomainname=test1gslbservicetype=udpdescription=test1_=1375434184015
 4. Assign LB1Zone1 to the above GSLB rule
 command=assignToGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Did=44be9c74-40b8-49ea-af7f-3e95fdf18230loadbalancerrulelist=06dae3f7-b65f-4f14-ae75-c2c22cbdaa40_=1375434216924
 2013-08-02 14:33:27,796 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully added GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com
 2013-08-02 14:33:27,883 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created GSLB site: cloudsite1
 2013-08-02 14:33:28,048 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created service: 
 cloud-gslb-service-cloudsite1-10.147.44.68-22 at site: cloudsite1
 2013-08-02 14:33:28,079 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-11:null) Ping from 1
 2013-08-02 14:33:28,080 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created service: 
 cloud-gslb-service-cloudsite1-10.147.44.68-22 and virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com binding
 2013-08-02 14:33:28,178 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully added virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com domain name: test1.xyztelco.com binding
 5. assign another LB1Zone2 rule to the above GSLB rule
 command=assignToGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Did=44be9c74-40b8-49ea-af7f-3e95fdf18230loadbalancerrulelist=ae92ca25-7c33-4545-a329-01602fb80daa_=1375434245185
 Observations:
 (i) Seen the following error in mgmt server logs.
 2013-08-02 14:33:56,094 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-440:null) Seq 9-788267021: Executing request
 2013-08-02 14:33:56,164 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Failed to add GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be 
 specified [netmask, lbMethod==LEASTCONNECTION]
 2013-08-02 14:33:56,320 WARN  [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
 retries remaining: 1
 2013-08-02 14:33:56,382 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Failed to add GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be 
 specified [netmask, lbMethod==LEASTCONNECTION]
 2013-08-02 14:33:56,433 WARN  [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
 retries remaining: 0
 2013-08-02 14:33:56,436 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-6:null) SeqA 3-11845: Processing Seq 3-11845:  { Cmd , 
 MgmtId: -1, via: 3, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2013-08-02 14:33:56,447 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-6:null) SeqA 3-11845: Sending Seq 3-11845:  { Ans: , 
 MgmtId: 7280707764394, via: 3, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2013-08-02 14:33:56,479 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Failed to add GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be 
 specified

[jira] [Updated] (CLOUDSTACK-4048) [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created with gslbmethod=leastconn

2013-08-02 Thread venkata swamybabu budumuru (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

venkata swamybabu budumuru updated CLOUDSTACK-4048:
---

Attachment: cloud.sql

 [GSLB] Failed to assign more than one LB rule to a GSLB rule that is created 
 with gslbmethod=leastconn
 --

 Key: CLOUDSTACK-4048
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4048
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.2.0
 Environment: commit id # 9cd4e089a5798f422961940efbf8ae33ed906b87
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.2.0

 Attachments: cloud.sql, logs.tgz


 Steps to reproduce:
 1. Have latest CloudStack setup with at least 2 zones which are GSLB enabled.
 2. create LB1Zone1, LB1Zone2 rules in each zone.
 3. Create a GSLB rule with gslbmethod=leastconn
 2013-08-02 14:32:54,633 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===START===  10.252.192.25 -- GET  
 command=createGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Dname=test1regionid=1gslblbmethod=leastconngslbstickysessionmethodname=sourceipgslbdomainname=test1gslbservicetype=udpdescription=test1_=1375434184015
 4. Assign LB1Zone1 to the above GSLB rule
 command=assignToGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Did=44be9c74-40b8-49ea-af7f-3e95fdf18230loadbalancerrulelist=06dae3f7-b65f-4f14-ae75-c2c22cbdaa40_=1375434216924
 2013-08-02 14:33:27,796 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully added GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com
 2013-08-02 14:33:27,883 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created GSLB site: cloudsite1
 2013-08-02 14:33:28,048 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created service: 
 cloud-gslb-service-cloudsite1-10.147.44.68-22 at site: cloudsite1
 2013-08-02 14:33:28,079 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-11:null) Ping from 1
 2013-08-02 14:33:28,080 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully created service: 
 cloud-gslb-service-cloudsite1-10.147.44.68-22 and virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com binding
 2013-08-02 14:33:28,178 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-126:null) Successfully added virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com domain name: test1.xyztelco.com binding
 5. assign another LB1Zone2 rule to the above GSLB rule
 command=assignToGlobalLoadBalancerRuleresponse=jsonsessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3Did=44be9c74-40b8-49ea-af7f-3e95fdf18230loadbalancerrulelist=ae92ca25-7c33-4545-a329-01602fb80daa_=1375434245185
 Observations:
 (i) Seen the following error in mgmt server logs.
 2013-08-02 14:33:56,094 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-440:null) Seq 9-788267021: Executing request
 2013-08-02 14:33:56,164 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Failed to add GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be 
 specified [netmask, lbMethod==LEASTCONNECTION]
 2013-08-02 14:33:56,320 WARN  [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
 retries remaining: 1
 2013-08-02 14:33:56,382 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Failed to add GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be 
 specified [netmask, lbMethod==LEASTCONNECTION]
 2013-08-02 14:33:56,433 WARN  [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of 
 retries remaining: 0
 2013-08-02 14:33:56,436 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-6:null) SeqA 3-11845: Processing Seq 3-11845:  { Cmd , 
 MgmtId: -1, via: 3, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2013-08-02 14:33:56,447 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-6:null) SeqA 3-11845: Sending Seq 3-11845:  { Ans: , 
 MgmtId: 7280707764394, via: 3, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2013-08-02 14:33:56,479 DEBUG [network.resource.NetscalerResource] 
 (DirectAgent-440:null) Failed to add GSLB virtual server: 
 cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be 
 specified

[jira] [Comment Edited] (CLOUDSTACK-3954) HA with Security Groups and ping disabled will cause split-brian

2013-08-02 Thread Lennert den Teuling (JIRA)

[
https://issues.apache.org/jira/browse/CLOUDSTACK-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727573#comment-13727573
]

Lennert den Teuling edited comment on CLOUDSTACK-3954 at 8/2/13 1:10 PM:
-

EDIT:
After looking futher into this, i think the issue is that we do not look if the
hypervisor itself is pingable. If you would do this, this issue won't exist. If
the hypervisor is pingable there should not be a HA, because we cannot make
sure if the VMs are running or not.

HA with Security Groups and ping disabled will cause split-brian

[jira] [Comment Edited] (CLOUDSTACK-3954) HA with Security Groups and ping disabled will cause split-brian

2013-08-02 Thread Lennert den Teuling (JIRA)

[
https://issues.apache.org/jira/browse/CLOUDSTACK-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727573#comment-13727573
]

Lennert den Teuling edited comment on CLOUDSTACK-3954 at 8/2/13 1:10 PM:
-

HA with Security Groups and ping disabled will cause split-brian

[jira] [Closed] (CLOUDSTACK-1640) overcommited memory is not getting displayed at zone level and used % is based on actual memory


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

prashant kumar mishra closed CLOUDSTACK-1640.
-


passed

  overcommited memory is not getting displayed at zone level and used % is 
 based on actual memory
 

 Key: CLOUDSTACK-1640
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1640
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: prashant kumar mishra
Assignee: Bharat Kumar
Priority: Critical
 Fix For: 4.2.0

 Attachments: screenshot-1.jpg


 Dashboard display overcommited memory at cluster and pod level with % of 
 utilization based on overcommited memory.At zone level actual memory is 
 getting displayed with % based on actual memory
 DB
 
 mysql select * from cluster_details where cluster_id=1;
 +++---+---+
 | id | cluster_id | name  | value |
 +++---+---+
 |  1 |  1 | cpuOvercommitRatio| 2.0   |
 |  2 |  1 | memoryOvercommitRatio | 2.0   |
 +++---+---+
 mysql select * from op_host_capacity where host_id=1\G;
 *** 1. row ***
id: 12
   host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
 used_capacity: 29393682432
 reserved_capacity: 0
total_capacity: 16190157312
 capacity_type: 0
capacity_state: Enabled
   update_time: 2013-03-12 07:10:50
   created: 2013-03-11 07:23:17
 *** 2. row ***
id: 13
   host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
 used_capacity: 4400
 reserved_capacity: 0
total_capacity: 9576
 capacity_type: 1
capacity_state: Enabled
   update_time: 2013-03-12 07:10:50
   created: 2013-03-11 07:23:17
 2 rows in set (0.00 sec)
 ERROR:
 No query specified
  

--
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

[jira] [Updated] (CLOUDSTACK-1640) overcommited memory is not getting displayed at zone level and used % is based on actual memory


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

prashant kumar mishra updated CLOUDSTACK-1640:
--

Attachment: test screenshots .jpg

  overcommited memory is not getting displayed at zone level and used % is 
 based on actual memory
 

 Key: CLOUDSTACK-1640
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1640
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: prashant kumar mishra
Assignee: Bharat Kumar
Priority: Critical
 Fix For: 4.2.0

 Attachments: screenshot-1.jpg, test screenshots .jpg


 Dashboard display overcommited memory at cluster and pod level with % of 
 utilization based on overcommited memory.At zone level actual memory is 
 getting displayed with % based on actual memory
 DB
 
 mysql select * from cluster_details where cluster_id=1;
 +++---+---+
 | id | cluster_id | name  | value |
 +++---+---+
 |  1 |  1 | cpuOvercommitRatio| 2.0   |
 |  2 |  1 | memoryOvercommitRatio | 2.0   |
 +++---+---+
 mysql select * from op_host_capacity where host_id=1\G;
 *** 1. row ***
id: 12
   host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
 used_capacity: 29393682432
 reserved_capacity: 0
total_capacity: 16190157312
 capacity_type: 0
capacity_state: Enabled
   update_time: 2013-03-12 07:10:50
   created: 2013-03-11 07:23:17
 *** 2. row ***
id: 13
   host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
 used_capacity: 4400
 reserved_capacity: 0
total_capacity: 9576
 capacity_type: 1
capacity_state: Enabled
   update_time: 2013-03-12 07:10:50
   created: 2013-03-11 07:23:17
 2 rows in set (0.00 sec)
 ERROR:
 No query specified
  

--
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

[jira] [Reopened] (CLOUDSTACK-3344) ldap:UI:sending wrong query filter(converting symbol to amp)during ldapconfig through UI[due to this ldap users fail to login]

2013-08-02 Thread sadhu suresh (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sadhu suresh reopened CLOUDSTACK-3344:
--


Now amp was decoded properly but fail  to login using ldap credentials


firefox response when we submit from UI,

http://10.147.38.166:8080/client/api?command=ldapConfigbinddn=CN%3Dtest%2CCN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcombindpass=_hostname=10.147.38.163searchbase=CN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcomqueryfilter=(%26(mail%3D%25e))port=389ssl=falseresponse=jsonsessionkey=soZA%2BQRFfu%2BNZ1kAKvoPfdFr7To%3D



here query filter was (%26(mail%3D%25e) but  when we change query filter like 
below
format then able to login with ldap credentials
 
%28%26%28mail%3D%25e%29%29


http://10.147.38.166:8080/client/api?command=ldapConfigbinddn=CN%3Dtest%2CCN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcombindpass=_hostname=10.147.38.163searchbase=CN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcomqueryfilter=%28%26%28mail%3D%25e%29%29port=389ssl=falseresponse=jsonsessionkey=soZA%2BQRFfu%2BNZ1kAKvoPfdFr7To%3D
 





 ldap:UI:sending wrong query filter(converting symbol to amp)during 
 ldapconfig through UI[due to this ldap users fail to login]
 --

 Key: CLOUDSTACK-3344
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3344
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.2.0

 Attachments: screenshot_ldap_ui.png


 Steps:
 1. Configured the LDAP through UI by providing query filter as email 
 (eg:((mail=%e)))
 2.check the configured values 
 Actual result:
 its converting  symbol into amp while configuring the ldap through UI due 
 to this  ldap users fail to login.
 through API ,its working fine.this is the only problem with UI side where 
 they converting  symbolto amp
 API fired while performing ldapconfig through UI:
 http://10.147.59.119:8080/client/api?command=ldapConfigbinddn=CN%3Dtest%2CCN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcombindpass=_hostname=10.147.38.163searchbase=CN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcomqueryfilter=(%26(mail%3D%25e))port=389ssl=falseresponse=jsonsessionkey=zlWVnEF2HA3R4ekSa8kDXaZrY5k%3D_=1372835435077
 { ldapconfigresponse :  { ldapconfig : 
 {hostname:10.147.38.163,port:389,ssl:false,searchbase:CN=Users,DC=hyd-qa,DC=com,queryfilter:(amp;(mail=%e)),binddn:CN=test,CN=Users,DC=hyd-qa,DC=com}
  }  }

--
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

[jira] [Updated] (CLOUDSTACK-3917) Console View of a VM on a VMWare host doesnt recognize certain keys on the keyboard

2013-08-02 Thread Ram Ganesh (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ram Ganesh updated CLOUDSTACK-3917:
---

Assignee: Sanjay Tripathi

 Console View of a VM on a VMWare host doesnt recognize certain keys on the 
 keyboard
 ---

 Key: CLOUDSTACK-3917
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3917
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Chandan Purushothama
Assignee: Sanjay Tripathi
Priority: Critical
 Fix For: 4.2.0


 https://issues.apache.org/jira/browse/CLOUDSTACK-3680 is seen on VMWare hosts 
 too. I filed this bug as a separate bug in case if the bug is on the System 
 VM Templates that are specific for each hypervisor.

--
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

[jira] [Closed] (CLOUDSTACK-3667) [Object_Store_Refactor][VMWare] System VMs StartCommand failed due to Exception: java.lang.Exception Message: secondary storage for dc 3 is not ready yet?

2013-08-02 Thread Sanjeev N (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjeev N closed CLOUDSTACK-3667.
-


Verified with latest build from ACS 4.2 branch. Works fine.

 [Object_Store_Refactor][VMWare] System VMs StartCommand failed due to 
 Exception: java.lang.Exception Message: secondary storage for dc 3 is not 
 ready yet?
 --

 Key: CLOUDSTACK-3667
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3667
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, VMware
Affects Versions: 4.2.0
 Environment: Latest build from ACS 4.2 Branch.
 Zone: Advanced with VMWare cluster
 Storage: S3 and ISCSI(Primary)
Reporter: Sanjeev N
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.2.0

 Attachments: management-server.rar


 [Object_Store_Refactor][VMWare] System VMs StartCommand failed due to 
 Exception: java.lang.Exception Message: secondary storage for dc 3 is not 
 ready yet?
 System VMs failed to start in case of VMWare cluster due to NULL in URL for  
 S3 image store in image_store table with role Image.
 I looked at the following code in 
 incubator-cloudstack/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
  :
  // prepare systemvm patch ISO
 if (vmSpec.getType() != VirtualMachine.Type.User) {
 // attach ISO (for patching of system VM)
 String secStoreUrl = 
 mgr.getSecondaryStorageStoreUrl(Long.parseLong(_dcId));
 if(secStoreUrl == null) {
 String msg = secondary storage for dc  + _dcId +  is 
 not ready yet?;
 throw new Exception(msg);
 }
 mgr.prepareSecondaryStorageStore(secStoreUrl);
 Since secStoreUrl  is matching with null , system vms starting failing with 
 following exception message:
 java.lang.Exception: secondary storage for dc 3 is not ready yet?
 Steps to Reproduce:
 
 1.Bring up CS in advanced zone with vmware cluster
 2.Add S3 image store and NFS cache store in the zone
 3.Enable the zone
 Observations:
 ===
  2013-07-19 11:50:10,861 WARN  [vmware.resource.VmwareResource] 
 (DirectAgent-97:10.147.40.13) StartCommand failed due to Exception: 
 java.lang.Exception
 Message: secondary storage for dc 3 is not ready yet?
 java.lang.Exception: secondary storage for dc 3 is not ready yet?
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2628)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:519)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
 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$101(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
 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:679)
 Enabled TRACE in log4j-cloud.xml and found the following sql statements 
 executed before the exception:
 mysql SELECT image_store.id, image_store.name, image_store.uuid, 
 image_store.protocol, image_store.url, image_store.image_provider_name, 
 image_store.data_center_id, image_store.scope, image_store.created, 
 image_store.removed, image_store.role, image_store.parent, 
 image_store.total_size, image_store.used_bytes FROM image_store WHERE 
 image_store.role = 'Image'  AND  (image_store.scope = 'REGION'  OR 
 image_store.data_center_id = 3 )  AND image_store.removed IS NULL;
 +++--+--+--+-+++-+-+---++++
 | id | name   | uuid | protocol | url  | 
 image_provider_name | data_center_id | scope  | created | removed 
 | role  | parent | total_size | used_bytes |

[jira] [Closed] (CLOUDSTACK-4039) NPE exception while ScaleVMCmd ;when i tried to change SO of a stopped vm on xen


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

prashant kumar mishra closed CLOUDSTACK-4039.
-


wrong API is being called for scale system vm action button , closing it 

 NPE exception while ScaleVMCmd ;when i tried to change SO of a stopped vm on 
 xen
 

 Key: CLOUDSTACK-4039
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4039
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
 Environment: xen 6.1
Reporter: prashant kumar mishra
Assignee: Harikrishna Patnala
 Fix For: 4.2.0

 Attachments: DB_LOG.rar, screenshot-1.jpg


 Steps to reproduce
 
 1-Prepare a CS setup  with xen6.1
 2-create a SO for cpvm
 3-disable zone and  change SO using scalevm
 Expected
 ---
 SO should get changed 
 Actual
 ---
 SO is getting changed but hitting NPE
 Logs
 ---
 2013-08-02 10:33:18,920 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-21:null) submit async job-119 = [ 
 01ee114d-4875-4f93-9377-85c3513b2e36 ], details: AsyncJobVO {id:119, userId: 
 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.user.vm.ScaleVMCmd, cmdOriginator: null, 
 cmdInfo: 
 {id:98922cc4-8f54-4770-802f-cbab622c8fba,response:json,serviceofferingid:1db62193-a936-4a4d-b997-040cc54b632c,sessionkey:VuBqe2DbIvWXqsQhQ+zdXplfMkE\u003d,cmdEventType:VM.UPGRADE,ctxUserId:2,httpmethod:GET,_:1375434522617,ctxAccountId:2,ctxStartEventId:460},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-08-02 10:33:18,924 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null) 
 ===END===  10.252.192.53 -- GET  
 command=scaleVirtualMachineid=98922cc4-8f54-4770-802f-cbab622c8fbaserviceofferingid=1db62193-a936-4a4d-b997-040cc54b632cresponse=jsonsessionkey=VuBqe2DbIvWXqsQhQ%2BzdXplfMkE%3D_=1375434522617
 2013-08-02 10:33:18,928 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-26:job-119 = [ 01ee114d-4875-4f93-9377-85c3513b2e36 ]) 
 Executing org.apache.cloudstack.api.command.user.vm.ScaleVMCmd for job-119 = 
 [ 01ee114d-4875-4f93-9377-85c3513b2e36 ]
 2013-08-02 10:33:18,940 DEBUG [cloud.api.ApiDispatcher] 
 (Job-Executor-26:job-119 = [ 01ee114d-4875-4f93-9377-85c3513b2e36 ]) 
 ControlledEntity name is:com.cloud.vm.VirtualMachine
 2013-08-02 10:33:18,942 DEBUG [cloud.api.ApiDispatcher] 
 (Job-Executor-26:job-119 = [ 01ee114d-4875-4f93-9377-85c3513b2e36 ]) 
 ControlledEntity name is:com.cloud.uservm.UserVm
 2013-08-02 10:33:18,945 DEBUG [cloud.api.ApiDispatcher] 
 (Job-Executor-26:job-119 = [ 01ee114d-4875-4f93-9377-85c3513b2e36 ]) 
 ControlledEntity name is:com.cloud.network.router.VirtualRouter
 2013-08-02 10:33:18,949 DEBUG [cloud.api.ApiDispatcher] 
 (Job-Executor-26:job-119 = [ 01ee114d-4875-4f93-9377-85c3513b2e36 ]) 
 InfrastructureEntity name is:com.cloud.offering.ServiceOffering
 2013-08-02 10:33:19,067 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-26:job-119 = [ 01ee114d-4875-4f93-9377-85c3513b2e36 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.ScaleVMCmd
 java.lang.NullPointerException
 at 
 com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1162)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:102)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-08-02 10:33:19,083 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-26:job-119 = [ 01ee114d-4875-4f93-9377-85c3513b2e36 ]) Complete 
 async job-119 = [ 01ee114d-4875-4f93-9377-85c3513b2e36 ], jobStatus: 2, 
 resultCode: 530, result: Error Code: 530 Error text: null
 2013-08-02 10:33:22,144 DEBUG

[jira] [Closed] (CLOUDSTACK-3703) change service offering of stopped vm on kvm is failing


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

prashant kumar mishra closed CLOUDSTACK-3703.
-


 change service offering of stopped vm on kvm is failing 
 

 Key: CLOUDSTACK-3703
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3703
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
 Environment: hypervisor :kvm
Reporter: prashant kumar mishra
Assignee: Harikrishna Patnala
Priority: Critical
 Fix For: 4.2.0

 Attachments: Logs_DB.rar, screenshot-1.jpg


 Steps to reproduce
 
 1-prepare CS setup with kvm host
 2-Deploy a vm 
 3-stop vm
 4-Try to update vm SO 
 Expected
 --
 SO should get updated
 Actual
 --
 Update service offering is failing
 My observation
 
 using API updateServiceOffering  i was able to update vms service offerings
 Logs
  
 2013-07-22 05:01:25,170 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) 
 ===END===  10.252.192.53 -- GET  
 command=listServiceOfferingsVirtualMachineId=6ba5b4cc-7f40-4638-a09f-5046016cf46aresponse=jsonsessionkey=3fAyCi4L%2FNGYESYM6ABmKVA7qTk%3D_=1374483685035
 2013-07-22 05:01:28,396 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) 
 ===START===  10.252.192.53 -- GET  
 command=scaleVirtualMachineid=6ba5b4cc-7f40-4638-a09f-5046016cf46aserviceofferingid=dfb785bd-5db6-4311-8324-c62891a24a31response=jsonsessionkey=3fAyCi4L%2FNGYESYM6ABmKVA7qTk%3D_=1374483688221
 2013-07-22 05:01:28,408 DEBUG [cloud.api.ApiDispatcher] 
 (catalina-exec-3:null) ControlledEntity name is:com.cloud.vm.VirtualMachine
 2013-07-22 05:01:28,411 DEBUG [cloud.api.ApiDispatcher] 
 (catalina-exec-3:null) ControlledEntity name is:com.cloud.uservm.UserVm
 2013-07-22 05:01:28,413 DEBUG [cloud.api.ApiDispatcher] 
 (catalina-exec-3:null) ControlledEntity name 
 is:com.cloud.network.router.VirtualRouter
 2013-07-22 05:01:28,416 DEBUG [cloud.api.ApiDispatcher] 
 (catalina-exec-3:null) InfrastructureEntity name 
 is:com.cloud.offering.ServiceOffering
 2013-07-22 05:01:28,443 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-3:null) submit async job-22 = [ 
 c7908990-7fd5-4580-8356-2a26e9138429 ], details: AsyncJobVO {id:22, userId: 
 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.user.vm.ScaleVMCmd, cmdOriginator: null, 
 cmdInfo: 
 {id:6ba5b4cc-7f40-4638-a09f-5046016cf46a,response:json,serviceofferingid:dfb785bd-5db6-4311-8324-c62891a24a31,sessionkey:3fAyCi4L/NGYESYM6ABmKVA7qTk\u003d,cmdEventType:VM.SCALE,ctxUserId:2,httpmethod:GET,_:1374483688221,ctxAccountId:2,ctxStartEventId:96},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 6615759585382, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-07-22 05:01:28,446 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) 
 ===END===  10.252.192.53 -- GET  
 command=scaleVirtualMachineid=6ba5b4cc-7f40-4638-a09f-5046016cf46aserviceofferingid=dfb785bd-5db6-4311-8324-c62891a24a31response=jsonsessionkey=3fAyCi4L%2FNGYESYM6ABmKVA7qTk%3D_=1374483688221
 2013-07-22 05:01:28,449 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-15:job-22 = [ c7908990-7fd5-4580-8356-2a26e9138429 ]) Executing 
 org.apache.cloudstack.api.command.user.vm.ScaleVMCmd for job-22 = [ 
 c7908990-7fd5-4580-8356-2a26e9138429 ]
 2013-07-22 05:01:28,458 DEBUG [cloud.api.ApiDispatcher] 
 (Job-Executor-15:job-22 = [ c7908990-7fd5-4580-8356-2a26e9138429 ]) 
 ControlledEntity name is:com.cloud.vm.VirtualMachine
 2013-07-22 05:01:28,461 DEBUG [cloud.api.ApiDispatcher] 
 (Job-Executor-15:job-22 = [ c7908990-7fd5-4580-8356-2a26e9138429 ]) 
 ControlledEntity name is:com.cloud.uservm.UserVm
 2013-07-22 05:01:28,463 DEBUG [cloud.api.ApiDispatcher] 
 (Job-Executor-15:job-22 = [ c7908990-7fd5-4580-8356-2a26e9138429 ]) 
 ControlledEntity name is:com.cloud.network.router.VirtualRouter
 2013-07-22 05:01:28,466 DEBUG [cloud.api.ApiDispatcher] 
 (Job-Executor-15:job-22 = [ c7908990-7fd5-4580-8356-2a26e9138429 ]) 
 InfrastructureEntity name is:com.cloud.offering.ServiceOffering
 2013-07-22 05:01:28,488 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-15:job-22 = [ c7908990-7fd5-4580-8356-2a26e9138429 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.ScaleVMCmd
 com.cloud.exception.InvalidParameterValueException: This operation not 
 permitted for this hypervisor of the vm
 at 
 com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1139)
 at

[jira] [Closed] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

prashant kumar mishra closed CLOUDSTACK-3446.
-


As per dev comment it is expected behavior so closing it 

 Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host 
 even there is no contention
 -

 Key: CLOUDSTACK-3446
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3446
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
 Environment: branch: master-stable, hypervisor :KVM
Reporter: prashant kumar mishra
Assignee: Bharat Kumar
 Fix For: 4.2.0

 Attachments: Logs_DB.rar


 Steps to reproduce
 ---
 1-prepare  CS setup with kvm
 2-set  memory overcommit ratio to 2
 3-deploy a vm with medium service offering(ram=1024MB, cpu=1000)
 4-run cat /proc/meminfo on guest OS
 Expected
 --
 since there is no contention Guest OS should get   1024 MB
 Actual
 -
 Guest OS is getting 512 MB even there is no contention on host
 My observation
 --
 --
 On KVM host
 virsh # dominfo 7
 Id: 7
 Name:   i-2-5-VM
 UUID:   ebe3a215-3893-4edd-97c0-0ad4e0793359
 OS Type:hvm
 State:  running
 CPU(s): 1
 CPU time:   45.8s
 Max memory: 1048576 kB
 Used memory:524288 kB
 Persistent: no
 Autostart:  disable
 Managed save:   no
 On Guest VM
 ---
 cat /proc/meminfo 
 MemTotal: 524288
 -Guest os gets memory=used memory on host(can be checked using dominfo )

--
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

[jira] [Commented] (CLOUDSTACK-1992) Cannot deploy VM from template on VMWare, no issues when deploying from ISO

2013-08-02 Thread Stuart Jennings (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727716#comment-13727716
 ] 

Stuart Jennings commented on CLOUDSTACK-1992:
-

I'm also seeing the same behaviour, single zone, single pod - 1x XenServer 
Cluster, 1x vSphere Cluster. XenServer CentOS template deploys successfully, 
VMware one fails. Tried local and shared storage with the same result. 

 Cannot deploy VM from template on VMWare, no issues when deploying from ISO
 ---

 Key: CLOUDSTACK-1992
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1992
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.1.0, 4.2.0
Reporter: Saksham Srivastava

 I am unable to deploy VMs from built-in template/registered templates. 
 However no issue observed while deploying VMs with ISO.
 Failing with following error:
 WARN  [agent.manager.AgentManagerImpl] (Job-Executor-2:job-34) Unsupported 
 Command: Unsupported command 
 issued:com.cloud.agent.api.storage.PrimaryStorageDownloadCommand.  Are you 
 sure you got the right type of server?
 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-2:job-34) Failed to 
 start instance VM[User|3e8592c8-09d5-4768-bedf-1117d9d3e3b8]
 java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be 
 cast to com.cloud.agent.api.storage.PrimaryStorageDownloadAnswer
   at 
 com.cloud.template.TemplateManagerImpl.prepareTemplateForCreate(TemplateManagerImpl.java:647)
   at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
   at 
 com.cloud.storage.StorageManagerImpl.createVolume(StorageManagerImpl.java:3582)
   at 
 com.cloud.storage.StorageManagerImpl.prepare(StorageManagerImpl.java:3473)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:748)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:212)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3860)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3458)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3444)
   at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
   at 
 org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:379)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
   at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
   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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
   at java.lang.Thread.run(Thread.java:722)
 INFO  [vmware.resource.VmwareResource] (DirectAgent-23:10.102.192.10) 
 Executing resource StopCommand: 
 {isProxy:false,vmName:i-2-14-VM,wait:0}
 INFO  [vmware.resource.VmwareResource] (DirectAgent-23:10.102.192.10) VM 
 i-2-14-VM is no longer in vSphere
 WARN  [user.vm.DeployVMCmd] (Job-Executor-2:job-34) Exception: 
 com.cloud.exception.AgentUnavailableException: Resource [Host:2] is 
 unreachable: Host 2: Unable to start instance due to 
 com.cloud.agent.api.UnsupportedAnswer cannot be cast to 
 com.cloud.agent.api.storage.PrimaryStorageDownloadAnswer
   at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:212)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3860)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3458)
   at

[jira] [Updated] (CLOUDSTACK-1992) Cannot deploy VM from template on VMWare, no issues when deploying from ISO

2013-08-02 Thread Stuart Jennings (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stuart Jennings updated CLOUDSTACK-1992:


Attachment: management-server.log

Management Server Log file attached for additional information. 

 Cannot deploy VM from template on VMWare, no issues when deploying from ISO
 ---

 Key: CLOUDSTACK-1992
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1992
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.1.0, 4.2.0
Reporter: Saksham Srivastava
 Attachments: management-server.log


 I am unable to deploy VMs from built-in template/registered templates. 
 However no issue observed while deploying VMs with ISO.
 Failing with following error:
 WARN  [agent.manager.AgentManagerImpl] (Job-Executor-2:job-34) Unsupported 
 Command: Unsupported command 
 issued:com.cloud.agent.api.storage.PrimaryStorageDownloadCommand.  Are you 
 sure you got the right type of server?
 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-2:job-34) Failed to 
 start instance VM[User|3e8592c8-09d5-4768-bedf-1117d9d3e3b8]
 java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be 
 cast to com.cloud.agent.api.storage.PrimaryStorageDownloadAnswer
   at 
 com.cloud.template.TemplateManagerImpl.prepareTemplateForCreate(TemplateManagerImpl.java:647)
   at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
   at 
 com.cloud.storage.StorageManagerImpl.createVolume(StorageManagerImpl.java:3582)
   at 
 com.cloud.storage.StorageManagerImpl.prepare(StorageManagerImpl.java:3473)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:748)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:212)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3860)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3458)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3444)
   at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
   at 
 org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:379)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
   at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
   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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
   at java.lang.Thread.run(Thread.java:722)
 INFO  [vmware.resource.VmwareResource] (DirectAgent-23:10.102.192.10) 
 Executing resource StopCommand: 
 {isProxy:false,vmName:i-2-14-VM,wait:0}
 INFO  [vmware.resource.VmwareResource] (DirectAgent-23:10.102.192.10) VM 
 i-2-14-VM is no longer in vSphere
 WARN  [user.vm.DeployVMCmd] (Job-Executor-2:job-34) Exception: 
 com.cloud.exception.AgentUnavailableException: Resource [Host:2] is 
 unreachable: Host 2: Unable to start instance due to 
 com.cloud.agent.api.UnsupportedAnswer cannot be cast to 
 com.cloud.agent.api.storage.PrimaryStorageDownloadAnswer
   at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:212)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3860)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3458)
   at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3444)
   at

[jira] [Closed] (CLOUDSTACK-3846) usage event is not generated for volume resize

2013-08-02 Thread Srikanteswararao Talluri (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Srikanteswararao Talluri closed CLOUDSTACK-3846.



i could see the usage event now.

| 1241 | VOLUME.CREATE   |  2 | 2013-08-02 19:08:59 |   1 | 
273 | ROOT-242  
  |NULL |NULL | 21474836480 | NULL   | 0 |  
   NULL |
| 1242 | VM.CREATE   |  2 | 2013-08-02 19:08:59 |   1 | 
242 | t 
  |  58 |   5 |NULL | XenServer  | 0 |  
   NULL |
| 1243 | NET.IPASSIGN|  2 | 2013-08-02 19:09:00 |   1 | 
  3 | 10.147.41.143 
  |NULL |   0 |   0 | DirectAttached | 0 |  
   NULL |
| 1244 | NETWORK.OFFERING.ASSIGN |  2 | 2013-08-02 19:09:49 |   1 | 
242 | 646   
  |   6 |NULL |   1 | NULL   | 0 |  
   NULL |
| 1245 | SG.ASSIGN   |  2 | 2013-08-02 19:09:50 |   1 | 
242 | NULL  
  |   1 |NULL |NULL | NULL   | 0 |  
   NULL |
| 1246 | VM.START|  2 | 2013-08-02 19:09:50 |   1 | 
242 | t 
  |  58 |   5 |NULL | XenServer  | 0 |  
   NULL |
| 1247 | VOLUME.CREATE   |  2 | 2013-08-02 20:33:17 |   1 | 
274 | t 
  |   3 |NULL |  5368709120 | NULL   | 0 |  
   NULL |
| 1248 | SG.REMOVE   |  2 | 2013-08-02 20:34:34 |   1 | 
242 | NULL  
  |   1 |NULL |NULL | NULL   | 0 |  
   NULL |
| 1249 | VM.STOP |  2 | 2013-08-02 20:34:34 |   1 | 
242 | t 
  |NULL |NULL |NULL | NULL   | 0 |  
   NULL |
| 1250 | NETWORK.OFFERING.REMOVE |  2 | 2013-08-02 20:34:34 |   1 | 
242 | 646   
  |   6 |NULL |   0 | NULL   | 0 |  
   NULL |
| 1251 | VOLUME.RESIZE   |  2 | 2013-08-02 20:35:24 |   1 | 
274 | t 
  |   4 |NULL | 21474836480 | NULL   | 0 |  
   NULL |
| 1252 | VOLUME.RESIZE   |  2 | 2013-08-02 20:36:30 |   1 | 
274 | t 
  |   6 |NULL | 37580963840 | NULL   | 0 |  
   NULL |
+--+-++-+-+-+-+-+-+-++---+--+


 usage event is not generated for volume resize 
 ---

 Key: CLOUDSTACK-3846
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3846
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Usage
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Rajesh Battala
Priority: Critical
 Fix For: 4.2.0


 Steps to reproduce:
 ==
 1. create a volume of size 5GB
 2. attach it to the VM
 3. resize the volume created in step 1 to 20GB.
 Observation:
 =
 Usage event is not getting generated for volume resize
 Before vol resize:
 ==
 mysql select * from usage_event;
 ++-++-+-+-++-+-+++---+
 | id | type| account_id | created | zone_id | 
 resource_id | resource_name  | offering_id | template_id | size   | 
 resource_type  | processed |
 ++-++-+-+-++-+-+++---+
 |  1 | VOLUME.CREATE   |

[jira] [Resolved] (CLOUDSTACK-4022) [Automation] Null pointer exception observed during API call ListProject

2013-08-02 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-4022.
---

Resolution: Fixed

Fixed with ed08f0f55174d449238c0e3cac93e022097045ae

 [Automation] Null pointer exception observed during API call ListProject
 

 Key: CLOUDSTACK-4022
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4022
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: 4.2 build
 KVM
Reporter: Rayees Namathponnan
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 Below Null Pointer Exception observed during automation run 
 NPE happened during ListProject API call
 2013-07-05 05:51:53,558 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-9:null) SeqA 12-2317: Processing Seq 12-2317:  { Cmd , 
 MgmtId: -1, via: 12, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:108,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2013-07-05 05:51:53,562 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-9:null) SeqA 12-2317: Sending Seq 12-2317:  { Ans: , 
 MgmtId: 29066118877352, via: 12, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2013-07-05 05:51:53,736 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
 ===START===  10.216.51.148 -- GET  
 command=listProjectsresponse=jsonsessionkey=llPmwPPnN6V7h6qUMhP3A2mD6fQ%3DlistAll=truepage=1pagesize=20_=1375361562728
 2013-07-05 05:51:53,781 ERROR [cloud.api.ApiServer] (catalina-exec-12:null) 
 unhandled exception executing api command: listProjects
 java.lang.NullPointerException
 at 
 com.cloud.api.query.dao.AccountJoinDaoImpl.newAccountView(AccountJoinDaoImpl.java:221)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at com.cloud.api.ApiDBUtils.newAccountView(ApiDBUtils.java:1595)
 at 
 com.cloud.api.query.dao.ProjectJoinDaoImpl.newProjectResponse(ProjectJoinDaoImpl.java:95)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at com.cloud.api.ApiDBUtils.newProjectResponse(ApiDBUtils.java:1492)
 at 
 com.cloud.api.query.ViewResponseHelper.createProjectResponse(ViewResponseHelper.java:188)
 at 
 com.cloud.api.query.QueryManagerImpl.listProjects(QueryManagerImpl.java:1198)
 at 
 org.apache.cloudstack.api.command.user.project.ListProjectsCmd.execute(ListProjectsCmd.java:110)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 
 org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
 at 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
 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:679)
 2013-07-05 05:51:53,824 DEBUG

[jira] [Commented] (CLOUDSTACK-4022) [Automation] Null pointer exception observed during API call ListProject


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727766#comment-13727766
 ] 

ASF subversion and git services commented on CLOUDSTACK-4022:
-

Commit ed08f0f55174d449238c0e3cac93e022097045ae in branch refs/heads/4.2 from 
[~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ed08f0f ]

CLOUDSTACK-4022: listProjects - do searchIncludingRemoved when getting info of 
corresponding projectAccount because when the project is being removed, its 
account is marked as Removed first, but we might still want to retrieve its info


 [Automation] Null pointer exception observed during API call ListProject
 

 Key: CLOUDSTACK-4022
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4022
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: 4.2 build
 KVM
Reporter: Rayees Namathponnan
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 Below Null Pointer Exception observed during automation run 
 NPE happened during ListProject API call
 2013-07-05 05:51:53,558 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-9:null) SeqA 12-2317: Processing Seq 12-2317:  { Cmd , 
 MgmtId: -1, via: 12, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:108,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2013-07-05 05:51:53,562 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-9:null) SeqA 12-2317: Sending Seq 12-2317:  { Ans: , 
 MgmtId: 29066118877352, via: 12, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2013-07-05 05:51:53,736 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
 ===START===  10.216.51.148 -- GET  
 command=listProjectsresponse=jsonsessionkey=llPmwPPnN6V7h6qUMhP3A2mD6fQ%3DlistAll=truepage=1pagesize=20_=1375361562728
 2013-07-05 05:51:53,781 ERROR [cloud.api.ApiServer] (catalina-exec-12:null) 
 unhandled exception executing api command: listProjects
 java.lang.NullPointerException
 at 
 com.cloud.api.query.dao.AccountJoinDaoImpl.newAccountView(AccountJoinDaoImpl.java:221)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at com.cloud.api.ApiDBUtils.newAccountView(ApiDBUtils.java:1595)
 at 
 com.cloud.api.query.dao.ProjectJoinDaoImpl.newProjectResponse(ProjectJoinDaoImpl.java:95)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at com.cloud.api.ApiDBUtils.newProjectResponse(ApiDBUtils.java:1492)
 at 
 com.cloud.api.query.ViewResponseHelper.createProjectResponse(ViewResponseHelper.java:188)
 at 
 com.cloud.api.query.QueryManagerImpl.listProjects(QueryManagerImpl.java:1198)
 at 
 org.apache.cloudstack.api.command.user.project.ListProjectsCmd.execute(ListProjectsCmd.java:110)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at

[jira] [Commented] (CLOUDSTACK-4022) [Automation] Null pointer exception observed during API call ListProject

2013-08-02 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727765#comment-13727765
 ] 

ASF subversion and git services commented on CLOUDSTACK-4022:
-

Commit 4e53ce067722f4ef9e091455243459e8b151164b in branch refs/heads/master 
from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4e53ce0 ]

CLOUDSTACK-4022: listProjects - do searchIncludingRemoved when getting info of 
corresponding projectAccount because when the project is being removed, its 
account is marked as Removed first, but we might still want to retrieve its info


 [Automation] Null pointer exception observed during API call ListProject
 

 Key: CLOUDSTACK-4022
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4022
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: 4.2 build
 KVM
Reporter: Rayees Namathponnan
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 Below Null Pointer Exception observed during automation run 
 NPE happened during ListProject API call
 2013-07-05 05:51:53,558 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-9:null) SeqA 12-2317: Processing Seq 12-2317:  { Cmd , 
 MgmtId: -1, via: 12, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:108,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2013-07-05 05:51:53,562 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-9:null) SeqA 12-2317: Sending Seq 12-2317:  { Ans: , 
 MgmtId: 29066118877352, via: 12, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2013-07-05 05:51:53,736 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
 ===START===  10.216.51.148 -- GET  
 command=listProjectsresponse=jsonsessionkey=llPmwPPnN6V7h6qUMhP3A2mD6fQ%3DlistAll=truepage=1pagesize=20_=1375361562728
 2013-07-05 05:51:53,781 ERROR [cloud.api.ApiServer] (catalina-exec-12:null) 
 unhandled exception executing api command: listProjects
 java.lang.NullPointerException
 at 
 com.cloud.api.query.dao.AccountJoinDaoImpl.newAccountView(AccountJoinDaoImpl.java:221)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at com.cloud.api.ApiDBUtils.newAccountView(ApiDBUtils.java:1595)
 at 
 com.cloud.api.query.dao.ProjectJoinDaoImpl.newProjectResponse(ProjectJoinDaoImpl.java:95)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at com.cloud.api.ApiDBUtils.newProjectResponse(ApiDBUtils.java:1492)
 at 
 com.cloud.api.query.ViewResponseHelper.createProjectResponse(ViewResponseHelper.java:188)
 at 
 com.cloud.api.query.QueryManagerImpl.listProjects(QueryManagerImpl.java:1198)
 at 
 org.apache.cloudstack.api.command.user.project.ListProjectsCmd.execute(ListProjectsCmd.java:110)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at

[jira] [Reopened] (CLOUDSTACK-2340) [AWS Style Health Checks] Response of the API listLoadBalancerRuleInstances should show the service state of a VM if health check is configured for it

2013-08-02 Thread Brian Federle (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brian Federle reopened CLOUDSTACK-2340:
---


 [AWS Style Health Checks] Response of the API listLoadBalancerRuleInstances 
 should show the service state of a VM if health check is configured for it
 --

 Key: CLOUDSTACK-2340
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2340
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, UI
Affects Versions: 4.2.0
Reporter: Abhinav Roy
Assignee: Brian Federle
Priority: Critical
 Fix For: 4.2.0


 In the current implementation of  the API listLoadBalancerRuleInstances we 
 don't see the service state of a VM which has health check configured and 
 hence the user doesn't get to know the state of that service from the UI.
 So, filing this bug so that we add some parameter in the API response which 
 shows the service state and hence using that we can make the state visible in 
 the UI also.

--
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

[jira] [Commented] (CLOUDSTACK-4010) Change required in the UI to pass startdate/enddate parameter rather than olderthan parameter in the archive/delete alerts/events API.

2013-08-02 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727796#comment-13727796
 ] 

ASF subversion and git services commented on CLOUDSTACK-4010:
-

Commit 80ae4830ae63ab73a06ab033bc3feb3dd701cbb2 in branch refs/heads/4.2 from 
[~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=80ae483 ]

CLOUDSTACK-4010: Events/alerts: Pass start date / end date

Original submitter: Sanjay Tripathi sanjay.tripa...@citrix.com
Reviewed by: Brian Federle brian.fede...@citrix.com


 Change required in the UI to pass startdate/enddate parameter rather than 
 olderthan parameter in the archive/delete alerts/events API.
 --

 Key: CLOUDSTACK-4010
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4010
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Sanjay Tripathi
Assignee: Sanjay Tripathi
Priority: Critical
 Fix For: 4.2.0




--
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

[jira] [Commented] (CLOUDSTACK-4010) Change required in the UI to pass startdate/enddate parameter rather than olderthan parameter in the archive/delete alerts/events API.

2013-08-02 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727797#comment-13727797
 ] 

ASF subversion and git services commented on CLOUDSTACK-4010:
-

Commit 977b0eca973b721fe158768f3f3c5515b9d2aab7 in branch refs/heads/master 
from [~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=977b0ec ]

CLOUDSTACK-4010: Events/alerts: Pass start date / end date

Original submitter: Sanjay Tripathi sanjay.tripa...@citrix.com
Reviewed by: Brian Federle brian.fede...@citrix.com


 Change required in the UI to pass startdate/enddate parameter rather than 
 olderthan parameter in the archive/delete alerts/events API.
 --

 Key: CLOUDSTACK-4010
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4010
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Sanjay Tripathi
Assignee: Sanjay Tripathi
Priority: Critical
 Fix For: 4.2.0




--
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

[jira] [Updated] (CLOUDSTACK-4035) [Upgrade][2.2.16 to 4.2] [UI] Autoscale wizard missing counter param in UI - fails configuration

2013-08-02 Thread Brian Federle (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brian Federle updated CLOUDSTACK-4035:
--

Component/s: (was: UI)
 Upgrade
 API

Change label to remove UI since this looks like a backend issue. If this indeed 
ends up requiring a UI fix, please re-add UI label.

 [Upgrade][2.2.16 to 4.2] [UI] Autoscale wizard missing counter param in UI - 
 fails configuration
 

 Key: CLOUDSTACK-4035
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4035
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Upgrade
Affects Versions: 4.2.0
 Environment: Upgraded setup from 2.2.16 to 4.2, Netscaler as external 
 LB device
Reporter: Sowmya Krishnan
Priority: Blocker
 Fix For: 4.2.0

 Attachments: countermissing.png, DB_DUMP_2216_before_upgrade.sql, 
 DB_DUMP_42_after_upgrade.sql


 Steps
 =
 Upgrade from 2.2.16 to 4.2.
 Create a network offering with LB service provided by Netscaler
 Acquire a public IP and configure autoscaling with it
 Fails during configuration since counter value is missing
 Firebug log:
 { conditionresponse : 
 {uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to 
 execute API command condition due to missing parameter counterid} }
 Attached screen shot 

--
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

[jira] [Created] (CLOUDSTACK-4049) db exception:management server failed to start

2013-08-02 Thread Srikanteswararao Talluri (JIRA)

Srikanteswararao Talluri created CLOUDSTACK-4049:


 Summary: db exception:management server failed to start
 Key: CLOUDSTACK-4049
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4049
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Priority: Blocker
 Fix For: 4.2.0


Steps to reproduce:
===
1. Install management server
2. run cloud-setup-databases
3. run cloud-setup-management

Observation:
=
Management server failed to start


job_status = 0 
2013-08-03 03:53:25,477 ERROR [utils.db.ScriptRunner] (Timer-1:null) 
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
'volumes.iso_id' in 'on clause'
2013-08-03 03:53:25,486 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
(Timer-1:null) Unable to execute upgrade script: 
/usr/share/cloudstack-management/setup/db/schema-410to420.sql
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
'volumes.iso_id' in 'on clause'
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
at 
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
at 
com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
2013-08-03 03:53:25,489 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
(Timer-1:null) Unable to upgrade the database
com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade 
script: /usr/share/cloudstack-management/setup/db/schema-410to420.sql
at 
com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:208)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
at 
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
at 
com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
column 'volumes.iso_id' in 'on clause'
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
... 6 more
2013-08-03 03:53:25,498 DEBUG [db.Transaction.Transaction] (Timer-1:null) 
Rolling back the transaction: Time = 1839 Name =  
-CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484; 
called by 
-Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
2013-08-03 03:53:25,500 ERROR [utils.component.ComponentContext] (Timer-1:null) 
System integrity check failed. Refuse to startup


--
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

[jira] [Updated] (CLOUDSTACK-4026) [Automation] NullPointer exception while cleaning up account

2013-08-02 Thread Rajesh Battala (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajesh Battala updated CLOUDSTACK-4026:
---

Assignee: (was: Rajesh Battala)

 [Automation] NullPointer exception while cleaning up account 
 -

 Key: CLOUDSTACK-4026
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4026
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: KVM
 build 4.2
Reporter: Rayees Namathponnan
Priority: Critical
 Fix For: 4.2.0


 Below null pointer exception happening while cleaning up account 
 2013-07-05 10:03:13,319 DEBUG [agent.transport.Request] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) Seq 
 5-943066240: Received:  { Ans: , MgmtId: 290
 66118877352, via: 5, Ver: v1, Flags: 0, { IpAssocAnswer } }
 2013-07-05 10:03:13,325 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) 
 Applying loadbalancing
  rules in network Ntwk[755|Guest|252]
 2013-07-05 10:03:13,338 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) Failed 
 to cleanup account Acct[735-test-vp
 c_networks-Z1QIO8] due to
 java.lang.NullPointerException
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.createApplyLoadBalancingRulesCommands(VirtualNetworkApplianceManagerImpl.java:3316)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendLBRules(VirtualNetworkApplianceManagerImpl.java:3681)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl$9.execute(VirtualNetworkApplianceManagerImpl.java:3674)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3799)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyLoadBalancingRules(VirtualNetworkApplianceManagerImpl.java:3660)
 at 
 com.cloud.network.element.VirtualRouterElement.applyLBRules(VirtualRouterElement.java:393)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:1549)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:2089)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerRules(LoadBalancingRulesManagerImpl.java:1586)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerConfig(LoadBalancingRulesManagerImpl.java:1506)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeFromLoadBalancerInternal(LoadBalancingRulesManagerImpl.java:1109)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeVmFromLoadBalancers(LoadBalancingRulesManagerImpl.java:1171)
 at 
 com.cloud.vm.UserVmManagerImpl.cleanupVmResources(UserVmManagerImpl.java:1672)
 at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1617)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:613)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1273)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-05 10:03:13,339 INFO  [cloud.user.AccountManagerImpl] 
 (Job-Executor-115:job-3473 = [

[jira] [Commented] (CLOUDSTACK-4026) [Automation] NullPointer exception while cleaning up account

2013-08-02 Thread Rajesh Battala (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727853#comment-13727853
 ] 

Rajesh Battala commented on CLOUDSTACK-4026:


I had tried to reproduce it. not able to  reproduce

 [Automation] NullPointer exception while cleaning up account 
 -

 Key: CLOUDSTACK-4026
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4026
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: KVM
 build 4.2
Reporter: Rayees Namathponnan
Assignee: Rajesh Battala
Priority: Critical
 Fix For: 4.2.0


 Below null pointer exception happening while cleaning up account 
 2013-07-05 10:03:13,319 DEBUG [agent.transport.Request] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) Seq 
 5-943066240: Received:  { Ans: , MgmtId: 290
 66118877352, via: 5, Ver: v1, Flags: 0, { IpAssocAnswer } }
 2013-07-05 10:03:13,325 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) 
 Applying loadbalancing
  rules in network Ntwk[755|Guest|252]
 2013-07-05 10:03:13,338 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) Failed 
 to cleanup account Acct[735-test-vp
 c_networks-Z1QIO8] due to
 java.lang.NullPointerException
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.createApplyLoadBalancingRulesCommands(VirtualNetworkApplianceManagerImpl.java:3316)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendLBRules(VirtualNetworkApplianceManagerImpl.java:3681)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl$9.execute(VirtualNetworkApplianceManagerImpl.java:3674)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3799)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyLoadBalancingRules(VirtualNetworkApplianceManagerImpl.java:3660)
 at 
 com.cloud.network.element.VirtualRouterElement.applyLBRules(VirtualRouterElement.java:393)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:1549)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:2089)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerRules(LoadBalancingRulesManagerImpl.java:1586)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerConfig(LoadBalancingRulesManagerImpl.java:1506)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeFromLoadBalancerInternal(LoadBalancingRulesManagerImpl.java:1109)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeVmFromLoadBalancers(LoadBalancingRulesManagerImpl.java:1171)
 at 
 com.cloud.vm.UserVmManagerImpl.cleanupVmResources(UserVmManagerImpl.java:1672)
 at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1617)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:613)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1273)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at

[jira] [Commented] (CLOUDSTACK-4026) [Automation] NullPointer exception while cleaning up account

2013-08-02 Thread Rayees Namathponnan (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727857#comment-13727857
 ] 

Rayees Namathponnan commented on CLOUDSTACK-4026:
-

Rajesh - Can you possible to handle the NPE ? 

 [Automation] NullPointer exception while cleaning up account 
 -

 Key: CLOUDSTACK-4026
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4026
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: KVM
 build 4.2
Reporter: Rayees Namathponnan
Priority: Critical
 Fix For: 4.2.0


 Below null pointer exception happening while cleaning up account 
 2013-07-05 10:03:13,319 DEBUG [agent.transport.Request] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) Seq 
 5-943066240: Received:  { Ans: , MgmtId: 290
 66118877352, via: 5, Ver: v1, Flags: 0, { IpAssocAnswer } }
 2013-07-05 10:03:13,325 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) 
 Applying loadbalancing
  rules in network Ntwk[755|Guest|252]
 2013-07-05 10:03:13,338 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) Failed 
 to cleanup account Acct[735-test-vp
 c_networks-Z1QIO8] due to
 java.lang.NullPointerException
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.createApplyLoadBalancingRulesCommands(VirtualNetworkApplianceManagerImpl.java:3316)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendLBRules(VirtualNetworkApplianceManagerImpl.java:3681)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl$9.execute(VirtualNetworkApplianceManagerImpl.java:3674)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3799)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyLoadBalancingRules(VirtualNetworkApplianceManagerImpl.java:3660)
 at 
 com.cloud.network.element.VirtualRouterElement.applyLBRules(VirtualRouterElement.java:393)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:1549)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:2089)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerRules(LoadBalancingRulesManagerImpl.java:1586)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerConfig(LoadBalancingRulesManagerImpl.java:1506)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeFromLoadBalancerInternal(LoadBalancingRulesManagerImpl.java:1109)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeVmFromLoadBalancers(LoadBalancingRulesManagerImpl.java:1171)
 at 
 com.cloud.vm.UserVmManagerImpl.cleanupVmResources(UserVmManagerImpl.java:1672)
 at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1617)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:613)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1273)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-05

[jira] [Resolved] (CLOUDSTACK-4026) [Automation] NullPointer exception while cleaning up account

2013-08-02 Thread Rajesh Battala (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajesh Battala resolved CLOUDSTACK-4026.


Resolution: Cannot Reproduce

 [Automation] NullPointer exception while cleaning up account 
 -

 Key: CLOUDSTACK-4026
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4026
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: KVM
 build 4.2
Reporter: Rayees Namathponnan
Assignee: Rajesh Battala
Priority: Critical
 Fix For: 4.2.0


 Below null pointer exception happening while cleaning up account 
 2013-07-05 10:03:13,319 DEBUG [agent.transport.Request] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) Seq 
 5-943066240: Received:  { Ans: , MgmtId: 290
 66118877352, via: 5, Ver: v1, Flags: 0, { IpAssocAnswer } }
 2013-07-05 10:03:13,325 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) 
 Applying loadbalancing
  rules in network Ntwk[755|Guest|252]
 2013-07-05 10:03:13,338 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-115:job-3473 = [ cd7c4d6e-1ce9-4713-9e04-ba2a2652b9c8 ]) Failed 
 to cleanup account Acct[735-test-vp
 c_networks-Z1QIO8] due to
 java.lang.NullPointerException
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.createApplyLoadBalancingRulesCommands(VirtualNetworkApplianceManagerImpl.java:3316)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendLBRules(VirtualNetworkApplianceManagerImpl.java:3681)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl$9.execute(VirtualNetworkApplianceManagerImpl.java:3674)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3799)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyLoadBalancingRules(VirtualNetworkApplianceManagerImpl.java:3660)
 at 
 com.cloud.network.element.VirtualRouterElement.applyLBRules(VirtualRouterElement.java:393)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:1549)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:2089)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerRules(LoadBalancingRulesManagerImpl.java:1586)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerConfig(LoadBalancingRulesManagerImpl.java:1506)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeFromLoadBalancerInternal(LoadBalancingRulesManagerImpl.java:1109)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeVmFromLoadBalancers(LoadBalancingRulesManagerImpl.java:1171)
 at 
 com.cloud.vm.UserVmManagerImpl.cleanupVmResources(UserVmManagerImpl.java:1672)
 at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1617)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:613)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1273)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-05 10:03:13,339 INFO  [cloud.user.AccountManagerImpl]

[jira] [Commented] (CLOUDSTACK-4049) db exception:management server failed to start


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727863#comment-13727863
 ] 

Chandan Purushothama commented on CLOUDSTACK-4049:
--

Looks like it is because of the fix made for 
https://issues.apache.org/jira/browse/CLOUDSTACK-3836

 db exception:management server failed to start
 --

 Key: CLOUDSTACK-4049
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4049
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Alena Prokharchyk
Priority: Blocker
 Fix For: 4.2.0


 Steps to reproduce:
 ===
 1. Install management server
 2. run cloud-setup-databases
 3. run cloud-setup-management
 Observation:
 =
 Management server failed to start
 job_status = 0 
 2013-08-03 03:53:25,477 ERROR [utils.db.ScriptRunner] (Timer-1:null) 
 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
 'volumes.iso_id' in 'on clause'
 2013-08-03 03:53:25,486 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-1:null) Unable to execute upgrade script: 
 /usr/share/cloudstack-management/setup/db/schema-410to420.sql
 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
 'volumes.iso_id' in 'on clause'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:534)
   at java.util.TimerThread.run(Timer.java:484)
 2013-08-03 03:53:25,489 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-1:null) Unable to upgrade the database
 com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade 
 script: /usr/share/cloudstack-management/setup/db/schema-410to420.sql
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:208)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:534)
   at java.util.TimerThread.run(Timer.java:484)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
 column 'volumes.iso_id' in 'on clause'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
   ... 6 more
 2013-08-03 03:53:25,498 DEBUG [db.Transaction.Transaction] (Timer-1:null) 
 Rolling back the transaction: Time = 1839 Name =  
 -CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484; 
 called by 
 -Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
 2013-08-03 03:53:25,500 ERROR [utils.component.ComponentContext] 
 (Timer-1:null) System integrity check failed. Refuse to startup

--
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

[jira] [Commented] (CLOUDSTACK-4049) db exception:management server failed to start


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727865#comment-13727865
 ] 

Alena Prokharchyk commented on CLOUDSTACK-4049:
---

Chandan is right.

 db exception:management server failed to start
 --

 Key: CLOUDSTACK-4049
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4049
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Alena Prokharchyk
Priority: Blocker
 Fix For: 4.2.0


 Steps to reproduce:
 ===
 1. Install management server
 2. run cloud-setup-databases
 3. run cloud-setup-management
 Observation:
 =
 Management server failed to start
 job_status = 0 
 2013-08-03 03:53:25,477 ERROR [utils.db.ScriptRunner] (Timer-1:null) 
 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
 'volumes.iso_id' in 'on clause'
 2013-08-03 03:53:25,486 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-1:null) Unable to execute upgrade script: 
 /usr/share/cloudstack-management/setup/db/schema-410to420.sql
 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
 'volumes.iso_id' in 'on clause'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:534)
   at java.util.TimerThread.run(Timer.java:484)
 2013-08-03 03:53:25,489 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-1:null) Unable to upgrade the database
 com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade 
 script: /usr/share/cloudstack-management/setup/db/schema-410to420.sql
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:208)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:534)
   at java.util.TimerThread.run(Timer.java:484)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
 column 'volumes.iso_id' in 'on clause'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
   ... 6 more
 2013-08-03 03:53:25,498 DEBUG [db.Transaction.Transaction] (Timer-1:null) 
 Rolling back the transaction: Time = 1839 Name =  
 -CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484; 
 called by 
 -Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
 2013-08-03 03:53:25,500 ERROR [utils.component.ComponentContext] 
 (Timer-1:null) System integrity check failed. Refuse to startup

--
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

[jira] [Resolved] (CLOUDSTACK-4049) db exception:management server failed to start

2013-08-02 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-4049.
---

Resolution: Fixed

Fixed with 922f902b3d2fa79cd03097c7c859f8762874f2f7

 db exception:management server failed to start
 --

 Key: CLOUDSTACK-4049
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4049
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Alena Prokharchyk
Priority: Blocker
 Fix For: 4.2.0


 Steps to reproduce:
 ===
 1. Install management server
 2. run cloud-setup-databases
 3. run cloud-setup-management
 Observation:
 =
 Management server failed to start
 job_status = 0 
 2013-08-03 03:53:25,477 ERROR [utils.db.ScriptRunner] (Timer-1:null) 
 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
 'volumes.iso_id' in 'on clause'
 2013-08-03 03:53:25,486 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-1:null) Unable to execute upgrade script: 
 /usr/share/cloudstack-management/setup/db/schema-410to420.sql
 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
 'volumes.iso_id' in 'on clause'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:534)
   at java.util.TimerThread.run(Timer.java:484)
 2013-08-03 03:53:25,489 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-1:null) Unable to upgrade the database
 com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade 
 script: /usr/share/cloudstack-management/setup/db/schema-410to420.sql
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:208)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:534)
   at java.util.TimerThread.run(Timer.java:484)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
 column 'volumes.iso_id' in 'on clause'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
   ... 6 more
 2013-08-03 03:53:25,498 DEBUG [db.Transaction.Transaction] (Timer-1:null) 
 Rolling back the transaction: Time = 1839 Name =  
 -CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484; 
 called by 
 -Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
 2013-08-03 03:53:25,500 ERROR [utils.component.ComponentContext] 
 (Timer-1:null) System integrity check failed. Refuse to startup

--
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

[jira] [Commented] (CLOUDSTACK-4049) db exception:management server failed to start


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727902#comment-13727902
 ] 

ASF subversion and git services commented on CLOUDSTACK-4049:
-

Commit 922f902b3d2fa79cd03097c7c859f8762874f2f7 in branch refs/heads/4.2 from 
[~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=922f902 ]

CLOUDSTACK-4049: insert iso_id field to volumes table before altering the 
volumes view


 db exception:management server failed to start
 --

 Key: CLOUDSTACK-4049
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4049
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Alena Prokharchyk
Priority: Blocker
 Fix For: 4.2.0


 Steps to reproduce:
 ===
 1. Install management server
 2. run cloud-setup-databases
 3. run cloud-setup-management
 Observation:
 =
 Management server failed to start
 job_status = 0 
 2013-08-03 03:53:25,477 ERROR [utils.db.ScriptRunner] (Timer-1:null) 
 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
 'volumes.iso_id' in 'on clause'
 2013-08-03 03:53:25,486 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-1:null) Unable to execute upgrade script: 
 /usr/share/cloudstack-management/setup/db/schema-410to420.sql
 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
 'volumes.iso_id' in 'on clause'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:534)
   at java.util.TimerThread.run(Timer.java:484)
 2013-08-03 03:53:25,489 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-1:null) Unable to upgrade the database
 com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade 
 script: /usr/share/cloudstack-management/setup/db/schema-410to420.sql
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:208)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:260)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:534)
   at java.util.TimerThread.run(Timer.java:484)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
 column 'volumes.iso_id' in 'on clause'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:199)
   ... 6 more
 2013-08-03 03:53:25,498 DEBUG [db.Transaction.Transaction] (Timer-1:null) 
 Rolling back the transaction: Time = 1839 Name =  
 -CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484; 
 called by 
 -Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
 2013-08-03 03:53:25,500 ERROR [utils.component.ComponentContext] 
 (Timer-1:null) System integrity check failed. Refuse to startup

--
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

[jira] [Closed] (CLOUDSTACK-2383) Entity already exists error at automatic virtual router VM creation.

2013-08-02 Thread Dominic Blais (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominic Blais closed CLOUDSTACK-2383.
-

Resolution: Fixed

 Entity already exists error at automatic virtual router VM creation.
 --

 Key: CLOUDSTACK-2383
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2383
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.0.2
 Environment: Ubuntu 12.04.2 on management node and compute nodes.
Reporter: Dominic Blais

 In advanced networking mode, whenever I have a new network created and needs 
 to spawn one or two virtual routers VM, as soon as I create a user VM 
 attached to that network, there will be a Entity already exists error. The 
 user VM is then in error state and the virtual router(s) is created but in 
 stopped state. That's also true for RVR with both VR. If I try again do 
 create a user VM, it's always the same thing. 
 To start a user VM on a new network, I need to:
 - Create a VM on a new network OR create a network and attach a new VM to it 
 for the first time
 - Launch the VM
 - Wait for the error
 - Start the virtual router manually
 - Launch the VM.

--
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

[jira] [Closed] (CLOUDSTACK-2388) HA Host Allocator returning 0 suitable hosts but starting the VM manually finds one.

2013-08-02 Thread Dominic Blais (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominic Blais closed CLOUDSTACK-2388.
-

Resolution: Fixed

 HA Host Allocator returning 0 suitable hosts but starting the VM manually 
 finds one.
 --

 Key: CLOUDSTACK-2388
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2388
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.0.2
 Environment: Ubuntu 12.04.2 amd64 Server on management and compute 
 nodes.
Reporter: Dominic Blais
 Attachments: Management Logs.txt


 Whenever I try to crash a compute node for the purpose of testing HA 
 respawning of VM on another host, HA-Worker returns  Host Allocator 
 returning 0 suitable hosts.
 2013-05-08 09:11:18,179 DEBUG [cloud.deploy.FirstFitPlanner] 
 (HA-Worker-2:work-2) Calling HostAllocators to find suitable hosts
 2013-05-08 09:11:18,179 DEBUG [allocator.impl.FirstFitAllocator] 
 (HA-Worker-2:work-2 FirstFitRoutingAllocator) Looking for hosts in dc: 1  
 pod:1  cluster:1
 2013-05-08 09:11:18,181 DEBUG [allocator.impl.FirstFitAllocator] 
 (HA-Worker-2:work-2 FirstFitRoutingAllocator) FirstFitAllocator has 0 hosts 
 to check for allocation: []
 2013-05-08 09:11:18,183 DEBUG [allocator.impl.FirstFitAllocator] 
 (HA-Worker-2:work-2 FirstFitRoutingAllocator) Found 0 hosts for allocation 
 after prioritization: []
 2013-05-08 09:11:18,184 DEBUG [allocator.impl.FirstFitAllocator] 
 (HA-Worker-2:work-2 FirstFitRoutingAllocator) Looking for speed=4000Mhz, 
 Ram=4096
 2013-05-08 09:11:18,184 DEBUG [allocator.impl.FirstFitAllocator] 
 (HA-Worker-2:work-2 FirstFitRoutingAllocator) Host Allocator returning 0 
 suitable hosts
 The thing is, starting the VM manually right after is working because there 
 are plenty enough of ressources 

--
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

[jira] [Updated] (CLOUDSTACK-3377) Error seen when system vms are started and due to which template download is not initiated : com.google.gson.JsonParseException: The JsonDeserializer com.cloud.agent


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama updated CLOUDSTACK-3377:
-

Priority: Blocker  (was: Major)

 Error seen when system vms are started and due to which template download is 
 not initiated : com.google.gson.JsonParseException: The JsonDeserializer 
 com.cloud.agent.transport.ArrayTypeAdaptor@697537aa failed to deserialize 
 json object 
 

 Key: CLOUDSTACK-3377
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3377
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Abhinav Roy
Priority: Blocker
 Fix For: 4.2.0


 Steps :
 
 1. Deploy an advanced zone setup with XenServer as host.
 Expected behaviour :
 ===
 1. Deployment should be successful and the system vms should be created and 
 started without any issue.
 Observed behaviour :
 ==
 Though the system vms get started and are in running state, during the start 
 process the following error is thrown due to which the templates don't get 
 downloaded
 013-07-05 11:52:03,688 ERROR [agent.transport.Request] 
 (AgentManager-Handler-8:null) Caught problem with 
 [{StartupSecondaryStorageCommand:{type:SecondaryStorage,dataCenter:1,pod:1,guid:s-1-VM-NfsSecondaryStorageResource,name:s-1-VM,version:4.2.0-SNAPSHOT,iqn:NoIqn,publicIpAddress:10.102.195.11,publicNetmask:255.255.252.0,publicMacAddress:06:7a:80:00:00:15,privateIpAddress:10.102.195.42,privateMacAddress:06:2c:6e:00:00:0c,privateNetmask:255.255.252.0,storageIpAddress:10.102.195.42,storageNetmask:255.255.252.0,storageMacAddress:06:2c:6e:00:00:0c,resourceName:NfsSecondaryStorageResource,contextMap:{},wait:0}}]
 com.google.gson.JsonParseException: The JsonDeserializer 
 com.cloud.agent.transport.ArrayTypeAdaptor@697537aa failed to deserialize 
 json object 
 [{StartupSecondaryStorageCommand:{type:SecondaryStorage,dataCenter:1,pod:1,guid:s-1-VM-NfsSecondaryStorageResource,name:s-1-VM,version:4.2.0-SNAPSHOT,iqn:NoIqn,publicIpAddress:10.102.195.11,publicNetmask:255.255.252.0,publicMacAddress:06:7a:80:00:00:15,privateIpAddress:10.102.195.42,privateMacAddress:06:2c:6e:00:00:0c,privateNetmask:255.255.252.0,storageIpAddress:10.102.195.42,storageNetmask:255.255.252.0,storageMacAddress:06:2c:6e:00:00:0c,resourceName:NfsSecondaryStorageResource,contextMap:{},wait:0}}]
  given the type class [Lcom.cloud.agent.api.Command;
 at 
 com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
 at 
 com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
 at 
 com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
 at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
 at 
 com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
 at 
 com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
 at com.google.gson.Gson.fromJson(Gson.java:551)
 at com.google.gson.Gson.fromJson(Gson.java:498)
 at com.cloud.agent.transport.Request.getCommands(Request.java:235)
 at 
 com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(AgentManagerImpl.java:1196)
 at 
 com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerImpl.java:1349)
 at 
 com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.doTask(ClusteredAgentManagerImpl.java:659)
 at com.cloud.utils.nio.Task.run(Task.java:83)
 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:679)
 Caused by: com.cloud.utils.exception.CloudRuntimeException: can't find 
 StartupSecondaryStorageCommand
 at 
 com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:77)
 at 
 com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:37)
 at 
 com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
 ... 15 more
 2013-07-05 11:52:03,692 WARN  [utils.nio.Task] (AgentManager-Handler-8:null) 
 Caught the following exception but

[jira] [Commented] (CLOUDSTACK-3377) Error seen when system vms are started and due to which template download is not initiated : com.google.gson.JsonParseException: The JsonDeserializer com.cloud.age


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727923#comment-13727923
 ] 

Chandan Purushothama commented on CLOUDSTACK-3377:
--

I increased the priority to blocker as I am facing the same issue during 
Upgrades. The workaround will bring down all the existing VMs present on the 
XenServer Host,

Thank you,
Chandan.

 Error seen when system vms are started and due to which template download is 
 not initiated : com.google.gson.JsonParseException: The JsonDeserializer 
 com.cloud.agent.transport.ArrayTypeAdaptor@697537aa failed to deserialize 
 json object 
 

 Key: CLOUDSTACK-3377
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3377
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Abhinav Roy
Priority: Blocker
 Fix For: 4.2.0


 Steps :
 
 1. Deploy an advanced zone setup with XenServer as host.
 Expected behaviour :
 ===
 1. Deployment should be successful and the system vms should be created and 
 started without any issue.
 Observed behaviour :
 ==
 Though the system vms get started and are in running state, during the start 
 process the following error is thrown due to which the templates don't get 
 downloaded
 013-07-05 11:52:03,688 ERROR [agent.transport.Request] 
 (AgentManager-Handler-8:null) Caught problem with 
 [{StartupSecondaryStorageCommand:{type:SecondaryStorage,dataCenter:1,pod:1,guid:s-1-VM-NfsSecondaryStorageResource,name:s-1-VM,version:4.2.0-SNAPSHOT,iqn:NoIqn,publicIpAddress:10.102.195.11,publicNetmask:255.255.252.0,publicMacAddress:06:7a:80:00:00:15,privateIpAddress:10.102.195.42,privateMacAddress:06:2c:6e:00:00:0c,privateNetmask:255.255.252.0,storageIpAddress:10.102.195.42,storageNetmask:255.255.252.0,storageMacAddress:06:2c:6e:00:00:0c,resourceName:NfsSecondaryStorageResource,contextMap:{},wait:0}}]
 com.google.gson.JsonParseException: The JsonDeserializer 
 com.cloud.agent.transport.ArrayTypeAdaptor@697537aa failed to deserialize 
 json object 
 [{StartupSecondaryStorageCommand:{type:SecondaryStorage,dataCenter:1,pod:1,guid:s-1-VM-NfsSecondaryStorageResource,name:s-1-VM,version:4.2.0-SNAPSHOT,iqn:NoIqn,publicIpAddress:10.102.195.11,publicNetmask:255.255.252.0,publicMacAddress:06:7a:80:00:00:15,privateIpAddress:10.102.195.42,privateMacAddress:06:2c:6e:00:00:0c,privateNetmask:255.255.252.0,storageIpAddress:10.102.195.42,storageNetmask:255.255.252.0,storageMacAddress:06:2c:6e:00:00:0c,resourceName:NfsSecondaryStorageResource,contextMap:{},wait:0}}]
  given the type class [Lcom.cloud.agent.api.Command;
 at 
 com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
 at 
 com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
 at 
 com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
 at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
 at 
 com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
 at 
 com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
 at com.google.gson.Gson.fromJson(Gson.java:551)
 at com.google.gson.Gson.fromJson(Gson.java:498)
 at com.cloud.agent.transport.Request.getCommands(Request.java:235)
 at 
 com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(AgentManagerImpl.java:1196)
 at 
 com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerImpl.java:1349)
 at 
 com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.doTask(ClusteredAgentManagerImpl.java:659)
 at com.cloud.utils.nio.Task.run(Task.java:83)
 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:679)
 Caused by: com.cloud.utils.exception.CloudRuntimeException: can't find 
 StartupSecondaryStorageCommand
 at 
 com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:77)
 at 
 com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:37)
 at

[jira] [Commented] (CLOUDSTACK-4021) [Automation] TestExplicitDedication.test_01_deploy_vm_with_explicit_dedication failed to deploy VM

2013-08-02 Thread Rayees Namathponnan (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727984#comment-13727984
 ] 

Rayees Namathponnan commented on CLOUDSTACK-4021:
-

1) We should skip the test; if there is no host without VM
2) Can you possible to check host on second zone ? there wil be host without 
any running VM

 [Automation] 
 TestExplicitDedication.test_01_deploy_vm_with_explicit_dedication failed to 
 deploy VM
 --

 Key: CLOUDSTACK-4021
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4021
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.2.0
 Environment: Automation
Reporter: Rayees Namathponnan
Assignee: Saksham Srivastava
 Fix For: 4.2.0


 Test case 
 integration.component.test_explicit_dedication.TestExplicitDedication.test_01_deploy_vm_with_explicit_dedication
  failing automation runs 
 Error Message
 Execute cmd: asyncquery failed, due to: {errorcode : 533, errortext : 
 u'Unable to create a deployment for 
 VM[User|dec11341-27b0-4fc9-86f4-7570037a456c], Please check the affinity 
 groups provided, there may not be sufficient capacity to follow them'}
 Stacktrace
 Traceback (most recent call last):
   File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
 testMethod()
   File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_explicit_dedication.py,
  line 204, in test_01_deploy_vm_with_explicit_dedication
 mode=self.services[mode]
   File 
 /usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py, line 
 388, in create
 virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
   File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 614, in deployVirtualMachine
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py, line 
 230, in marvin_request
 response = self.poll(asyncJobId, response_type)
   File 
 /usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py, line 
 91, in poll
 asyncquery, asyncResonse.jobresult)
 cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode : 
 533, errortext : u'Unable to create a deployment for 
 VM[User|dec11341-27b0-4fc9-86f4-7570037a456c], Please check the affinity 
 groups provided, there may not be sufficient capacity to follow them'}
 Looks like test case trying to create VM eventhough there is no host with 
 emplty VM 

--
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

[jira] [Closed] (CLOUDSTACK-3248) XenServer Host got removed successfully inspite of running VMs on the host


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandan Purushothama closed CLOUDSTACK-3248.



Verified that when the Admin removes a host from the Cluster. The stopped VMs 
with local storage on the host gets destroyed and the host gets successfully 
removed.

 XenServer Host got removed successfully inspite of running VMs on the host
 --

 Key: CLOUDSTACK-3248
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3248
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Chandan Purushothama
Assignee: Koushik Das
Priority: Critical
 Fix For: 4.2.0


 ==
 From the API log:
 ==
 2013-06-27 11:48:36,855 INFO [cloud.api.ApiServer] (catalina-exec-15:null) 
 (userId=2 accountId=2 sessionId=62A69AC91786781EA9BC2F5E534F5590) 
 10.252.120.177 -- GET 
 command=deleteHostid=405585d6-3579-4c8b-82a0-425158ac061aforced=falseresponse=jsonsessionkey=LAHSBLWAfVc8ti8IX%2FCBeUyvaJQ%3D_=1372358962625
  200 { deletehostresponse : { success : true} }
 ==
 From the Management Server Log:
 ==
 2013-06-27 11:48:36,765 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null) 
 ===START=== 10.252.120.177 -- GET 
 command=deleteHostid=405585d6-3579-4c8b-82a0-425158ac061aforced=falseresponse=jsonsessionkey=LAHSBLWAfVc8ti8IX%2FCBeUyvaJQ%3D_=1372358962625
 2013-06-27 11:48:36,800 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 ConsoleProxyManagerImpl_EnhancerByCloudStack_edb8e808
 2013-06-27 11:48:36,800 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 PremiumSecondaryStorageManagerImpl_EnhancerByCloudStack_9f8bf2f0
 2013-06-27 11:48:36,800 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 JuniperSRXExternalFirewallElement_EnhancerByCloudStack_c0d55fca
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 KvmServerDiscoverer_EnhancerByCloudStack_6a93cc3b
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 VmwareServerDiscoverer_EnhancerByCloudStack_c0f46d01
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 NetscalerElement_EnhancerByCloudStack_2c0cf22
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 NetworkUsageManagerImpl_EnhancerByCloudStack_fed7434f
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 F5ExternalLoadBalancerElement_EnhancerByCloudStack_91202979
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 NiciraNvp
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 CiscoVnmcElement_EnhancerByCloudStack_439d7cf0
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 OvmDiscoverer_EnhancerByCloudStack_d6ea6366
 2013-06-27 11:48:36,802 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 LxcServerDiscoverer_EnhancerByCloudStack_2f0a46f8
 2013-06-27 11:48:36,801 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 OvmDiscoverer_EnhancerByCloudStack_d6ea6366
 2013-06-27 11:48:36,802 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 LxcServerDiscoverer_EnhancerByCloudStack_2f0a46f8
 2013-06-27 11:48:36,802 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Dispatching resource state event DELETE_HOST to 
 XcpServerDiscoverer_EnhancerByCloudStack_6d80ebbf
 2013-06-27 11:48:36,802 DEBUG [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-15:null) Deleting Host: 5 
 Guid:b213f6c1-16d6-4fa3-8998-dce12a65d1e3
 2013-06-27 11:48:36,806 DEBUG [dc.dao.DataCenterIpAddressDaoImpl] 
 (catalina-exec-15:null) Releasing ip address: 10.223.57.194 data center 1
 2013-06-27

[jira] [Closed] (CLOUDSTACK-2777) AWSAPI: build and packaging issue causing EC2 SOAP test failures

2013-08-02 Thread Rayees Namathponnan (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rayees Namathponnan closed CLOUDSTACK-2777.
---


Closing this, as per the comment from Prachi

 AWSAPI: build and packaging issue causing EC2 SOAP test failures
 

 Key: CLOUDSTACK-2777
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2777
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Packaging
Affects Versions: 4.2.0
Reporter: Prachi Damle
Assignee: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.2.0


 awsapi webapp is not getting deployed on axis2 when management server is 
 started. 
 Following  file is missing and causing this issue: 
 webapps7080/awsapi/WEB-INF/services/cloud-ec2.aar
 I don’t see this file on a setup using rpm packages under:  
 /usr/share/cloudstack-bridge/webapps/awsapi/WEB-INF/services. So looks like 
 the .aar file is not being generated by the apache build.
 Apache build should  create this jar file [cloud-ec2.aar] too and package it 
 under webapps7080/awsapi/WEB-INF/services

--
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

[jira] [Resolved] (CLOUDSTACK-2777) AWSAPI: build and packaging issue causing EC2 SOAP test failures

2013-08-02 Thread Prachi Damle (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prachi Damle resolved CLOUDSTACK-2777.
--

Resolution: Fixed

 AWSAPI: build and packaging issue causing EC2 SOAP test failures
 

 Key: CLOUDSTACK-2777
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2777
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Packaging
Affects Versions: 4.2.0
Reporter: Prachi Damle
Assignee: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.2.0


 awsapi webapp is not getting deployed on axis2 when management server is 
 started. 
 Following  file is missing and causing this issue: 
 webapps7080/awsapi/WEB-INF/services/cloud-ec2.aar
 I don’t see this file on a setup using rpm packages under:  
 /usr/share/cloudstack-bridge/webapps/awsapi/WEB-INF/services. So looks like 
 the .aar file is not being generated by the apache build.
 Apache build should  create this jar file [cloud-ec2.aar] too and package it 
 under webapps7080/awsapi/WEB-INF/services

--
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

[jira] [Reopened] (CLOUDSTACK-2777) AWSAPI: build and packaging issue causing EC2 SOAP test failures

2013-08-02 Thread Prachi Damle (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prachi Damle reopened CLOUDSTACK-2777:
--


No, this cannot be closed.  This shouyld be verified using 4.2 rpm packages by 
QA.

 AWSAPI: build and packaging issue causing EC2 SOAP test failures
 

 Key: CLOUDSTACK-2777
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2777
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Packaging
Affects Versions: 4.2.0
Reporter: Prachi Damle
Assignee: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.2.0


 awsapi webapp is not getting deployed on axis2 when management server is 
 started. 
 Following  file is missing and causing this issue: 
 webapps7080/awsapi/WEB-INF/services/cloud-ec2.aar
 I don’t see this file on a setup using rpm packages under:  
 /usr/share/cloudstack-bridge/webapps/awsapi/WEB-INF/services. So looks like 
 the .aar file is not being generated by the apache build.
 Apache build should  create this jar file [cloud-ec2.aar] too and package it 
 under webapps7080/awsapi/WEB-INF/services

--
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

[jira] [Commented] (CLOUDSTACK-3858) [Upgrade from 2.2.15 to 4.2] After upgrade from 2.2.15 to 4.2 the tomcat.conf file and server.xml file is missing due to which the management server can't be start

2013-08-02 Thread Sudha Ponnaganti (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728032#comment-13728032
 ] 

Sudha Ponnaganti commented on CLOUDSTACK-3858:
--

Should not create links manually - need to fix this for 4.2 release

 [Upgrade from 2.2.15 to 4.2] After upgrade from 2.2.15 to 4.2 the tomcat.conf 
 file and server.xml file is missing due to which the management server can't 
 be started 
 --

 Key: CLOUDSTACK-3858
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3858
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Infra
Affects Versions: 4.2.0
 Environment: MS : CentOS 6.1
 Host : Xen 6.0.2
 2.2.15 build : CloudStack-2.2.15-2-rhel6.2
 4.2 : The relevant upgrade build
Reporter: Abhinav Roy
Assignee: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.2.0


 Steps :
 ==
 1. Deploy a CS advanced zone setup with CentOS 6.1 and MS and Xen 6.0.2 as 
 the Host.
 2. Do some pre-upgrade configurations.
 3. Upgrade to 4.2 using the following steps... ( i am just pasting the 
 console output i got on executing those steps)
 ./install.sh 
 Setting up the temporary repository...
 Cleaning Yum cache...
 Loaded plugins: fastestmirror
 Cleaning repos: base cloud-temp extras updates
 7 metadata files removed
 Welcome to the CloudPlatform Installer.  What would you like to do?
 NOTE:   For installing KVM agent, please setup 
 EPELhttp://fedoraproject.org/wiki/EPEL yum repo first;
 For installing CloudPlatform on RHEL6.x, please setup 
 distribution yum repo either from ISO or from your registeration account.
 3.We detect you already have MySql server installed, you can 
 bypass mysql install chapter in CloudPlatform installation guide.
 Or you can use E) to remove current mysql then re-run install.sh 
 selecting D) to reinstall if you think existing MySql server has some trouble.
 For MySql downloaded from community, the script may not be able to 
 detect it.
 M) Install the Management Server   
 A) Install the Agent
 B) Install BareMetal Agent
 S) Install the Usage Monitor
 U) Upgrade the CloudPlatform packages installed on this computer
 R) Stop any running CloudPlatform services and remove the CloudPlatform 
 packages from this computer
 E) Remove the MySQL server (will not remove the MySQL databases)
 Q) Quit
   u
 Updating the CloudPlatform and its dependencies...
 Loaded plugins: fastestmirror
 Loading mirror speeds from cached hostfile
  * base: mirrors.ispros.com.bd
  * extras: mirrors.ispros.com.bd
  * updates: mirrors.ispros.com.bd
 base  
   
   | 3.7 kB 00:00 
 cloud-temp
   
   | 1.3 kB 00:00 ... 
 cloud-temp/primary
   
   | 2.4 kB 00:00 ... 
 cloud-temp
   
  6/6
 extras
   
   | 3.4 kB 00:00 
 updates   
   
   | 3.4 kB 00:00 
 Setting up Update Process
 Resolving Dependencies
 -- Running transaction check
 --- Package cloud-client.x86_64 0:2.2.15-2.el6 will be obsoleted
 --- Package cloud-client-ui.x86_64 0:2.2.15-2.el6 will be obsoleted
 --- Package cloud-core.x86_64 0:2.2.15-2.el6 will be obsoleted
 --- Package cloud-deps.x86_64 0:2.2.15-2.el6 will be obsoleted
 --- Package cloud-python.x86_64 0:2.2.15-2.el6 will be obsoleted
 --- Package cloud-server.x86_64 0:2.2.15-2.el6 will be obsoleted
 --- Package cloud-setup.x86_64 0:2.2.15-2.el6 will be obsoleted
 --- Package cloud-utils.x86_64 0:2.2.15-2.el6 will be obsoleted
 --- Package cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el6 will be obsoleting
 --- Package cloudstack-management.x86_64

[jira] [Resolved] (CLOUDSTACK-4023) [Automation] NPE happening while shutdown the router as part of network clean

2013-08-02 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-4023.
---

Resolution: Fixed

Fixed with 8fe4c240bf25063491c44c55015a24bd19f831fd

 [Automation] NPE happening while shutdown the router as  part of network clean
 --

 Key: CLOUDSTACK-4023
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4023
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Network Controller
Affects Versions: 4.2.0
 Environment: KVM
 Build 4.2
Reporter: Rayees Namathponnan
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 This issue observed during  automation regression test execution;  NPE 
 happening while clean up account 
 2013-07-05 06:48:11,300 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-94:job-2022 = [ e3f4f9a6-2ed4-4a22-a57e-c3a92b9831c5 ]) 
 Expunged VM[DomainRouter|r-676-QA]
 2013-07-05 06:48:11,325 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-1:null) Seq 4-1845363589: Processing:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10, [{com.cloud.age
 nt.api.StopAnswer:{vncPort:0,result:true,wait:0}}] }
 2013-07-05 06:48:11,325 DEBUG [agent.transport.Request] 
 (Network-Scavenger-1:null) Seq 4-1845363589: Received:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10, { StopAnswer } }
 2013-07-05 06:48:11,327 WARN  [cloud.network.NetworkManagerImpl] 
 (Network-Scavenger-1:null) Unable to complete shutdown of the network 
 elements due to element: VirtualRouter
 com.cloud.utils.exception.CloudRuntimeException: Problem updating stats after 
 reboot/stop
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.processStopOrRebootAnswer(VirtualNetworkApplianceManagerImpl.java:608)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.finalizeStop(VirtualNetworkApplianceManagerImpl.java:2632)
 at 
 com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.finalizeStop(VpcVirtualNetworkApplianceManagerImpl.java:1397)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1282)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2765)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:266)
 at 
 com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:660)
 at 
 com.cloud.network.NetworkManagerImpl.shutdownNetworkElementsAndResources(NetworkManagerImpl.java:2855)
 at 
 com.cloud.network.NetworkManagerImpl.shutdownNetwork(NetworkManagerImpl.java:2785)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.network.NetworkManagerImpl$NetworkGarbageCollector.reallyRun(NetworkManagerImpl.java:3197)
 at 
 com.cloud.network.NetworkManagerImpl$NetworkGarbageCollector.run(NetworkManagerImpl.java:3142)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 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:679)
 Caused by: java.lang.NullPointerException
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.processStopOrRebootAnswer(VirtualNetworkApplianceManagerImpl.java:586)
 ... 29 more
 2013-07-05 06:48:11,334 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-94:job-2022 = [ e3f4f9a6-2ed4-4a22-a57e-c3a92b9831c5 ]) Network 
 id=542 is destroyed successfully, cleaning up corresponding resources now.
 2013-07-05 06:48:11,338 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-94:job-2022 = [ e3f4f9a6-2ed4-4a22-a57e-c3a92b9831c5 ]) Deleted 
 ip range for private

[jira] [Commented] (CLOUDSTACK-4023) [Automation] NPE happening while shutdown the router as part of network clean


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728057#comment-13728057
 ] 

ASF subversion and git services commented on CLOUDSTACK-4023:
-

Commit 8fe4c240bf25063491c44c55015a24bd19f831fd in branch refs/heads/4.2 from 
[~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8fe4c24 ]

CLOUDSTACK-4023: lock the network during the shutdownNetwork (just the way we 
do when implement network)


 [Automation] NPE happening while shutdown the router as  part of network clean
 --

 Key: CLOUDSTACK-4023
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4023
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Network Controller
Affects Versions: 4.2.0
 Environment: KVM
 Build 4.2
Reporter: Rayees Namathponnan
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 This issue observed during  automation regression test execution;  NPE 
 happening while clean up account 
 2013-07-05 06:48:11,300 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-94:job-2022 = [ e3f4f9a6-2ed4-4a22-a57e-c3a92b9831c5 ]) 
 Expunged VM[DomainRouter|r-676-QA]
 2013-07-05 06:48:11,325 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-1:null) Seq 4-1845363589: Processing:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10, [{com.cloud.age
 nt.api.StopAnswer:{vncPort:0,result:true,wait:0}}] }
 2013-07-05 06:48:11,325 DEBUG [agent.transport.Request] 
 (Network-Scavenger-1:null) Seq 4-1845363589: Received:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10, { StopAnswer } }
 2013-07-05 06:48:11,327 WARN  [cloud.network.NetworkManagerImpl] 
 (Network-Scavenger-1:null) Unable to complete shutdown of the network 
 elements due to element: VirtualRouter
 com.cloud.utils.exception.CloudRuntimeException: Problem updating stats after 
 reboot/stop
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.processStopOrRebootAnswer(VirtualNetworkApplianceManagerImpl.java:608)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.finalizeStop(VirtualNetworkApplianceManagerImpl.java:2632)
 at 
 com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.finalizeStop(VpcVirtualNetworkApplianceManagerImpl.java:1397)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1282)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2765)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:266)
 at 
 com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:660)
 at 
 com.cloud.network.NetworkManagerImpl.shutdownNetworkElementsAndResources(NetworkManagerImpl.java:2855)
 at 
 com.cloud.network.NetworkManagerImpl.shutdownNetwork(NetworkManagerImpl.java:2785)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.network.NetworkManagerImpl$NetworkGarbageCollector.reallyRun(NetworkManagerImpl.java:3197)
 at 
 com.cloud.network.NetworkManagerImpl$NetworkGarbageCollector.run(NetworkManagerImpl.java:3142)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 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:679)
 Caused by: java.lang.NullPointerException
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.processStopOrRebootAnswer(VirtualNetworkApplianceManagerImpl.java:586)
 ... 29 more
 2013-07-05 06:48:11,334 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-94:job-2022 = [

[jira] [Created] (CLOUDSTACK-4051) UI UCS: Add UCS Manager : password entered should not be echoed in plain text

2013-08-02 Thread ASF subversion and git services (JIRA)

angeline shen created CLOUDSTACK-4051:
-

 Summary: UI  UCS: Add UCS Manager :  password entered  should not 
be echoed in plain text
 Key: CLOUDSTACK-4051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UCS, UI
Affects Versions: 4.2.0
 Environment: MS 10.223.195.117build   
CloudPlatform-4.2-316-rhel6.3.tar.gz
host10.223.51.4  baremetal
Reporter: angeline shen
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.2.0


1. Add UCS Manager dialog:  password entry being entered  should not be echoed 
in plain text

--
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

[jira] [Commented] (CLOUDSTACK-3748) AddS3Cmd NPE


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728080#comment-13728080
 ] 

ASF subversion and git services commented on CLOUDSTACK-3748:
-

Commit 838c972da06ed2c55ba03a2533fe8b4b9cfddbbf in branch refs/heads/4.2 from 
[~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=838c972 ]

CLOUDSTACK-3748: AddS3Cmd NPE.


 AddS3Cmd NPE 
 -

 Key: CLOUDSTACK-3748
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3748
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: John Burwell
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.2.0


 When executing the addS3 API command using the following parameters:
 The following NPE occurred:
 s3 : {
 accesskey: CIQFFQ7NAACERI99P9_B,
 secretkey: 6jmfhptBBvWile1bUTSbnJCYW8qnPoU8WaNpIw==,
 bucket: jsb-cloudstack-templates,
 endpoint: 192.168.56.100:8080,
 usehttps: false
 }
 ERROR [cloud.api.ApiServer] (705052256@qtp-836177268-0:) unhandled exception 
 executing api command: addS3
 java.lang.NullPointerException
   at 
 org.apache.cloudstack.api.command.admin.storage.AddS3Cmd.execute(AddS3Cmd.java:104)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
   at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
   at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at 
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
   at 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
   at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
   at org.mortbay.jetty.Server.handle(Server.java:326)
   at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
   at 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
   at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
   at 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 This NPE causes the API call to fail with a 530 error as depicted in the 
 following Marvin traceback:
 Traceback (most recent call last):
   File /Users/jburwell/.virtualenvs/cloudstack/bin/nosetests, line 8, in 
 module
 load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 118, in __init__
 **extra_args)
   File 
 /Users/jburwell/.homebrew/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/main.py,
  line 94, in __init__
 self.parseArgs(argv)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 135, in parseArgs
 self.config.configure(argv, doc=self.usage())
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/config.py,
  line 344, in configure
 self.plugins.configure(options, self)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 284, in configure
 cfg(options, config)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 99, in __call__
 return self.call(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 167, in simple
 result = meth(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/marvinPlugin.py,
  line 68, in configure

[jira] [Commented] (CLOUDSTACK-3426) UCS: Session cookie refresh must be supported.

2013-08-02 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728082#comment-13728082
 ] 

angeline shen commented on CLOUDSTACK-3426:
---

verified  CloudPlatform-4.2-316-rhel6.3.tar.gz

 UCS: Session cookie refresh must be supported.
 --

 Key: CLOUDSTACK-3426
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3426
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Management Server
Affects Versions: 4.2.0
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 A stale cookie will raise authentication error and subsequent API calls will 
 fail.
 We need a mechanism to refresh cookie based on recommendations below.
 While executing listUCSProfiles::
 { listucsprofileresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ 
 classId=\lsServer\ /\nresponse: configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ response=\yes\ 
 errorCode=\552\ invocationResult=\service-unavailable\ 
 errorDescr=\Authorization required\ /configFindDnsByClassId\n} }
 Here is the description from UCS API programming guide. (Full version here:: 
 http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/api/overview.html#wp1127584)
 Failed Requests
 The response to a failed request includes XML attributes for errorCode and 
 errorDescr. The following is an example of a response to a failed request:
 configConfMo dn=fabric/server
   cookie=real_cookie
   response=yes
   errorCode=103
   invocationResult=unidentified-fail
   errorDescr=can't create; object already exists.
 /configConfMo
 From forums 
 (http://developer.cisco.com/web/unifiedcomputing/community/-/message_boards/message/2774526?p_p_auth=iBnpvD2j)
 And from here 
 (http://developer.cisco.com/web/unifiedcomputing/blogroll/-/blogs/ucs-xml-api-hello-world)
 We have an authentication cookie but this cookie will expire in two hours, 
 the output from the aaaLogin recommends a cookie refresh every 10 minutes. To 
 refresh the authentication cookie use the aaaRefresh method.
 So basically we need a mechanism for cookie refresh. Which we do not have for 
 now.
 When I tried to add a new manager (so that cookie is fresh ??) ListProfiles 
 succeeded. 

--
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

[jira] [Commented] (CLOUDSTACK-3748) AddS3Cmd NPE


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728079#comment-13728079
 ] 

ASF subversion and git services commented on CLOUDSTACK-3748:
-

Commit ad20a9b6fa09d3595c2dec8c213cb3fee35d1973 in branch refs/heads/4.2 from 
[~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ad20a9b ]

CLOUDSTACK-3748:AddS3Cmd NPE.


 AddS3Cmd NPE 
 -

 Key: CLOUDSTACK-3748
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3748
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: John Burwell
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.2.0


 When executing the addS3 API command using the following parameters:
 The following NPE occurred:
 s3 : {
 accesskey: CIQFFQ7NAACERI99P9_B,
 secretkey: 6jmfhptBBvWile1bUTSbnJCYW8qnPoU8WaNpIw==,
 bucket: jsb-cloudstack-templates,
 endpoint: 192.168.56.100:8080,
 usehttps: false
 }
 ERROR [cloud.api.ApiServer] (705052256@qtp-836177268-0:) unhandled exception 
 executing api command: addS3
 java.lang.NullPointerException
   at 
 org.apache.cloudstack.api.command.admin.storage.AddS3Cmd.execute(AddS3Cmd.java:104)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
   at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
   at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at 
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
   at 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
   at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
   at org.mortbay.jetty.Server.handle(Server.java:326)
   at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
   at 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
   at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
   at 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 This NPE causes the API call to fail with a 530 error as depicted in the 
 following Marvin traceback:
 Traceback (most recent call last):
   File /Users/jburwell/.virtualenvs/cloudstack/bin/nosetests, line 8, in 
 module
 load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 118, in __init__
 **extra_args)
   File 
 /Users/jburwell/.homebrew/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/main.py,
  line 94, in __init__
 self.parseArgs(argv)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 135, in parseArgs
 self.config.configure(argv, doc=self.usage())
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/config.py,
  line 344, in configure
 self.plugins.configure(options, self)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 284, in configure
 cfg(options, config)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 99, in __call__
 return self.call(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 167, in simple
 result = meth(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/marvinPlugin.py,
  line 68, in configure

[jira] [Commented] (CLOUDSTACK-3986) baremetal - create basic zone for baremetal fail - Dhcp service provider for this network does not support the dhcp across multiple subnets


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728078#comment-13728078
 ] 

angeline shen commented on CLOUDSTACK-3986:
---

verifiedCloudPlatform-4.2-316-rhel6.3.tar.gz

 baremetal - create basic zone for baremetal fail - Dhcp service provider for 
 this network does not support the dhcp across multiple subnets
 ---

 Key: CLOUDSTACK-3986
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3986
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Baremetal, Management Server
Affects Versions: 4.2.0
 Environment: MS10.223.195.117build
 CloudPlatform-4.2-297-rhel6.3.tar.gz
Reporter: angeline shen
Assignee: frank zhang
Priority: Blocker
 Fix For: 4.2.0

 Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - 
 Mozilla Firefox.png


 1. create network offering for baremetal
 2. create basic zone for baremetal with network offering failed -  
 Result:
 UI error:Dhcp service provider for this network does not support the dhcp 
 across multiple subnets

--
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

[jira] [Closed] (CLOUDSTACK-3426) UCS: Session cookie refresh must be supported.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angeline shen closed CLOUDSTACK-3426.
-


 UCS: Session cookie refresh must be supported.
 --

 Key: CLOUDSTACK-3426
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3426
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Management Server
Affects Versions: 4.2.0
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 A stale cookie will raise authentication error and subsequent API calls will 
 fail.
 We need a mechanism to refresh cookie based on recommendations below.
 While executing listUCSProfiles::
 { listucsprofileresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ 
 classId=\lsServer\ /\nresponse: configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ response=\yes\ 
 errorCode=\552\ invocationResult=\service-unavailable\ 
 errorDescr=\Authorization required\ /configFindDnsByClassId\n} }
 Here is the description from UCS API programming guide. (Full version here:: 
 http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/api/overview.html#wp1127584)
 Failed Requests
 The response to a failed request includes XML attributes for errorCode and 
 errorDescr. The following is an example of a response to a failed request:
 configConfMo dn=fabric/server
   cookie=real_cookie
   response=yes
   errorCode=103
   invocationResult=unidentified-fail
   errorDescr=can't create; object already exists.
 /configConfMo
 From forums 
 (http://developer.cisco.com/web/unifiedcomputing/community/-/message_boards/message/2774526?p_p_auth=iBnpvD2j)
 And from here 
 (http://developer.cisco.com/web/unifiedcomputing/blogroll/-/blogs/ucs-xml-api-hello-world)
 We have an authentication cookie but this cookie will expire in two hours, 
 the output from the aaaLogin recommends a cookie refresh every 10 minutes. To 
 refresh the authentication cookie use the aaaRefresh method.
 So basically we need a mechanism for cookie refresh. Which we do not have for 
 now.
 When I tried to add a new manager (so that cookie is fresh ??) ListProfiles 
 succeeded. 

--
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

[jira] [Commented] (CLOUDSTACK-3386) NPE from VolumeMotionService when creating a template

2013-08-02 Thread Animesh Chaturvedi (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728086#comment-13728086
 ] 

Animesh Chaturvedi commented on CLOUDSTACK-3386:


Prasanna can you confirm if this is not seen for 4.2

 NPE from VolumeMotionService when creating a template
 -

 Key: CLOUDSTACK-3386
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3386
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: Future
Reporter: Prasanna Santhanam
Priority: Critical
 Fix For: Future

 Attachments: kvm.tar.bz2, xcp.tar.bz2


 On deploying a VM sometimes the template fails to create on primary storage.
 The following NPE is observed at these times. It's not clear why this would
 fail sometimes yet. Attaching agent (DEBUG) and management server logs
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,817 DEBUG [storage.volume.VolumeServiceImpl] 
 (Job-Executor-72:job-185) failed to create template on storage
 Jul  5 20:31:01 java.lang.NullPointerException  
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:45)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:390)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:490)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2482)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2539)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:852)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:230)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3317)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2877)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2863)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:514)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.FutureTask.run(FutureTask.java:166)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.lang.Thread.run(Thread.java:679)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,826 DEBUG [cloud.storage.VolumeManagerImpl] 
 (Job-Executor-72:job-185) Unable to create 
 Vol[61|vm=58|ROOT]:java.lang.NullPointerException
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,826 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-72:job-185) Unable to contact resource.
 Jul  5 20:31:01

[jira] [Closed] (CLOUDSTACK-3432) UCS:API: associatesUscProfileToBlade fails with authentication error.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angeline shen closed CLOUDSTACK-3432.
-

Resolution: Fixed

 UCS:API: associatesUscProfileToBlade fails with authentication error.
 -

 Key: CLOUDSTACK-3432
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3432
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 associatesUscProfileToBlade fails with authentication error.
 Refer to request and response below.
 Request is 
 http://10.223.132.160:8080/client/api?command=associatesUcsProfileToBladeucsmanagerid=14profiledn=org-root/ls-UCS_Testingbladeid=26response=jsonsessionkey=AgmkzfbrMK3YEVyj1qPahEtaPk4%3DfetchLatest=falsesortBy=usagepage=0pagesize=8_=1373411256093
 Response is
 { associateucsprofiletobladeresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configConfMos 
 inHierarchical=\true\inConfigspair 
 key=\org-root/ls-profile-for-blade-26\lsServer 
 statsPolicyName=\default\ mgmtFwPolicyName=\\ status=\\ 
 dynamicConPolicyName=\\ usrLbl=\\ hostFwPolicyName=\\ 
 vconProfileName=\\ agentPolicyName=\\ biosProfileName=\\ 
 powerPolicyName=\\ extIPState=\none\ scrubPolicyName=\\ 
 localDiskPolicyName=\\ mgmtAccessPolicyName=\\ identPoolName=\\ 
 solPolicyName=\\ bootPolicyName=\\ srcTemplName=\\ uuid=\\ 
 dn=\org-root/ls-profile-for-blade-26\ descr=\\ 
 maintPolicyName=\\lsBinding rn=\pn\ restrictMigration=\no\ 
 pnDn=\sys/chassis-1/blade-2\ 
 //lsServer/pair/inConfigs/configConfMos\nresponse: configConfMos 
 cookie=\\ response=\yes\ errorCode=\552\ 
 invocationResult=\service-unavailable\ errorDescr=\Authorization 
 required\ /configConfMos\n} }
 is cookie missing?

--
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

[jira] [Commented] (CLOUDSTACK-3432) UCS:API: associatesUscProfileToBlade fails with authentication error.


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728092#comment-13728092
 ] 

angeline shen commented on CLOUDSTACK-3432:
---

Verifiedbuild

Associate profile to blade:  org-root/ls-simpleProfile   succeeds

2013-08-02 13:38:13,077 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
===START===  10.216.133.70 -- GET  
command=associateUcsProfileToBladeresponse=jsonsessionkey=TNL5%2FuKPp8B7zw%2B28T10DXjx5HY%3Ducsmanagerid=e17249fa-edfe-460c-a6e5-67e539976789profiledn=org-root%2Fls-simpleProfilebladeid=abc01993-7959-4392-8a68-5737a855c1f5_=1375476505297
2013-08-02 13:38:13,114 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-22:null) submit async job-41 = [ 
d95ea087-4dda-4a66-a531-3923477b33f2 ], details: AsyncJobVO {id:41, userId: 2, 
accountId: 2, sessionKey: null, instanceType: None, instanceId: null, cmd: 
org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd, cmdOriginator: null, 
cmdInfo: 
{response:json,bladeid:abc01993-7959-4392-8a68-5737a855c1f5,sessionkey:TNL5/uKPp8B7zw+28T10DXjx5HY\u003d,profiledn:org-root/ls-simpleProfile,cmdEventType:UCS.ASSOCIATEPROFILE,ctxUserId:2,httpmethod:GET,_:1375476505297,ctxAccountId:2,ctxStartEventId:133,ucsmanagerid:e17249fa-edfe-460c-a6e5-67e539976789},
 cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
processStatus: 0, resultCode: 0, result: null, initMsid: 7662288766739, 
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-02 13:38:13,116 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) 
===END===  10.216.133.70 -- GET  
command=associateUcsProfileToBladeresponse=jsonsessionkey=TNL5%2FuKPp8B7zw%2B28T10DXjx5HY%3Ducsmanagerid=e17249fa-edfe-460c-a6e5-67e539976789profiledn=org-root%2Fls-simpleProfilebladeid=abc01993-7959-4392-8a68-5737a855c1f5_=1375476505297
2013-08-02 13:38:13,120 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-41:job-41 = [ d95ea087-4dda-4a66-a531-3923477b33f2 ]) Executing 
org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd for job-41 = [ 
d95ea087-4dda-4a66-a531-3923477b33f2 ]
2013-08-02 13:38:13,219 DEBUG [ucs.manager.UcsManagerImpl] 
(Job-Executor-41:job-41 = [ d95ea087-4dda-4a66-a531-3923477b33f2 ]) association 
response is  configResolveDn dn=sys/chassis-1/blade-1 
cookie=1375476153/7d9068f7-64af-4f8e-b25e-c229166dd426 response=yes 
outConfig computeBlade adminPower=policy adminState=in-service 
assignedToDn=org-root/ls-profile-for-blade-1 association=establishing 
availability=unavailable availableMemory=65536 chassisId=1 
checkPoint=discovered  connPath=A connStatus=A descr= 
discovery=complete dn=sys/chassis-1/blade-1 fltAggr=0 fsmDescr=Service 
profile org-root/ls-profile-for-blade-1 association with server 
sys/chassis-1/blade-1(FSM:sam:dme:ComputePhysicalAssociate) fsmFlags= 
fsmPrev=AssociatePreSanitize fsmProgr=4 fsmRmtInvErrCode=none 
fsmRmtInvErrDescr= fsmRmtInvRslt= fsmStageDescr=Preparing to check 
hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PreSanitize) 
fsmStamp=2013-08-02T13:44:42.487 fsmStatus=AssociatePreSanitize fsmTry=1 
intId=36071 lc=discovered lcTs=1969-12-31T16:00:00.000 
lowVoltageMemory=low-voltage managingInst=A memorySpeed=1333 
mfgTime=2012-10-13T17:00:00.000 model=UCSB-B200-M3 name= 
numOfAdaptors=1 numOfCores=12 numOfCoresEnabled=12 numOfCpus=2 
numOfEthHostIfs=1 numOfFcHostIfs=1 numOfThreads=24 operPower=off 
operQualifier= operState=config operability=operable 
originalUuid=78eb1a7d-7665-4cdb-a995-e4953a63d1d7 partNumber=73-13217-08 
presence=equipped revision=0  serial=FCH16407N8A serverId=1/1 
slotId=1  totalMemory=65536 usrLbl= 
uuid=78eb1a7d-7665-4cdb-a995-e4953a63d1d7 vendor=Cisco Systems Inc 
vid=V03/ /outConfig /configResolveDn
2013-08-02 13:38:15,228 DEBUG [ucs.manager.UcsManagerImpl] 
(Job-Executor-41:job-41 = [ d95ea087-4dda-4a66-a531-3923477b33f2 ]) association 
response is  configResolveDn dn=sys/chassis-1/blade-1 
cookie=1375476153/7d9068f7-64af-4f8e-b25e-c229166dd426 response=yes 
outConfig computeBlade adminPower=policy adminState=in-service 
assignedToDn=org-root/ls-profile-for-blade-1 association=establishing 
availability=unavailable availableMemory=65536 chassisId=1 
checkPoint=discovered  connPath=A connStatus=A descr= 
discovery=complete dn=sys/chassis-1/blade-1 fltAggr=0 fsmDescr=Service 
profile org-root/ls-profile-for-blade-1 association with server 
sys/chassis-1/blade-1(FSM:sam:dme:ComputePhysicalAssociate) fsmFlags= 
fsmPrev=AssociatePreSanitize fsmProgr=4 fsmRmtInvErrCode=none 
fsmRmtInvErrDescr= fsmRmtInvRslt= fsmStageDescr=Preparing to check 
hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PreSanitize) 
fsmStamp=2013-08-02T13:44:42.487 fsmStatus=AssociatePreSanitize fsmTry=1 
intId=36071 lc=discovered lcTs=1969-12-31T16:00:00.000 
lowVoltageMemory=low-voltage managingInst=A memorySpeed=1333

[jira] [Closed] (CLOUDSTACK-3453) UCS:API: List Blades after decommissioning a blade, listUcsBlades API returns wrong number of total blades

2013-08-02 Thread ASF subversion and git services (JIRA)

[
https://issues.apache.org/jira/browse/CLOUDSTACK-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

angeline shen closed CLOUDSTACK-3453.
-

Frank Zhang instruction: this is invalid test, close bug

UCS:API: List Blades after decommissioning a blade, listUcsBlades API returns
wrong number of total blades
--

Key: CLOUDSTACK-3453
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3453
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API, UCS
Affects Versions: 4.2.0
Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: frank zhang
Priority: Critical
Fix For: 4.2.0

If a user decommissions a blade from UCS Chassis; List BLades still returns
the previos number of blades.
Assuming this is due to data being fetched from MS DB rather then polling UCS
for latest Blade information and status.
We need to update the DB with latest information regarding total number of
blades and their status.
To reproduce: disconnect a blade physically from chassis.
Re register the UCS Manager to CS.
Issue a listUcsBlade API.
Also note that re-registering of UCS should not be required. A dynamic
polling of Blades and other relevant info should be supported. And Cs DB
should be updated accordingly.

[jira] [Commented] (CLOUDSTACK-3748) AddS3Cmd NPE


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728097#comment-13728097
 ] 

ASF subversion and git services commented on CLOUDSTACK-3748:
-

Commit 9f3f13f70a9d4c2c2fc3058cde425cdde2bb43a0 in branch refs/heads/master 
from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9f3f13f ]

CLOUDSTACK-3748:AddS3Cmd NPE.


 AddS3Cmd NPE 
 -

 Key: CLOUDSTACK-3748
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3748
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: John Burwell
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.2.0


 When executing the addS3 API command using the following parameters:
 The following NPE occurred:
 s3 : {
 accesskey: CIQFFQ7NAACERI99P9_B,
 secretkey: 6jmfhptBBvWile1bUTSbnJCYW8qnPoU8WaNpIw==,
 bucket: jsb-cloudstack-templates,
 endpoint: 192.168.56.100:8080,
 usehttps: false
 }
 ERROR [cloud.api.ApiServer] (705052256@qtp-836177268-0:) unhandled exception 
 executing api command: addS3
 java.lang.NullPointerException
   at 
 org.apache.cloudstack.api.command.admin.storage.AddS3Cmd.execute(AddS3Cmd.java:104)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
   at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
   at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at 
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
   at 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
   at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
   at org.mortbay.jetty.Server.handle(Server.java:326)
   at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
   at 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
   at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
   at 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 This NPE causes the API call to fail with a 530 error as depicted in the 
 following Marvin traceback:
 Traceback (most recent call last):
   File /Users/jburwell/.virtualenvs/cloudstack/bin/nosetests, line 8, in 
 module
 load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 118, in __init__
 **extra_args)
   File 
 /Users/jburwell/.homebrew/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/main.py,
  line 94, in __init__
 self.parseArgs(argv)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 135, in parseArgs
 self.config.configure(argv, doc=self.usage())
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/config.py,
  line 344, in configure
 self.plugins.configure(options, self)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 284, in configure
 cfg(options, config)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 99, in __call__
 return self.call(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 167, in simple
 result = meth(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/marvinPlugin.py,
  line 68, in configure

[jira] [Commented] (CLOUDSTACK-3748) AddS3Cmd NPE

2013-08-02 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728098#comment-13728098
 ] 

ASF subversion and git services commented on CLOUDSTACK-3748:
-

Commit a2f1d233787b9182a1ef4ae45eee3bfc0f4d6eb5 in branch refs/heads/master 
from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a2f1d23 ]

CLOUDSTACK-3748: AddS3Cmd NPE.


 AddS3Cmd NPE 
 -

 Key: CLOUDSTACK-3748
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3748
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: John Burwell
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.2.0


 When executing the addS3 API command using the following parameters:
 The following NPE occurred:
 s3 : {
 accesskey: CIQFFQ7NAACERI99P9_B,
 secretkey: 6jmfhptBBvWile1bUTSbnJCYW8qnPoU8WaNpIw==,
 bucket: jsb-cloudstack-templates,
 endpoint: 192.168.56.100:8080,
 usehttps: false
 }
 ERROR [cloud.api.ApiServer] (705052256@qtp-836177268-0:) unhandled exception 
 executing api command: addS3
 java.lang.NullPointerException
   at 
 org.apache.cloudstack.api.command.admin.storage.AddS3Cmd.execute(AddS3Cmd.java:104)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
   at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
   at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at 
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
   at 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
   at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
   at org.mortbay.jetty.Server.handle(Server.java:326)
   at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
   at 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
   at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
   at 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 This NPE causes the API call to fail with a 530 error as depicted in the 
 following Marvin traceback:
 Traceback (most recent call last):
   File /Users/jburwell/.virtualenvs/cloudstack/bin/nosetests, line 8, in 
 module
 load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 118, in __init__
 **extra_args)
   File 
 /Users/jburwell/.homebrew/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/main.py,
  line 94, in __init__
 self.parseArgs(argv)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 135, in parseArgs
 self.config.configure(argv, doc=self.usage())
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/config.py,
  line 344, in configure
 self.plugins.configure(options, self)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 284, in configure
 cfg(options, config)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 99, in __call__
 return self.call(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 167, in simple
 result = meth(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/marvinPlugin.py,
  line 68, in configure

[jira] [Resolved] (CLOUDSTACK-3748) AddS3Cmd NPE


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen resolved CLOUDSTACK-3748.
--

Resolution: Fixed

 AddS3Cmd NPE 
 -

 Key: CLOUDSTACK-3748
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3748
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: John Burwell
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.2.0


 When executing the addS3 API command using the following parameters:
 The following NPE occurred:
 s3 : {
 accesskey: CIQFFQ7NAACERI99P9_B,
 secretkey: 6jmfhptBBvWile1bUTSbnJCYW8qnPoU8WaNpIw==,
 bucket: jsb-cloudstack-templates,
 endpoint: 192.168.56.100:8080,
 usehttps: false
 }
 ERROR [cloud.api.ApiServer] (705052256@qtp-836177268-0:) unhandled exception 
 executing api command: addS3
 java.lang.NullPointerException
   at 
 org.apache.cloudstack.api.command.admin.storage.AddS3Cmd.execute(AddS3Cmd.java:104)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
   at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
   at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at 
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
   at 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
   at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
   at org.mortbay.jetty.Server.handle(Server.java:326)
   at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
   at 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
   at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
   at 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 This NPE causes the API call to fail with a 530 error as depicted in the 
 following Marvin traceback:
 Traceback (most recent call last):
   File /Users/jburwell/.virtualenvs/cloudstack/bin/nosetests, line 8, in 
 module
 load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 118, in __init__
 **extra_args)
   File 
 /Users/jburwell/.homebrew/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/main.py,
  line 94, in __init__
 self.parseArgs(argv)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py,
  line 135, in parseArgs
 self.config.configure(argv, doc=self.usage())
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/config.py,
  line 344, in configure
 self.plugins.configure(options, self)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 284, in configure
 cfg(options, config)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 99, in __call__
 return self.call(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py,
  line 167, in simple
 result = meth(*arg, **kw)
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/marvinPlugin.py,
  line 68, in configure
 deploy.loadCfg() if options.load else deploy.deploy()
   File 
 /Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployDataCenter.py,
  line 577, in deploy
 self.configureS3(self.config.s3)
   File

[jira] [Created] (CLOUDSTACK-4052) vSphere VM state not updated within cloudstack

Ahmad Emneina created CLOUDSTACK-4052:
-

 Summary: vSphere VM state not updated within cloudstack
 Key: CLOUDSTACK-4052
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4052
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server, VMware
Affects Versions: 4.2.0
Reporter: Ahmad Emneina
Priority: Critical
 Fix For: 4.2.0


Issue 1: vSphere HA 
Admin powered off a host within the cluster. VMware behaved as expected and 
restarted the VMs on a different host within a minute or two. CloudStack also 
detected the host going down within about a minute. 
However, CloudStack never detects the VM as being 'started' again, when it was 
booted by VMware HA. 

Issue 2: vSphere VM Sync - State Not Updated 
When a VM is shutdown from within the OS, CloudStack correctly detects that it 
is down and changes the state to 'Stopped'. 
However, If they turn this back on from within VMware, it never changes back to 
'Running'. 

This means that in a HA scenario, the machine will never be manageable from 
within CS until the user clicks the 'Start' button. However, this also triggers 
CS to shut the machine down before it starts it again, which would cause 
another outage for all machines that were recovered by HA. 
The alert email from CS says that HA will be attempted within 1800 seconds (30 
minutes). We wouldnt want it to then try to start the VM itself 30 minutes 
later and cause another outage. bad. bad CS!

--
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

[jira] [Created] (CLOUDSTACK-4053) Removal of AddSwiftCmd and ListSwiftsCmd APIs broke api back compatibility

Min Chen created CLOUDSTACK-4053:


 Summary: Removal of AddSwiftCmd and ListSwiftsCmd APIs broke api 
back compatibility
 Key: CLOUDSTACK-4053
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4053
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.2.0
Reporter: Min Chen
Priority: Critical
 Fix For: 4.2.0


In Swift implementation rework, AddSwiftCmd and ListSwiftsCmd are removed, this 
will break api back-compatibility.

--
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

[jira] [Created] (CLOUDSTACK-4054) Register template missing some fields

Ahmad Emneina created CLOUDSTACK-4054:
-

 Summary: Register template missing some fields
 Key: CLOUDSTACK-4054
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4054
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Ahmad Emneina
Priority: Critical
 Fix For: 4.2.0


Fields highlighted (see attachment) are missing until you change from All Zones 
to Single Zone and back to All Zones again.

--
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

[jira] [Updated] (CLOUDSTACK-4054) Register template missing some fields


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ahmad Emneina updated CLOUDSTACK-4054:
--

Attachment: screenshot-1.jpg

screenshot of missing fields

 Register template missing some fields
 -

 Key: CLOUDSTACK-4054
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4054
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Ahmad Emneina
Priority: Critical
 Fix For: 4.2.0

 Attachments: screenshot-1.jpg


 Fields highlighted (see attachment) are missing until you change from All 
 Zones to Single Zone and back to All Zones again.

--
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

[jira] [Created] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type

Ahmad Emneina created CLOUDSTACK-4055:
-

 Summary: Windows Server 2012 (64-Bit) being deployed as 'Other OS' 
type
 Key: CLOUDSTACK-4055
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Ahmad Emneina
Priority: Critical
 Fix For: 4.2.0


Registered a Windows Server 2012 64-bit template in ACS and made sure Windows 
Server 2012 (64-Bit) was selected as the OS type when registering the template, 
however when we build an instance in CS it creates the OS type in VMware as 
Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS type is an 
available option in VMware.

--
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

[jira] [Updated] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type

2013-08-02 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ahmad Emneina updated CLOUDSTACK-4055:
--

Attachment: win2012_other_os.png

screen cap of what happens when deploying win 2012 via CS

 Windows Server 2012 (64-Bit) being deployed as 'Other OS' type
 --

 Key: CLOUDSTACK-4055
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Ahmad Emneina
Priority: Critical
 Fix For: 4.2.0

 Attachments: win2012_other_os.png


 Registered a Windows Server 2012 64-bit template in ACS and made sure Windows 
 Server 2012 (64-Bit) was selected as the OS type when registering the 
 template, however when we build an instance in CS it creates the OS type in 
 VMware as Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS 
 type is an available option in VMware.

--
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

[jira] [Commented] (CLOUDSTACK-4053) Removal of AddSwiftCmd and ListSwiftsCmd APIs broke api back compatibility


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728142#comment-13728142
 ] 

ASF subversion and git services commented on CLOUDSTACK-4053:
-

Commit 612ac971bc2b8c7b4284c0491bebefec6ba3002c in branch refs/heads/4.2 from 
[~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=612ac97 ]

CLOUDSTACK-4053: Removal of AddSwiftCmd and ListSwiftsCmd APIs broke api
back compatibility.


 Removal of AddSwiftCmd and ListSwiftsCmd APIs broke api back compatibility
 --

 Key: CLOUDSTACK-4053
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4053
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: Min Chen
Assignee: Min Chen
Priority: Critical
 Fix For: 4.2.0


 In Swift implementation rework, AddSwiftCmd and ListSwiftsCmd are removed, 
 this will break api back-compatibility.

--
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

[jira] [Created] (CLOUDSTACK-4056) System VMs are connected to untagged Management Port Group on ESX when a Tagged Management Port Group is created

Ahmad Emneina created CLOUDSTACK-4056:
-

 Summary: System VMs are connected to untagged Management Port 
Group on ESX when a Tagged Management Port Group is created
 Key: CLOUDSTACK-4056
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4056
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server, VMware
Affects Versions: 4.2.0
Reporter: Ahmad Emneina
Priority: Critical
 Fix For: 4.2.0


Management Network Port group is VLAN tagged on vSwitch0.

After creating an advanced Zone and enabling it CloudStack created 2 private 
port-groups on vSwitch0 (management vSwitch), one tagged with correct VLAN 
(same VLAN ID as the management network port group) and one untagged private 
port group without any VLAN ID..but for some reason system VM private NICs are 
connected to the untagged port group, which fails connect to CloudStack and the 
setup was staled (until we manually added the VLAN ID to the port group, which 
was removed later somehow).

--
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

[jira] [Assigned] (CLOUDSTACK-3237) [vmware][SM] Migrate volume is failing when there are snapshots for that volume

2013-08-02 Thread Kelven Yang (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kelven Yang reassigned CLOUDSTACK-3237:
---

Assignee: Kelven Yang

 [vmware][SM] Migrate volume is failing when there are snapshots for that 
 volume
 ---

 Key: CLOUDSTACK-3237
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3237
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.2.0
 Environment: vmware, 
Reporter: Srikanteswararao Talluri
Assignee: Kelven Yang
Priority: Blocker
 Fix For: 4.2.0

 Attachments: mgmt_27.log.zip


 Steps to reproduce:
 1. create a VM 
 2. take snapshot of root volume of VM
 3. migrate root volume to a suitable storage pool
 ===START===  10.101.255.87 -- GET  
 command=findStoragePoolsForMigrationid=f7c12988-61a8-49dc-a5d3-cd8653744a8eresponse=jsonsessionkey=dfd5NAw2qEmBOi3931kcin3eZtQ%3D_=1372333879848
 2013-06-27 22:46:36,408 DEBUG [storage.allocator.LocalStoragePoolAllocator] 
 (catalina-exec-14:null) LocalStoragePoolAllocator trying to find storage pool 
 to fit the vm
 2013-06-27 22:46:36,410 DEBUG 
 [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null) 
 ClusterScopeStoragePoolAllocator looking for storage pool
 2013-06-27 22:46:36,410 DEBUG 
 [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null) 
 Looking for pools in dc: 1  pod:1  cluster:1
 2013-06-27 22:46:36,419 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null) 
 Checking if storage pool is suitable, name: null ,poolId: 1
 2013-06-27 22:46:36,419 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null) 
 StoragePool is in avoid set, skipping this pool
 2013-06-27 22:46:36,421 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null) 
 Checking if storage pool is suitable, name: null ,poolId: 3
 2013-06-27 22:46:36,429 DEBUG [cloud.storage.StorageManagerImpl] 
 (catalina-exec-14:null) Checking pool 3 for storage, totalSize: 
 590228480, usedBytes: 3490243883008, usedPct: 0.5913377617779474, disable 
 threshold: 0.85
 2013-06-27 22:46:36,461 DEBUG [cloud.storage.StorageManagerImpl] 
 (catalina-exec-14:null) Checking pool: 3 for volume allocation 
 [Vol[4|vm=4|ROOT]], maxSize : 1180456960, totalAllocatedSize : 
 23622320128, askingSize : 0, allocated disable threshold: 0.85
 2013-06-27 22:46:36,464 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null) 
 Checking if storage pool is suitable, name: null ,poolId: 5
 2013-06-27 22:46:36,471 DEBUG [cloud.storage.StorageManagerImpl] 
 (catalina-exec-14:null) Checking pool 5 for storage, totalSize: 
 590228480, usedBytes: 3490243883008, usedPct: 0.5913377617779474, disable 
 threshold: 0.85
 2013-06-27 22:46:36,492 DEBUG [cloud.storage.StorageManagerImpl] 
 (catalina-exec-14:null) Checking pool: 5 for volume allocation 
 [Vol[4|vm=4|ROOT]], maxSize : 1180456960, totalAllocatedSize : 
 35433480192, askingSize : 0, allocated disable threshold: 0.85
 2013-06-27 22:46:36,492 DEBUG 
 [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null) 
 FirstFitStoragePoolAllocator returning 2 suitable storage pools
 2013-06-27 22:46:36,506 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null) 
 ===END===  10.101.255.87 -- GET  
 command=findStoragePoolsForMigrationid=f7c12988-61a8-49dc-a5d3-cd8653744a8eresponse=jsonsessionkey=dfd5NAw2qEmBOi3931kcin3eZtQ%3D_=1372333879848
 2013-06-27 22:46:39,967 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-9:null) Ping from 4
 2013-06-27 22:46:40,804 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-11:null) SeqA 3-10940: Processing Seq 3-10940:  { Cmd , 
 MgmtId: -1, via: 3, Ver: v1, Flags: 11, 
 [{ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n  
 \connections\: []\n},wait:0}}] }
 2013-06-27 22:46:40,813 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-11:null) SeqA 3-10940: Sending Seq 3-10940:  { Ans: , 
 MgmtId: 7566222426160, via: 3, Ver: v1, Flags: 100010, 
 [{AgentControlAnswer:{result:true,wait:0}}] }
 2013-06-27 22:46:41,091 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
 ===START===  10.101.255.87 -- GET  
 command=migrateVolumelivemigrate=truestorageid=e690ef30-851c-33b0-a1b3-38fd7fa4c40cvolumeid=f7c12988-61a8-49dc-a5d3-cd8653744a8eresponse=jsonsessionkey=dfd5NAw2qEmBOi3931kcin3eZtQ%3D_=1372333884566
 2013-06-27 22:46:41,135 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-18:null) submit async job-42, details: AsyncJobVO {id:42, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: None,

[jira] [Created] (CLOUDSTACK-4057) Cannot unselect VPC network when only want to select isolated network

Ahmad Emneina created CLOUDSTACK-4057:
-

 Summary: Cannot unselect VPC network when only want to select 
isolated network
 Key: CLOUDSTACK-4057
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4057
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Ahmad Emneina
Priority: Blocker
 Fix For: 4.2.0
 Attachments: vpc_issue.png

I got an environment where an isolated network (non-VPC, cfiso1) and an 
isolated network (VPC, WebTier) is present. 
When trying to add to a new instance cfiso01 only this is not possible in the 
GUI. I am not able to unselect “WebTier”. 
 

--
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

[jira] [Updated] (CLOUDSTACK-4057) Cannot unselect VPC network when only want to select isolated network

2013-08-02 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ahmad Emneina updated CLOUDSTACK-4057:
--

Attachment: vpc_issue.png

ui issue screen cap, cant unselect vpc network.

 Cannot unselect VPC network when only want to select isolated network
 -

 Key: CLOUDSTACK-4057
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4057
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Ahmad Emneina
Priority: Blocker
 Fix For: 4.2.0

 Attachments: vpc_issue.png


 I got an environment where an isolated network (non-VPC, cfiso1) and an 
 isolated network (VPC, WebTier) is present. 
 When trying to add to a new instance cfiso01 only this is not possible in the 
 GUI. I am not able to unselect “WebTier”. 
  

--
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

[jira] [Commented] (CLOUDSTACK-2569) [UI]Option to Enable/Disable CiscoVnmc provider in not available

[
https://issues.apache.org/jira/browse/CLOUDSTACK-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728156#comment-13728156
]

ASF subversion and git services commented on CLOUDSTACK-2569:
-

Commit 6940d256c9b0e3161f5cda7838b614c8a84fb899 in branch refs/heads/4.2 from
[~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6940d25 ]

CLOUDSTACK-2569: UI Infrastructure zone physical network VNMC provider
fix a bug that queryAsyncJobResult API kept being called even after the async
job was finished.

[UI]Option to Enable/Disable CiscoVnmc provider in not available
-

Key: CLOUDSTACK-2569
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2569
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Jessica Wang
Priority: Critical
Fix For: 4.2.0

Attachments: apilog.log, CISCOVNMCUI.png, management-server.log,
screenshot-1.jpg, vnmcclouddmp.sql

Setup: Advanced Networking Zone with Nexus VMWARE Cluster
Steps:
1. Access Management server as adimin
2. Infrastructure - Physical Network - Network service providers - Add
VNMC provider and Add ASA provider
Observation:
1. By default Cisco VNMC provider is in disabled state. After adding VNMC
provider it got enabled.
2. But there is no option provided to enable/disable it. (Attached the snap)

[jira] [Updated] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone(showing SG enabled to true eventhough zone created with sharednetwork)

2013-08-02 Thread Animesh Chaturvedi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-2730:
---

Fix Version/s: 4.2.0

 vmware:addcluster failed in basiczone(showing SG enabled to true eventhough 
 zone created with sharednetwork)
 

 Key: CLOUDSTACK-2730
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Venkata Siva Vijayendra Bhamidipati
 Fix For: 4.2.0

 Attachments: management-server.log


 In case of vmware ,when i try to configure basic zone with shared 
 network.addcluster failed with 
 Creating cluster Something went wrong; please correct the following:Don't 
 support hypervisor type VMware in advanced security enabled zone even though 
 i select the bassic and shared network.
 1.select the  zone type as basic
 2.select the network type as shared
 3.provide pod ,guest details  and configure primary and secondary detaisl
 4.click on finish to create basic zone with shared network mode
 Actual result:
 even though i select shared network in basic zone,it sends security group 
 enble to true internally. due to this  addcluster failed .
 It throws following error:
 Creating cluster Something went wrong; please correct the following:Don't 
 support hypervisor type VMware in advanced security enabled zone
 mysql select * from data_center where id=2\G;
 *** 1. row ***
id: 2
  name: zone1
  uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
   description: NULL
  dns1: 10.103.128.16
  dns2: NULL
 internal_dns1: 10.103.128.16
 internal_dns2: NULL
   gateway: NULL
   netmask: NULL
router_mac_address: 02:00:00:00:00:01
   mac_address: 23
guest_network_cidr: NULL
domain: NULL
 domain_id: NULL
   networktype: Basic
  dns_provider: VirtualRouter
  gateway_provider: NULL
 firewall_provider: NULL
 dhcp_provider: VirtualRouter
   lb_provider: ElasticLoadBalancerVm
  vpn_provider: NULL
 userdata_provider: VirtualRouter
  allocation_state: Disabled
zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
 is_security_group_enabled: 1
  is_local_storage_enabled: 0
   removed: NULL
 owner: NULL
   created: NULL
   lastUpdated: NULL
  engine_state: Disabled
  ip6_dns1: NULL
  ip6_dns2: NULL
 1 row in set (0.00 sec)
 mysql select * from networks where id=209\G;
 *** 1. row ***
id: 209
  name: defaultGuestNetwork
  uuid: eca88272-2ad4-47a8-ab90-442393b6d034
  display_text: defaultGuestNetwork
  traffic_type: Guest
 broadcast_domain_type: Native
 broadcast_uri: vlan://untagged
   gateway: NULL
  cidr: NULL
  mode: Dhcp
   network_offering_id: 7
   physical_network_id: 201
data_center_id: 2
 guru_name: DirectPodBasedNetworkGuru
 state: Setup
   related: 209
 domain_id: 1
account_id: 1
  dns1: NULL
  dns2: NULL
 guru_data: NULL
set_fields: 0
  acl_type: Domain
network_domain: cs1cloud.internal
reservation_id: NULL
guest_type: Shared
  restart_required: 0
   created: 2013-05-29 12:21:04
   removed: NULL
 specify_ip_ranges: 1
vpc_id: NULL
   ip6_gateway: NULL
  ip6_cidr: NULL
  network_cidr: NULL
   display_network: 1
network_acl_id: NULL
 1 row in set (0.00 sec)
 http://10.147.59.83:8080/client/api?command=createZonenetworktype=Basicname=zone1dns1=10.103.128.16internaldns1=10.103.128.16response=jsonsessionkey=6%2BUi17Y6gpixRBAR9s4yhQCQkhs%3D_=1369810303912
 { createzoneresponse :  { zone : 
 {id:c642382d-8587-4cd7-a1e9-5a488bb47da7,name:zone1,dns1:10.103.128.16,internaldns1:10.103.128.16,networktype:Basic,securitygroupsenabled:true,allocationstate:Disabled,zonetoken:68de3ddf-3a08-3371-9506-a57a4a0a8af5,dhcpprovider:VirtualRouter,localstorageenabled:false}
  }  }

[jira] [Resolved] (CLOUDSTACK-2569) [UI]Option to Enable/Disable CiscoVnmc provider in not available

2013-08-02 Thread Jessica Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-2569.
--

Resolution: Fixed

 [UI]Option to Enable/Disable CiscoVnmc provider in not available 
 -

 Key: CLOUDSTACK-2569
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2569
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.2.0

 Attachments: apilog.log, CISCOVNMCUI.png, management-server.log, 
 screenshot-1.jpg, vnmcclouddmp.sql


 Setup: Advanced Networking Zone with Nexus VMWARE Cluster 
 Steps:
 1. Access Management server as adimin
 2. Infrastructure - Physical Network - Network service providers - Add 
 VNMC provider and Add ASA provider 
 Observation:
 1. By default Cisco VNMC provider is in disabled state. After adding VNMC 
 provider it got enabled. 
 2. But there is no option provided to enable/disable it. (Attached the snap)
  

--
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

[jira] [Commented] (CLOUDSTACK-2569) [UI]Option to Enable/Disable CiscoVnmc provider in not available

2013-08-02 Thread ASF subversion and git services (JIRA)

[
https://issues.apache.org/jira/browse/CLOUDSTACK-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728158#comment-13728158
]

ASF subversion and git services commented on CLOUDSTACK-2569:
-

Commit ab91def10c22b9a19423ba91146b4262a3af9a53 in branch refs/heads/master
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ab91def ]

CLOUDSTACK-2569: UI Infrastructure zone physical network VNMC provider
fix a bug that queryAsyncJobResult API kept being called even after the async
job was finished.

[UI]Option to Enable/Disable CiscoVnmc provider in not available
-

Attachments: apilog.log, CISCOVNMCUI.png, management-server.log,
screenshot-1.jpg, vnmcclouddmp.sql

[jira] [Commented] (CLOUDSTACK-3905) [VMWARE]Can not add Standard/DVSwitch when Nexus global config is set to true

2013-08-02 Thread Venkata Siva Vijayendra Bhamidipati (JIRA)

[
https://issues.apache.org/jira/browse/CLOUDSTACK-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728166#comment-13728166
]

Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3905:
-

The usage of nexus 1000v and vmware dvs are each controlled by their global
configuration flags vmware.use.nexus.vswitch and vmware.use.dvswitch
respectively. If one is set, the other cannot be used. If both are set, it
pretty much boils down to the code that checks for one flag before the other.

Currently, the mgmt server doesn't have a way to specify mutual exclusivity
between global flags. Either we should put this in, or move these flags from a
global config level to the zone level, where explicit code checks can be put in
to disallow both flags to be set.

[VMWARE]Can not add Standard/DVSwitch when Nexus global config is set to true
-

Key: CLOUDSTACK-3905
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3905
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Devices
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.2.0

Steps:
1. Set below Global config parameters to true :
vmware.use.dvswitch Enable/Disable Nexus/Vmware dvSwitch in VMware
environment true

vmware.use.nexus.vswitch Enable/Disable Cisco Nexus 1000v vSwitch in
VMware environment true
2. Tried to add Standard vSwitch/DVSwitch Cluster :
Observations:
1. Nexus 1000v Switch configuration details are mandatory to add cluster
2. It will not let to add new cluster with DVS/Standard vSwitch.

[jira] [Updated] (CLOUDSTACK-4035) [Upgrade][2.2.16 to 4.2] Autoscale wizard missing counter param in UI - fails configuration

2013-08-02 Thread Animesh Chaturvedi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-4035:
---

Summary: [Upgrade][2.2.16 to 4.2] Autoscale wizard missing counter param in 
UI - fails configuration  (was: [Upgrade][2.2.16 to 4.2] [UI] Autoscale wizard 
missing counter param in UI - fails configuration)

 [Upgrade][2.2.16 to 4.2] Autoscale wizard missing counter param in UI - fails 
 configuration
 ---

 Key: CLOUDSTACK-4035
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4035
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Upgrade
Affects Versions: 4.2.0
 Environment: Upgraded setup from 2.2.16 to 4.2, Netscaler as external 
 LB device
Reporter: Sowmya Krishnan
Priority: Blocker
 Fix For: 4.2.0

 Attachments: countermissing.png, DB_DUMP_2216_before_upgrade.sql, 
 DB_DUMP_42_after_upgrade.sql


 Steps
 =
 Upgrade from 2.2.16 to 4.2.
 Create a network offering with LB service provided by Netscaler
 Acquire a public IP and configure autoscaling with it
 Fails during configuration since counter value is missing
 Firebug log:
 { conditionresponse : 
 {uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to 
 execute API command condition due to missing parameter counterid} }
 Attached screen shot 

--
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

[jira] [Resolved] (CLOUDSTACK-4053) Removal of AddSwiftCmd and ListSwiftsCmd APIs broke api back compatibility


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen resolved CLOUDSTACK-4053.
--

Resolution: Fixed

 Removal of AddSwiftCmd and ListSwiftsCmd APIs broke api back compatibility
 --

 Key: CLOUDSTACK-4053
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4053
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: Min Chen
Assignee: Min Chen
Priority: Critical
 Fix For: 4.2.0


 In Swift implementation rework, AddSwiftCmd and ListSwiftsCmd are removed, 
 this will break api back-compatibility.

--
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

[jira] [Assigned] (CLOUDSTACK-3386) NPE from VolumeMotionService when creating a template


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen reassigned CLOUDSTACK-3386:


Assignee: Min Chen

 NPE from VolumeMotionService when creating a template
 -

 Key: CLOUDSTACK-3386
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3386
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: Future
Reporter: Prasanna Santhanam
Assignee: Min Chen
Priority: Critical
 Fix For: Future

 Attachments: kvm.tar.bz2, xcp.tar.bz2


 On deploying a VM sometimes the template fails to create on primary storage.
 The following NPE is observed at these times. It's not clear why this would
 fail sometimes yet. Attaching agent (DEBUG) and management server logs
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,817 DEBUG [storage.volume.VolumeServiceImpl] 
 (Job-Executor-72:job-185) failed to create template on storage
 Jul  5 20:31:01 java.lang.NullPointerException  
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:45)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:390)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:490)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2482)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2539)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:852)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:230)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3317)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2877)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2863)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:514)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.FutureTask.run(FutureTask.java:166)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.lang.Thread.run(Thread.java:679)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,826 DEBUG [cloud.storage.VolumeManagerImpl] 
 (Job-Executor-72:job-185) Unable to create 
 Vol[61|vm=58|ROOT]:java.lang.NullPointerException
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,826 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-72:job-185) Unable to contact resource.
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com 
 com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1] is

[jira] [Assigned] (CLOUDSTACK-4040) [Object_store_refactor] System VMs are not spinning up if S3 storage configuration is not part of zone creation wizard

[
https://issues.apache.org/jira/browse/CLOUDSTACK-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Min Chen reassigned CLOUDSTACK-4040:

Assignee: Min Chen

[Object_store_refactor] System VMs are not spinning up if S3 storage
configuration is not part of zone creation wizard
--

Key: CLOUDSTACK-4040
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4040
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Environment: Latest build from ACS 4.2 branch
Storage: S3 for secondary and NFS for primary
Reporter: Sanjeev N
Assignee: Min Chen
Priority: Blocker
Fix For: 4.2.0

Attachments: cloud.dmp, management-server.rar

System VMs are not spinning up if S3 storage configuration is not part of
zone creation wizard. They are coming up only when s3 is added during zone
creation wizard.
Steps to Reproduce:

1.Install CS and start MS
2.Add secondary storage with S3 as the storage provider before creating the
zone.
3.Create zone with xen cluster and skip adding secondary storage during zone
creation.
4.Add secondary staging storage in the zone created
5.Enable zone.
Expected Result:
=
After zone creation routing template should be downloaded to S3 and after
adding staging storage system vms spinning up should be initiated.
Actual Result:
===
Routing template was not downloaded to S3 after zone creation and system vm
spinning up not initiated.
Observations:
===
1.After step2 kvm routing template was downloaded to S3 and I could see the
template info in template_store_ref table.
2.After step3 and step4 I expected xen routing template info in
template_store_ref table. However the entry was not made in the table.
System vms initiation failed because:
Zone host is ready, but console proxy template: 1 is not ready on secondary
storage.

3.Now added another vmware zone and provided s3 storage (with different
bucket) and secondary staging storage during zone creation and enabled the
zone.
4.Immediately after enabling second zone, xen routing template downloaded to
S3 and System VMs spinning up got initiated and they came up successfully in
zone 1. (Even vmware template downloaded to S3 and system vms start up
initiated )
Looks like zone to image store mapping is missing if we add image store first
and zone later. Hence system vms spinning up is failing.

[jira] [Updated] (CLOUDSTACK-3386) NPE from VolumeMotionService when creating a template


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen updated CLOUDSTACK-3386:
-

Assignee: (was: Min Chen)

 NPE from VolumeMotionService when creating a template
 -

 Key: CLOUDSTACK-3386
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3386
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: Future
Reporter: Prasanna Santhanam
Priority: Critical
 Fix For: Future

 Attachments: kvm.tar.bz2, xcp.tar.bz2


 On deploying a VM sometimes the template fails to create on primary storage.
 The following NPE is observed at these times. It's not clear why this would
 fail sometimes yet. Attaching agent (DEBUG) and management server logs
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,817 DEBUG [storage.volume.VolumeServiceImpl] 
 (Job-Executor-72:job-185) failed to create template on storage
 Jul  5 20:31:01 java.lang.NullPointerException  
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:45)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:390)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:490)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2482)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2539)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:852)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:230)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3317)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2877)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2863)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:514)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.FutureTask.run(FutureTask.java:166)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com at 
 java.lang.Thread.run(Thread.java:679)
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,826 DEBUG [cloud.storage.VolumeManagerImpl] 
 (Job-Executor-72:job-185) Unable to create 
 Vol[61|vm=58|ROOT]:java.lang.NullPointerException
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com local0: 2013-07-06 
 03:31:01,826 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-72:job-185) Unable to contact resource.
 Jul  5 20:31:01 cloudstack-centos63.fmt.vmops.com 
 com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1] is 
 unreachable: Unable to

[jira] [Assigned] (CLOUDSTACK-4034) Following global configuration missing from upgraded enviornment