[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861321#comment-13861321 ] Wei Zhou commented on CLOUDSTACK-5709: -- It looks -s is not valid in redhat 6. https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html It is valid in Ubuntu 12.04 and later http://manpages.ubuntu.com/manpages/precise/man1/qemu-img.1.html > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou reassigned CLOUDSTACK-5709: Assignee: edison su Edison, Can you have a look at this issue? It seems CentOS 6 does not support -s in converting disk images because of the old qemu-img (0.12.1?). > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux >Assignee: edison su > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-4945) [Doc] Pluggable VM Snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4945: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf > [Doc] Pluggable VM Snapshot > --- > > Key: CLOUDSTACK-4945 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4945 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair > Fix For: 4.3.0 > > Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf, > Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861329#comment-13861329 ] Nux commented on CLOUDSTACK-5709: - Right, finally I get it. EL6 KVM does not support this feature. Thanks a lot Wei for guiding me! I found that using the KVM from RedHat's RHEV repo[1] fixes the problem. This can be done as a temporary workaround until EL6 backports this feature (if ever) or EL7 is launched whose KVM should not have these problems. I found that using these RPMs[2] the problems go away and I can snapshot volumes, turn them into templates, launch templates and so on. [1] - http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/ [2] - http://li.nux.ro/download/nux/tmp/kvm-rhev/el6/ > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux >Assignee: edison su > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5744) [Hyper-v] White screen on console window when more than two console sessions are opened
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861330#comment-13861330 ] Rajesh Battala commented on CLOUDSTACK-5744: on IE11, I had opening 4 VM's consoles. Am able to view all the consoles > [Hyper-v] White screen on console window when more than two console sessions > are opened > --- > > Key: CLOUDSTACK-5744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: console.PNG, console2.PNG > > > [Hyper-v] white screen on console window when more than two console sessions > are opened > Steps to reproduce: > > 1.Bring up CS with hyperv host > 2.Deploy few guest vms > 3.Open console sessions for all the guest and system vms > Result: > === > From 3rd console window onwards we see while screen blinking on all the > further console windows. > Attaching screen shot to describe the issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5744) [Hyper-v] White screen on console window when more than two console sessions are opened
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861332#comment-13861332 ] Anshul Gangwar commented on CLOUDSTACK-5744: I am not able to reproduce with above steps. Have you tried restarting browser? May be some cache issue. > [Hyper-v] White screen on console window when more than two console sessions > are opened > --- > > Key: CLOUDSTACK-5744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: console.PNG, console2.PNG > > > [Hyper-v] white screen on console window when more than two console sessions > are opened > Steps to reproduce: > > 1.Bring up CS with hyperv host > 2.Deploy few guest vms > 3.Open console sessions for all the guest and system vms > Result: > === > From 3rd console window onwards we see while screen blinking on all the > further console windows. > Attaching screen shot to describe the issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5744) [Hyper-v] White screen on console window when more than two console sessions are opened
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar reassigned CLOUDSTACK-5744: -- Assignee: Anshul Gangwar > [Hyper-v] White screen on console window when more than two console sessions > are opened > --- > > Key: CLOUDSTACK-5744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: console.PNG, console2.PNG > > > [Hyper-v] white screen on console window when more than two console sessions > are opened > Steps to reproduce: > > 1.Bring up CS with hyperv host > 2.Deploy few guest vms > 3.Open console sessions for all the guest and system vms > Result: > === > From 3rd console window onwards we see while screen blinking on all the > further console windows. > Attaching screen shot to describe the issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Reopened] (CLOUDSTACK-5314) [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in the resource count table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi reopened CLOUDSTACK-5314: - > [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in > the resource count table > - > > Key: CLOUDSTACK-5314 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5314 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Management Server >Affects Versions: 4.3.0 > Environment: Hyper-V >Reporter: Abhinav Roy >Assignee: Devdeep Singh >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > Description : > > The resource count value for primary storage and volumes in the > cloud.resource_count table is shown as negative (-ve) > mysql> select * from resource_count; > +++---+---+---+ > | id | account_id | domain_id | type | count | > +++---+---+---+ > | 1 | NULL | 1 | cpu | 6 | > | 2 | NULL | 1 | memory| 3072 | > | 3 | NULL | 1 | primary_storage | -103079215104 | > | 4 | NULL | 1 | secondary_storage | 56863775232 | > | 9 | NULL | 1 | user_vm | 6 | > | 10 | NULL | 1 | public_ip | 2 | > | 11 | NULL | 1 | volume|-5 | > | 12 | NULL | 1 | snapshot | 0 | > | 13 | NULL | 1 | template | 4 | > | 14 | NULL | 1 | project | 0 | > | 15 | NULL | 1 | network | 1 | > | 16 | NULL | 1 | vpc | 0 | > | 17 | 1 | NULL | user_vm | 0 | > | 18 | 1 | NULL | public_ip | 0 | > | 19 | 1 | NULL | volume| 0 | > | 20 | 1 | NULL | snapshot | 0 | > | 21 | 1 | NULL | template | 0 | > | 22 | 1 | NULL | project | 0 | > | 23 | 1 | NULL | network | 0 | > | 24 | 1 | NULL | vpc | 0 | > | 25 | 1 | NULL | cpu | 0 | > | 26 | 1 | NULL | memory| 0 | > | 27 | 1 | NULL | primary_storage | 0 | > | 28 | 1 | NULL | secondary_storage | 0 | > | 29 | 2 | NULL | user_vm | 6 | > | 30 | 2 | NULL | public_ip | 2 | > | 31 | 2 | NULL | volume|-5 | > | 32 | 2 | NULL | snapshot | 0 | > | 33 | 2 | NULL | template | 4 | > | 34 | 2 | NULL | project | 0 | > | 35 | 2 | NULL | network | 1 | > | 36 | 2 | NULL | vpc | 0 | > | 37 | 2 | NULL | cpu | 6 | > | 38 | 2 | NULL | memory| 3072 | > | 39 | 2 | NULL | primary_storage | -103079215104 | > | 40 | 2 | NULL | secondary_storage | 163220937216 | > +++---+---+---+ > 36 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5314) [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in the resource count table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi reassigned CLOUDSTACK-5314: --- Assignee: Sanjay Tripathi (was: Devdeep Singh) > [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in > the resource count table > - > > Key: CLOUDSTACK-5314 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5314 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Management Server >Affects Versions: 4.3.0 > Environment: Hyper-V >Reporter: Abhinav Roy >Assignee: Sanjay Tripathi >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > Description : > > The resource count value for primary storage and volumes in the > cloud.resource_count table is shown as negative (-ve) > mysql> select * from resource_count; > +++---+---+---+ > | id | account_id | domain_id | type | count | > +++---+---+---+ > | 1 | NULL | 1 | cpu | 6 | > | 2 | NULL | 1 | memory| 3072 | > | 3 | NULL | 1 | primary_storage | -103079215104 | > | 4 | NULL | 1 | secondary_storage | 56863775232 | > | 9 | NULL | 1 | user_vm | 6 | > | 10 | NULL | 1 | public_ip | 2 | > | 11 | NULL | 1 | volume|-5 | > | 12 | NULL | 1 | snapshot | 0 | > | 13 | NULL | 1 | template | 4 | > | 14 | NULL | 1 | project | 0 | > | 15 | NULL | 1 | network | 1 | > | 16 | NULL | 1 | vpc | 0 | > | 17 | 1 | NULL | user_vm | 0 | > | 18 | 1 | NULL | public_ip | 0 | > | 19 | 1 | NULL | volume| 0 | > | 20 | 1 | NULL | snapshot | 0 | > | 21 | 1 | NULL | template | 0 | > | 22 | 1 | NULL | project | 0 | > | 23 | 1 | NULL | network | 0 | > | 24 | 1 | NULL | vpc | 0 | > | 25 | 1 | NULL | cpu | 0 | > | 26 | 1 | NULL | memory| 0 | > | 27 | 1 | NULL | primary_storage | 0 | > | 28 | 1 | NULL | secondary_storage | 0 | > | 29 | 2 | NULL | user_vm | 6 | > | 30 | 2 | NULL | public_ip | 2 | > | 31 | 2 | NULL | volume|-5 | > | 32 | 2 | NULL | snapshot | 0 | > | 33 | 2 | NULL | template | 4 | > | 34 | 2 | NULL | project | 0 | > | 35 | 2 | NULL | network | 1 | > | 36 | 2 | NULL | vpc | 0 | > | 37 | 2 | NULL | cpu | 6 | > | 38 | 2 | NULL | memory| 3072 | > | 39 | 2 | NULL | primary_storage | -103079215104 | > | 40 | 2 | NULL | secondary_storage | 163220937216 | > +++---+---+---+ > 36 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861340#comment-13861340 ] Nux commented on CLOUDSTACK-5709: - BTW, using this version of KVM one can perform VM snapshots perfectly, too ie virsh snapshot-create-as i-2-15-VM snapshot "snapshot description" --atomic (this snapshotts disk AND memory) virsh snapshot-revert i-2-15-VM snapshot --force > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux >Assignee: edison su > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861340#comment-13861340 ] Nux edited comment on CLOUDSTACK-5709 at 1/3/14 8:34 AM: - BTW, using this version of KVM one can perform VM snapshots perfectly, too ie virsh snapshot-create-as i-2-15-VM snapshot "snapshot description" --atomic (this snapshotts disk AND memory) virsh snapshot-revert i-2-15-VM snapshot --force Edit: with the RHEV KVM most of this works great on EL 6.5 https://fedoraproject.org/wiki/Features/Virt_Live_Snapshots was (Author: nuxro): BTW, using this version of KVM one can perform VM snapshots perfectly, too ie virsh snapshot-create-as i-2-15-VM snapshot "snapshot description" --atomic (this snapshotts disk AND memory) virsh snapshot-revert i-2-15-VM snapshot --force > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux >Assignee: edison su > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5408) [Automation] Failed to deploy vm in vmware environment with error "due to java.io.IOException: Cannot run program "mount": java.io.IOException: error=12, Cannot al
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861343#comment-13861343
]
Sateesh Chodapuneedi commented on CLOUDSTACK-5408:
--
Increased swap space to 256MB. This has helped. Now snapshot operation on
volume was successful.
root@s-12-VM:~# free -m
total used free sharedbuffers cached
Mem: 241238 3 0 0 9
-/+ buffers/cache:228 13
Swap: 255192 63
2014-01-03 07:22:34,663 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) volss: copy vmdk and ovf file finishes
1388733754663
2014-01-03 07:22:34,664 INFO [vmware.mo.HttpNfcLeaseMO]
(agentRequest-Handler-1:null) close ProgressReporter, interrupt reporter runner
to let it quit
2014-01-03 07:22:34,664 INFO [vmware.mo.HttpNfcLeaseMO] (Thread-3:null)
ProgressReporter is interrupted, quiting
2014-01-03 07:22:34,764 INFO [vmware.mo.HttpNfcLeaseMO] (Thread-3:null)
ProgressReporter stopped
2014-01-03 07:23:10,095 INFO [storage.resource.VmwareStorageProcessor]
(agentRequest-Handler-1:null) Check if we have disk consolidation after
snapshot operation
2014-01-03 07:23:10,096 INFO [storage.resource.VmwareStorageProcessor]
(agentRequest-Handler-1:null) Validate disk chain
file:[7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk
2014-01-03 07:23:10,110 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Look for disk device info from volume :
[7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk
2014-01-03 07:23:10,111 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk device, controller key: 200,
unit number: 1
2014-01-03 07:23:10,111 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk backing :
[20cd70ee163932ecaedf8541162dc393] i-2-9-VM/ROOT-9.vmdk
2014-01-03 07:23:10,112 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk backing :
[20cd70ee163932ecaedf8541162dc393]
286ac1c57c9f3f8a8d2089f6e9d6452c/286ac1c57c9f3f8a8d2089f6ed6452c.vmdk
2014-01-03 07:23:10,113 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk device, controller key: 1000,
unit number: 0
2014-01-03 07:23:10,113 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk backing :
[7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk
2014-01-03 07:23:10,113 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Disk backing : [7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk matches ==> scsi0:0
2014-01-03 07:23:10,114 INFO [storage.resource.VmwareStorageProcessor]
(agentRequest-Handler-1:null) [7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk is found still in chain
2014-01-03 07:23:10,155 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null)
Seq 6-866189338: { Ans: , MgmtId: 227080256212965, via: 6, Ver: v1, Flags: 10,
[{"org.apache.cloudstack.storage.command.CopyCmdAnwer":{"newData":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"snapshots/2/15/c6d4811f-fccb-4345-a1b2-607af05254c4/c6d4811f-fccb-4345-a1b2-607af05254c4","id":0,"quiescevm":false}},"result":true,"ait":0}}]
}
> [Automation] Failed to deploy vm in vmware environment with error "due to
> java.io.IOException: Cannot run program "mount": java.io.IOException:
> error=12, Cannot allocate memory"
> --
>
> Key: CLOUDSTACK-5408
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5408
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.3.0
> Environment: vmware 5.0 update 3
> 64 bit template
>Reporter: Rayees Namathponnan
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: CLOUDSTACK-5408.rar
>
>
> Steps to reproduce
> Create advanced zone in vmware
> use 64 bit template
> deploy VM
> Result
> SSVM are crated
> Routers are created
> VM deployment failed with below error
> yStorageResource.mountUri(NfsSecondaryStorageResource.java:2293)\n\tat
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1934)\n\tat
>
> com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.getMountPoint(VmwareSecondaryStorageResourceHandler.java:311)\n\tat
>
> com.cloud.storage.re
[jira] [Comment Edited] (CLOUDSTACK-5408) [Automation] Failed to deploy vm in vmware environment with error "due to java.io.IOException: Cannot run program "mount": java.io.IOException: error=12, Cann
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861343#comment-13861343
]
Sateesh Chodapuneedi edited comment on CLOUDSTACK-5408 at 1/3/14 8:42 AM:
--
Increased swap space inside SSVM to 256MB. This has helped. Now snapshot
operation on volume was successful.
root@s-12-VM:~# free -m
total used free sharedbuffers cached
Mem: 241238 3 0 0 9
-/+ buffers/cache:228 13
Swap: 255192 63
2014-01-03 07:22:34,663 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) volss: copy vmdk and ovf file finishes
1388733754663
2014-01-03 07:22:34,664 INFO [vmware.mo.HttpNfcLeaseMO]
(agentRequest-Handler-1:null) close ProgressReporter, interrupt reporter runner
to let it quit
2014-01-03 07:22:34,664 INFO [vmware.mo.HttpNfcLeaseMO] (Thread-3:null)
ProgressReporter is interrupted, quiting
2014-01-03 07:22:34,764 INFO [vmware.mo.HttpNfcLeaseMO] (Thread-3:null)
ProgressReporter stopped
2014-01-03 07:23:10,095 INFO [storage.resource.VmwareStorageProcessor]
(agentRequest-Handler-1:null) Check if we have disk consolidation after
snapshot operation
2014-01-03 07:23:10,096 INFO [storage.resource.VmwareStorageProcessor]
(agentRequest-Handler-1:null) Validate disk chain
file:[7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk
2014-01-03 07:23:10,110 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Look for disk device info from volume :
[7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk
2014-01-03 07:23:10,111 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk device, controller key: 200,
unit number: 1
2014-01-03 07:23:10,111 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk backing :
[20cd70ee163932ecaedf8541162dc393] i-2-9-VM/ROOT-9.vmdk
2014-01-03 07:23:10,112 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk backing :
[20cd70ee163932ecaedf8541162dc393]
286ac1c57c9f3f8a8d2089f6e9d6452c/286ac1c57c9f3f8a8d2089f6ed6452c.vmdk
2014-01-03 07:23:10,113 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk device, controller key: 1000,
unit number: 0
2014-01-03 07:23:10,113 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Test against disk backing :
[7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk
2014-01-03 07:23:10,113 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Disk backing : [7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk matches ==> scsi0:0
2014-01-03 07:23:10,114 INFO [storage.resource.VmwareStorageProcessor]
(agentRequest-Handler-1:null) [7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk is found still in chain
2014-01-03 07:23:10,155 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null)
Seq 6-866189338: { Ans: , MgmtId: 227080256212965, via: 6, Ver: v1, Flags: 10,
[{"org.apache.cloudstack.storage.command.CopyCmdAnwer":{"newData":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"snapshots/2/15/c6d4811f-fccb-4345-a1b2-607af05254c4/c6d4811f-fccb-4345-a1b2-607af05254c4","id":0,"quiescevm":false}},"result":true,"ait":0}}]
}
was (Author: sateeshc):
Increased swap space to 256MB. This has helped. Now snapshot operation on
volume was successful.
root@s-12-VM:~# free -m
total used free sharedbuffers cached
Mem: 241238 3 0 0 9
-/+ buffers/cache:228 13
Swap: 255192 63
2014-01-03 07:22:34,663 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) volss: copy vmdk and ovf file finishes
1388733754663
2014-01-03 07:22:34,664 INFO [vmware.mo.HttpNfcLeaseMO]
(agentRequest-Handler-1:null) close ProgressReporter, interrupt reporter runner
to let it quit
2014-01-03 07:22:34,664 INFO [vmware.mo.HttpNfcLeaseMO] (Thread-3:null)
ProgressReporter is interrupted, quiting
2014-01-03 07:22:34,764 INFO [vmware.mo.HttpNfcLeaseMO] (Thread-3:null)
ProgressReporter stopped
2014-01-03 07:23:10,095 INFO [storage.resource.VmwareStorageProcessor]
(agentRequest-Handler-1:null) Check if we have disk consolidation after
snapshot operation
2014-01-03 07:23:10,096 INFO [storage.resource.VmwareStorageProcessor]
(agentRequest-Handler-1:null) Validate disk chain
file:[7b2ba866ca873954a935a354f3889574]
i-2-9-VM/419e86326c6e400487228ffb1e7ec805.vmdk
2014-01-03 07:23:10,110 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-1:null) Look for disk device info from volume :
[7b2ba866ca873954a935a354f3889574]
i
[jira] [Created] (CLOUDSTACK-5752) Persistent network fails to implement
Sowmya Krishnan created CLOUDSTACK-5752: --- Summary: Persistent network fails to implement Key: CLOUDSTACK-5752 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5752 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.3.0 Environment: Advanced zone, any hypervisor Reporter: Sowmya Krishnan Priority: Blocker Fix For: 4.3.0 Latest build fails to implement a persistent network. Steps: Create isolated network offering with persistent = true Launch a network with this offering. Logs simply say that it fails to implement the network and router fails to launch and throws an NPE: 2014-01-03 14:02:36,344 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Starting router VM[DomainRouter|r-34-VM] 2014-01-03 14:02:36,344 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Cleaning up because we're unable to implement the network Ntwk[219|Guest|22] 2014-01-03 14:02:36,349 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Lock is acquired for network Ntwk[219|Guest|22] as a part of network shutdown 2014-01-03 14:02:36,355 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 port forwarding rules for network id=219 as a part of shutdownNetworkRu les 2014-01-03 14:02:36,355 DEBUG [c.c.n.f.FirewallManagerImpl] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to the network elements 2014-01-03 14:02:36,356 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 static nat rules for network id=219 as a part of shutdownNetworkRules 2014-01-03 14:02:36,356 DEBUG [c.c.n.f.FirewallManagerImpl] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to the network elements 2014-01-03 14:02:36,357 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Revoking 0 Public load balancing rules for network id=219 ... ... 2014-01-03 14:02:36,383 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Sending network shutdown to VirtualRouter 2014-01-03 14:02:36,384 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Stopping router VM[DomainRouter|r-34-VM] 2014-01-03 14:02:36,384 WARN [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Unable to complete shutdown of the network elements due to element: VirtualRouter java.lang.NullPointerException at com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1268) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2702) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy240.stop(Unknown Source) at com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:665) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2052) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:1965) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:989) at com.cloud.network.NetworkServiceImpl.createGuestNetwork(NetworkServiceImpl.java:1272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.Delega
[jira] [Updated] (CLOUDSTACK-5752) Persistent network fails to implement
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sowmya Krishnan updated CLOUDSTACK-5752: Attachment: ms.log Attached management server logs > Persistent network fails to implement > -- > > Key: CLOUDSTACK-5752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5752 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 > Environment: Advanced zone, any hypervisor >Reporter: Sowmya Krishnan >Priority: Blocker > Fix For: 4.3.0 > > Attachments: ms.log > > > Latest build fails to implement a persistent network. > Steps: > Create isolated network offering with persistent = true > Launch a network with this offering. > Logs simply say that it fails to implement the network and router fails to > launch and throws an NPE: > 2014-01-03 14:02:36,344 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Starting router > VM[DomainRouter|r-34-VM] > 2014-01-03 14:02:36,344 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Cleaning up because we're unable > to implement the network Ntwk[219|Guest|22] > 2014-01-03 14:02:36,349 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Lock is acquired for network > Ntwk[219|Guest|22] as a part of network shutdown > 2014-01-03 14:02:36,355 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 port forwarding rules > for network id=219 as a part of shutdownNetworkRu > les > 2014-01-03 14:02:36,355 DEBUG [c.c.n.f.FirewallManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to > the network elements > 2014-01-03 14:02:36,356 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 static nat rules for > network id=219 as a part of shutdownNetworkRules > 2014-01-03 14:02:36,356 DEBUG [c.c.n.f.FirewallManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to > the network elements > 2014-01-03 14:02:36,357 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Revoking 0 Public load balancing > rules for network id=219 > ... > ... > 2014-01-03 14:02:36,383 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Sending network shutdown to > VirtualRouter > 2014-01-03 14:02:36,384 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Stopping router > VM[DomainRouter|r-34-VM] > 2014-01-03 14:02:36,384 WARN [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Unable to complete shutdown of > the network elements due to element: VirtualRouter > java.lang.NullPointerException > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1268) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2702) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy240.stop(Unknown Source) > at > com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:665) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2052) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:1965) >
[jira] [Commented] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861356#comment-13861356 ] Jayapal Reddy commented on CLOUDSTACK-5144: --- I am not looking into this, I am working on other issues. > [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when > there is no ingress rule defined for the security group > - > > Key: CLOUDSTACK-5144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 >Reporter: Gaurav Aradhye >Assignee: Wei Zhou >Priority: Critical > Labels: automation > Fix For: 4.3.0 > > Attachments: MS-Log.txt, agent.log, ipset-L output.txt, > iptables-rules.txt > > > In Basic Zone Setup: > 1. Create an account > 2. Deploy a VM in that account > 3. Verify that any ingress rule is not defined for the security group > belonging to the account > 4. Try SSH to VM using the nic ipaddress from external client > SSH is successful to the VM where as it should fail when the ingress rule is > not defined. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5753) [Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of consoleproxy.loadscan.interval which is 10sec
Sanjeev N created CLOUDSTACK-5753:
-
Summary: [Hyper-v] ConsoleProxyLoadReportCommand does not honor
the default value of consoleproxy.loadscan.interval which is 10sec
Key: CLOUDSTACK-5753
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5753
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Environment: Latest build from 4.3branch with commit:
95b6a7b96dab1c77e25987d6fe6003b4447281f1
Reporter: Sanjeev N
Fix For: 4.3.0
[Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of
consoleproxy.loadscan.interval which is 10sec
Steps to reproduce:
===
1.Bring up CS in advanced zone with Hyper-v cluster
2.Wait for the system vms to come up.
3.Deploy one guest vm with default centos template
4.Observe MS log for events related to ConsoleProxyLoadReportCommand
Result:
==
ConsoleProxyLoadReportCommand is getting executed for every 5 sec. However the
default value for consoleproxy.loadscan.interval is set to 10sec. So the
command should be exected at 10sec interval.
Few events grepped for the above command:
[root@RIAK-57 ~]# tail -f /var/log/cloudstack/management/management-server.log
| grep ConsoleProxyLoadReportCommand
2014-01-03 12:56:10,881 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-8:null) SeqA 4-11496: Processing Seq 4-11496: { Cmd ,
MgmtId: -1, via: 4, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
2014-01-03 12:56:15,885 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-5:null) SeqA 4-11497: Processing Seq 4-11497: { Cmd ,
MgmtId: -1, via: 4, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
2014-01-03 12:56:20,889 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-12:null) SeqA 4-11498: Processing Seq 4-11498: { Cmd ,
MgmtId: -1, via: 4, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
2014-01-03 12:56:25,933 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-7:null) SeqA 4-11500: Processing Seq 4-11500: { Cmd ,
MgmtId: -1, via: 4, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
2014-01-03 12:56:30,896 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) SeqA 4-11501: Processing Seq 4-11501: { Cmd ,
MgmtId: -1, via: 4, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5715) Creating private gateway giving 'Unable to serialize' error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayapal Reddy updated CLOUDSTACK-5715:
--
Priority: Blocker (was: Critical)
> Creating private gateway giving 'Unable to serialize' error
> ---
>
> Key: CLOUDSTACK-5715
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5715
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.3.0
>Reporter: Jayapal Reddy
>Priority: Blocker
>
> 1. Created VPC.
> 2. Creating private gateway in the VPC.
> 3. Observed the below error.
> 4. In the same VPC vm got deployed successfully.
> 014-01-02 16:34:18,044 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (279776273@qtp-1396125647-17:ctx-7d9ae2fa ctx-2e9427ef) submit async job-153,
> details: AsyncJobVO {id:153, userId: 2, accountId: 2,instanceType:
> PrivateGateway, instanceId: 1, cmd:
> org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd, cmdInfo:
> {"physicalnetworkid":"1d0afe0b-a51e-4261-880d-9734cea25169","sessi
> onkey":"l0SKFGXAOKRI0PshHyMmVAR47Kg\u003d","cmdEventType":"PRIVATE.GATEWAY.CREATE","sourcenatsupported":"false","ctxUserId":"2","gateway":"10.147.43.1","httpmethod":"GET","ipaddress":"10.147.43.1
>
> 00","netmask":"255.255.255.0","response":"json","id":"1","aclid":"236a5d3e-7392-11e3-b360-a552ac66fcbb","vlan":"43","_":"1388660657895","ctxAccountId":"2","vpcid":"828d3a23-e969-44f7-b16d-38a0fce
>82b3d","ctxStartEventId":"52"}, cmdVersion: 0, status: IN_PROGRESS,
> processStatus: 0, resultCode: 0, result: null, initMsid: 1, completeMsid:
> null, lastUpdated: null, lastPolled: null, created: n ull}
> 313425 2014-01-02 16:34:18,044 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-106:ctx-0019a244) Add job-153 into job monitoring
> 313426 2014-01-02 16:34:18,044 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-106:ctx-0019a244) Executing AsyncJobVO {id:153, userId: 2,
> accountId: 2, instanceType: PrivateGateway, instanceId: 1,cmd:
> org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd, cmdInfo:
> {"physicalnetworkid":"1d0afe0b-a51e-4261-880d-9734cea25169","sessionkey":"l0SKFGXAOKRI0PshHyMmVAR47Kg\u003d","c
>
> mdEventType":"PRIVATE.GATEWAY.CREATE","sourcenatsupported":"false","ctxUserId":"2","gateway":"10.147.43.1","httpmethod":"GET","ipaddress":"10.147.43.100","netmask":"255.255.255.0","response":"jso
>
> n","id":"1","aclid":"236a5d3e-7392-11e3-b360-a552ac66fcbb","vlan":"43","_":"1388660657895","ctxAccountId":"2","vpcid":"828d3a23-e969-44f7-b16d-38a0fce82b3d","ctxStartEventId":"52"},
> cmdVersion: 0 , status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 1, completeMsid: null, lastUpdated: null, lastPolled:
> null, created: null}
> 313427 2014-01-02 16:34:18,045 DEBUG [c.c.a.ApiServlet]
> (279776273@qtp-1396125647-17:ctx-7d9ae2fa ctx-2e9427ef) ===END===
> 10.252.193.7 -- GET
> command=createPrivateGateway&sourcenatsupported=false&resp
> onse=json&sessionkey=l0SKFGXAOKRI0PshHyMmVAR47Kg%3D&physicalnetworkid=1d0afe0b-a51e-4261-880d-9734cea25169&vpcid=828d3a23-e969-44f7-b16d-38a0fce82b3d&ipaddress=10.147.43.100&gateway=10.147.43.1&n
>
> etmask=255.255.255.0&vlan=43&aclid=236a5d3e-7392-11e3-b360-a552ac66fcbb&_=1388660657895
> 313428 2014-01-02 16:34:18,109 DEBUG [c.c.u.d.T.Transaction]
> (Job-Executor-106:ctx-0019a244 ctx-2e9427ef) Rolling back the transaction:
> Time = 25 Name = Job-Executor-106; called by -TransactionLegacy.r
> ollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue:4530-VirtualMachineM
>
> anagerImpl.addVmToNetwork:3118-VpcVirtualNetworkApplianceManagerImpl.setupPrivateGateway:918-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:39-DelegatingMethodAccessorImpl.in
>voke:25-Method.invoke:597
> 313429 2014-01-02 16:34:18,110 WARN
> [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl]
> (Job-Executor-106:ctx-0019a244 ctx-2e9427ef) Failed to create private gateway
> com.cloud.network.vpc.PrivateGatewayPro file@74f4b7b3 on router
> VM[DomainRouter|r-3-VM] due to
> 313430 com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
> com.cloud.vm.VmWorkAddVmToNetwork@5933adb8
> 313431 at
> org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
> 313432 at
> com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
> 313433 at
> com.cloud.vm.VirtualMachineManagerImpl$10.doInTransa
[jira] [Commented] (CLOUDSTACK-5728) [Automation] ReplaceNetworkACLListCmd command failing with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861359#comment-13861359 ] Jayapal Reddy commented on CLOUDSTACK-5728: --- Currently creating private gateway is failing. Here is the ticket. https://issues.apache.org/jira/browse/CLOUDSTACK-5715 > [Automation] ReplaceNetworkACLListCmd command failing with NPE > -- > > Key: CLOUDSTACK-5728 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5728 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 > Environment: KVM and vmware > branch 4.3 >Reporter: Rayees Namathponnan >Assignee: Jayapal Reddy >Priority: Blocker > Fix For: 4.3.0 > > Attachments: management-server.rar > > > BVT test case test_privategw_acl.TestPrivateGwACL.test_privategw_acl failing > with NPE, this failure observed from Dec 27th on words > Test case performing below steps > # 1) Create VPC > # 2) Create ACl > # 3) Create ACl Item > # 4) Create network with ACL > # 6) update acl id > Observed below error > 7577-47b5-bb33-db9f8c542de0","httpmethod":"GET","ctxAccountId":"2","ctxStartEventId":"1063","apiKey":"EHF5nlA7E3UW18UHPpnUOrB1KScPXUdMPFtCl8t7tNc2k_1n0ZkD0Tv-X8Lp9OXMy4uPGReYq3R9q2ddkIb-2g","signature":"vIdDK7TNp5mRqcgsEs+m3lGSdjc\u > 003d"}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, > result: null, initMsid: 29066118877352, completeMsid: null, lastUpdated: > null, lastPolled: null, created: null} > 2014-01-02 14:14:51,316 DEBUG [c.c.a.ApiServlet] > (catalina-exec-18:ctx-607621af ctx-a91ea8f3 ctx-6baa9395) ===END=== > 10.223.240.194 -- GET > apiKey=EHF5nlA7E3UW18UHPpnUOrB1KScPXUdMPFtCl8t7tNc2k_1n0ZkD0Tv-X8Lp9OXMy4uPGReYq3R9q2ddkIb- > 2g&aclid=5db946bd-d5a2-47bd-8dda-1653c21b2af5&command=replaceNetworkACLList&signature=vIdDK7TNp5mRqcgsEs%2Bm3lGSdjc%3D&gatewayid=a51a8831-7577-47b5-bb33-db9f8c542de0&response=json > 2014-01-02 14:14:51,320 DEBUG [c.c.a.ApiServlet] > (catalina-exec-17:ctx-a8650844) ===START=== 10.223.240.194 -- GET > signature=Im99pBFJIOBuch6mHvf4WilMbwU%3D&apiKey=EHF5nlA7E3UW18UHPpnUOrB1KScPXUdMPFtCl8t7tNc2k_1n0ZkD0Tv-X8Lp9OXMy4u > PGReYq3R9q2ddkIb-2g&command=queryAsyncJobResult&response=json&jobid=e9391f75-b3ee-4255-8bc7-5439dd7ba68f > 2014-01-02 14:14:51,341 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (Job-Executor-1:ctx-f84f626a ctx-6baa9395) Applying network acls in network > Ntwk[239|Guest|5] > 2014-01-02 14:14:51,346 DEBUG [c.c.a.ApiServlet] > (catalina-exec-17:ctx-a8650844 ctx-36cff002 ctx-0b21bcc7) ===END=== > 10.223.240.194 -- GET > signature=Im99pBFJIOBuch6mHvf4WilMbwU%3D&apiKey=EHF5nlA7E3UW18UHPpnUOrB1KScPXUdMPFtCl8t7tNc > 2k_1n0ZkD0Tv-X8Lp9OXMy4uPGReYq3R9q2ddkIb-2g&command=queryAsyncJobResult&response=json&jobid=e9391f75-b3ee-4255-8bc7-5439dd7ba68f > 2014-01-02 14:14:51,364 ERROR [c.c.a.ApiAsyncJobDispatcher] > (Job-Executor-1:ctx-f84f626a) Unexpected exception while executing > org.apache.cloudstack.api.command.user.network.ReplaceNetworkACLListCmd > java.lang.NullPointerException > at > com.cloud.hypervisor.HypervisorGuruBase.toNicTO(HypervisorGuruBase.java:60) > at > com.cloud.vm.VirtualMachineManagerImpl.toNicTO(VirtualMachineManagerImpl.java:3212) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.getNicTO(VpcVirtualNetworkApplianceManagerImpl.java:489) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createNetworkACLsCommands(VpcVirtualNetworkApplianceManagerImpl.java:699) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.sendNetworkACLs(VpcVirtualNetworkApplianceManagerImpl.java:673) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl$2.execute(VpcVirtualNetworkApplianceManagerImpl.java:665) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3738) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.applyNetworkACLs(VpcVirtualNetworkApplianceManagerImpl.java:662) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocatio
[jira] [Created] (CLOUDSTACK-5754) Japanese keys are not working with CentOS CLI operating system VM
Sanjay Tripathi created CLOUDSTACK-5754: --- Summary: Japanese keys are not working with CentOS CLI operating system VM Key: CLOUDSTACK-5754 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5754 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sanjay Tripathi Japanese keys are not properly with CenOS CLI operating system. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5557) [UI] Invalid UI for Network->Guest Network->.Able to see all configuration(FW/PF/LB)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861367#comment-13861367 ] manasaveloori commented on CLOUDSTACK-5557: --- Expected Behavior: For VPC networks we have ACL/PF/LB configurations under Network->VPC->VPC configuration. So there is no meaning for the UI under Network->GuestNetworks->Click on VPC tier network->IPaddresses for firewall/PF/LB configurations. Those configurations should not be there for VPC networks as they are already present under VPC networks tab. When trying to configure the firewall rule from Network->GuestNetworks->Click on VPC tier network->IPaddresses ,Error message is displayed as "there is no new provider for ip "10.x.x.x" of service firewall. Attaching the db dumps and MS logs > [UI] Invalid UI for Network->Guest Network->.Able to see all > configuration(FW/PF/LB) > --- > > Key: CLOUDSTACK-5557 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5557 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: manasaveloori >Assignee: manasaveloori >Priority: Critical > Fix For: 4.3.0 > > Attachments: VPCTierNW.jpg > > > Steps: > 1. Create a VPC. > 2. Create a tier network and VM using that network. > 3. Acquire IP and enable PF/LB rule. > Obseravation: > Under Network->GuestNetworks->Click on VPC tier network->IPaddresses. > Able to view the IP address and all the configurable items in > UI(firewall,PF,LB)like for normal networks. > Also user is allowed to configure the rules which results in exception > Attaching the SC -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5557) [UI] Invalid UI for Network->Guest Network->.Able to see all configuration(FW/PF/LB)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori updated CLOUDSTACK-5557: -- Attachment: management-server.log > [UI] Invalid UI for Network->Guest Network->.Able to see all > configuration(FW/PF/LB) > --- > > Key: CLOUDSTACK-5557 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5557 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: manasaveloori >Assignee: manasaveloori >Priority: Critical > Fix For: 4.3.0 > > Attachments: VPCTierNW.jpg, management-server.log > > > Steps: > 1. Create a VPC. > 2. Create a tier network and VM using that network. > 3. Acquire IP and enable PF/LB rule. > Obseravation: > Under Network->GuestNetworks->Click on VPC tier network->IPaddresses. > Able to view the IP address and all the configurable items in > UI(firewall,PF,LB)like for normal networks. > Also user is allowed to configure the rules which results in exception > Attaching the SC -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5755) [Monitoring] Include VPC and make monitoring configurable
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy reassigned CLOUDSTACK-5755: - Assignee: Jayapal Reddy > [Monitoring] Include VPC and make monitoring configurable > - > > Key: CLOUDSTACK-5755 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5755 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy > > 1. Currently VPC VR services are not included in monitoring. Add vpc VR > services monitoring > 2. Monitoring VR services needs to be configurable. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5755) [Monitoring] Include VPC and make monitoring configurable
Jayapal Reddy created CLOUDSTACK-5755: - Summary: [Monitoring] Include VPC and make monitoring configurable Key: CLOUDSTACK-5755 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5755 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Reporter: Jayapal Reddy 1. Currently VPC VR services are not included in monitoring. Add vpc VR services monitoring 2. Monitoring VR services needs to be configurable. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5752) Persistent network fails to implement
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-5752: --- Assignee: Likitha Shetty > Persistent network fails to implement > -- > > Key: CLOUDSTACK-5752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5752 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 > Environment: Advanced zone, any hypervisor >Reporter: Sowmya Krishnan >Assignee: Likitha Shetty >Priority: Blocker > Fix For: 4.3.0 > > Attachments: ms.log > > > Latest build fails to implement a persistent network. > Steps: > Create isolated network offering with persistent = true > Launch a network with this offering. > Logs simply say that it fails to implement the network and router fails to > launch and throws an NPE: > 2014-01-03 14:02:36,344 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Starting router > VM[DomainRouter|r-34-VM] > 2014-01-03 14:02:36,344 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Cleaning up because we're unable > to implement the network Ntwk[219|Guest|22] > 2014-01-03 14:02:36,349 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Lock is acquired for network > Ntwk[219|Guest|22] as a part of network shutdown > 2014-01-03 14:02:36,355 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 port forwarding rules > for network id=219 as a part of shutdownNetworkRu > les > 2014-01-03 14:02:36,355 DEBUG [c.c.n.f.FirewallManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to > the network elements > 2014-01-03 14:02:36,356 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 static nat rules for > network id=219 as a part of shutdownNetworkRules > 2014-01-03 14:02:36,356 DEBUG [c.c.n.f.FirewallManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to > the network elements > 2014-01-03 14:02:36,357 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Revoking 0 Public load balancing > rules for network id=219 > ... > ... > 2014-01-03 14:02:36,383 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Sending network shutdown to > VirtualRouter > 2014-01-03 14:02:36,384 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Stopping router > VM[DomainRouter|r-34-VM] > 2014-01-03 14:02:36,384 WARN [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Unable to complete shutdown of > the network elements due to element: VirtualRouter > java.lang.NullPointerException > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1268) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2702) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy240.stop(Unknown Source) > at > com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:665) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2052) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:1965) >
[jira] [Updated] (CLOUDSTACK-5739) [vmware] Vcenter 5.5 host ESXi 5.5 host maintenance mode some VMs in stop state not migrated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-5739: --- Assignee: Likitha Shetty > [vmware] Vcenter 5.5 host ESXi 5.5 host maintenance mode some VMs in stop > state not migrated > -- > > Key: CLOUDSTACK-5739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5739 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: MS4.3 build 1/2/2014 > vcenter 5.5host1 host2 ESXi 5.5 >Reporter: angeline shen >Assignee: Likitha Shetty >Priority: Critical > Fix For: 4.3.0 > > Attachments: management-server.log.gz, vm43.png, vm431.png, > vm432.png, vm5131.png, vm5132.png, vm5133.png, vm5134.png, vm5135.png, > vm5136.png > > > 1. advance zone, create VMs > 2. Put host1 in maintenance mode. > 3. 1 guest VM remain in stop state , not migrated > VRs remain in stop state, not migrated > host remain in PrepareForMaintenance mode -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856767#comment-13856767 ] Radhika Nair edited comment on CLOUDSTACK-5604 at 1/3/14 9:33 AM: -- Updated the doc, and is posting was (Author: radhikap): Hi, Greetings and thank you for the message. I am on vacation until 5/01/14 with no access to the Internet; therefore, please expect a delay in my response. Merry X-Mas and Happy New Year ! Thanks -Radhika > [DOC] dynamic compute offering > -- > > Key: CLOUDSTACK-5604 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.3.0 >Reporter: Radhika Nair > Fix For: 4.3.0 > > Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5743) [Hyper-V] Download ROOT Volume when the VM is in stopped state is failing with "Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07d
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-5743: --- Assignee: Devdeep Singh > [Hyper-V] Download ROOT Volume when the VM is in stopped state is failing > with "Forbidden You don't have permission to access > /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server" > -- > > Key: CLOUDSTACK-5743 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server >Affects Versions: 4.3.0 > Environment: 4.3, Hyper-V >Reporter: Abhinav Roy >Assignee: Devdeep Singh >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > > Steps : > > 1. Create an advanced zone setup with hyper-v as the host hypervisor type and > shared CIFS storage for primary storage > 2. Deploy a VM > 3. stop the VM > 4. Goto the ROOT/Data volume of the VM and try to download it. > Expected behaviour : > = > The volume should be successfully downloaded . > Observed behaviour : > = > ROOT volume download fails with the following message in the UI : > Forbidden > You don't have permission to access > /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server > There is nothing in the MS log or Agent logs. > NOTE : Tried the same operation on VMware and it is working fine. > In case of Hyperv also, template download is going through but volume > download is failing. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5756) [Monitoring] Avoid race condition while service restart
Jayapal Reddy created CLOUDSTACK-5756: - Summary: [Monitoring] Avoid race condition while service restart Key: CLOUDSTACK-5756 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5756 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jayapal Reddy There MS and monitoring script restart the services, we need to avoid the race condition -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5604: - Attachment: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf > [DOC] dynamic compute offering > -- > > Key: CLOUDSTACK-5604 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.3.0 >Reporter: Radhika Nair > Fix For: 4.3.0 > > Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf, > Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5743) [Hyper-V] Download ROOT Volume when the VM is in stopped state is failing with "Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Roy resolved CLOUDSTACK-5743. - Resolution: Invalid > [Hyper-V] Download ROOT Volume when the VM is in stopped state is failing > with "Forbidden You don't have permission to access > /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server" > -- > > Key: CLOUDSTACK-5743 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server >Affects Versions: 4.3.0 > Environment: 4.3, Hyper-V >Reporter: Abhinav Roy >Assignee: Devdeep Singh >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > > Steps : > > 1. Create an advanced zone setup with hyper-v as the host hypervisor type and > shared CIFS storage for primary storage > 2. Deploy a VM > 3. stop the VM > 4. Goto the ROOT/Data volume of the VM and try to download it. > Expected behaviour : > = > The volume should be successfully downloaded . > Observed behaviour : > = > ROOT volume download fails with the following message in the UI : > Forbidden > You don't have permission to access > /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server > There is nothing in the MS log or Agent logs. > NOTE : Tried the same operation on VMware and it is working fine. > In case of Hyperv also, template download is going through but volume > download is failing. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5604) [DOC] dynamic compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-5604: - Attachment: (was: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf) > [DOC] dynamic compute offering > -- > > Key: CLOUDSTACK-5604 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5604 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.3.0 >Reporter: Radhika Nair > Fix For: 4.3.0 > > Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5670) [Automation] VirtualRouter failed to stop with NullPointerException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861382#comment-13861382
]
Kishan Kavala commented on CLOUDSTACK-5670:
---
jobcontext is null when stopping VR during network GC.
Kelven,
Can you plz look into it.
> [Automation] VirtualRouter failed to stop with NullPointerException
> ---
>
> Key: CLOUDSTACK-5670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
>Affects Versions: 4.3.0
> Environment: KVM
> Branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: management-server.rar
>
>
> Steps to reproduce
> Step 1 : Create Advanced zone in kvm
> Step 2 : create an account
> Step 3 : deploy a vm
> step 4 : make sure new router and vm got deployed
> step 5 : destroy the account
> Expected result
> account and corresponding router should be depleted
> actual result
> router delete failed with NPE
> 2013-12-28 22:53:34,600 DEBUG [c.c.a.t.Request]
> (StatsCollector-2:ctx-4c64000f) Seq 7-1306657158: Received: { Ans: , MgmtId:
> 29066118877352, via: 7, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-12-28 22:53:34,758 DEBUG [c.c.a.t.Request] (AgentManager-Handler-3:null)
> Seq 1-1538730432: Processing: { Ans: , MgmtId: 29066118877352, via: 1, Ver:
> v1, Flags: 0,
> [{"com.cloud.agent.api.routing.IpAssocAnswer":{"results":["10.223.122.85 -
> success"],"result":true,"wait":0}}] }
> 2013-12-28 22:53:34,758 DEBUG [c.c.a.t.Request]
> (Network-Scavenger-1:ctx-2a427ae4) Seq 1-1538730432: Received: { Ans: ,
> MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 0, { IpAssocAnswer } }
> 2013-12-28 22:53:34,760 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Network-Scavenger-1:ctx-2a427ae4) Sending network shutdown to VirtualRouter
> 2013-12-28 22:53:34,762 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Network-Scavenger-1:ctx-2a427ae4) Stopping router VM[DomainRouter|r-171-QA]
> 2013-12-28 22:53:34,762 WARN [o.a.c.e.o.NetworkOrchestrator]
> (Network-Scavenger-1:ctx-2a427ae4) Unable to complete shutdown of the network
> elements due to element: VirtualRouter
> java.lang.NullPointerException
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1263)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2698)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139)
> at sun.reflect.GeneratedMethodAccessor570.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy240.stop(Unknown Source)
> at
> com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:665)
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2052)
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:1965)
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.reallyRun(NetworkOrchestrator.java:2305)
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.runInContext(NetworkOrchestrator.java:2248)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
[jira] [Updated] (CLOUDSTACK-5670) [Automation] VirtualRouter failed to stop with NullPointerException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishan Kavala updated CLOUDSTACK-5670:
--
Assignee: Kelven Yang (was: Kishan Kavala)
> [Automation] VirtualRouter failed to stop with NullPointerException
> ---
>
> Key: CLOUDSTACK-5670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
>Affects Versions: 4.3.0
> Environment: KVM
> Branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Kelven Yang
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: management-server.rar
>
>
> Steps to reproduce
> Step 1 : Create Advanced zone in kvm
> Step 2 : create an account
> Step 3 : deploy a vm
> step 4 : make sure new router and vm got deployed
> step 5 : destroy the account
> Expected result
> account and corresponding router should be depleted
> actual result
> router delete failed with NPE
> 2013-12-28 22:53:34,600 DEBUG [c.c.a.t.Request]
> (StatsCollector-2:ctx-4c64000f) Seq 7-1306657158: Received: { Ans: , MgmtId:
> 29066118877352, via: 7, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-12-28 22:53:34,758 DEBUG [c.c.a.t.Request] (AgentManager-Handler-3:null)
> Seq 1-1538730432: Processing: { Ans: , MgmtId: 29066118877352, via: 1, Ver:
> v1, Flags: 0,
> [{"com.cloud.agent.api.routing.IpAssocAnswer":{"results":["10.223.122.85 -
> success"],"result":true,"wait":0}}] }
> 2013-12-28 22:53:34,758 DEBUG [c.c.a.t.Request]
> (Network-Scavenger-1:ctx-2a427ae4) Seq 1-1538730432: Received: { Ans: ,
> MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 0, { IpAssocAnswer } }
> 2013-12-28 22:53:34,760 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Network-Scavenger-1:ctx-2a427ae4) Sending network shutdown to VirtualRouter
> 2013-12-28 22:53:34,762 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Network-Scavenger-1:ctx-2a427ae4) Stopping router VM[DomainRouter|r-171-QA]
> 2013-12-28 22:53:34,762 WARN [o.a.c.e.o.NetworkOrchestrator]
> (Network-Scavenger-1:ctx-2a427ae4) Unable to complete shutdown of the network
> elements due to element: VirtualRouter
> java.lang.NullPointerException
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1263)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2698)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139)
> at sun.reflect.GeneratedMethodAccessor570.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy240.stop(Unknown Source)
> at
> com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:665)
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2052)
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:1965)
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.reallyRun(NetworkOrchestrator.java:2305)
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.runInContext(NetworkOrchestrator.java:2248)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedCon
[jira] [Assigned] (CLOUDSTACK-5729) [Automation]Deletion of a Account reported Success inspite of VM Expunge Failures
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala reassigned CLOUDSTACK-5729:
---
Assignee: Harikrishna Patnala
> [Automation]Deletion of a Account reported Success inspite of VM Expunge
> Failures
> -
>
> Key: CLOUDSTACK-5729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5729
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
>Reporter: Chandan Purushothama
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.zip
>
>
> Deletion of Account failed due to VM Exunge job failure. Inspite of that
> Account Deletion is reported as success.
> 2014-01-03 07:39:16,839 ERROR [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Unable to expunge vm: 44
> 2014-01-03 07:39:16,869 INFO [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) deleteAccount: Deleted 1 network
> groups for account 26
> 2014-01-03 07:39:16,870 INFO [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) deleteAccount: Deleted 0 affinity
> groups for account 26
> 2014-01-03 07:39:16,871 DEBUG [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Deleting networks for account 26
> 2014-01-03 07:39:16,884 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-f044cb4e ctx-e5d3f936 ctx-efc2b479) ===END===
> 10.147.38.149 -- GET
> signature=shTK1s%2FnQv84C1gwQYEUo%2F5WFW4%3D&apiKey=SyITk_W_BpbLs73aYJqNRBu9Sir1d7k6hqoKVUmFCMSVG-vshSHHKOdj_nVVTOQHqyvfR3ZSXhDzL2QUquSdJA&command=queryAsyncJobResult&response=json&jobid=fb908e1c-cdf8-4ae9-8c0d-09116061c3f7
> 2014-01-03 07:39:16,894 WARN [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Can't delete the network, not all
> user vms are expunged. Vm VM[User|QA-03d9e9fa-081a-4175-9bf2-2508034b6e17] is
> in Expunging state
> 2014-01-03 07:39:16,894 WARN [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Unable to destroy network
> Ntwk[229|Guest|8] as a part of account id=26 cleanup.
> 2014-01-03 07:39:16,895 DEBUG [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Deleting vpcs for account 26
> 2014-01-03 07:39:16,897 DEBUG [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Deleting site-to-site VPN
> customer gateways for account 26
> 2014-01-03 07:39:16,908 INFO [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) deleteAccount: Released 0
> dedicated guest vlan ranges from account 26
> 2014-01-03 07:39:17,034 INFO [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleanup for account 26 is needed.
> 2014-01-03 07:39:17,048 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Complete async job-359,
> jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.SuccessResponse/null/{"success":true}
> 2014-01-03 07:39:17,056 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-72:ctx-d82a5609) Done executing
> org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd for job-359
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5757) [Monitoring] Add the vpn service in monitoring
Jayapal Reddy created CLOUDSTACK-5757: - Summary: [Monitoring] Add the vpn service in monitoring Key: CLOUDSTACK-5757 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5757 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jayapal Reddy Configure the monitoring tool to monitor vpn service which is running in VR -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5730) [Automation]DirectAgentAttache's send command fails due to ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures as part of Delete Account J
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala reassigned CLOUDSTACK-5730:
---
Assignee: Harikrishna Patnala
> [Automation]DirectAgentAttache's send command fails due to
> ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures
> as part of Delete Account Job
> --
>
> Key: CLOUDSTACK-5730
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5730
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
>Reporter: Chandan Purushothama
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.3.0
>
>
> ===
> ArrayIndexOutOfBoundsException during DeleteAccount Job Execution:
> ===
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Destroying vm
> VM[User|QA-88cfa2c8-e8ef-4133-8cf1-002ea3cb0c7b]
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up NICS
> 2014-01-03 07:39:16,752 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning network for vm: 44
> 2014-01-03 07:39:16,763 DEBUG [c.c.n.NetworkModelImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Service SecurityGroup is not
> supported in the network id=229
> 2014-01-03 07:39:16,780 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Removed nic id=81
> 2014-01-03 07:39:16,782 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Revoving nic secondary ip entry
> ...
> 2014-01-03 07:39:16,783 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up hypervisor data
> structures (ex. SRs in XenServer) for managed storage
> 2014-01-03 07:39:16,796 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-f044cb4e) ===START=== 10.147.38.149 -- GET
> signature=shTK1s%2FnQv84C1gwQYEUo%2F5WFW4%3D&apiKey=SyITk_W_BpbLs73aYJqNRBu9Sir1d7k6hqoKVUmFCMSVG-vshSHHKOdj_nVVTOQHqyvfR3ZSXhDzL2QUquSdJA&command=queryAsyncJobResult&response=json&jobid=fb908e1c-cdf8-4ae9-8c0d-09116061c3f7
> 2014-01-03 07:39:16,800 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Sending { Cmd , MgmtId: 6631563722783, via:
> 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Executing: { Cmd , MgmtId: 6631563722783,
> via: 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 WARN [c.c.a.m.AgentAttache]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Seq 1-678298558: Unable to send
> due to
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:100)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:374)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:398)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:497)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:448)
> at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1704)
> at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:
[jira] [Created] (CLOUDSTACK-5758) [Monitoring] Add monitoring in SSVM/CPVM
Jayapal Reddy created CLOUDSTACK-5758: - Summary: [Monitoring] Add monitoring in SSVM/CPVM Key: CLOUDSTACK-5758 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5758 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jayapal Reddy Add the monitoring to monitor the services which are running in CPVM/SSVM -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5759) [Monitoring] Report service failure/restart events to MS
Jayapal Reddy created CLOUDSTACK-5759: - Summary: [Monitoring] Report service failure/restart events to MS Key: CLOUDSTACK-5759 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5759 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jayapal Reddy Currently there is no way to report service failures to MS or external event receivers -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5760) [Monitoring] Check the service for its functionality
Jayapal Reddy created CLOUDSTACK-5760: - Summary: [Monitoring] Check the service for its functionality Key: CLOUDSTACK-5760 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5760 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jayapal Reddy Currently the monitoring checking only wether the service is running or not. It should also test for its functionality. Because some the service may run but it may not handle its requests. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5761) [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up extra CPVMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N updated CLOUDSTACK-5761: -- Attachment: management-server.rar Attached MS log file > [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up > extra CPVMs > -- > > Key: CLOUDSTACK-5761 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5761 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3branch with commit : > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: management-server.rar > > > [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up > extra CPVMs > Steps to reproduce: > > 1.Bring up CS in advanced zone with Hyper-v cluster > 2.Wait for the system vms to comeup > 3.Deploy few guest vms > 4.Open console view sessions for two guest vms > 5. Set consoleproxy.session.max=2 and restart MS > 6.Open console view for another vm > Result: > == > Immediately continuous CPVMs spin up strated one after the other until the > resources were available even though there were only 3 console view sessions > opened. > mysql> select id,name,instance_name,state from vm_instance where name like > "v%VM"; > ++-+---+-+ > | id | name| instance_name | state | > ++-+---+-+ > | 2 | v-2-VM | v-2-VM| Running | > | 13 | v-13-VM | v-13-VM | Running | > | 14 | v-14-VM | v-14-VM | Running | > | 15 | v-15-VM | v-15-VM | Running | > | 16 | v-16-VM | v-16-VM | Running | > ++-+---+-+ > 5 rows in set (0.00 sec) > v-2-VM was the initial vm before restarting MS. Immediately after MS restart > all the remaining cpvms spinned up. > Observations: > === > I closed all the console view sessions and destroyed all the cpvms except the > v-2-VM. Again CS started creating CPVMs even though there were no console > view sessions opened. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5730) [Automation]DirectAgentAttache's send command fails due to ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures as part of Delete Account Jo
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala updated CLOUDSTACK-5730:
Status: Ready To Review (was: In Progress)
> [Automation]DirectAgentAttache's send command fails due to
> ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures
> as part of Delete Account Job
> --
>
> Key: CLOUDSTACK-5730
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5730
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
>Reporter: Chandan Purushothama
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.3.0
>
>
> ===
> ArrayIndexOutOfBoundsException during DeleteAccount Job Execution:
> ===
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Destroying vm
> VM[User|QA-88cfa2c8-e8ef-4133-8cf1-002ea3cb0c7b]
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up NICS
> 2014-01-03 07:39:16,752 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning network for vm: 44
> 2014-01-03 07:39:16,763 DEBUG [c.c.n.NetworkModelImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Service SecurityGroup is not
> supported in the network id=229
> 2014-01-03 07:39:16,780 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Removed nic id=81
> 2014-01-03 07:39:16,782 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Revoving nic secondary ip entry
> ...
> 2014-01-03 07:39:16,783 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up hypervisor data
> structures (ex. SRs in XenServer) for managed storage
> 2014-01-03 07:39:16,796 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-f044cb4e) ===START=== 10.147.38.149 -- GET
> signature=shTK1s%2FnQv84C1gwQYEUo%2F5WFW4%3D&apiKey=SyITk_W_BpbLs73aYJqNRBu9Sir1d7k6hqoKVUmFCMSVG-vshSHHKOdj_nVVTOQHqyvfR3ZSXhDzL2QUquSdJA&command=queryAsyncJobResult&response=json&jobid=fb908e1c-cdf8-4ae9-8c0d-09116061c3f7
> 2014-01-03 07:39:16,800 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Sending { Cmd , MgmtId: 6631563722783, via:
> 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Executing: { Cmd , MgmtId: 6631563722783,
> via: 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 WARN [c.c.a.m.AgentAttache]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Seq 1-678298558: Unable to send
> due to
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:100)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:374)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:398)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:497)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:448)
> at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1704)
> at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopPro
[jira] [Created] (CLOUDSTACK-5761) [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up extra CPVMs
Sanjeev N created CLOUDSTACK-5761: - Summary: [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up extra CPVMs Key: CLOUDSTACK-5761 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5761 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.3.0 Environment: Latest build from 4.3branch with commit : 95b6a7b96dab1c77e25987d6fe6003b4447281f1 Reporter: Sanjeev N Priority: Critical Fix For: 4.3.0 [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up extra CPVMs Steps to reproduce: 1.Bring up CS in advanced zone with Hyper-v cluster 2.Wait for the system vms to comeup 3.Deploy few guest vms 4.Open console view sessions for two guest vms 5. Set consoleproxy.session.max=2 and restart MS 6.Open console view for another vm Result: == Immediately continuous CPVMs spin up strated one after the other until the resources were available even though there were only 3 console view sessions opened. mysql> select id,name,instance_name,state from vm_instance where name like "v%VM"; ++-+---+-+ | id | name| instance_name | state | ++-+---+-+ | 2 | v-2-VM | v-2-VM| Running | | 13 | v-13-VM | v-13-VM | Running | | 14 | v-14-VM | v-14-VM | Running | | 15 | v-15-VM | v-15-VM | Running | | 16 | v-16-VM | v-16-VM | Running | ++-+---+-+ 5 rows in set (0.00 sec) v-2-VM was the initial vm before restarting MS. Immediately after MS restart all the remaining cpvms spinned up. Observations: === I closed all the console view sessions and destroyed all the cpvms except the v-2-VM. Again CS started creating CPVMs even though there were no console view sessions opened. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5742) #cpu,cpu speed, and ram is getting updated under wrong usage_type(2) for dynamic compute offering in usage_vm_instance table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5742: - Assignee: Harikrishna Patnala (was: Bharat Kumar) > #cpu,cpu speed, and ram is getting updated under wrong usage_type(2) for > dynamic compute offering in usage_vm_instance table > > > Key: CLOUDSTACK-5742 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5742 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra >Assignee: Harikrishna Patnala >Priority: Critical > Fix For: 4.3.0 > > Attachments: LOG_DB.rar > > > STEPS TO REPO > == > 1-prepare a CS setup 4.3 > 2-deploy a vm with small CO > 3-Change the vm CO to dynamic CO. > 4-check the usage_vm_instance table after cloud_usage db synch > EXPECTED > = > cpu and ram should get updated under usage type 1 > ACTUAL > === > cpu and ram is getting updated under usage type2 > DB > === > | 2 | 1 | 2 | 8 | test| > 12 | 202 | XenServer | 2014-01-03 10:10:15 | NULL > | 100 | 1 |256 | > | 1 | 1 | 2 | 8 | test| > 12 | 202 | XenServer | 2014-01-03 10:11:21 | NULL > | NULL | NULL | NULL | > ++-+++-+-+-+-+-+-+---+---++ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5762) [dynamic compute offerings]UI change required for select compute offerinngs in add instance wizard
prashant kumar mishra created CLOUDSTACK-5762: - Summary: [dynamic compute offerings]UI change required for select compute offerinngs in add instance wizard Key: CLOUDSTACK-5762 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5762 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: prashant kumar mishra Fix For: 4.3.0 "required" is overlapping on memory and cpu if dynamic compute offering selected in deploy vm wizard .please check screenshot Steps to repro === 1-preapare a CS 4.3 setup 2-check select compute offering page in deploy vm wizard. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5730) [Automation]DirectAgentAttache's send command fails due to ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures as part of Delete Account
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861395#comment-13861395
]
ASF subversion and git services commented on CLOUDSTACK-5730:
-
Commit 6ce46e94f522f08c91db2cde33829f5b41539397 in branch refs/heads/4.3 from
[~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6ce46e9 ]
CLOUDSTACK-5730: [Automation]DirectAgentAttache's send command fails due to
ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures
as part of Delete Account Job
Signed-off-by: Koushik Das
> [Automation]DirectAgentAttache's send command fails due to
> ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures
> as part of Delete Account Job
> --
>
> Key: CLOUDSTACK-5730
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5730
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
>Reporter: Chandan Purushothama
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.3.0
>
>
> ===
> ArrayIndexOutOfBoundsException during DeleteAccount Job Execution:
> ===
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Destroying vm
> VM[User|QA-88cfa2c8-e8ef-4133-8cf1-002ea3cb0c7b]
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up NICS
> 2014-01-03 07:39:16,752 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning network for vm: 44
> 2014-01-03 07:39:16,763 DEBUG [c.c.n.NetworkModelImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Service SecurityGroup is not
> supported in the network id=229
> 2014-01-03 07:39:16,780 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Removed nic id=81
> 2014-01-03 07:39:16,782 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Revoving nic secondary ip entry
> ...
> 2014-01-03 07:39:16,783 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up hypervisor data
> structures (ex. SRs in XenServer) for managed storage
> 2014-01-03 07:39:16,796 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-f044cb4e) ===START=== 10.147.38.149 -- GET
> signature=shTK1s%2FnQv84C1gwQYEUo%2F5WFW4%3D&apiKey=SyITk_W_BpbLs73aYJqNRBu9Sir1d7k6hqoKVUmFCMSVG-vshSHHKOdj_nVVTOQHqyvfR3ZSXhDzL2QUquSdJA&command=queryAsyncJobResult&response=json&jobid=fb908e1c-cdf8-4ae9-8c0d-09116061c3f7
> 2014-01-03 07:39:16,800 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Sending { Cmd , MgmtId: 6631563722783, via:
> 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Executing: { Cmd , MgmtId: 6631563722783,
> via: 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 WARN [c.c.a.m.AgentAttache]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Seq 1-678298558: Unable to send
> due to
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:100)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:374)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:398)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:497)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:448)
> at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1704)
> at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.a
[jira] [Reopened] (CLOUDSTACK-5329) MigrateVMCmd on stopped VM is failing with NPE when trying to migrate to zone-wide-primary storage.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori reopened CLOUDSTACK-5329:
---
Able to reproduce the issue on latest 4.3 build
Steps:
1. Deploy CS4.3 with KVM host ---Basic zone.
2. Create 2 zone wide primary storages.
3. Create an instance.
4. Stop the instance.
5. Go to instance "migrate VM to another primary storage"
Observing the following NPE:
2014-01-03 21:13:10,432 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-f620504d
ctx-f9bd9d51) ===END=== 10.252.192.34 -- GET
command=migrateVirtualMachine&storageid=a85f0b79-1c84-3291-9c45-10510d327eee&virtualmachineid=c73b26ad-4fee-4c20-9626-2f11672c8018&response=json&sessionkey=toMTqmwjN9SSHxVGHaflXD3mfXY%3D&_=1388744586643
2014-01-03 21:13:10,436 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-18:ctx-500673c4) Add job-18 into job monitoring
2014-01-03 21:13:10,436 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-18:ctx-500673c4) Executing AsyncJobVO {id:18, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{"response":"json","sessionkey":"toMTqmwjN9SSHxVGHaflXD3mfXY\u003d","virtualmachineid":"c73b26ad-4fee-4c20-9626-2f11672c8018","cmdEventType":"VM.MIGRATE","ctxUserId":"2","storageid":"a85f0b79-1c84-3291-9c45-10510d327eee","httpmethod":"GET","_":"1388744586643","ctxAccountId":"2","ctxStartEventId":"41"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7494415941730, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-01-03 21:13:10,469 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-18:ctx-500673c4) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
java.lang.NullPointerException
at
com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:4061)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy169.vmStorageMigration(Unknown Source)
at
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:150)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at
com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at
com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lan
[jira] [Comment Edited] (CLOUDSTACK-5730) [Automation]DirectAgentAttache's send command fails due to ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures as part of Delete Acc
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861402#comment-13861402
]
Harikrishna Patnala edited comment on CLOUDSTACK-5730 at 1/3/14 10:30 AM:
--
As part of Checkin for https://issues.apache.org/jira/browse/CLOUDSTACK-5662
(Mike) caused this issue.
Fixed it on 4.3.
was (Author: harikrishna.patnala):
As part of Checkin for https://issues.apache.org/jira/browse/CLOUDSTACK-5662
(Mike) cause this issue.
Fixed it on 4.3.
> [Automation]DirectAgentAttache's send command fails due to
> ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures
> as part of Delete Account Job
> --
>
> Key: CLOUDSTACK-5730
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5730
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
>Reporter: Chandan Purushothama
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.3.0
>
>
> ===
> ArrayIndexOutOfBoundsException during DeleteAccount Job Execution:
> ===
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Destroying vm
> VM[User|QA-88cfa2c8-e8ef-4133-8cf1-002ea3cb0c7b]
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up NICS
> 2014-01-03 07:39:16,752 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning network for vm: 44
> 2014-01-03 07:39:16,763 DEBUG [c.c.n.NetworkModelImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Service SecurityGroup is not
> supported in the network id=229
> 2014-01-03 07:39:16,780 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Removed nic id=81
> 2014-01-03 07:39:16,782 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Revoving nic secondary ip entry
> ...
> 2014-01-03 07:39:16,783 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up hypervisor data
> structures (ex. SRs in XenServer) for managed storage
> 2014-01-03 07:39:16,796 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-f044cb4e) ===START=== 10.147.38.149 -- GET
> signature=shTK1s%2FnQv84C1gwQYEUo%2F5WFW4%3D&apiKey=SyITk_W_BpbLs73aYJqNRBu9Sir1d7k6hqoKVUmFCMSVG-vshSHHKOdj_nVVTOQHqyvfR3ZSXhDzL2QUquSdJA&command=queryAsyncJobResult&response=json&jobid=fb908e1c-cdf8-4ae9-8c0d-09116061c3f7
> 2014-01-03 07:39:16,800 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Sending { Cmd , MgmtId: 6631563722783, via:
> 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Executing: { Cmd , MgmtId: 6631563722783,
> via: 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 WARN [c.c.a.m.AgentAttache]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Seq 1-678298558: Unable to send
> due to
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:100)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:374)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:398)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:497)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:448)
> at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1704)
> at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150
[jira] [Resolved] (CLOUDSTACK-5730) [Automation]DirectAgentAttache's send command fails due to ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures as part of Delete Account J
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala resolved CLOUDSTACK-5730.
-
Resolution: Fixed
As part of Checkin for https://issues.apache.org/jira/browse/CLOUDSTACK-5662
(Mike) cause this issue.
Fixed it on 4.3.
> [Automation]DirectAgentAttache's send command fails due to
> ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures
> as part of Delete Account Job
> --
>
> Key: CLOUDSTACK-5730
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5730
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
>Reporter: Chandan Purushothama
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.3.0
>
>
> ===
> ArrayIndexOutOfBoundsException during DeleteAccount Job Execution:
> ===
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Destroying vm
> VM[User|QA-88cfa2c8-e8ef-4133-8cf1-002ea3cb0c7b]
> 2014-01-03 07:39:16,752 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up NICS
> 2014-01-03 07:39:16,752 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning network for vm: 44
> 2014-01-03 07:39:16,763 DEBUG [c.c.n.NetworkModelImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Service SecurityGroup is not
> supported in the network id=229
> 2014-01-03 07:39:16,780 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Removed nic id=81
> 2014-01-03 07:39:16,782 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Revoving nic secondary ip entry
> ...
> 2014-01-03 07:39:16,783 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleaning up hypervisor data
> structures (ex. SRs in XenServer) for managed storage
> 2014-01-03 07:39:16,796 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-f044cb4e) ===START=== 10.147.38.149 -- GET
> signature=shTK1s%2FnQv84C1gwQYEUo%2F5WFW4%3D&apiKey=SyITk_W_BpbLs73aYJqNRBu9Sir1d7k6hqoKVUmFCMSVG-vshSHHKOdj_nVVTOQHqyvfR3ZSXhDzL2QUquSdJA&command=queryAsyncJobResult&response=json&jobid=fb908e1c-cdf8-4ae9-8c0d-09116061c3f7
> 2014-01-03 07:39:16,800 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Sending { Cmd , MgmtId: 6631563722783, via:
> 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 DEBUG [c.c.a.t.Request] (Job-Executor-72:ctx-d82a5609
> ctx-1472cd68) Seq 1-678298558: Executing: { Cmd , MgmtId: 6631563722783,
> via: 1(Rack1Pod1Host15), Ver: v1, Flags: 100011, [] }
> 2014-01-03 07:39:16,801 WARN [c.c.a.m.AgentAttache]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Seq 1-678298558: Unable to send
> due to
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:100)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:374)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:398)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:497)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:448)
> at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1704)
> at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.jav
[jira] [Commented] (CLOUDSTACK-5556) [Automation] Failed to re-attach the volume in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861406#comment-13861406
]
Kishan Kavala commented on CLOUDSTACK-5556:
---
Unable to repo this issue in my setup.
Rayees,
Can check the repo steps?
I tried attach n detach multiple times.
2014-01-03 16:01:09,410 DEBUG [c.c.a.t.Request] (Job-Executor-15:ctx-9baf94bc
ctx-aa570dc8) Seq 2-1026555996: Sending { Cmd , MgmtId: 101318455136477, via:
2(idc-kvm11), Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"feade795-8572-417e-9f20-093b4760f613","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"4ef8642c-29a6-3a4f-ab8f-138f2f0ecbfb","id":2,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/kishan/primary","port":2049,"url":"NetworkFilesystem://10.147.28.7//export/home/kishan/primary/?ROLE=Primary&STOREUUID=4ef8642c-29a6-3a4f-ab8f-138f2f0ecbfb"}},"name":"d1","size":5368709120,"path":"feade795-8572-417e-9f20-093b4760f613","volumeId":13,"accountId":2,"format":"QCOW2","id":13,"hypervisorType":"KVM"}},"diskSeq":1,"path":"feade795-8572-417e-9f20-093b4760f613","type":"DATADISK","_details":{"managed":"false","storagePort":"2049","storageHost":"10.147.28.7","volumeSize":"5368709120"}},"vmName":"i-2-5-VM","wait":0}}]
}
2014-01-03 16:01:09,864 DEBUG [c.c.a.t.Request] (AgentManager-Handler-4:null)
Seq 2-1026555996: Processing: { Ans: , MgmtId: 101318455136477, via: 2, Ver:
v1, Flags: 10,
[{"org.apache.cloudstack.storage.command.AttachAnswer":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"feade795-8572-417e-9f20-093b4760f613","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"4ef8642c-29a6-3a4f-ab8f-138f2f0ecbfb","id":2,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/kishan/primary","port":2049,"url":"NetworkFilesystem://10.147.28.7//export/home/kishan/primary/?ROLE=Primary&STOREUUID=4ef8642c-29a6-3a4f-ab8f-138f2f0ecbfb"}},"name":"d1","size":5368709120,"path":"feade795-8572-417e-9f20-093b4760f613","volumeId":13,"accountId":2,"format":"QCOW2","id":13,"hypervisorType":"KVM"}},"diskSeq":1,"path":"feade795-8572-417e-9f20-093b4760f613","type":"DATADISK","_details":{"managed":"false","storagePort":"2049","storageHost":"10.147.28.7","volumeSize":"5368709120"}},"result":true,"wait":0}}]
}
> [Automation] Failed to re-attach the volume in KVM
> --
>
> Key: CLOUDSTACK-5556
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5556
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.3.0
> Environment: KVM (RHEL 6.3)
> Branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Kishan Kavala
>Priority: Critical
> Fix For: 4.3.0
>
>
> Steps to reproduce
> Step 1 : Create advanced zone in KVM
> Step 2 : Deploy a VM
> Step 3 : Add new Volume
> Step 4 : Attach the volume to vm
> Step 5 : Remove volume from the vm
> Step 6 : attach the same volume again
> Result
> Failed to attach the volume second time, with error "Failed to attach volume:
> vol1 to VM: RYZ1; org.libvirt.LibvirtException: internal error unable to
> execute QEMU command '__com.redhat_drive_add': Duplicate ID
> 'drive-virtio-disk1' for drive"
> Observed below error in MS log
> 2013-12-18 22:20:49,276 DEBUG [c.c.a.t.Request] (Job-Executor-51:ctx-98ec33fc
> ctx-5303d6ac) Seq 1-1588070511: Sending { Cmd , MgmtId: 29066118877352, via:
> 1(Rack2Host11.lab.vmops.com), Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"afcc7fa1-dd56-49cb-9246-2806d20dbcc4","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/rayees/SC_QA_AUTO4/primary","port":2049,"url":"NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=Primary&STOREUUID=fff90cb5-06dd-33b3-8815-d78c08ca01d9"}},"name":"vol1","size":5368709120,"path":"afcc7fa1-dd56-49cb-9246-2806d20dbcc4","volumeId":484,"accountId":2,"format":"QCOW2","id":484,"hypervisorType":"KVM"}},"diskSeq":1,"path":"afcc7fa1-dd56-49cb-9246-2806d20dbcc4","type":"DATADISK","_details":{"managed":"false","storagePort":"2049","storageHost":"10.223.110.232","volumeSize":"5368709120"}},"vmName":"i-2-433-QA","wait":0}}]
> }
> 2013-12-18 22:20:49,568 DEBUG [c.c.a.t.Request] (AgentManager-Handler-4:null)
>
[jira] [Updated] (CLOUDSTACK-5556) [Automation] Failed to re-attach the volume in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishan Kavala updated CLOUDSTACK-5556:
--
Assignee: Rayees Namathponnan (was: Kishan Kavala)
> [Automation] Failed to re-attach the volume in KVM
> --
>
> Key: CLOUDSTACK-5556
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5556
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.3.0
> Environment: KVM (RHEL 6.3)
> Branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.3.0
>
>
> Steps to reproduce
> Step 1 : Create advanced zone in KVM
> Step 2 : Deploy a VM
> Step 3 : Add new Volume
> Step 4 : Attach the volume to vm
> Step 5 : Remove volume from the vm
> Step 6 : attach the same volume again
> Result
> Failed to attach the volume second time, with error "Failed to attach volume:
> vol1 to VM: RYZ1; org.libvirt.LibvirtException: internal error unable to
> execute QEMU command '__com.redhat_drive_add': Duplicate ID
> 'drive-virtio-disk1' for drive"
> Observed below error in MS log
> 2013-12-18 22:20:49,276 DEBUG [c.c.a.t.Request] (Job-Executor-51:ctx-98ec33fc
> ctx-5303d6ac) Seq 1-1588070511: Sending { Cmd , MgmtId: 29066118877352, via:
> 1(Rack2Host11.lab.vmops.com), Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"afcc7fa1-dd56-49cb-9246-2806d20dbcc4","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/rayees/SC_QA_AUTO4/primary","port":2049,"url":"NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=Primary&STOREUUID=fff90cb5-06dd-33b3-8815-d78c08ca01d9"}},"name":"vol1","size":5368709120,"path":"afcc7fa1-dd56-49cb-9246-2806d20dbcc4","volumeId":484,"accountId":2,"format":"QCOW2","id":484,"hypervisorType":"KVM"}},"diskSeq":1,"path":"afcc7fa1-dd56-49cb-9246-2806d20dbcc4","type":"DATADISK","_details":{"managed":"false","storagePort":"2049","storageHost":"10.223.110.232","volumeSize":"5368709120"}},"vmName":"i-2-433-QA","wait":0}}]
> }
> 2013-12-18 22:20:49,568 DEBUG [c.c.a.t.Request] (AgentManager-Handler-4:null)
> Seq 1-1588070511: Processing: { Ans: , MgmtId: 29066118877352, via: 1, Ver:
> v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.AttachAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
> internal error unable to execute QEMU command '__com.redhat_drive_add':
> Duplicate ID 'drive-virtio-disk1' for drive","wait":0}}] }
> 2013-12-18 22:20:49,568 DEBUG [c.c.a.t.Request] (Job-Executor-51:ctx-98ec33fc
> ctx-5303d6ac) Seq 1-1588070511: Received: { Ans: , MgmtId: 29066118877352,
> via: 1, Ver: v1, Flags: 10, { AttachAnswer } }
> 2013-12-18 22:20:49,568 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-51:ctx-98ec33fc) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume:
> vol1 to VM: RYZ1; org.libvirt.LibvirtException: internal error unable to
> execute QEMU command '__com.redhat_drive_add': Duplicate ID
> 'drive-virtio-disk1' for drive
> at
> com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1879)
> at
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1264)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1088)
> at
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1063)
> at sun.reflect.GeneratedMethodAccessor610.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynam
[jira] [Resolved] (CLOUDSTACK-5729) [Automation]Deletion of a Account reported Success inspite of VM Expunge Failures
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala resolved CLOUDSTACK-5729.
-
Resolution: Fixed
Commit 6ce46e94f522f08c91db2cde33829f5b41539397 in branch refs/heads/4.3 from
Harikrishna Patnala
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6ce46e9 ]
CLOUDSTACK-5730: [Automation]DirectAgentAttache's send command fails due to
ArrayIndexOutOfBoundsException; Unable to cleanup hypervisor's datastructures
as part of Delete Account Job
This issue is related to CLOUDSTACK-5730 because of that VM expunge got failed.
In the normal working scenario when we delete an account, it tries to clean the
resources with in the account. If any error occurs CS marks the account as
"cleanup_needed" in account table. After that CS checks for accounts the needs
to be cleanup per interval "account.cleanup.interval".
> [Automation]Deletion of a Account reported Success inspite of VM Expunge
> Failures
> -
>
> Key: CLOUDSTACK-5729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5729
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
>Reporter: Chandan Purushothama
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.zip
>
>
> Deletion of Account failed due to VM Exunge job failure. Inspite of that
> Account Deletion is reported as success.
> 2014-01-03 07:39:16,839 ERROR [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Unable to expunge vm: 44
> 2014-01-03 07:39:16,869 INFO [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) deleteAccount: Deleted 1 network
> groups for account 26
> 2014-01-03 07:39:16,870 INFO [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) deleteAccount: Deleted 0 affinity
> groups for account 26
> 2014-01-03 07:39:16,871 DEBUG [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Deleting networks for account 26
> 2014-01-03 07:39:16,884 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-f044cb4e ctx-e5d3f936 ctx-efc2b479) ===END===
> 10.147.38.149 -- GET
> signature=shTK1s%2FnQv84C1gwQYEUo%2F5WFW4%3D&apiKey=SyITk_W_BpbLs73aYJqNRBu9Sir1d7k6hqoKVUmFCMSVG-vshSHHKOdj_nVVTOQHqyvfR3ZSXhDzL2QUquSdJA&command=queryAsyncJobResult&response=json&jobid=fb908e1c-cdf8-4ae9-8c0d-09116061c3f7
> 2014-01-03 07:39:16,894 WARN [o.a.c.e.o.NetworkOrchestrator]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Can't delete the network, not all
> user vms are expunged. Vm VM[User|QA-03d9e9fa-081a-4175-9bf2-2508034b6e17] is
> in Expunging state
> 2014-01-03 07:39:16,894 WARN [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Unable to destroy network
> Ntwk[229|Guest|8] as a part of account id=26 cleanup.
> 2014-01-03 07:39:16,895 DEBUG [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Deleting vpcs for account 26
> 2014-01-03 07:39:16,897 DEBUG [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Deleting site-to-site VPN
> customer gateways for account 26
> 2014-01-03 07:39:16,908 INFO [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) deleteAccount: Released 0
> dedicated guest vlan ranges from account 26
> 2014-01-03 07:39:17,034 INFO [c.c.u.AccountManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Cleanup for account 26 is needed.
> 2014-01-03 07:39:17,048 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-72:ctx-d82a5609 ctx-1472cd68) Complete async job-359,
> jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.SuccessResponse/null/{"success":true}
> 2014-01-03 07:39:17,056 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-72:ctx-d82a5609) Done executing
> org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd for job-359
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5714) [upgrade]getting blank console;failed to destroy CPVM in upgraded setup ;Unable to send due to java.lang.ArrayIndexOutOfBoundsException: 0
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koushik Das reassigned CLOUDSTACK-5714:
---
Assignee: Koushik Das
> [upgrade]getting blank console;failed to destroy CPVM in upgraded setup
> ;Unable to send due to java.lang.ArrayIndexOutOfBoundsException: 0
> --
>
> Key: CLOUDSTACK-5714
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5714
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: hyp:xen6.2
>Reporter: prashant kumar mishra
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: Logs_Db.rar, screenshot-1.jpg
>
>
> STEPS TO REPRODUCE
> =
> 1-prepare a CS setup with ACS4.2+xen server
> 2-register 64 bit template and upgrade it to 4.3
> 3-run the
> " nohup cloudstack-sysvmadm -d -u cloud -p password
> -s > sysvm.log 2>&1 &"
> EXPECTED
> ==
> system vm should be successfully stopped and started
> ACTUAL
> ==
> CPVM failed to start
> Tried to destroy CPVM manually
>
> ran in this "Fail to destroy system vm" but actually cpvm got destroyed
> ,after new CPVM came up , whenever i am trying to access console of any vm i
> am getting blank console (please check the screenshot).
> LOG
> ===
> [root@rh63 CloudPlatform-4.3-1011-rhel6.3]# nohup cloudstack-sysvmadm -d
> 10.147.38.206 -u cloud -p password -s > sysvm.log 2>&1 &
> [1] 28994
> [root@rh63 CloudPlatform-4.3-1011-rhel6.3]# tail -f sysvm.log
> nohup: ignoring input
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
> Stopping and starting 1 console proxy vm(s)...
> ERROR: Failed to start console proxy vm with id 2
> Done stopping and starting console proxy vm(s) .
> LOG
>
> 014-01-02 09:27:54,583 DEBUG [c.c.a.t.Request] (Job-Executor-18:ctx-48b44e7f
> ctx-4c2c4411) Seq 1-1441792111: Executing: { Cmd , MgmtId: 7145449848920,
> via: 1(Rack1Pod1Host7), Ver: v1, Flags: 100011, [] }
> 2014-01-02 09:27:54,583 WARN [c.c.a.m.AgentAttache]
> (Job-Executor-18:ctx-48b44e7f ctx-4c2c4411) Seq 1-1441792111: Unable to send
> due to
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:100)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:374)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:398)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:497)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:448)
> at
> com.cloud.vm.VirtualMachineManagerImpl.expunge(VirtualMachineManagerImpl.java:437)
> at
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.destroyProxy(ConsoleProxyManagerImpl.java:1162)
> at
> com.cloud.server.ManagementServerImpl.destroyConsoleProxy(ManagementServerImpl.java:2155)
> at
> com.cloud.server.ManagementServerImpl.destroySystemVM(ManagementServerImpl.java:3220)
> at
> com.cloud.server.ManagementServerImpl.destroySystemVM(ManagementServerImpl.java:609)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframe
[jira] [Updated] (CLOUDSTACK-5329) MigrateVMCmd on stopped VM is failing with NPE when trying to migrate to zone-wide-primary storage.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori updated CLOUDSTACK-5329:
--
Attachment: management-server.log
> MigrateVMCmd on stopped VM is failing with NPE when trying to migrate to
> zone-wide-primary storage.
> ---
>
> Key: CLOUDSTACK-5329
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5329
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
>Reporter: manasaveloori
>Assignee: edison su
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.log, management-server.rar
>
>
> Steps:
> 1.Have a CS with multiple zone wide primary storage using KVM host.
> 2.Deploy a VM and stop it.
> 3.Now goto Migrate VM.Drop down lists the available primary storage to
> migrate.
> 4.Now migrate the VM to another zone wide primary storage.
> Observation:
> Observed the following NPE:
> 2013-12-02 21:16:04,537 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-49:ctx-63bbd88b) Executing AsyncJobVO {id:91, userId: 2,
> accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
> {"response":"json","sessionkey":"bETJCcI/wg7sd2gWxD7zzG5wotQ\u003d","virtualmachineid":"d22ce820-339c-4c80-a16b-dd21bd7a8804","cmdEventType":"VM.MIGRATE","ctxUserId":"2","storageid":"b01ec063-b9c5-3685-b5ea-c816554f1ffe","httpmethod":"GET","_":"1385979761075","ctxAccountId":"2","ctxStartEventId":"293"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6758231703598, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-02 21:16:04,562 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-49:ctx-63bbd88b) Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> java.lang.NullPointerException
> at
> com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:3954)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy169.vmStorageMigration(Unknown Source)
> at
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:150)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
> at
> com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:520)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.Ma
[jira] [Updated] (CLOUDSTACK-5762) [dynamic compute offerings]UI change required for select compute offerinngs in add instance wizard
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-5762: -- Attachment: screenshot-1.jpg > [dynamic compute offerings]UI change required for select compute offerinngs > in add instance wizard > --- > > Key: CLOUDSTACK-5762 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5762 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra > Fix For: 4.3.0 > > Attachments: screenshot-1.jpg > > > "required" is overlapping on memory and cpu if dynamic compute offering > selected in deploy vm wizard .please check screenshot > Steps to repro > === > 1-preapare a CS 4.3 setup > 2-check select compute offering page in deploy vm wizard. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5714) [upgrade]getting blank console;failed to destroy CPVM in upgraded setup ;Unable to send due to java.lang.ArrayIndexOutOfBoundsException: 0
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koushik Das resolved CLOUDSTACK-5714.
-
Resolution: Fixed
This is fixed as part of commit 6ce46e94f522f08c91db2cde33829f5b41539397
> [upgrade]getting blank console;failed to destroy CPVM in upgraded setup
> ;Unable to send due to java.lang.ArrayIndexOutOfBoundsException: 0
> --
>
> Key: CLOUDSTACK-5714
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5714
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: hyp:xen6.2
>Reporter: prashant kumar mishra
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: Logs_Db.rar, screenshot-1.jpg
>
>
> STEPS TO REPRODUCE
> =
> 1-prepare a CS setup with ACS4.2+xen server
> 2-register 64 bit template and upgrade it to 4.3
> 3-run the
> " nohup cloudstack-sysvmadm -d -u cloud -p password
> -s > sysvm.log 2>&1 &"
> EXPECTED
> ==
> system vm should be successfully stopped and started
> ACTUAL
> ==
> CPVM failed to start
> Tried to destroy CPVM manually
>
> ran in this "Fail to destroy system vm" but actually cpvm got destroyed
> ,after new CPVM came up , whenever i am trying to access console of any vm i
> am getting blank console (please check the screenshot).
> LOG
> ===
> [root@rh63 CloudPlatform-4.3-1011-rhel6.3]# nohup cloudstack-sysvmadm -d
> 10.147.38.206 -u cloud -p password -s > sysvm.log 2>&1 &
> [1] 28994
> [root@rh63 CloudPlatform-4.3-1011-rhel6.3]# tail -f sysvm.log
> nohup: ignoring input
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
> Stopping and starting 1 console proxy vm(s)...
> ERROR: Failed to start console proxy vm with id 2
> Done stopping and starting console proxy vm(s) .
> LOG
>
> 014-01-02 09:27:54,583 DEBUG [c.c.a.t.Request] (Job-Executor-18:ctx-48b44e7f
> ctx-4c2c4411) Seq 1-1441792111: Executing: { Cmd , MgmtId: 7145449848920,
> via: 1(Rack1Pod1Host7), Ver: v1, Flags: 100011, [] }
> 2014-01-02 09:27:54,583 WARN [c.c.a.m.AgentAttache]
> (Job-Executor-18:ctx-48b44e7f ctx-4c2c4411) Seq 1-1441792111: Unable to send
> due to
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:100)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:374)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:398)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:497)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:448)
> at
> com.cloud.vm.VirtualMachineManagerImpl.expunge(VirtualMachineManagerImpl.java:437)
> at
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.destroyProxy(ConsoleProxyManagerImpl.java:1162)
> at
> com.cloud.server.ManagementServerImpl.destroyConsoleProxy(ManagementServerImpl.java:2155)
> at
> com.cloud.server.ManagementServerImpl.destroySystemVM(ManagementServerImpl.java:3220)
> at
> com.cloud.server.ManagementServerImpl.destroySystemVM(ManagementServerImpl.java:609)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Re
[jira] [Commented] (CLOUDSTACK-5329) MigrateVMCmd on stopped VM is failing with NPE when trying to migrate to zone-wide-primary storage.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861411#comment-13861411
]
manasaveloori commented on CLOUDSTACK-5329:
---
Observed "Unable to serialize: com.cloud.vm.VmWorkStorageMigration@30d0bbff"
when trying to migrate from zone wide primary to cluster-wide primary storage:
2014-01-03 21:27:53,340 DEBUG [c.c.a.ApiServlet] (catalina-exec-18:ctx-2a553cfb
ctx-a2f9d489) ===END=== 10.252.192.34 -- GET
command=migrateVirtualMachine&storageid=485d70e8-8ee0-31f4-bcd6-b716f7dd5bac&virtualmachineid=c73b26ad-4fee-4c20-9626-2f11672c8018&response=json&sessionkey=toMTqmwjN9SSHxVGHaflXD3mfXY%3D&_=1388745469500
2014-01-03 21:27:53,343 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-51:ctx-fbfeb722) Add job-43 into job monitoring
2014-01-03 21:27:53,344 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-51:ctx-fbfeb722) Executing AsyncJobVO {id:43, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{"response":"json","sessionkey":"toMTqmwjN9SSHxVGHaflXD3mfXY\u003d","virtualmachineid":"c73b26ad-4fee-4c20-9626-2f11672c8018","cmdEventType":"VM.MIGRATE","ctxUserId":"2","storageid":"485d70e8-8ee0-31f4-bcd6-b716f7dd5bac","httpmethod":"GET","_":"1388745469500","ctxAccountId":"2","ctxStartEventId":"69"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7494415941730, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-01-03 21:27:53,411 DEBUG [c.c.u.d.T.Transaction]
(Job-Executor-51:ctx-fbfeb722 ctx-a2f9d489) Rolling back the transaction: Time
= 35 Name = Job-Executor-51; called by
-TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.migrateVmStorageThroughJobQueue:4479-VirtualMachineManagerImpl.storageMigration:1562-UserVmManagerImpl.vmStorageMigration:4069-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:57-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616
2014-01-03 21:27:53,415 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-51:ctx-fbfeb722) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
com.cloud.vm.VmWorkStorageMigration@30d0bbff
at
org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
at com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
at
com.cloud.vm.VirtualMachineManagerImpl$9.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:4508)
at
com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
at
com.cloud.vm.VirtualMachineManagerImpl.migrateVmStorageThroughJobQueue(VirtualMachineManagerImpl.java:4479)
at
com.cloud.vm.VirtualMachineManagerImpl.storageMigration(VirtualMachineManagerImpl.java:1562)
at
com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:4069)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy169.vmStorageMigration(Unknown Source)
at
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:150)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at
com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at
com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.
[jira] [Commented] (CLOUDSTACK-5138) [Automation] NPE while create template from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861415#comment-13861415
]
Srikanteswararao Talluri commented on CLOUDSTACK-5138:
--
I don't hit this issue in 4.3 , i could create template from snapshot.
> [Automation] NPE while create template from snapshot
>
>
> Key: CLOUDSTACK-5138
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5138
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template
>Affects Versions: 4.2.1
>Reporter: Srikanteswararao Talluri
>Assignee: Nitin Mehta
> Fix For: 4.3.0
>
>
> create a template from snapshot
> Following exception is observed:
> Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
> u'Failed to create templatejava.lang.NullPointerException\n\tat
> java.lang.ProcessBuilder.start(ProcessBuilder.java:457)\n\tat
> com.cloud.utils.script.Script.execute(Script.java:183)\n\tat
> com.cloud.utils.script.Script.execute(Script.java:161)\n\tat
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copySnapshotToTemplateFromNfsToNfsXenserver(NfsSecondaryStorageResource.java:365)\n\tat
>
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copySnapshotToTemplateFromNfsToNfs(NfsSecondaryStorageResource.java:408)\n\tat
>
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.createTemplateFromSnapshot(NfsSecondaryStorageResource.java:509)\n\tat
>
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:588)\n\tat
>
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:201)\n\tat
>
> org.apache.cloudstack.storage.resource.LocalNfsSecondaryStorageResource.executeRequest(LocalNfsSecondaryStorageResource.java:76)\n\tat
>
> org.apache.cloudstack.storage.LocalHostEndpoint.sendMessage(LocalHostEndpoint.java:93)\n\tat
>
> org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.createTemplateFromSnapshot(AncientDataMotionStrategy.java:429)\n\tat
>
> org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:382)\n\tat
>
> org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:58)\n\tat
>
> org.apache.cloudstack.storage.image.TemplateServiceImpl.copyAsync(TemplateServiceImpl.java:594)\n\tat
>
> org.apache.cloudstack.storage.image.TemplateServiceImpl.createTemplateFromSnapshotAsync(TemplateServiceImpl.java:601)\n\tat
>
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1382)\n\tat
>
> com.cloud.template.TemplateManagerImpl_EnhancerByCloudStack_c9e35bba.CGLIB$createPrivateTemplate$32()\n\tat
>
> com.cloud.template.TemplateManagerImpl_EnhancerByCloudStack_c9e35bba_FastClassByCloudStack_d12ad427.invoke()\n\tat
> net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)\n\tat
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)\n\tat
>
> com.cloud.template.TemplateManagerImpl_EnhancerByCloudStack_c9e35bba.createPrivateTemplate()\n\tat
>
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)\n\tat
> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)\n\tat
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)\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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
> java.lang.Thread.run(Thread.java:679)\n'}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5307) Same router is listed twice in router view of project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861416#comment-13861416
]
Kishan Kavala commented on CLOUDSTACK-5307:
---
Jessica,
There are 2 API calls sent from UI. In the 2nd call projectId is sent twice.
http://localhost:8080/client/api?command=listRouters&zoneid=b315fdc8-f018-4875-8ac3-f8ed4d31edf8&listAll=true&page=1&pagesize=20&response=json&sessionkey=0tyxov%2FVjxYLGiqu2O4ZwW7lLkM%3D&projectid=be1d7bc9-154a-45fa-8f25-4f36e80f14a3&forvpc=false&_=1388745961754
http://localhost:8080/client/api?command=listRouters&zoneid=b315fdc8-f018-4875-8ac3-f8ed4d31edf8&listAll=true&page=1&pagesize=20&projectid=-1&response=json&sessionkey=0tyxov%2FVjxYLGiqu2O4ZwW7lLkM%3D&projectid=be1d7bc9-154a-45fa-8f25-4f36e80f14a3&forvpc=false&_=1388745961795
> Same router is listed twice in router view of project
> -
>
> Key: CLOUDSTACK-5307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5307
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
>Reporter: shweta agarwal
>Assignee: Jessica Wang
>Priority: Minor
> Fix For: 4.3.0
>
> Attachments: tow times router listing.png
>
>
> Repro steps :
> 1. Create a project.
> 2. Create a VM
> 3. Goto Router or VPC router view either via infrastructure ->router or via
> infrastructure->zone->physical network - > network service provider ->
> virtual router->router or
> infrastructure->zone->physical network - > network service provider -> vpc
> virtual router->router
> bug:
> Same router is shown twice
> API calls:
> http://10.147.40.27:8080/client/api?command=listRouters&listAll=true&page=1&pagesize=20&response=json&sessionkey=Z75KXzYgYh7eR8tFxVNqX%2FUtBVw%3D&projectid=31511e06-9fb3-480a-b0b8-6a502207d062&forvpc=false&_=1385705460290
> Response:
> { "listroutersresponse" : { "count":1 ,"router" : [
> {"id":"8800bb36-e96c-4af5-be5e-2dd5fde71b6a","zoneid":"71c3d210-e0f7-4ea0-80b3-1a3769cdaeb2","zonename":"xen","dns1":"10.140.50.6","networkdomain":"cs5cloud.internal","gateway":"10.147.51.1","name":"r-33-VM","podid":"a294449c-0048-4102-b438-0afc67d9854f","hostid":"713fafd1-b2df-4461-8b9a-db6fa1c6c8bd","hostname":"Rack1Pod1Host24","linklocalip":"169.254.3.173","linklocalmacaddress":"0e:00:a9:fe:03:ad","linklocalnetmask":"255.255.0.0","linklocalnetworkid":"89e82b30-1456-4c5d-8346-761a9bfde0c4","publicip":"10.147.51.90","publicmacaddress":"06:35:34:00:00:79","publicnetmask":"255.255.255.0","publicnetworkid":"c1e501e4-41a3-47a0-8cf3-472895bc68ae","guestipaddress":"10.1.1.1","guestmacaddress":"02:00:19:3f:00:02","guestnetmask":"255.255.255.0","guestnetworkid":"0c5d1cb8-9756-4b04-a551-bc53d7553420","templateid":"5d5b6245-fc06-4d7b-9d26-9656d6a991fe","created":"2013-11-28T11:57:33+0530","state":"Running","projectid":"31511e06-9fb3-480a-b0b8-6a502207d062","project":"shweta","domainid":"1","domain":"ROOT","serviceofferingid":"0852bf4c-3f04-4747-89b2-a37f6828149c","serviceofferingname":"System
> Offering For Software
> Router","isredundantrouter":false,"redundantstate":"UNKNOWN","version":"3.0","role":"VIRTUAL_ROUTER","nic":[{"id":"bf7dbef2-7f7d-41a9-9963-680d8e0551bf","networkid":"0c5d1cb8-9756-4b04-a551-bc53d7553420","networkname":"project","netmask":"255.255.255.0","ipaddress":"10.1.1.1","isolationuri":"vlan://1049","broadcasturi":"vlan://1049","traffictype":"Guest","type":"Isolated","isdefault":false,"macaddress":"02:00:19:3f:00:02"},{"id":"f070d8e4-88be-4f5e-a6e9-2d883fa026d3","networkid":"89e82b30-1456-4c5d-8346-761a9bfde0c4","netmask":"255.255.0.0","gateway":"169.254.0.1","ipaddress":"169.254.3.173","traffictype":"Control","isdefault":false,"macaddress":"0e:00:a9:fe:03:ad"},{"id":"d2110f33-dc7f-49a5-bb35-808ee2ba9251","networkid":"c1e501e4-41a3-47a0-8cf3-472895bc68ae","netmask":"255.255.255.0","gateway":"10.147.51.1","ipaddress":"10.147.51.90","isolationuri":"vlan://51","broadcasturi":"vlan://51","traffictype":"Public","isdefault":true,"macaddress":"06:35:34:00:00:79"}],"requiresupgrade":true}
> ] } }
> http://10.147.40.27:8080/client/api?command=listRouters&listAll=true&page=1&pagesize=20&projectid=-1&response=json&sessionkey=Z75KXzYgYh7eR8tFxVNqX%2FUtBVw%3D&projectid=31511e06-9fb3-480a-b0b8-6a502207d062&forvpc=false&_=1385705460399
> { "listroutersresponse" : { "count":1 ,"router" : [
> {"id":"8800bb36-e96c-4af5-be5e-2dd5fde71b6a","zoneid":"71c3d210-e0f7-4ea0-80b3-1a3769cdaeb2","zonename":"xen","dns1":"10.140.50.6","networkdomain":"cs5cloud.internal","gateway":"10.147.51.1","name":"r-33-VM","podid":"a294449c-0048-4102-b438-0afc67d9854f","hostid":"713fafd1-b2df-4461-8b9a-db6fa1c6c8bd","hostname":"Rack1Pod1Host24","linklocalip":"169.254.3.1
[jira] [Updated] (CLOUDSTACK-5307) Same router is listed twice in router view of project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishan Kavala updated CLOUDSTACK-5307:
--
Assignee: Jessica Wang (was: Kishan Kavala)
> Same router is listed twice in router view of project
> -
>
> Key: CLOUDSTACK-5307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5307
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
>Reporter: shweta agarwal
>Assignee: Jessica Wang
>Priority: Minor
> Fix For: 4.3.0
>
> Attachments: tow times router listing.png
>
>
> Repro steps :
> 1. Create a project.
> 2. Create a VM
> 3. Goto Router or VPC router view either via infrastructure ->router or via
> infrastructure->zone->physical network - > network service provider ->
> virtual router->router or
> infrastructure->zone->physical network - > network service provider -> vpc
> virtual router->router
> bug:
> Same router is shown twice
> API calls:
> http://10.147.40.27:8080/client/api?command=listRouters&listAll=true&page=1&pagesize=20&response=json&sessionkey=Z75KXzYgYh7eR8tFxVNqX%2FUtBVw%3D&projectid=31511e06-9fb3-480a-b0b8-6a502207d062&forvpc=false&_=1385705460290
> Response:
> { "listroutersresponse" : { "count":1 ,"router" : [
> {"id":"8800bb36-e96c-4af5-be5e-2dd5fde71b6a","zoneid":"71c3d210-e0f7-4ea0-80b3-1a3769cdaeb2","zonename":"xen","dns1":"10.140.50.6","networkdomain":"cs5cloud.internal","gateway":"10.147.51.1","name":"r-33-VM","podid":"a294449c-0048-4102-b438-0afc67d9854f","hostid":"713fafd1-b2df-4461-8b9a-db6fa1c6c8bd","hostname":"Rack1Pod1Host24","linklocalip":"169.254.3.173","linklocalmacaddress":"0e:00:a9:fe:03:ad","linklocalnetmask":"255.255.0.0","linklocalnetworkid":"89e82b30-1456-4c5d-8346-761a9bfde0c4","publicip":"10.147.51.90","publicmacaddress":"06:35:34:00:00:79","publicnetmask":"255.255.255.0","publicnetworkid":"c1e501e4-41a3-47a0-8cf3-472895bc68ae","guestipaddress":"10.1.1.1","guestmacaddress":"02:00:19:3f:00:02","guestnetmask":"255.255.255.0","guestnetworkid":"0c5d1cb8-9756-4b04-a551-bc53d7553420","templateid":"5d5b6245-fc06-4d7b-9d26-9656d6a991fe","created":"2013-11-28T11:57:33+0530","state":"Running","projectid":"31511e06-9fb3-480a-b0b8-6a502207d062","project":"shweta","domainid":"1","domain":"ROOT","serviceofferingid":"0852bf4c-3f04-4747-89b2-a37f6828149c","serviceofferingname":"System
> Offering For Software
> Router","isredundantrouter":false,"redundantstate":"UNKNOWN","version":"3.0","role":"VIRTUAL_ROUTER","nic":[{"id":"bf7dbef2-7f7d-41a9-9963-680d8e0551bf","networkid":"0c5d1cb8-9756-4b04-a551-bc53d7553420","networkname":"project","netmask":"255.255.255.0","ipaddress":"10.1.1.1","isolationuri":"vlan://1049","broadcasturi":"vlan://1049","traffictype":"Guest","type":"Isolated","isdefault":false,"macaddress":"02:00:19:3f:00:02"},{"id":"f070d8e4-88be-4f5e-a6e9-2d883fa026d3","networkid":"89e82b30-1456-4c5d-8346-761a9bfde0c4","netmask":"255.255.0.0","gateway":"169.254.0.1","ipaddress":"169.254.3.173","traffictype":"Control","isdefault":false,"macaddress":"0e:00:a9:fe:03:ad"},{"id":"d2110f33-dc7f-49a5-bb35-808ee2ba9251","networkid":"c1e501e4-41a3-47a0-8cf3-472895bc68ae","netmask":"255.255.255.0","gateway":"10.147.51.1","ipaddress":"10.147.51.90","isolationuri":"vlan://51","broadcasturi":"vlan://51","traffictype":"Public","isdefault":true,"macaddress":"06:35:34:00:00:79"}],"requiresupgrade":true}
> ] } }
> http://10.147.40.27:8080/client/api?command=listRouters&listAll=true&page=1&pagesize=20&projectid=-1&response=json&sessionkey=Z75KXzYgYh7eR8tFxVNqX%2FUtBVw%3D&projectid=31511e06-9fb3-480a-b0b8-6a502207d062&forvpc=false&_=1385705460399
> { "listroutersresponse" : { "count":1 ,"router" : [
> {"id":"8800bb36-e96c-4af5-be5e-2dd5fde71b6a","zoneid":"71c3d210-e0f7-4ea0-80b3-1a3769cdaeb2","zonename":"xen","dns1":"10.140.50.6","networkdomain":"cs5cloud.internal","gateway":"10.147.51.1","name":"r-33-VM","podid":"a294449c-0048-4102-b438-0afc67d9854f","hostid":"713fafd1-b2df-4461-8b9a-db6fa1c6c8bd","hostname":"Rack1Pod1Host24","linklocalip":"169.254.3.173","linklocalmacaddress":"0e:00:a9:fe:03:ad","linklocalnetmask":"255.255.0.0","linklocalnetworkid":"89e82b30-1456-4c5d-8346-761a9bfde0c4","publicip":"10.147.51.90","publicmacaddress":"06:35:34:00:00:79","publicnetmask":"255.255.255.0","publicnetworkid":"c1e501e4-41a3-47a0-8cf3-472895bc68ae","guestipaddress":"10.1.1.1","guestmacaddress":"02:00:19:3f:00:02","guestnetmask":"255.255.255.0","guestnetworkid":"0c5d1cb8-9756-4b04-a551-bc53d7553420","templateid":"5d5b6245-fc06-4d7b-9d26-9656d6a991fe","created":"2013-11-28T11:57:33+0530","state":"Running","projectid":"31511e06-9fb3-480a-b0b8-6a502207d062","project":"shweta","domainid":"1"
[jira] [Assigned] (CLOUDSTACK-5746) [Hyper-v] Can't access vm console from IE browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar reassigned CLOUDSTACK-5746: -- Assignee: Anshul Gangwar > [Hyper-v] Can't access vm console from IE browser > - > > Key: CLOUDSTACK-5746 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5746 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: console3.PNG > > > [Hyper-v] Can't access vm console vm from IE browser > Steps to reproduce: > > 1.Bring up CS in advanced zone with Hyper-v host > 2.Deploy couple of guest vms using default cent os template > 3.Try to access any of the vms (System/guest) using Internet Explorer > Result: > == > Blank screen is displayed in IE browser. > Observations: > > MS generates URL with secure token and opens console session in new browser. > However browser displays blank white screen. > 2014-01-03 12:14:53,651 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Port info > instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,651 INFO [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Parse host info returned from executing > GetVNCPortCommand. host info: instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Compose console url: > https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) the console url is :: > win7 src="https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows";> > Tried this with enabling/disabling compatablity view available on IE > IE version 9 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5746) [Hyper-v] Can't access vm console from IE browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861419#comment-13861419 ] Anshul Gangwar commented on CLOUDSTACK-5746: This bug is not hyperv specific. Removing hyperv label from the bug > [Hyper-v] Can't access vm console from IE browser > - > > Key: CLOUDSTACK-5746 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5746 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: console3.PNG > > > [Hyper-v] Can't access vm console vm from IE browser > Steps to reproduce: > > 1.Bring up CS in advanced zone with Hyper-v host > 2.Deploy couple of guest vms using default cent os template > 3.Try to access any of the vms (System/guest) using Internet Explorer > Result: > == > Blank screen is displayed in IE browser. > Observations: > > MS generates URL with secure token and opens console session in new browser. > However browser displays blank white screen. > 2014-01-03 12:14:53,651 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Port info > instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,651 INFO [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Parse host info returned from executing > GetVNCPortCommand. host info: instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Compose console url: > https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) the console url is :: > win7 src="https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows";> > Tried this with enabling/disabling compatablity view available on IE > IE version 9 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5742) #cpu,cpu speed, and ram is getting updated under wrong usage_type(2) for dynamic compute offering in usage_vm_instance table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala reassigned CLOUDSTACK-5742: --- Assignee: Bharat Kumar (was: Harikrishna Patnala) > #cpu,cpu speed, and ram is getting updated under wrong usage_type(2) for > dynamic compute offering in usage_vm_instance table > > > Key: CLOUDSTACK-5742 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5742 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.3.0 > > Attachments: LOG_DB.rar > > > STEPS TO REPO > == > 1-prepare a CS setup 4.3 > 2-deploy a vm with small CO > 3-Change the vm CO to dynamic CO. > 4-check the usage_vm_instance table after cloud_usage db synch > EXPECTED > = > cpu and ram should get updated under usage type 1 > ACTUAL > === > cpu and ram is getting updated under usage type2 > DB > === > | 2 | 1 | 2 | 8 | test| > 12 | 202 | XenServer | 2014-01-03 10:10:15 | NULL > | 100 | 1 |256 | > | 1 | 1 | 2 | 8 | test| > 12 | 202 | XenServer | 2014-01-03 10:11:21 | NULL > | NULL | NULL | NULL | > ++-+++-+-+-+-+-+-+---+---++ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5658) [Hyper-v] Template created from root volume has size set to NULL hence failed to deploy VM from that template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861421#comment-13861421 ] ASF subversion and git services commented on CLOUDSTACK-5658: - Commit 9313a35f41e84b967ba6773fe56258be898516c3 in branch refs/heads/4.3 from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9313a35 ] CLOUDSTACK-5658 CLOUDSTACK-5563 deploying VM from template created from volumes fails > [Hyper-v] Template created from root volume has size set to NULL hence failed > to deploy VM from that template > - > > Key: CLOUDSTACK-5658 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5658 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Template >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 3282d19cca4afe65d049c2db9b63f0ef528e81e1 > Storage: SMB for both primary and secondary > Hypervisor: Hyper-v >Reporter: Sanjeev N >Assignee: Rajesh Battala >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: cloud.dmp, management-server.rar > > > [Hyper-v] Template created from root volume has size set to NULL hence failed > to deploy VM from that template > Steps to Reproduce: > == > 1.Bring up CS in advanced zone with Hyper-v host using SMB shares for primary > and secondary > 2.Deploy one or more guest vms with the default cent of template > 3.Stop the vm > 4.Create template from the root disk of the vm > Expected Result: > == > Template creation should be successful and size of the template should be > equal to the root volume size > Actual Result: > > Template creation succeeded however template size was set to NULL > Impact: > == > 1.VM creation failed at allocating disks for VM with NPE > 2.Since usage is NULL TEMPLATE_CREATE event got generated with size set to 0 > which will have huge impact on the billing. > Following is the log snippet while deploying a vm with the template: > 2013-12-27 16:02:00,874 DEBUG [c.c.a.ApiServlet] > (catalina-exec-21:ctx-1b6ca1b9) ===START=== 10.146.0.134 -- GET > command=deployVirtualMachine&response=json&sessionkey=0Is7NdFczbwiApJPUUVO8LG1Lj4%3D&zoneid=20042051-b332-497b-a0cd-57078d9f423a&templateid=c0d9df5d-e782-47b8-8479-d39f8a69864c&hypervisor=Hyperv&serviceofferingid=d2b5b96b-b042-405e-aafb-be7ea95ab1be&networkids=63660749-0d6b-457a-b6c2-1d80a9ae2b70&displayname=ex1&name=ex1&_=1388140306272 > 2013-12-27 16:02:00,881 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) InfrastructureEntity name > is:com.cloud.offering.ServiceOffering > 2013-12-27 16:02:00,884 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) ControlledEntity name > is:com.cloud.template.VirtualMachineTemplate > 2013-12-27 16:02:00,886 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) ControlledEntity name > is:com.cloud.network.Network > 2013-12-27 16:02:00,897 DEBUG [c.c.n.NetworkModelImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Service SecurityGroup is not > supported in the network id=204 > 2013-12-27 16:02:00,971 DEBUG [c.c.v.UserVmManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating in the DB for vm > 2013-12-27 16:02:00,979 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating entries for VM: > VM[User|ex1] > 2013-12-27 16:02:00,980 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating nics for VM[User|ex1] > 2013-12-27 16:02:00,980 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating nic for vm > VM[User|ex1] in network Ntwk[204|Guest|8] with requested profile > NicProfile[0-0-null-null-null > 2013-12-27 16:02:01,053 DEBUG [c.c.n.NetworkModelImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Service SecurityGroup is not > supported in the network id=204 > 2013-12-27 16:02:01,054 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating disks for VM[User|ex1] > 2013-12-27 16:02:01,057 DEBUG [c.c.u.d.T.Transaction] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Rolling back the transaction: > Time = 89 Name = catalina-exec-21; called by > -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-VirtualMachineManagerImpl.allocate:386-CloudOrchestrator.createVirtualMachine:217-UserVmManagerImpl$3.doInTransa
[jira] [Updated] (CLOUDSTACK-5746) [Hyper-v] Can't access vm console from IE browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-5746: --- Labels: (was: hyper-V, hyper-v hyperv) > [Hyper-v] Can't access vm console from IE browser > - > > Key: CLOUDSTACK-5746 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5746 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Priority: Critical > Fix For: 4.3.0 > > Attachments: console3.PNG > > > [Hyper-v] Can't access vm console vm from IE browser > Steps to reproduce: > > 1.Bring up CS in advanced zone with Hyper-v host > 2.Deploy couple of guest vms using default cent os template > 3.Try to access any of the vms (System/guest) using Internet Explorer > Result: > == > Blank screen is displayed in IE browser. > Observations: > > MS generates URL with secure token and opens console session in new browser. > However browser displays blank white screen. > 2014-01-03 12:14:53,651 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Port info > instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,651 INFO [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Parse host info returned from executing > GetVNCPortCommand. host info: instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Compose console url: > https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) the console url is :: > win7 src="https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows";> > Tried this with enabling/disabling compatablity view available on IE > IE version 9 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CLOUDSTACK-5746) [Hyper-v] Can't access vm console from IE browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861419#comment-13861419 ] Anshul Gangwar edited comment on CLOUDSTACK-5746 at 1/3/14 10:54 AM: - This bug is not hyperv specific. Other hypervisors console are also not opening in ie 9. Removing hyperv label from the bug was (Author: anshulg): This bug is not hyperv specific. Removing hyperv label from the bug > [Hyper-v] Can't access vm console from IE browser > - > > Key: CLOUDSTACK-5746 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5746 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Assignee: Anshul Gangwar >Priority: Critical > Fix For: 4.3.0 > > Attachments: console3.PNG > > > [Hyper-v] Can't access vm console vm from IE browser > Steps to reproduce: > > 1.Bring up CS in advanced zone with Hyper-v host > 2.Deploy couple of guest vms using default cent os template > 3.Try to access any of the vms (System/guest) using Internet Explorer > Result: > == > Blank screen is displayed in IE browser. > Observations: > > MS generates URL with secure token and opens console session in new browser. > However browser displays blank white screen. > 2014-01-03 12:14:53,651 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Port info > instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,651 INFO [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Parse host info returned from executing > GetVNCPortCommand. host info: instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Compose console url: > https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) the console url is :: > win7 src="https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows";> > Tried this with enabling/disabling compatablity view available on IE > IE version 9 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5746) [Hyper-v] Can't access vm console from IE browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-5746: --- Assignee: (was: Anshul Gangwar) > [Hyper-v] Can't access vm console from IE browser > - > > Key: CLOUDSTACK-5746 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5746 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Priority: Critical > Fix For: 4.3.0 > > Attachments: console3.PNG > > > [Hyper-v] Can't access vm console vm from IE browser > Steps to reproduce: > > 1.Bring up CS in advanced zone with Hyper-v host > 2.Deploy couple of guest vms using default cent os template > 3.Try to access any of the vms (System/guest) using Internet Explorer > Result: > == > Blank screen is displayed in IE browser. > Observations: > > MS generates URL with secure token and opens console session in new browser. > However browser displays blank white screen. > 2014-01-03 12:14:53,651 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Port info > instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,651 INFO [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Parse host info returned from executing > GetVNCPortCommand. host info: instanceId=F13DECA2-8B6E-4774-83AD-FE87F277DC5B > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) Compose console url: > https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows > 2014-01-03 12:14:53,656 DEBUG [c.c.s.ConsoleProxyServlet] > (catalina-exec-20:null) the console url is :: > win7 src="https://10-147-48-4.realhostip.com/ajax?token=LIQeT_aw7lO4F6dZyLAurjpusihlj-Q7OPX0svZwWMyB0mYcmbo6uZYki6HKGHHMkyypvJ71x9gKH177BfQSUaQbkxpamH62n4dkA0NRkG71PL3dMPtQRjINN3s2zMGGhcU5y2rfDxhsa6CY_VxhDX7I4-hJ314tOKdhJ1E43QCBjYPHiyPFT_JXG34dvj59eImIQN-7a7n8H5jDi0pMtekhmM4lov7dmQP3BbWir2ac2kW_SVlOz2vXIz-u9qkPd8ztm_V_KW0T2RPSY592__I0FxTVfKFidzhU5OqylUCyD3bzN4osPkx_X3e0UhYA9mWRp78LH_P18h0TLcoi31hRoFri_mKUtD2XnehBQtSPUcztmdUjBUCYgGC0N-m7k9DGYmSUKgfGXUkj5tn8mw&guest=windows";> > Tried this with enabling/disabling compatablity view available on IE > IE version 9 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5563) path field is set to null in volumes table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861422#comment-13861422 ] ASF subversion and git services commented on CLOUDSTACK-5563: - Commit 9313a35f41e84b967ba6773fe56258be898516c3 in branch refs/heads/4.3 from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9313a35 ] CLOUDSTACK-5658 CLOUDSTACK-5563 deploying VM from template created from volumes fails > path field is set to null in volumes table > --- > > Key: CLOUDSTACK-5563 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5563 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, Volumes >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 with commit > :197ef921f7b3c80998359f376fe045b13558633c >Reporter: Sanjeev N >Assignee: Rajesh Battala > Labels: hyper-V, > Fix For: 4.3.0 > > > path field is set to null in volumes table > Steps to Reproduce: > = > 1.Bring up CS in advanced zone with hyper-v host using CIFS for both primary > and secondary storage > 2.Deploy a vm using default cent-os template > 3.Check root volume details in volumes table. > Following is the volume details from cloud DB: > mysql> select * from volumes where instance_id=6\G; > *** 1. row *** > id: 8 > account_id: 2 > domain_id: 1 >pool_id: 1 > last_pool_id: NULL >instance_id: 6 > device_id: 0 > name: ROOT-6 > uuid: 70c71522-16ec-4329-a91d-c6006534078d > size: 5368709120 > folder: NULL > path: NULL > pod_id: NULL > data_center_id: 1 > iscsi_name: NULL >host_ip: NULL >volume_type: ROOT > pool_type: NULL > disk_offering_id: 1 >template_id: 6 > first_snapshot_backup_uuid: NULL >recreatable: 0 >created: 2013-12-19 10:04:33 > attached: NULL >updated: 2013-12-19 10:04:38 >removed: NULL > state: Ready > chain_info: NULL > update_count: 2 > disk_type: NULL > vm_snapshot_chain_size: NULL > iso_id: NULL > display_volume: 1 > format: NULL > min_iops: NULL > max_iops: NULL > hv_ss_reserve: NULL > 1 row in set (0.00 sec) > ERROR: > No query specified -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5763) "InvalidParameterValueException" when migrating the root volume of the stppoed VM to another primary storage.
manasaveloori created CLOUDSTACK-5763:
-
Summary: "InvalidParameterValueException" when migrating the root
volume of the stppoed VM to another primary storage.
Key: CLOUDSTACK-5763
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5763
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller
Affects Versions: 4.3.0
Reporter: manasaveloori
Priority: Critical
Fix For: 4.3.0
Attachments: management-server.log
Steps:
1. Deploy CS 4.3 (any HV tried with KVM and Xen5.6 sp2)
2. Have multiple primary storages.
3. Deploy an instance and stop it.
4. Migrate the root volume of the stopped VM to another primary storage.
Observation:
Observed the following exception:
2014-01-03 21:43:10,826 DEBUG [c.c.a.ApiServlet] (catalina-exec-21:ctx-5da1e45c
ctx-2b2c35f8) ===END=== 10.252.192.34 -- GET
command=migrateVolume&livemigrate=true&storageid=a85f0b79-1c84-3291-9c45-10510d327eee&volumeid=4e5f1fe0-29be-49dc-b74e-5d66e207e22c&response=json&sessionkey=toMTqmwjN9SSHxVGHaflXD3mfXY%3D&_=1388746387010
2014-01-03 21:43:10,830 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-63:ctx-8fe672b3) Add job-52 into job monitoring
2014-01-03 21:43:10,830 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-63:ctx-8fe672b3) Executing AsyncJobVO {id:52, userId: 2,
accountId: 2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd, cmdInfo:
{"response":"json","sessionkey":"toMTqmwjN9SSHxVGHaflXD3mfXY\u003d","cmdEventType":"VOLUME.MIGRATE","ctxUserId":"2","storageid":"a85f0b79-1c84-3291-9c45-10510d327eee","livemigrate":"true","httpmethod":"GET","_":"1388746387010","volumeid":"4e5f1fe0-29be-49dc-b74e-5d66e207e22c","ctxAccountId":"2","ctxStartEventId":"79"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7494415941730, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-01-03 21:43:10,849 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-63:ctx-8fe672b3) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd
com.cloud.exception.InvalidParameterValueException: Volume needs to be detached
from VM
at
com.cloud.storage.VolumeApiServiceImpl.migrateVolume(VolumeApiServiceImpl.java:1555)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy195.migrateVolume(Unknown Source)
at
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd.execute(MigrateVolumeCmd.java:103)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at
com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at
com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.jav
[jira] [Updated] (CLOUDSTACK-5763) "InvalidParameterValueException" when migrating the root volume of the stopped VM to another primary storage.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori updated CLOUDSTACK-5763:
--
Summary: "InvalidParameterValueException" when migrating the root volume of
the stopped VM to another primary storage. (was:
"InvalidParameterValueException" when migrating the root volume of the stppoed
VM to another primary storage.)
> "InvalidParameterValueException" when migrating the root volume of the
> stopped VM to another primary storage.
> -
>
> Key: CLOUDSTACK-5763
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5763
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
>Reporter: manasaveloori
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.log
>
>
> Steps:
> 1. Deploy CS 4.3 (any HV tried with KVM and Xen5.6 sp2)
> 2. Have multiple primary storages.
> 3. Deploy an instance and stop it.
> 4. Migrate the root volume of the stopped VM to another primary storage.
> Observation:
> Observed the following exception:
> 2014-01-03 21:43:10,826 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-21:ctx-5da1e45c ctx-2b2c35f8) ===END=== 10.252.192.34 -- GET
> command=migrateVolume&livemigrate=true&storageid=a85f0b79-1c84-3291-9c45-10510d327eee&volumeid=4e5f1fe0-29be-49dc-b74e-5d66e207e22c&response=json&sessionkey=toMTqmwjN9SSHxVGHaflXD3mfXY%3D&_=1388746387010
> 2014-01-03 21:43:10,830 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-63:ctx-8fe672b3) Add job-52 into job monitoring
> 2014-01-03 21:43:10,830 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-63:ctx-8fe672b3) Executing AsyncJobVO {id:52, userId: 2,
> accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd, cmdInfo:
> {"response":"json","sessionkey":"toMTqmwjN9SSHxVGHaflXD3mfXY\u003d","cmdEventType":"VOLUME.MIGRATE","ctxUserId":"2","storageid":"a85f0b79-1c84-3291-9c45-10510d327eee","livemigrate":"true","httpmethod":"GET","_":"1388746387010","volumeid":"4e5f1fe0-29be-49dc-b74e-5d66e207e22c","ctxAccountId":"2","ctxStartEventId":"79"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7494415941730, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-01-03 21:43:10,849 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-63:ctx-8fe672b3) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd
> com.cloud.exception.InvalidParameterValueException: Volume needs to be
> detached from VM
> at
> com.cloud.storage.VolumeApiServiceImpl.migrateVolume(VolumeApiServiceImpl.java:1555)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy195.migrateVolume(Unknown Source)
> at
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd.execute(MigrateVolumeCmd.java:103)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
> at
> com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJob
[jira] [Updated] (CLOUDSTACK-5763) "InvalidParameterValueException" when migrating the root volume of the stppoed VM to another primary storage.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori updated CLOUDSTACK-5763:
--
Attachment: management-server.log
> "InvalidParameterValueException" when migrating the root volume of the
> stppoed VM to another primary storage.
> -
>
> Key: CLOUDSTACK-5763
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5763
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
>Reporter: manasaveloori
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.log
>
>
> Steps:
> 1. Deploy CS 4.3 (any HV tried with KVM and Xen5.6 sp2)
> 2. Have multiple primary storages.
> 3. Deploy an instance and stop it.
> 4. Migrate the root volume of the stopped VM to another primary storage.
> Observation:
> Observed the following exception:
> 2014-01-03 21:43:10,826 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-21:ctx-5da1e45c ctx-2b2c35f8) ===END=== 10.252.192.34 -- GET
> command=migrateVolume&livemigrate=true&storageid=a85f0b79-1c84-3291-9c45-10510d327eee&volumeid=4e5f1fe0-29be-49dc-b74e-5d66e207e22c&response=json&sessionkey=toMTqmwjN9SSHxVGHaflXD3mfXY%3D&_=1388746387010
> 2014-01-03 21:43:10,830 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-63:ctx-8fe672b3) Add job-52 into job monitoring
> 2014-01-03 21:43:10,830 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-63:ctx-8fe672b3) Executing AsyncJobVO {id:52, userId: 2,
> accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd, cmdInfo:
> {"response":"json","sessionkey":"toMTqmwjN9SSHxVGHaflXD3mfXY\u003d","cmdEventType":"VOLUME.MIGRATE","ctxUserId":"2","storageid":"a85f0b79-1c84-3291-9c45-10510d327eee","livemigrate":"true","httpmethod":"GET","_":"1388746387010","volumeid":"4e5f1fe0-29be-49dc-b74e-5d66e207e22c","ctxAccountId":"2","ctxStartEventId":"79"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7494415941730, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-01-03 21:43:10,849 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-63:ctx-8fe672b3) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd
> com.cloud.exception.InvalidParameterValueException: Volume needs to be
> detached from VM
> at
> com.cloud.storage.VolumeApiServiceImpl.migrateVolume(VolumeApiServiceImpl.java:1555)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy195.migrateVolume(Unknown Source)
> at
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd.execute(MigrateVolumeCmd.java:103)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
> at
> com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
> at
> org.apache.cloudstack.managed.context.ManagedCo
[jira] [Commented] (CLOUDSTACK-5691) [Hyper-V] Attaching an uploaded volume to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861442#comment-13861442
]
ASF subversion and git services commented on CLOUDSTACK-5691:
-
Commit 741634b87e72aba66c64afabc2fb5e7183af1484 in branch refs/heads/4.3 from
[~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=741634b ]
CLOUDSTACK-5691: Fix for attaching an uploaded volume to instance running
on hyperv. There were multiple issues here. Upload volume was actually
failing because the post download check for vhd on the cifs share was
unsuccessful. Also the agent code wasn't parsing the volume path correctly.
Fixed it too.
> [Hyper-V] Attaching an uploaded volume to a VM is failing
> -
>
> Key: CLOUDSTACK-5691
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5691
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Management Server
>Affects Versions: 4.3.0
> Environment: hyperv, 4.3, CIFS as primary and secondary storage
>Reporter: Abhinav Roy
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.3.0
>
>
> Steps :
> =
> 1. Deploy an advanced zone setup with hyperv.
> 2. Create a VM.
> 3. upload a volume.
> 4. Attach the volume uploaded in step 3 to the VM created in step 2.
> Expected behaviour:
> =
> Attach volume should succeed.
> Observed behaviour:
> =
> Attach volume fails with :
> MS logs :
> --
> 013-12-31 16:18:14,644 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-7:ctx-e8c1f6eb) ===START=== 10.144.7.20 -- GET
> command=attachVolume&id=86c04ec1-d29e-404b-b9c6-a42db8b5afe6&virtualMachineId=51ba1f12-34a1-4108-968e-bbd9f6893545&response=json&sessionkey=Hy%2BMYL%2B00HT2HmcPy%2FMiDAr%2FQBw%3D&_=1388486725851
> 2013-12-31 16:18:14,660 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-7:ctx-e8c1f6eb ctx-687f028b) submit async job-239, details:
> AsyncJobVO {id:239, userId: 2, accountId: 2, instanceType: Volume,
> instanceId: 55, cmd:
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdInfo:
> {"response":"json","id":"86c04ec1-d29e-404b-b9c6-a42db8b5afe6","sessionkey":"Hy+MYL+00HT2HmcPy/MiDAr/QBw\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"51ba1f12-34a1-4108-968e-bbd9f6893545","httpmethod":"GET","_":"1388486725851","ctxAccountId":"2","ctxStartEventId":"672"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-31 16:18:14,660 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-7:ctx-e8c1f6eb ctx-687f028b) ===END=== 10.144.7.20 -- GET
> command=attachVolume&id=86c04ec1-d29e-404b-b9c6-a42db8b5afe6&virtualMachineId=51ba1f12-34a1-4108-968e-bbd9f6893545&response=json&sessionkey=Hy%2BMYL%2B00HT2HmcPy%2FMiDAr%2FQBw%3D&_=1388486725851
> 2013-12-31 16:18:14,661 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-35:ctx-4fc638a9) Add job-239 into job monitoring
> 2013-12-31 16:18:14,662 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-35:ctx-4fc638a9) Executing AsyncJobVO {id:239, userId: 2,
> accountId: 2, instanceType: Volume, instanceId: 55, cmd:
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdInfo:
> {"response":"json","id":"86c04ec1-d29e-404b-b9c6-a42db8b5afe6","sessionkey":"Hy+MYL+00HT2HmcPy/MiDAr/QBw\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"51ba1f12-34a1-4108-968e-bbd9f6893545","httpmethod":"GET","_":"1388486725851","ctxAccountId":"2","ctxStartEventId":"672"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) LocalStoragePoolAllocator trying
> to find storage pool to fit the vm
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) ClusterScopeStoragePoolAllocator
> looking for storage pool
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) Looking for pools in dc: 2 pod:2
> cluster:2
> 2013-12-31 16:18:14,691 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) Checking if storage pool is
> suitable, name: null ,poolId: 4
> 2013-12-31 16:18:14,696 DE
[jira] [Assigned] (CLOUDSTACK-5752) Persistent network fails to implement
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty reassigned CLOUDSTACK-5752: -- Assignee: Kelven Yang (was: Likitha Shetty) As part of Persistent network creation, while the Router VM is being started during the network implementation, an NPE is thrown. NPE is thrown at VirtualMachineManagerImpl->advanceStart() line 743 because the current AsyncJobExecutionContext is null. When i disabled vmsync the issue was not observed and persistent network creation was successful. Kelven, could you please take a look at this bug? > Persistent network fails to implement > -- > > Key: CLOUDSTACK-5752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5752 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 > Environment: Advanced zone, any hypervisor >Reporter: Sowmya Krishnan >Assignee: Kelven Yang >Priority: Blocker > Fix For: 4.3.0 > > Attachments: ms.log > > > Latest build fails to implement a persistent network. > Steps: > Create isolated network offering with persistent = true > Launch a network with this offering. > Logs simply say that it fails to implement the network and router fails to > launch and throws an NPE: > 2014-01-03 14:02:36,344 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Starting router > VM[DomainRouter|r-34-VM] > 2014-01-03 14:02:36,344 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Cleaning up because we're unable > to implement the network Ntwk[219|Guest|22] > 2014-01-03 14:02:36,349 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Lock is acquired for network > Ntwk[219|Guest|22] as a part of network shutdown > 2014-01-03 14:02:36,355 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 port forwarding rules > for network id=219 as a part of shutdownNetworkRu > les > 2014-01-03 14:02:36,355 DEBUG [c.c.n.f.FirewallManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to > the network elements > 2014-01-03 14:02:36,356 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 static nat rules for > network id=219 as a part of shutdownNetworkRules > 2014-01-03 14:02:36,356 DEBUG [c.c.n.f.FirewallManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to > the network elements > 2014-01-03 14:02:36,357 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Revoking 0 Public load balancing > rules for network id=219 > ... > ... > 2014-01-03 14:02:36,383 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Sending network shutdown to > VirtualRouter > 2014-01-03 14:02:36,384 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Stopping router > VM[DomainRouter|r-34-VM] > 2014-01-03 14:02:36,384 WARN [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Unable to complete shutdown of > the network elements due to element: VirtualRouter > java.lang.NullPointerException > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1268) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2702) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProx
[jira] [Closed] (CLOUDSTACK-5714) [upgrade]getting blank console;failed to destroy CPVM in upgraded setup ;Unable to send due to java.lang.ArrayIndexOutOfBoundsException: 0
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra closed CLOUDSTACK-5714.
-
closing it, will open a new ticket for console proxy issue
> [upgrade]getting blank console;failed to destroy CPVM in upgraded setup
> ;Unable to send due to java.lang.ArrayIndexOutOfBoundsException: 0
> --
>
> Key: CLOUDSTACK-5714
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5714
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: hyp:xen6.2
>Reporter: prashant kumar mishra
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: Logs_Db.rar, screenshot-1.jpg
>
>
> STEPS TO REPRODUCE
> =
> 1-prepare a CS setup with ACS4.2+xen server
> 2-register 64 bit template and upgrade it to 4.3
> 3-run the
> " nohup cloudstack-sysvmadm -d -u cloud -p password
> -s > sysvm.log 2>&1 &"
> EXPECTED
> ==
> system vm should be successfully stopped and started
> ACTUAL
> ==
> CPVM failed to start
> Tried to destroy CPVM manually
>
> ran in this "Fail to destroy system vm" but actually cpvm got destroyed
> ,after new CPVM came up , whenever i am trying to access console of any vm i
> am getting blank console (please check the screenshot).
> LOG
> ===
> [root@rh63 CloudPlatform-4.3-1011-rhel6.3]# nohup cloudstack-sysvmadm -d
> 10.147.38.206 -u cloud -p password -s > sysvm.log 2>&1 &
> [1] 28994
> [root@rh63 CloudPlatform-4.3-1011-rhel6.3]# tail -f sysvm.log
> nohup: ignoring input
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
> Stopping and starting 1 console proxy vm(s)...
> ERROR: Failed to start console proxy vm with id 2
> Done stopping and starting console proxy vm(s) .
> LOG
>
> 014-01-02 09:27:54,583 DEBUG [c.c.a.t.Request] (Job-Executor-18:ctx-48b44e7f
> ctx-4c2c4411) Seq 1-1441792111: Executing: { Cmd , MgmtId: 7145449848920,
> via: 1(Rack1Pod1Host7), Ver: v1, Flags: 100011, [] }
> 2014-01-02 09:27:54,583 WARN [c.c.a.m.AgentAttache]
> (Job-Executor-18:ctx-48b44e7f ctx-4c2c4411) Seq 1-1441792111: Unable to send
> due to
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:100)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:374)
> at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:398)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
> at
> com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:497)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:448)
> at
> com.cloud.vm.VirtualMachineManagerImpl.expunge(VirtualMachineManagerImpl.java:437)
> at
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.destroyProxy(ConsoleProxyManagerImpl.java:1162)
> at
> com.cloud.server.ManagementServerImpl.destroyConsoleProxy(ManagementServerImpl.java:2155)
> at
> com.cloud.server.ManagementServerImpl.destroySystemVM(ManagementServerImpl.java:3220)
> at
> com.cloud.server.ManagementServerImpl.destroySystemVM(ManagementServerImpl.java:609)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvoca
[jira] [Updated] (CLOUDSTACK-5314) [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in the resource count table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5314: -- Labels: (was: hyper-V,) > [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in > the resource count table > - > > Key: CLOUDSTACK-5314 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5314 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Management Server >Affects Versions: 4.3.0 > Environment: Hyper-V >Reporter: Abhinav Roy >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.3.0 > > > Description : > > The resource count value for primary storage and volumes in the > cloud.resource_count table is shown as negative (-ve) > mysql> select * from resource_count; > +++---+---+---+ > | id | account_id | domain_id | type | count | > +++---+---+---+ > | 1 | NULL | 1 | cpu | 6 | > | 2 | NULL | 1 | memory| 3072 | > | 3 | NULL | 1 | primary_storage | -103079215104 | > | 4 | NULL | 1 | secondary_storage | 56863775232 | > | 9 | NULL | 1 | user_vm | 6 | > | 10 | NULL | 1 | public_ip | 2 | > | 11 | NULL | 1 | volume|-5 | > | 12 | NULL | 1 | snapshot | 0 | > | 13 | NULL | 1 | template | 4 | > | 14 | NULL | 1 | project | 0 | > | 15 | NULL | 1 | network | 1 | > | 16 | NULL | 1 | vpc | 0 | > | 17 | 1 | NULL | user_vm | 0 | > | 18 | 1 | NULL | public_ip | 0 | > | 19 | 1 | NULL | volume| 0 | > | 20 | 1 | NULL | snapshot | 0 | > | 21 | 1 | NULL | template | 0 | > | 22 | 1 | NULL | project | 0 | > | 23 | 1 | NULL | network | 0 | > | 24 | 1 | NULL | vpc | 0 | > | 25 | 1 | NULL | cpu | 0 | > | 26 | 1 | NULL | memory| 0 | > | 27 | 1 | NULL | primary_storage | 0 | > | 28 | 1 | NULL | secondary_storage | 0 | > | 29 | 2 | NULL | user_vm | 6 | > | 30 | 2 | NULL | public_ip | 2 | > | 31 | 2 | NULL | volume|-5 | > | 32 | 2 | NULL | snapshot | 0 | > | 33 | 2 | NULL | template | 4 | > | 34 | 2 | NULL | project | 0 | > | 35 | 2 | NULL | network | 1 | > | 36 | 2 | NULL | vpc | 0 | > | 37 | 2 | NULL | cpu | 6 | > | 38 | 2 | NULL | memory| 3072 | > | 39 | 2 | NULL | primary_storage | -103079215104 | > | 40 | 2 | NULL | secondary_storage | 163220937216 | > +++---+---+---+ > 36 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5691) [Hyper-V] Attaching an uploaded volume to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861456#comment-13861456
]
ASF subversion and git services commented on CLOUDSTACK-5691:
-
Commit e59420c5146387977530b4720e6ec7dd7a83703c in branch refs/heads/master
from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e59420c ]
CLOUDSTACK-5691: Fix for attaching an uploaded volume to instance running
on hyperv. There were multiple issues here. Upload volume was actually
failing because the post download check for vhd on the cifs share was
unsuccessful. Also the agent code wasn't parsing the volume path correctly.
Fixed it too.
> [Hyper-V] Attaching an uploaded volume to a VM is failing
> -
>
> Key: CLOUDSTACK-5691
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5691
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Management Server
>Affects Versions: 4.3.0
> Environment: hyperv, 4.3, CIFS as primary and secondary storage
>Reporter: Abhinav Roy
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.3.0
>
>
> Steps :
> =
> 1. Deploy an advanced zone setup with hyperv.
> 2. Create a VM.
> 3. upload a volume.
> 4. Attach the volume uploaded in step 3 to the VM created in step 2.
> Expected behaviour:
> =
> Attach volume should succeed.
> Observed behaviour:
> =
> Attach volume fails with :
> MS logs :
> --
> 013-12-31 16:18:14,644 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-7:ctx-e8c1f6eb) ===START=== 10.144.7.20 -- GET
> command=attachVolume&id=86c04ec1-d29e-404b-b9c6-a42db8b5afe6&virtualMachineId=51ba1f12-34a1-4108-968e-bbd9f6893545&response=json&sessionkey=Hy%2BMYL%2B00HT2HmcPy%2FMiDAr%2FQBw%3D&_=1388486725851
> 2013-12-31 16:18:14,660 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-7:ctx-e8c1f6eb ctx-687f028b) submit async job-239, details:
> AsyncJobVO {id:239, userId: 2, accountId: 2, instanceType: Volume,
> instanceId: 55, cmd:
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdInfo:
> {"response":"json","id":"86c04ec1-d29e-404b-b9c6-a42db8b5afe6","sessionkey":"Hy+MYL+00HT2HmcPy/MiDAr/QBw\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"51ba1f12-34a1-4108-968e-bbd9f6893545","httpmethod":"GET","_":"1388486725851","ctxAccountId":"2","ctxStartEventId":"672"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-31 16:18:14,660 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-7:ctx-e8c1f6eb ctx-687f028b) ===END=== 10.144.7.20 -- GET
> command=attachVolume&id=86c04ec1-d29e-404b-b9c6-a42db8b5afe6&virtualMachineId=51ba1f12-34a1-4108-968e-bbd9f6893545&response=json&sessionkey=Hy%2BMYL%2B00HT2HmcPy%2FMiDAr%2FQBw%3D&_=1388486725851
> 2013-12-31 16:18:14,661 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-35:ctx-4fc638a9) Add job-239 into job monitoring
> 2013-12-31 16:18:14,662 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-35:ctx-4fc638a9) Executing AsyncJobVO {id:239, userId: 2,
> accountId: 2, instanceType: Volume, instanceId: 55, cmd:
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdInfo:
> {"response":"json","id":"86c04ec1-d29e-404b-b9c6-a42db8b5afe6","sessionkey":"Hy+MYL+00HT2HmcPy/MiDAr/QBw\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"51ba1f12-34a1-4108-968e-bbd9f6893545","httpmethod":"GET","_":"1388486725851","ctxAccountId":"2","ctxStartEventId":"672"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) LocalStoragePoolAllocator trying
> to find storage pool to fit the vm
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) ClusterScopeStoragePoolAllocator
> looking for storage pool
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) Looking for pools in dc: 2 pod:2
> cluster:2
> 2013-12-31 16:18:14,691 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) Checking if storage pool is
> suitable, name: null ,poolId: 4
> 2013-12-31 16:18:14,696
[jira] [Updated] (CLOUDSTACK-5734) Console not working for SSVM CPVM VR guest VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-5734: --- Summary: Console not working for SSVM CPVM VR guest VMs (was: [vmware] Vcenter 5.5 host ESXi 5.5 Console not working for SSVM CPVM VR guest VMs) Updated the summary because this issue is not specific to a VMware deployment. > Console not working for SSVM CPVM VR guest VMs > -- > > Key: CLOUDSTACK-5734 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5734 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: MS4.3 release 1/2/14 > vcenter 5.5 host1 ESXi 5.5 host2 ESXi 5.5 >Reporter: angeline shen >Priority: Critical > Fix For: 4.3.0 > > Attachments: management-server(1).log.gz, vm43.png > > > 1. advance zone. Create VPC, VPC network, create VMs > 2. create windows 2008R2 iso -based VM > 3. Open console to SSVM CPVMVRguest VMs - blank -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5753) [Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of consoleproxy.loadscan.interval which is 10sec
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshul Gangwar reassigned CLOUDSTACK-5753:
--
Assignee: Anshul Gangwar
> [Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of
> consoleproxy.loadscan.interval which is 10sec
> -
>
> Key: CLOUDSTACK-5753
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5753
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller
>Affects Versions: 4.3.0
> Environment: Latest build from 4.3branch with commit:
> 95b6a7b96dab1c77e25987d6fe6003b4447281f1
>Reporter: Sanjeev N
>Assignee: Anshul Gangwar
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.3.0
>
>
> [Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of
> consoleproxy.loadscan.interval which is 10sec
> Steps to reproduce:
> ===
> 1.Bring up CS in advanced zone with Hyper-v cluster
> 2.Wait for the system vms to come up.
> 3.Deploy one guest vm with default centos template
> 4.Observe MS log for events related to ConsoleProxyLoadReportCommand
> Result:
> ==
> ConsoleProxyLoadReportCommand is getting executed for every 5 sec. However
> the default value for consoleproxy.loadscan.interval is set to 10sec. So the
> command should be exected at 10sec interval.
> Few events grepped for the above command:
> [root@RIAK-57 ~]# tail -f
> /var/log/cloudstack/management/management-server.log | grep
> ConsoleProxyLoadReportCommand
> 2014-01-03 12:56:10,881 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-8:null) SeqA 4-11496: Processing Seq 4-11496: { Cmd ,
> MgmtId: -1, via: 4, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2014-01-03 12:56:15,885 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-5:null) SeqA 4-11497: Processing Seq 4-11497: { Cmd ,
> MgmtId: -1, via: 4, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2014-01-03 12:56:20,889 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-12:null) SeqA 4-11498: Processing Seq 4-11498: { Cmd ,
> MgmtId: -1, via: 4, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2014-01-03 12:56:25,933 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 4-11500: Processing Seq 4-11500: { Cmd ,
> MgmtId: -1, via: 4, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2014-01-03 12:56:30,896 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-10:null) SeqA 4-11501: Processing Seq 4-11501: { Cmd ,
> MgmtId: -1, via: 4, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5761) [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up extra CPVMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar reassigned CLOUDSTACK-5761: -- Assignee: Anshul Gangwar > [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up > extra CPVMs > -- > > Key: CLOUDSTACK-5761 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5761 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Latest build from 4.3branch with commit : > 95b6a7b96dab1c77e25987d6fe6003b4447281f1 >Reporter: Sanjeev N >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: management-server.rar > > > [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up > extra CPVMs > Steps to reproduce: > > 1.Bring up CS in advanced zone with Hyper-v cluster > 2.Wait for the system vms to comeup > 3.Deploy few guest vms > 4.Open console view sessions for two guest vms > 5. Set consoleproxy.session.max=2 and restart MS > 6.Open console view for another vm > Result: > == > Immediately continuous CPVMs spin up strated one after the other until the > resources were available even though there were only 3 console view sessions > opened. > mysql> select id,name,instance_name,state from vm_instance where name like > "v%VM"; > ++-+---+-+ > | id | name| instance_name | state | > ++-+---+-+ > | 2 | v-2-VM | v-2-VM| Running | > | 13 | v-13-VM | v-13-VM | Running | > | 14 | v-14-VM | v-14-VM | Running | > | 15 | v-15-VM | v-15-VM | Running | > | 16 | v-16-VM | v-16-VM | Running | > ++-+---+-+ > 5 rows in set (0.00 sec) > v-2-VM was the initial vm before restarting MS. Immediately after MS restart > all the remaining cpvms spinned up. > Observations: > === > I closed all the console view sessions and destroyed all the cpvms except the > v-2-VM. Again CS started creating CPVMs even though there were no console > view sessions opened. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5716) [Hyper-v] Can't type Special character in console view
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshul Gangwar updated CLOUDSTACK-5716:
---
Status: Ready To Review (was: In Progress)
> [Hyper-v] Can't type Special character in console view
> --
>
> Key: CLOUDSTACK-5716
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5716
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller
>Affects Versions: 4.3.0
> Environment: Latest build from 4.3 branch with
> commit:95b6a7b96dab1c77e25987d6fe6003b4447281f1
>Reporter: Sanjeev N
>Assignee: Anshul Gangwar
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.3.0
>
>
> [Hyper-v] Can't type Special character in console view
> Steps to Reproduce:
>
> 1.Bring up CS with Hyperv cluster
> 2.Wait for the CPVM to come up
> 3.Deploy guest vm with default cent os template
> 4.Try accessing the system/guest vms console from CS
> 5.Login and try to type special characters
> Result:
> =
> Can't type the special characters(Shift+(1-9,0)) and also other characters
> like below:
> ~
> `
> {
> }
> |
> <
> >
> ?
> :
> "
> +
> _
> -
> =
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5764) "java.lang.IllegalArgumentException" in CPVM agent logs when accessing the console of any VM.Blank console for all VMs.
manasaveloori created CLOUDSTACK-5764:
-
Summary: "java.lang.IllegalArgumentException" in CPVM agent logs
when accessing the console of any VM.Blank console for all VMs.
Key: CLOUDSTACK-5764
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5764
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.3.0
Reporter: manasaveloori
Priority: Critical
Fix For: 4.3.0
Attachments: cloud.log, management-server.log
Steps:
1. Deploy CS 4.3 with KVM HV.
2. view the CPVM/SSVM/userVM console.
Observing blank console.
In CPVM agent logs observing the following exception when trying to access the
console.
2014-01-03 11:30:47,362 DEBUG [cloud.agent.Agent] (Agent-Handler-4:null)
Received response: Seq 4-44: { Ans: , MgmtId: 7494415941730, via: 4, Ver: v1,
Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2014-01-03 11:30:49,769 WARN [cloud.consoleproxy.ConsoleProxyAjaxHandler]
(Thread-14:null) Exception,
java.lang.IllegalArgumentException
at
com.cloud.consoleproxy.ConsoleProxyAjaxHandler.doHandle(ConsoleProxyAjaxHandler.java:96)
at
com.cloud.consoleproxy.ConsoleProxyAjaxHandler.handle(ConsoleProxyAjaxHandler.java:49)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:83)
at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:83)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:86)
at
sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:598)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:83)
at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:568)
at java.lang.Thread.run(Thread.java:679)
2014-01-03 11:30:52,352 DEBUG [cloud.consoleproxy.ConsoleProxyGCThread]
(Console Proxy GC Thread:null) connMap={}
2014-01-03 11:30:52,353 DEBUG [resource.consoleproxy.ConsoleProxyResource]
(Console Proxy GC Thread:null) Report proxy load info, proxy : 5, load: {
"connections": []
}
Attaching the CPVM logs and MS logs
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5716) [Hyper-v] Can't type Special character in console view
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861458#comment-13861458
]
Anshul Gangwar commented on CLOUDSTACK-5716:
submitted the patch for review
> [Hyper-v] Can't type Special character in console view
> --
>
> Key: CLOUDSTACK-5716
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5716
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller
>Affects Versions: 4.3.0
> Environment: Latest build from 4.3 branch with
> commit:95b6a7b96dab1c77e25987d6fe6003b4447281f1
>Reporter: Sanjeev N
>Assignee: Anshul Gangwar
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.3.0
>
>
> [Hyper-v] Can't type Special character in console view
> Steps to Reproduce:
>
> 1.Bring up CS with Hyperv cluster
> 2.Wait for the CPVM to come up
> 3.Deploy guest vm with default cent os template
> 4.Try accessing the system/guest vms console from CS
> 5.Login and try to type special characters
> Result:
> =
> Can't type the special characters(Shift+(1-9,0)) and also other characters
> like below:
> ~
> `
> {
> }
> |
> <
> >
> ?
> :
> "
> +
> _
> -
> =
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5764) "java.lang.IllegalArgumentException" in CPVM agent logs when accessing the console of any VM.Blank console for all VMs.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori updated CLOUDSTACK-5764:
--
Attachment: cloud.log
management-server.log
> "java.lang.IllegalArgumentException" in CPVM agent logs when accessing the
> console of any VM.Blank console for all VMs.
> ---
>
> Key: CLOUDSTACK-5764
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5764
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
>Reporter: manasaveloori
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: cloud.log, management-server.log
>
>
> Steps:
> 1. Deploy CS 4.3 with KVM HV.
> 2. view the CPVM/SSVM/userVM console.
> Observing blank console.
> In CPVM agent logs observing the following exception when trying to access
> the console.
> 2014-01-03 11:30:47,362 DEBUG [cloud.agent.Agent] (Agent-Handler-4:null)
> Received response: Seq 4-44: { Ans: , MgmtId: 7494415941730, via: 4, Ver:
> v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2014-01-03 11:30:49,769 WARN [cloud.consoleproxy.ConsoleProxyAjaxHandler]
> (Thread-14:null) Exception,
> java.lang.IllegalArgumentException
> at
> com.cloud.consoleproxy.ConsoleProxyAjaxHandler.doHandle(ConsoleProxyAjaxHandler.java:96)
> at
> com.cloud.consoleproxy.ConsoleProxyAjaxHandler.handle(ConsoleProxyAjaxHandler.java:49)
> at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:83)
> at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:83)
> at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:86)
> at
> sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:598)
> at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:83)
> at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:568)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-03 11:30:52,352 DEBUG [cloud.consoleproxy.ConsoleProxyGCThread]
> (Console Proxy GC Thread:null) connMap={}
> 2014-01-03 11:30:52,353 DEBUG [resource.consoleproxy.ConsoleProxyResource]
> (Console Proxy GC Thread:null) Report proxy load info, proxy : 5, load: {
> "connections": []
> }
> Attaching the CPVM logs and MS logs
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5691) [Hyper-V] Attaching an uploaded volume to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5691.
---
Resolution: Fixed
> [Hyper-V] Attaching an uploaded volume to a VM is failing
> -
>
> Key: CLOUDSTACK-5691
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5691
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Management Server
>Affects Versions: 4.3.0
> Environment: hyperv, 4.3, CIFS as primary and secondary storage
>Reporter: Abhinav Roy
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.3.0
>
>
> Steps :
> =
> 1. Deploy an advanced zone setup with hyperv.
> 2. Create a VM.
> 3. upload a volume.
> 4. Attach the volume uploaded in step 3 to the VM created in step 2.
> Expected behaviour:
> =
> Attach volume should succeed.
> Observed behaviour:
> =
> Attach volume fails with :
> MS logs :
> --
> 013-12-31 16:18:14,644 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-7:ctx-e8c1f6eb) ===START=== 10.144.7.20 -- GET
> command=attachVolume&id=86c04ec1-d29e-404b-b9c6-a42db8b5afe6&virtualMachineId=51ba1f12-34a1-4108-968e-bbd9f6893545&response=json&sessionkey=Hy%2BMYL%2B00HT2HmcPy%2FMiDAr%2FQBw%3D&_=1388486725851
> 2013-12-31 16:18:14,660 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-7:ctx-e8c1f6eb ctx-687f028b) submit async job-239, details:
> AsyncJobVO {id:239, userId: 2, accountId: 2, instanceType: Volume,
> instanceId: 55, cmd:
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdInfo:
> {"response":"json","id":"86c04ec1-d29e-404b-b9c6-a42db8b5afe6","sessionkey":"Hy+MYL+00HT2HmcPy/MiDAr/QBw\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"51ba1f12-34a1-4108-968e-bbd9f6893545","httpmethod":"GET","_":"1388486725851","ctxAccountId":"2","ctxStartEventId":"672"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-31 16:18:14,660 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-7:ctx-e8c1f6eb ctx-687f028b) ===END=== 10.144.7.20 -- GET
> command=attachVolume&id=86c04ec1-d29e-404b-b9c6-a42db8b5afe6&virtualMachineId=51ba1f12-34a1-4108-968e-bbd9f6893545&response=json&sessionkey=Hy%2BMYL%2B00HT2HmcPy%2FMiDAr%2FQBw%3D&_=1388486725851
> 2013-12-31 16:18:14,661 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-35:ctx-4fc638a9) Add job-239 into job monitoring
> 2013-12-31 16:18:14,662 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-35:ctx-4fc638a9) Executing AsyncJobVO {id:239, userId: 2,
> accountId: 2, instanceType: Volume, instanceId: 55, cmd:
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdInfo:
> {"response":"json","id":"86c04ec1-d29e-404b-b9c6-a42db8b5afe6","sessionkey":"Hy+MYL+00HT2HmcPy/MiDAr/QBw\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"51ba1f12-34a1-4108-968e-bbd9f6893545","httpmethod":"GET","_":"1388486725851","ctxAccountId":"2","ctxStartEventId":"672"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) LocalStoragePoolAllocator trying
> to find storage pool to fit the vm
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) ClusterScopeStoragePoolAllocator
> looking for storage pool
> 2013-12-31 16:18:14,688 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) Looking for pools in dc: 2 pod:2
> cluster:2
> 2013-12-31 16:18:14,691 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) Checking if storage pool is
> suitable, name: null ,poolId: 4
> 2013-12-31 16:18:14,696 DEBUG [c.c.s.StorageManagerImpl]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) Checking pool: 4 for volume
> allocation [Vol[55|vm=null|DATADISK]], maxSize : 1997545660416,
> totalAllocatedSize : 89599652352, askingSize : 0, allocated disable
> threshold: 0.85
> 2013-12-31 16:18:14,696 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Job-Executor-35:ctx-4fc638a9 ctx-687f028b) ClusterScopeStoragePoolAllocator
> returning 1 suitable storage pools
> 2013-12-31 16:18:14,697 DEBUG [o.a.c.e.o.VolumeOrchestrator]
> (Job-Executor
[jira] [Updated] (CLOUDSTACK-5314) Negative (-ve) values for primary storage and volumes are shown in the resource count table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi updated CLOUDSTACK-5314: Summary: Negative (-ve) values for primary storage and volumes are shown in the resource count table (was: [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in the resource count table) > Negative (-ve) values for primary storage and volumes are shown in the > resource count table > --- > > Key: CLOUDSTACK-5314 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5314 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Management Server >Affects Versions: 4.3.0 > Environment: Hyper-V >Reporter: Abhinav Roy >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.3.0 > > > Description : > > The resource count value for primary storage and volumes in the > cloud.resource_count table is shown as negative (-ve) > mysql> select * from resource_count; > +++---+---+---+ > | id | account_id | domain_id | type | count | > +++---+---+---+ > | 1 | NULL | 1 | cpu | 6 | > | 2 | NULL | 1 | memory| 3072 | > | 3 | NULL | 1 | primary_storage | -103079215104 | > | 4 | NULL | 1 | secondary_storage | 56863775232 | > | 9 | NULL | 1 | user_vm | 6 | > | 10 | NULL | 1 | public_ip | 2 | > | 11 | NULL | 1 | volume|-5 | > | 12 | NULL | 1 | snapshot | 0 | > | 13 | NULL | 1 | template | 4 | > | 14 | NULL | 1 | project | 0 | > | 15 | NULL | 1 | network | 1 | > | 16 | NULL | 1 | vpc | 0 | > | 17 | 1 | NULL | user_vm | 0 | > | 18 | 1 | NULL | public_ip | 0 | > | 19 | 1 | NULL | volume| 0 | > | 20 | 1 | NULL | snapshot | 0 | > | 21 | 1 | NULL | template | 0 | > | 22 | 1 | NULL | project | 0 | > | 23 | 1 | NULL | network | 0 | > | 24 | 1 | NULL | vpc | 0 | > | 25 | 1 | NULL | cpu | 0 | > | 26 | 1 | NULL | memory| 0 | > | 27 | 1 | NULL | primary_storage | 0 | > | 28 | 1 | NULL | secondary_storage | 0 | > | 29 | 2 | NULL | user_vm | 6 | > | 30 | 2 | NULL | public_ip | 2 | > | 31 | 2 | NULL | volume|-5 | > | 32 | 2 | NULL | snapshot | 0 | > | 33 | 2 | NULL | template | 4 | > | 34 | 2 | NULL | project | 0 | > | 35 | 2 | NULL | network | 1 | > | 36 | 2 | NULL | vpc | 0 | > | 37 | 2 | NULL | cpu | 6 | > | 38 | 2 | NULL | memory| 3072 | > | 39 | 2 | NULL | primary_storage | -103079215104 | > | 40 | 2 | NULL | secondary_storage | 163220937216 | > +++---+---+---+ > 36 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5658) [Hyper-v] Template created from root volume has size set to NULL hence failed to deploy VM from that template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861462#comment-13861462 ] ASF subversion and git services commented on CLOUDSTACK-5658: - Commit cd43921fda02a391ae461095ae95893c7a2c4817 in branch refs/heads/master from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cd43921 ] CLOUDSTACK-5658 CLOUDSTACK-5563 deploying VM from template created from volumes fails > [Hyper-v] Template created from root volume has size set to NULL hence failed > to deploy VM from that template > - > > Key: CLOUDSTACK-5658 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5658 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Template >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 3282d19cca4afe65d049c2db9b63f0ef528e81e1 > Storage: SMB for both primary and secondary > Hypervisor: Hyper-v >Reporter: Sanjeev N >Assignee: Rajesh Battala >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: cloud.dmp, management-server.rar > > > [Hyper-v] Template created from root volume has size set to NULL hence failed > to deploy VM from that template > Steps to Reproduce: > == > 1.Bring up CS in advanced zone with Hyper-v host using SMB shares for primary > and secondary > 2.Deploy one or more guest vms with the default cent of template > 3.Stop the vm > 4.Create template from the root disk of the vm > Expected Result: > == > Template creation should be successful and size of the template should be > equal to the root volume size > Actual Result: > > Template creation succeeded however template size was set to NULL > Impact: > == > 1.VM creation failed at allocating disks for VM with NPE > 2.Since usage is NULL TEMPLATE_CREATE event got generated with size set to 0 > which will have huge impact on the billing. > Following is the log snippet while deploying a vm with the template: > 2013-12-27 16:02:00,874 DEBUG [c.c.a.ApiServlet] > (catalina-exec-21:ctx-1b6ca1b9) ===START=== 10.146.0.134 -- GET > command=deployVirtualMachine&response=json&sessionkey=0Is7NdFczbwiApJPUUVO8LG1Lj4%3D&zoneid=20042051-b332-497b-a0cd-57078d9f423a&templateid=c0d9df5d-e782-47b8-8479-d39f8a69864c&hypervisor=Hyperv&serviceofferingid=d2b5b96b-b042-405e-aafb-be7ea95ab1be&networkids=63660749-0d6b-457a-b6c2-1d80a9ae2b70&displayname=ex1&name=ex1&_=1388140306272 > 2013-12-27 16:02:00,881 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) InfrastructureEntity name > is:com.cloud.offering.ServiceOffering > 2013-12-27 16:02:00,884 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) ControlledEntity name > is:com.cloud.template.VirtualMachineTemplate > 2013-12-27 16:02:00,886 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) ControlledEntity name > is:com.cloud.network.Network > 2013-12-27 16:02:00,897 DEBUG [c.c.n.NetworkModelImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Service SecurityGroup is not > supported in the network id=204 > 2013-12-27 16:02:00,971 DEBUG [c.c.v.UserVmManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating in the DB for vm > 2013-12-27 16:02:00,979 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating entries for VM: > VM[User|ex1] > 2013-12-27 16:02:00,980 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating nics for VM[User|ex1] > 2013-12-27 16:02:00,980 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating nic for vm > VM[User|ex1] in network Ntwk[204|Guest|8] with requested profile > NicProfile[0-0-null-null-null > 2013-12-27 16:02:01,053 DEBUG [c.c.n.NetworkModelImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Service SecurityGroup is not > supported in the network id=204 > 2013-12-27 16:02:01,054 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating disks for VM[User|ex1] > 2013-12-27 16:02:01,057 DEBUG [c.c.u.d.T.Transaction] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Rolling back the transaction: > Time = 89 Name = catalina-exec-21; called by > -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-VirtualMachineManagerImpl.allocate:386-CloudOrchestrator.createVirtualMachine:217-UserVmManagerImpl$3.doInTra
[jira] [Commented] (CLOUDSTACK-5608) HyperV Builtin and System vm template entries missing in 4.3 upgrade setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861464#comment-13861464 ] ASF subversion and git services commented on CLOUDSTACK-5608: - Commit 28fcd362907f80505860b72cef523b1d19fdda1f in branch refs/heads/master from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=28fcd36 ] CLOUDSTACK-5608: HyperV Builtin and System vm template entries missing/need to update in 4.3 upgrade setup > HyperV Builtin and System vm template entries missing in 4.3 upgrade setup > -- > > Key: CLOUDSTACK-5608 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5608 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.2.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala >Priority: Critical > Fix For: 4.3.0 > > > On upgrade to 4.3 from any version, > 1) Hyperv default builtin template is missing > 2) Hyperv System vm template entry is missing or having invalid URL. > Needs to be fixed upon upgrade to 4.3 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5563) path field is set to null in volumes table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861463#comment-13861463 ] ASF subversion and git services commented on CLOUDSTACK-5563: - Commit cd43921fda02a391ae461095ae95893c7a2c4817 in branch refs/heads/master from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cd43921 ] CLOUDSTACK-5658 CLOUDSTACK-5563 deploying VM from template created from volumes fails > path field is set to null in volumes table > --- > > Key: CLOUDSTACK-5563 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5563 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, Volumes >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 with commit > :197ef921f7b3c80998359f376fe045b13558633c >Reporter: Sanjeev N >Assignee: Rajesh Battala > Labels: hyper-V, > Fix For: 4.3.0 > > > path field is set to null in volumes table > Steps to Reproduce: > = > 1.Bring up CS in advanced zone with hyper-v host using CIFS for both primary > and secondary storage > 2.Deploy a vm using default cent-os template > 3.Check root volume details in volumes table. > Following is the volume details from cloud DB: > mysql> select * from volumes where instance_id=6\G; > *** 1. row *** > id: 8 > account_id: 2 > domain_id: 1 >pool_id: 1 > last_pool_id: NULL >instance_id: 6 > device_id: 0 > name: ROOT-6 > uuid: 70c71522-16ec-4329-a91d-c6006534078d > size: 5368709120 > folder: NULL > path: NULL > pod_id: NULL > data_center_id: 1 > iscsi_name: NULL >host_ip: NULL >volume_type: ROOT > pool_type: NULL > disk_offering_id: 1 >template_id: 6 > first_snapshot_backup_uuid: NULL >recreatable: 0 >created: 2013-12-19 10:04:33 > attached: NULL >updated: 2013-12-19 10:04:38 >removed: NULL > state: Ready > chain_info: NULL > update_count: 2 > disk_type: NULL > vm_snapshot_chain_size: NULL > iso_id: NULL > display_volume: 1 > format: NULL > min_iops: NULL > max_iops: NULL > hv_ss_reserve: NULL > 1 row in set (0.00 sec) > ERROR: > No query specified -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5563) path field is set to null in volumes table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-5563. Resolution: Fixed > path field is set to null in volumes table > --- > > Key: CLOUDSTACK-5563 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5563 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, Volumes >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 with commit > :197ef921f7b3c80998359f376fe045b13558633c >Reporter: Sanjeev N >Assignee: Rajesh Battala > Labels: hyper-V, > Fix For: 4.3.0 > > > path field is set to null in volumes table > Steps to Reproduce: > = > 1.Bring up CS in advanced zone with hyper-v host using CIFS for both primary > and secondary storage > 2.Deploy a vm using default cent-os template > 3.Check root volume details in volumes table. > Following is the volume details from cloud DB: > mysql> select * from volumes where instance_id=6\G; > *** 1. row *** > id: 8 > account_id: 2 > domain_id: 1 >pool_id: 1 > last_pool_id: NULL >instance_id: 6 > device_id: 0 > name: ROOT-6 > uuid: 70c71522-16ec-4329-a91d-c6006534078d > size: 5368709120 > folder: NULL > path: NULL > pod_id: NULL > data_center_id: 1 > iscsi_name: NULL >host_ip: NULL >volume_type: ROOT > pool_type: NULL > disk_offering_id: 1 >template_id: 6 > first_snapshot_backup_uuid: NULL >recreatable: 0 >created: 2013-12-19 10:04:33 > attached: NULL >updated: 2013-12-19 10:04:38 >removed: NULL > state: Ready > chain_info: NULL > update_count: 2 > disk_type: NULL > vm_snapshot_chain_size: NULL > iso_id: NULL > display_volume: 1 > format: NULL > min_iops: NULL > max_iops: NULL > hv_ss_reserve: NULL > 1 row in set (0.00 sec) > ERROR: > No query specified -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5658) [Hyper-v] Template created from root volume has size set to NULL hence failed to deploy VM from that template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-5658. Resolution: Fixed > [Hyper-v] Template created from root volume has size set to NULL hence failed > to deploy VM from that template > - > > Key: CLOUDSTACK-5658 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5658 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Template >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 branch with commit: > 3282d19cca4afe65d049c2db9b63f0ef528e81e1 > Storage: SMB for both primary and secondary > Hypervisor: Hyper-v >Reporter: Sanjeev N >Assignee: Rajesh Battala >Priority: Critical > Labels: hyper-V,, hyper-v, hyperv > Fix For: 4.3.0 > > Attachments: cloud.dmp, management-server.rar > > > [Hyper-v] Template created from root volume has size set to NULL hence failed > to deploy VM from that template > Steps to Reproduce: > == > 1.Bring up CS in advanced zone with Hyper-v host using SMB shares for primary > and secondary > 2.Deploy one or more guest vms with the default cent of template > 3.Stop the vm > 4.Create template from the root disk of the vm > Expected Result: > == > Template creation should be successful and size of the template should be > equal to the root volume size > Actual Result: > > Template creation succeeded however template size was set to NULL > Impact: > == > 1.VM creation failed at allocating disks for VM with NPE > 2.Since usage is NULL TEMPLATE_CREATE event got generated with size set to 0 > which will have huge impact on the billing. > Following is the log snippet while deploying a vm with the template: > 2013-12-27 16:02:00,874 DEBUG [c.c.a.ApiServlet] > (catalina-exec-21:ctx-1b6ca1b9) ===START=== 10.146.0.134 -- GET > command=deployVirtualMachine&response=json&sessionkey=0Is7NdFczbwiApJPUUVO8LG1Lj4%3D&zoneid=20042051-b332-497b-a0cd-57078d9f423a&templateid=c0d9df5d-e782-47b8-8479-d39f8a69864c&hypervisor=Hyperv&serviceofferingid=d2b5b96b-b042-405e-aafb-be7ea95ab1be&networkids=63660749-0d6b-457a-b6c2-1d80a9ae2b70&displayname=ex1&name=ex1&_=1388140306272 > 2013-12-27 16:02:00,881 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) InfrastructureEntity name > is:com.cloud.offering.ServiceOffering > 2013-12-27 16:02:00,884 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) ControlledEntity name > is:com.cloud.template.VirtualMachineTemplate > 2013-12-27 16:02:00,886 DEBUG [c.c.a.ApiDispatcher] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) ControlledEntity name > is:com.cloud.network.Network > 2013-12-27 16:02:00,897 DEBUG [c.c.n.NetworkModelImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Service SecurityGroup is not > supported in the network id=204 > 2013-12-27 16:02:00,971 DEBUG [c.c.v.UserVmManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating in the DB for vm > 2013-12-27 16:02:00,979 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating entries for VM: > VM[User|ex1] > 2013-12-27 16:02:00,980 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating nics for VM[User|ex1] > 2013-12-27 16:02:00,980 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating nic for vm > VM[User|ex1] in network Ntwk[204|Guest|8] with requested profile > NicProfile[0-0-null-null-null > 2013-12-27 16:02:01,053 DEBUG [c.c.n.NetworkModelImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Service SecurityGroup is not > supported in the network id=204 > 2013-12-27 16:02:01,054 DEBUG [c.c.v.VirtualMachineManagerImpl] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Allocating disks for VM[User|ex1] > 2013-12-27 16:02:01,057 DEBUG [c.c.u.d.T.Transaction] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) Rolling back the transaction: > Time = 89 Name = catalina-exec-21; called by > -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-VirtualMachineManagerImpl.allocate:386-CloudOrchestrator.createVirtualMachine:217-UserVmManagerImpl$3.doInTransaction:3055-UserVmManagerImpl$3.doInTransaction:2971-Transaction.execute:37-UserVmManagerImpl.commitUserVm:2971-UserVmManagerImpl.createVirtualMachine:2935-UserVmManagerImpl.createAdvancedVirtualMachine:2591 > 2013-12-27 16:02:01,157 ERROR [c.c.a.ApiServer] > (catalina-exec-21:ctx-1b6ca1b9 ctx-ab3dd031) unhandled exception
[jira] [Updated] (CLOUDSTACK-5614) [UI] improvements for Report Sockets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-5614: Summary: [UI] improvements for Report Sockets (was: UI improvements for Report Sockets) > [UI] improvements for Report Sockets > > > Key: CLOUDSTACK-5614 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5614 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Kiran Koneti > Fix For: 4.3.0 > > Attachments: InfraTab.jpg, Number_of_sockets.jpg > > > The below mentioned improvements are requested for the report sockets. > 1)UI Icon in the infrastructure tab. > The current implementation of the Infrastructure tab is attached as > screenshot InfraTab.jpg whcih shows that all the other tab links has some > image in the box related to it ,So please add some image to the sockets which > would make the UI look good. > 2)number of sockets in the Sockets tab. > The current implementation of number of sockets is attached as the screen > shot Number_of_sockets.jpg in which the number of sockets for all the hosts > is listed as 0 for the hosts which are not added and also not supported.in th > egiven screenshot you can see the number of hypervisor hosts are 2 and the > sockets number is 0.It is listed so because the number of sockets for the > hyper-V is not yet implemented.So the number of sockets should be either N/A > of just -(hyphen) for the hypervisors which we doesn't support. > 3)Seperate List should be maintained for Xenserver 6.2 version and versions > prior to that. > We support the Report sockets only for the Xen 6.2 version and not for the > versions prior to that.So we have to have 2 columns one for Xenserver 6.2 for > which we can list number of hosts and number of sockets and other one saying > just Xenserver where we report only the number of hosts and the number of > sockets should be either N/A or -(hyphen). > 4)Report the socket information in the Host information UI also. > When we navigate to the Infrastructure-->Hosts -->(hostname/IP) for the host > details we don't have a UI column for the Number of sockets this info is > displayed in the API output ,So fetch the data fro the api and display it in > the UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5614) [UI] improvements for Report Sockets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-5614: Priority: Critical (was: Major) > [UI] improvements for Report Sockets > > > Key: CLOUDSTACK-5614 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5614 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Kiran Koneti >Priority: Critical > Fix For: 4.3.0 > > Attachments: InfraTab.jpg, Number_of_sockets.jpg > > > The below mentioned improvements are requested for the report sockets. > 1)UI Icon in the infrastructure tab. > The current implementation of the Infrastructure tab is attached as > screenshot InfraTab.jpg whcih shows that all the other tab links has some > image in the box related to it ,So please add some image to the sockets which > would make the UI look good. > 2)number of sockets in the Sockets tab. > The current implementation of number of sockets is attached as the screen > shot Number_of_sockets.jpg in which the number of sockets for all the hosts > is listed as 0 for the hosts which are not added and also not supported.in th > egiven screenshot you can see the number of hypervisor hosts are 2 and the > sockets number is 0.It is listed so because the number of sockets for the > hyper-V is not yet implemented.So the number of sockets should be either N/A > of just -(hyphen) for the hypervisors which we doesn't support. > 3)Seperate List should be maintained for Xenserver 6.2 version and versions > prior to that. > We support the Report sockets only for the Xen 6.2 version and not for the > versions prior to that.So we have to have 2 columns one for Xenserver 6.2 for > which we can list number of hosts and number of sockets and other one saying > just Xenserver where we report only the number of hosts and the number of > sockets should be either N/A or -(hyphen). > 4)Report the socket information in the Host information UI also. > When we navigate to the Infrastructure-->Hosts -->(hostname/IP) for the host > details we don't have a UI column for the Number of sockets this info is > displayed in the API output ,So fetch the data fro the api and display it in > the UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5701) size column is not getting updated in snapshot_store_ref table.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi updated CLOUDSTACK-5701: Summary: size column is not getting updated in snapshot_store_ref table. (was: physical size is not getting updated in snapshot_store_ref table.) > size column is not getting updated in snapshot_store_ref table. > --- > > Key: CLOUDSTACK-5701 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5701 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.1 >Reporter: Sanjay Tripathi >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.3.0 > > > Physical size is not getting updated in snapshot_store_ref table. Because of > that, CS doesn't has any record of delta snapshots size created in XenServer. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5701) size column is not getting updated in snapshot_store_ref table.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861484#comment-13861484 ] ASF subversion and git services commented on CLOUDSTACK-5701: - Commit 3964a566f7e6bf5db837973b2f065796764d2269 in branch refs/heads/4.3 from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3964a56 ] CLOUDSTACK-5701: physical size is not getting updated in snapshot_store_ref table. > size column is not getting updated in snapshot_store_ref table. > --- > > Key: CLOUDSTACK-5701 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5701 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.1 >Reporter: Sanjay Tripathi >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.3.0 > > > Physical size is not getting updated in snapshot_store_ref table. Because of > that, CS doesn't has any record of delta snapshots size created in XenServer. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5679) No Error message is shown when the Connection from the MS is lost Db server in case of multiple MS and DB HA enabled.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-5679. - Resolution: Cannot Reproduce When we are adding a rule to the iptables to block the connection it is not dropping connections which are already established and new connections are rejected to that DB node.. Kiran: I am not sure how to add a rule to drop even established connections as well, so I tested by stopping the db node and able to see exceptions in logs of 2nd MS node.. > No Error message is shown when the Connection from the MS is lost Db server > in case of multiple MS and DB HA enabled. > - > > Key: CLOUDSTACK-5679 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5679 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 >Reporter: Kiran Koneti >Assignee: Damodar Reddy T >Priority: Critical > Fix For: 4.3.0 > > > Setup and issue details: > 1)Created a CS setup with multiple MS say MS1 and MS2 with DBHA enabled. > 2)Created a DB replication has 2 db servers say DB1 and DB2. > 3)Initially the setup was in such a way that both MS1 and MS2 are talking to > the DB1 and DB2 was acting as a slave. > 4)Then Blocked the communication from the MS2 to DB1 using the IPtables. > 5)When the connection is blocked from the MS2 to DB1 there is no error > message shown in the logs and it simply switches to the DB2 . -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5715) Creating private gateway giving 'Unable to serialize' error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-5715:
---
Assignee: Kelven Yang
> Creating private gateway giving 'Unable to serialize' error
> ---
>
> Key: CLOUDSTACK-5715
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5715
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.3.0
>Reporter: Jayapal Reddy
>Assignee: Kelven Yang
>Priority: Blocker
>
> 1. Created VPC.
> 2. Creating private gateway in the VPC.
> 3. Observed the below error.
> 4. In the same VPC vm got deployed successfully.
> 014-01-02 16:34:18,044 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (279776273@qtp-1396125647-17:ctx-7d9ae2fa ctx-2e9427ef) submit async job-153,
> details: AsyncJobVO {id:153, userId: 2, accountId: 2,instanceType:
> PrivateGateway, instanceId: 1, cmd:
> org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd, cmdInfo:
> {"physicalnetworkid":"1d0afe0b-a51e-4261-880d-9734cea25169","sessi
> onkey":"l0SKFGXAOKRI0PshHyMmVAR47Kg\u003d","cmdEventType":"PRIVATE.GATEWAY.CREATE","sourcenatsupported":"false","ctxUserId":"2","gateway":"10.147.43.1","httpmethod":"GET","ipaddress":"10.147.43.1
>
> 00","netmask":"255.255.255.0","response":"json","id":"1","aclid":"236a5d3e-7392-11e3-b360-a552ac66fcbb","vlan":"43","_":"1388660657895","ctxAccountId":"2","vpcid":"828d3a23-e969-44f7-b16d-38a0fce
>82b3d","ctxStartEventId":"52"}, cmdVersion: 0, status: IN_PROGRESS,
> processStatus: 0, resultCode: 0, result: null, initMsid: 1, completeMsid:
> null, lastUpdated: null, lastPolled: null, created: n ull}
> 313425 2014-01-02 16:34:18,044 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-106:ctx-0019a244) Add job-153 into job monitoring
> 313426 2014-01-02 16:34:18,044 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-106:ctx-0019a244) Executing AsyncJobVO {id:153, userId: 2,
> accountId: 2, instanceType: PrivateGateway, instanceId: 1,cmd:
> org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd, cmdInfo:
> {"physicalnetworkid":"1d0afe0b-a51e-4261-880d-9734cea25169","sessionkey":"l0SKFGXAOKRI0PshHyMmVAR47Kg\u003d","c
>
> mdEventType":"PRIVATE.GATEWAY.CREATE","sourcenatsupported":"false","ctxUserId":"2","gateway":"10.147.43.1","httpmethod":"GET","ipaddress":"10.147.43.100","netmask":"255.255.255.0","response":"jso
>
> n","id":"1","aclid":"236a5d3e-7392-11e3-b360-a552ac66fcbb","vlan":"43","_":"1388660657895","ctxAccountId":"2","vpcid":"828d3a23-e969-44f7-b16d-38a0fce82b3d","ctxStartEventId":"52"},
> cmdVersion: 0 , status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 1, completeMsid: null, lastUpdated: null, lastPolled:
> null, created: null}
> 313427 2014-01-02 16:34:18,045 DEBUG [c.c.a.ApiServlet]
> (279776273@qtp-1396125647-17:ctx-7d9ae2fa ctx-2e9427ef) ===END===
> 10.252.193.7 -- GET
> command=createPrivateGateway&sourcenatsupported=false&resp
> onse=json&sessionkey=l0SKFGXAOKRI0PshHyMmVAR47Kg%3D&physicalnetworkid=1d0afe0b-a51e-4261-880d-9734cea25169&vpcid=828d3a23-e969-44f7-b16d-38a0fce82b3d&ipaddress=10.147.43.100&gateway=10.147.43.1&n
>
> etmask=255.255.255.0&vlan=43&aclid=236a5d3e-7392-11e3-b360-a552ac66fcbb&_=1388660657895
> 313428 2014-01-02 16:34:18,109 DEBUG [c.c.u.d.T.Transaction]
> (Job-Executor-106:ctx-0019a244 ctx-2e9427ef) Rolling back the transaction:
> Time = 25 Name = Job-Executor-106; called by -TransactionLegacy.r
> ollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue:4530-VirtualMachineM
>
> anagerImpl.addVmToNetwork:3118-VpcVirtualNetworkApplianceManagerImpl.setupPrivateGateway:918-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:39-DelegatingMethodAccessorImpl.in
>voke:25-Method.invoke:597
> 313429 2014-01-02 16:34:18,110 WARN
> [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl]
> (Job-Executor-106:ctx-0019a244 ctx-2e9427ef) Failed to create private gateway
> com.cloud.network.vpc.PrivateGatewayPro file@74f4b7b3 on router
> VM[DomainRouter|r-3-VM] due to
> 313430 com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
> com.cloud.vm.VmWorkAddVmToNetwork@5933adb8
> 313431 at
> org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
> 313432 at
> com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
> 313433 at
> com.cloud.vm.Virtual
[jira] [Commented] (CLOUDSTACK-5715) Creating private gateway giving 'Unable to serialize' error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861526#comment-13861526
]
Abhinandan Prateek commented on CLOUDSTACK-5715:
Hi Kelven,
I observed bug CLOUDSTACK-5715 while create private gateway in vpc.
It seems you have changed code in
virtualmachinemanagerimpl.java:addVmToNetworkThroughJobQueue().
Can you please check if it is causing the issue.
Thanks,
Jayapal
> Creating private gateway giving 'Unable to serialize' error
> ---
>
> Key: CLOUDSTACK-5715
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5715
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.3.0
>Reporter: Jayapal Reddy
>Assignee: Kelven Yang
>Priority: Blocker
>
> 1. Created VPC.
> 2. Creating private gateway in the VPC.
> 3. Observed the below error.
> 4. In the same VPC vm got deployed successfully.
> 014-01-02 16:34:18,044 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (279776273@qtp-1396125647-17:ctx-7d9ae2fa ctx-2e9427ef) submit async job-153,
> details: AsyncJobVO {id:153, userId: 2, accountId: 2,instanceType:
> PrivateGateway, instanceId: 1, cmd:
> org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd, cmdInfo:
> {"physicalnetworkid":"1d0afe0b-a51e-4261-880d-9734cea25169","sessi
> onkey":"l0SKFGXAOKRI0PshHyMmVAR47Kg\u003d","cmdEventType":"PRIVATE.GATEWAY.CREATE","sourcenatsupported":"false","ctxUserId":"2","gateway":"10.147.43.1","httpmethod":"GET","ipaddress":"10.147.43.1
>
> 00","netmask":"255.255.255.0","response":"json","id":"1","aclid":"236a5d3e-7392-11e3-b360-a552ac66fcbb","vlan":"43","_":"1388660657895","ctxAccountId":"2","vpcid":"828d3a23-e969-44f7-b16d-38a0fce
>82b3d","ctxStartEventId":"52"}, cmdVersion: 0, status: IN_PROGRESS,
> processStatus: 0, resultCode: 0, result: null, initMsid: 1, completeMsid:
> null, lastUpdated: null, lastPolled: null, created: n ull}
> 313425 2014-01-02 16:34:18,044 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-106:ctx-0019a244) Add job-153 into job monitoring
> 313426 2014-01-02 16:34:18,044 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-106:ctx-0019a244) Executing AsyncJobVO {id:153, userId: 2,
> accountId: 2, instanceType: PrivateGateway, instanceId: 1,cmd:
> org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd, cmdInfo:
> {"physicalnetworkid":"1d0afe0b-a51e-4261-880d-9734cea25169","sessionkey":"l0SKFGXAOKRI0PshHyMmVAR47Kg\u003d","c
>
> mdEventType":"PRIVATE.GATEWAY.CREATE","sourcenatsupported":"false","ctxUserId":"2","gateway":"10.147.43.1","httpmethod":"GET","ipaddress":"10.147.43.100","netmask":"255.255.255.0","response":"jso
>
> n","id":"1","aclid":"236a5d3e-7392-11e3-b360-a552ac66fcbb","vlan":"43","_":"1388660657895","ctxAccountId":"2","vpcid":"828d3a23-e969-44f7-b16d-38a0fce82b3d","ctxStartEventId":"52"},
> cmdVersion: 0 , status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 1, completeMsid: null, lastUpdated: null, lastPolled:
> null, created: null}
> 313427 2014-01-02 16:34:18,045 DEBUG [c.c.a.ApiServlet]
> (279776273@qtp-1396125647-17:ctx-7d9ae2fa ctx-2e9427ef) ===END===
> 10.252.193.7 -- GET
> command=createPrivateGateway&sourcenatsupported=false&resp
> onse=json&sessionkey=l0SKFGXAOKRI0PshHyMmVAR47Kg%3D&physicalnetworkid=1d0afe0b-a51e-4261-880d-9734cea25169&vpcid=828d3a23-e969-44f7-b16d-38a0fce82b3d&ipaddress=10.147.43.100&gateway=10.147.43.1&n
>
> etmask=255.255.255.0&vlan=43&aclid=236a5d3e-7392-11e3-b360-a552ac66fcbb&_=1388660657895
> 313428 2014-01-02 16:34:18,109 DEBUG [c.c.u.d.T.Transaction]
> (Job-Executor-106:ctx-0019a244 ctx-2e9427ef) Rolling back the transaction:
> Time = 25 Name = Job-Executor-106; called by -TransactionLegacy.r
> ollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue:4530-VirtualMachineM
>
> anagerImpl.addVmToNetwork:3118-VpcVirtualNetworkApplianceManagerImpl.setupPrivateGateway:918-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:39-DelegatingMethodAccessorImpl.in
>voke:25-Method.invoke:597
> 313429 2014-01-02 16:34:18,110 WARN
> [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl]
> (Job-Executor-106:ctx-0019a244 ctx-2e9427ef) Failed to create private gateway
> com.cloud.network.vpc.PrivateGatewayPro file@74f4b7b3 on router
> VM[DomainRouter|r-3-VM] due to
> 313430 com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
> com.cloud.vm.VmWorkAddVmToNetwork@5933adb
[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861532#comment-13861532 ] Sudha Ponnaganti commented on CLOUDSTACK-5709: -- Closing this as Nux has confirmed that it is working fine with revised version of KVM -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Friday, January 03, 2014 12:33 AM To: d...@cloudstack.apache.org Subject: RE: [VOTE] 3rd round of voting for ASF 4.2.1 RC On 03.01.2014 07:40, Nux! wrote: > Guys, this is really confusing! > First of all I could swear I had this feature working on me previously > on a similar setup, second of all why has your colleague Sadhu said > this is working[1]? > Also Andrei Mikhailovsky claims in this same thread the feature is > working, though he is facing other issues (launching new VMs from > volume backups/snapshots). Ok, I think I got it. For EL6 (CentOS6) users the workaround is to use a patched version of KVM, then all the features start working (btw "VM snapshots" could work as well with this!). The confusion comes from the fact the issue is not present in Ubuntu latest for example since they package a newer kvm, so this differs from one distro to another. With the version from RHEV everything worked great and I'll test this soon with GlusterFS shared mount point as well. More here https://issues.apache.org/jira/browse/CLOUDSTACK-5709?focusedCommentId=13861329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13861329 -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux >Assignee: edison su > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-5709. -- Resolution: Fixed Updated KVM is needed > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux >Assignee: edison su > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5715) [Automation]Creating private gateway giving 'Unable to serialize' error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri updated CLOUDSTACK-5715:
-
Summary: [Automation]Creating private gateway giving 'Unable to serialize'
error (was: Creating private gateway giving 'Unable to serialize' error)
> [Automation]Creating private gateway giving 'Unable to serialize' error
> ---
>
> Key: CLOUDSTACK-5715
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5715
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.3.0
>Reporter: Jayapal Reddy
>Assignee: Kelven Yang
>Priority: Blocker
>
> 1. Created VPC.
> 2. Creating private gateway in the VPC.
> 3. Observed the below error.
> 4. In the same VPC vm got deployed successfully.
> 014-01-02 16:34:18,044 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (279776273@qtp-1396125647-17:ctx-7d9ae2fa ctx-2e9427ef) submit async job-153,
> details: AsyncJobVO {id:153, userId: 2, accountId: 2,instanceType:
> PrivateGateway, instanceId: 1, cmd:
> org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd, cmdInfo:
> {"physicalnetworkid":"1d0afe0b-a51e-4261-880d-9734cea25169","sessi
> onkey":"l0SKFGXAOKRI0PshHyMmVAR47Kg\u003d","cmdEventType":"PRIVATE.GATEWAY.CREATE","sourcenatsupported":"false","ctxUserId":"2","gateway":"10.147.43.1","httpmethod":"GET","ipaddress":"10.147.43.1
>
> 00","netmask":"255.255.255.0","response":"json","id":"1","aclid":"236a5d3e-7392-11e3-b360-a552ac66fcbb","vlan":"43","_":"1388660657895","ctxAccountId":"2","vpcid":"828d3a23-e969-44f7-b16d-38a0fce
>82b3d","ctxStartEventId":"52"}, cmdVersion: 0, status: IN_PROGRESS,
> processStatus: 0, resultCode: 0, result: null, initMsid: 1, completeMsid:
> null, lastUpdated: null, lastPolled: null, created: n ull}
> 313425 2014-01-02 16:34:18,044 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-106:ctx-0019a244) Add job-153 into job monitoring
> 313426 2014-01-02 16:34:18,044 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-106:ctx-0019a244) Executing AsyncJobVO {id:153, userId: 2,
> accountId: 2, instanceType: PrivateGateway, instanceId: 1,cmd:
> org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd, cmdInfo:
> {"physicalnetworkid":"1d0afe0b-a51e-4261-880d-9734cea25169","sessionkey":"l0SKFGXAOKRI0PshHyMmVAR47Kg\u003d","c
>
> mdEventType":"PRIVATE.GATEWAY.CREATE","sourcenatsupported":"false","ctxUserId":"2","gateway":"10.147.43.1","httpmethod":"GET","ipaddress":"10.147.43.100","netmask":"255.255.255.0","response":"jso
>
> n","id":"1","aclid":"236a5d3e-7392-11e3-b360-a552ac66fcbb","vlan":"43","_":"1388660657895","ctxAccountId":"2","vpcid":"828d3a23-e969-44f7-b16d-38a0fce82b3d","ctxStartEventId":"52"},
> cmdVersion: 0 , status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 1, completeMsid: null, lastUpdated: null, lastPolled:
> null, created: null}
> 313427 2014-01-02 16:34:18,045 DEBUG [c.c.a.ApiServlet]
> (279776273@qtp-1396125647-17:ctx-7d9ae2fa ctx-2e9427ef) ===END===
> 10.252.193.7 -- GET
> command=createPrivateGateway&sourcenatsupported=false&resp
> onse=json&sessionkey=l0SKFGXAOKRI0PshHyMmVAR47Kg%3D&physicalnetworkid=1d0afe0b-a51e-4261-880d-9734cea25169&vpcid=828d3a23-e969-44f7-b16d-38a0fce82b3d&ipaddress=10.147.43.100&gateway=10.147.43.1&n
>
> etmask=255.255.255.0&vlan=43&aclid=236a5d3e-7392-11e3-b360-a552ac66fcbb&_=1388660657895
> 313428 2014-01-02 16:34:18,109 DEBUG [c.c.u.d.T.Transaction]
> (Job-Executor-106:ctx-0019a244 ctx-2e9427ef) Rolling back the transaction:
> Time = 25 Name = Job-Executor-106; called by -TransactionLegacy.r
> ollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue:4530-VirtualMachineM
>
> anagerImpl.addVmToNetwork:3118-VpcVirtualNetworkApplianceManagerImpl.setupPrivateGateway:918-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:39-DelegatingMethodAccessorImpl.in
>voke:25-Method.invoke:597
> 313429 2014-01-02 16:34:18,110 WARN
> [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl]
> (Job-Executor-106:ctx-0019a244 ctx-2e9427ef) Failed to create private gateway
> com.cloud.network.vpc.PrivateGatewayPro file@74f4b7b3 on router
> VM[DomainRouter|r-3-VM] due to
> 313430 com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
> com.cloud.vm.VmWorkAddVmToNetwork@5933adb8
> 313431 at
> org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedStrin
