cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3260) [Automation] Volume attach and detach failed with null pointer exception in vmware
Date Fri, 28 Jun 2013 20:00:20 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695728#comment-13695728
] 

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

Commit 75f98eea4e89c6cbbf0762ee13bac77229e86e3c in branch refs/heads/master-6-17-stable from
[~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=75f98ee ]

CLOUDSTACK-3260 [Automation] Volume attach and detach failed with null pointer exception in
vmware

Log files shows multiple Exceptions where some of the NPE are observed when file is non-existant
file in datastore.
Fixing NullPointerExceptions seen while searching for file in datastore.

                
> [Automation] Volume attach and detach failed with null pointer exception in vmware
> ----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3260
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3260
>             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
> Build from master_stable build 
>            Reporter: Rayees Namathponnan
>            Assignee: edison su
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: CLOUDSTACK-3260.rar
>
>
> Regression test case ntegration.component.test_volumes.TestAttachDetachVolume.test_01_volume_attach_detach
failed  with null pointer exception 
> 2013-06-27 20:12:45,487 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-500:null)
Seq 1-94963056: Executing request
> 2013-06-27 20:12:45,487 INFO  [vmware.resource.VmwareResource] (DirectAgent-500:10.223.250.130)
Executing resource CreateCommand: {"volId":217,"pool":{
> "id":1,"uuid":"4faf04c2-6dd8-3025-b43f-65d32cc49d02","host":"10.223.110.232","path":"/export/home/automation/SC-CLOUD-QA03/primary1","port":2049,"type"
> :"NetworkFilesystem"},"diskCharacteristics":{"size":1073741824,"tags":[],"type":"DATADISK","name":"TestDiskServ","useLocalStorage":false,"recreatable":
> false,"diskOfferingId":107,"volumeId":217},"executeInSequence":false,"wait":0}
> 2013-06-27 20:12:46,060 DEBUG [vmware.mo.HostMO] (DirectAgent-500:10.223.250.130) find
VM e5ed7f8bea2c499b94c74c9ff35ae23c on host
> 2013-06-27 20:12:46,060 DEBUG [vmware.mo.HostMO] (DirectAgent-500:10.223.250.130) load
VM cache on host
> 2013-06-27 20:12:46,066 INFO  [vmware.resource.VmwareResource] (DirectAgent-500:10.223.250.130)
Destroy dummy VM after volume creation
> 2013-06-27 20:12:46,066 ERROR [vmware.resource.VmwareResource] (DirectAgent-500:10.223.250.130)
CreateCommand failed due to Exception: java.lang.NullPo
> interException
> Message: null
> java.lang.NullPointerException
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4765)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:378)
>         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$201(ScheduledThreadPoolExecutor.java:178)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:722)
> 2013-06-27 20:12:46,067 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-500:null)
Seq 1-94963056: Response Received:
> 2013-06-27 20:12:46,067 DEBUG [agent.transport.Request] (DirectAgent-500:null) Seq 1-94963056:
Processing:  { Ans: , MgmtId: 90928106758026, via: 1, Ver: v1, Flags: 10, [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception:
java.lang.Exception\nMessage: java.lang.NullPointerException\nStack: java.lang.Exception:
java.lang.NullPointerException\n\tat com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4777)\n\tat
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:378)\n\tat
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)\n\tat
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:166)\n\tat
java.util.concurrent.Sched:
> 1. Deploy a vm and create 5 data disk
> 2. Attach all the created Volume to the vm. 
> 3. Detach all the volumes attached.
> 4. Reboot the VM. VM should be successfully rebooted
> 5. Stop the VM. Stop VM should be successful
> 6. Start The VM. Start VM should be successful

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

Mime
View raw message