[jira] [Assigned] (CLOUDSTACK-4645) There is no upgrade path from 4.1.1 to 4.2.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4645: --- Assignee: Venkata Siva Vijayendra Bhamidipati There is no upgrade path from 4.1.1 to 4.2.0 Key: CLOUDSTACK-4645 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4645 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Milamber Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker I've try to upgrade my CS test platform from 4.1.1 to 4.2.0 (from Commit: e39a7d8e0d3f2fd3e326b1bdf4aaf9ba5d900b02 + CLVM issue cherry-pick from 4.2-forward with commitId f2c5b5fbfe45196dfad2821fca513ddd6efa25c9.) The path 4.1.1-4.2.0 seems miss? 2013-09-11 14:32:55,619 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Grabbing lock to check for database upgrade. 2013-09-11 14:32:55,631 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 4.1.1 Code Version = 4.2.0 2013-09-11 14:32:55,632 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 4.1.1 to 4.2.0 2013-09-11 14:32:55,632 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) There is no upgrade path from 4.1.1 to 4.2.0 2013-09-11 14:32:55,639 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup com.cloud.utils.exception.CloudRuntimeException: There is no upgrade path from 4.1.1 to 4.2.0 at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:221) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:534) at java.util.TimerThread.run(Timer.java:484) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4539) [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13754162#comment-13754162 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4539: - Hi Prashant, I discussed this bug with Kelven/Alex/Will. Alex was of the view that merely shifting from one version to the next should not be the criterion for updating this flag. The business case would be to set this flag to false if deployments (data centers) already exist on the setup, and true otherwise. I've made the changes appropriately. So, when you test this, you will have three scenarios: 1) Upgrade from 3.0.6 that has no data centers created in it, to 4.2, and the flag must be set to true post upgrade. 2) Upgrade from 3.0.6 that has data centers created in it, to 4.2, and the flag must be set to false post upgrade. 3) Deploy a fresh 4.2.0 setup, and the flag must be set to true post deployment. The VMs should get created accordingly. Thanks, Regards, Vijay [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone --- Key: CLOUDSTACK-4539 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4539 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: prashant kumar mishra Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0, 4.2.1 Attachments: Logs_DB.rar In upgraded setup vm should get deployed as linked clone ,default value of global parameter vmware.create.full.clone should be false in upgraded setup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4539) [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4539. - Resolution: Fixed [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone --- Key: CLOUDSTACK-4539 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4539 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: prashant kumar mishra Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0, 4.2.1 Attachments: Logs_DB.rar In upgraded setup vm should get deployed as linked clone ,default value of global parameter vmware.create.full.clone should be false in upgraded setup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4539) [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4539: --- Assignee: Venkata Siva Vijayendra Bhamidipati [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone --- Key: CLOUDSTACK-4539 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4539 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: prashant kumar mishra Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0, 4.2.1 In upgraded setup vm should get deployed as linked clone ,default value of global parameter vmware.create.full.clone should be false in upgraded setup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4539) [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4539. - Resolution: Fixed [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone --- Key: CLOUDSTACK-4539 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4539 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: prashant kumar mishra Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0, 4.2.1 In upgraded setup vm should get deployed as linked clone ,default value of global parameter vmware.create.full.clone should be false in upgraded setup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone(showing SG enabled to true eventhough zone created with sharednetwork)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751820#comment-13751820 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2730: - Hi Sadhu, I re-ran this with the latest 4.2-forward build and basic zone creation and cluster addition goes through fine as before. I am not running into the message Don't support hypervisor type VMware in advanced security enabled zone that you encountered because Anthony has fixed this as part of commit # 9905f656a5307c9d9b990ed988c2ea82b432231a. You shouldn't be having an issue with addcluster anymore. However, you are right in that the db entry for the zone in the data_center table shows security groups as enabled. I took a look at the code and I see that when a basic zone is created, it is always enabled with security groups by default, because except vmware, all other hypervisors can implement this as a service. This setting will be ignored/errored out for vmware deployments. vmware:addcluster failed in basiczone(showing SG enabled to true eventhough zone created with sharednetwork) Key: CLOUDSTACK-2730 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: sadhu suresh Assignee: Venkata Siva Vijayendra Bhamidipati Fix For: 4.2.0 Attachments: management-server.log In case of vmware ,when i try to configure basic zone with shared network.addcluster failed with Creating cluster Something went wrong; please correct the following:Don't support hypervisor type VMware in advanced security enabled zone even though i select the bassic and shared network. 1.select the zone type as basic 2.select the network type as shared 3.provide pod ,guest details and configure primary and secondary detaisl 4.click on finish to create basic zone with shared network mode Actual result: even though i select shared network in basic zone,it sends security group enble to true internally. due to this addcluster failed . It throws following error: Creating cluster Something went wrong; please correct the following:Don't support hypervisor type VMware in advanced security enabled zone mysql select * from data_center where id=2\G; *** 1. row *** id: 2 name: zone1 uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7 description: NULL dns1: 10.103.128.16 dns2: NULL internal_dns1: 10.103.128.16 internal_dns2: NULL gateway: NULL netmask: NULL router_mac_address: 02:00:00:00:00:01 mac_address: 23 guest_network_cidr: NULL domain: NULL domain_id: NULL networktype: Basic dns_provider: VirtualRouter gateway_provider: NULL firewall_provider: NULL dhcp_provider: VirtualRouter lb_provider: ElasticLoadBalancerVm vpn_provider: NULL userdata_provider: VirtualRouter allocation_state: Disabled zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5 is_security_group_enabled: 1 is_local_storage_enabled: 0 removed: NULL owner: NULL created: NULL lastUpdated: NULL engine_state: Disabled ip6_dns1: NULL ip6_dns2: NULL 1 row in set (0.00 sec) mysql select * from networks where id=209\G; *** 1. row *** id: 209 name: defaultGuestNetwork uuid: eca88272-2ad4-47a8-ab90-442393b6d034 display_text: defaultGuestNetwork traffic_type: Guest broadcast_domain_type: Native broadcast_uri: vlan://untagged gateway: NULL cidr: NULL mode: Dhcp network_offering_id: 7 physical_network_id: 201 data_center_id: 2 guru_name: DirectPodBasedNetworkGuru state: Setup related: 209 domain_id: 1 account_id: 1 dns1: NULL dns2: NULL guru_data: NULL set_fields: 0 acl_type: Domain network_domain: cs1cloud.internal reservation_id: NULL
[jira] [Resolved] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone(showing SG enabled to true eventhough zone created with sharednetwork)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-2730.
-
Resolution: Fixed
Anthony has fixed this issue in commit#
9905f656a5307c9d9b990ed988c2ea82b432231a. Please refer to previous comments for
an explanation of the security group flag being enabled by default at the zone
level.
vmware:addcluster failed in basiczone(showing SG enabled to true eventhough
zone created with sharednetwork)
Key: CLOUDSTACK-2730
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Venkata Siva Vijayendra Bhamidipati
Fix For: 4.2.0
Attachments: management-server.log
In case of vmware ,when i try to configure basic zone with shared
network.addcluster failed with
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone even though
i select the bassic and shared network.
1.select the zone type as basic
2.select the network type as shared
3.provide pod ,guest details and configure primary and secondary detaisl
4.click on finish to create basic zone with shared network mode
Actual result:
even though i select shared network in basic zone,it sends security group
enble to true internally. due to this addcluster failed .
It throws following error:
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone
mysql select * from data_center where id=2\G;
*** 1. row ***
id: 2
name: zone1
uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
description: NULL
dns1: 10.103.128.16
dns2: NULL
internal_dns1: 10.103.128.16
internal_dns2: NULL
gateway: NULL
netmask: NULL
router_mac_address: 02:00:00:00:00:01
mac_address: 23
guest_network_cidr: NULL
domain: NULL
domain_id: NULL
networktype: Basic
dns_provider: VirtualRouter
gateway_provider: NULL
firewall_provider: NULL
dhcp_provider: VirtualRouter
lb_provider: ElasticLoadBalancerVm
vpn_provider: NULL
userdata_provider: VirtualRouter
allocation_state: Disabled
zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
is_security_group_enabled: 1
is_local_storage_enabled: 0
removed: NULL
owner: NULL
created: NULL
lastUpdated: NULL
engine_state: Disabled
ip6_dns1: NULL
ip6_dns2: NULL
1 row in set (0.00 sec)
mysql select * from networks where id=209\G;
*** 1. row ***
id: 209
name: defaultGuestNetwork
uuid: eca88272-2ad4-47a8-ab90-442393b6d034
display_text: defaultGuestNetwork
traffic_type: Guest
broadcast_domain_type: Native
broadcast_uri: vlan://untagged
gateway: NULL
cidr: NULL
mode: Dhcp
network_offering_id: 7
physical_network_id: 201
data_center_id: 2
guru_name: DirectPodBasedNetworkGuru
state: Setup
related: 209
domain_id: 1
account_id: 1
dns1: NULL
dns2: NULL
guru_data: NULL
set_fields: 0
acl_type: Domain
network_domain: cs1cloud.internal
reservation_id: NULL
guest_type: Shared
restart_required: 0
created: 2013-05-29 12:21:04
removed: NULL
specify_ip_ranges: 1
vpc_id: NULL
ip6_gateway: NULL
ip6_cidr: NULL
network_cidr: NULL
display_network: 1
network_acl_id: NULL
1 row in set (0.00 sec)
http://10.147.59.83:8080/client/api?command=createZonenetworktype=Basicname=zone1dns1=10.103.128.16internaldns1=10.103.128.16response=jsonsessionkey=6%2BUi17Y6gpixRBAR9s4yhQCQkhs%3D_=1369810303912
{ createzoneresponse : { zone :
[jira] [Assigned] (CLOUDSTACK-4513) [Vmware] new mapping vmware datacenter cloudstack zone - Host in second cluster in DC put in maintenance mode, CPVM and guest VMs that were migrated failed to come
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4513: --- Assignee: Venkata Siva Vijayendra Bhamidipati [Vmware] new mapping vmware datacenter cloudstack zone - Host in second cluster in DC put in maintenance mode, CPVM and guest VMs that were migrated failed to come up --- Key: CLOUDSTACK-4513 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4513 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: MS10.223.195.52 build 479 host ESXi 5.0 Reporter: angeline shen Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.1 Attachments: management-server.log.gz, management-server.log.gz, Screenshot-CloudPlatform™ - Mozilla Firefox-1.png, Screenshot-CloudPlatform™ - Mozilla Firefox-2.png, Screenshot-CloudPlatform™ - Mozilla Firefox-9.png, Screenshot-CloudPlatform™ - Mozilla Firefox.png 1. Vcenter CPP 4.2. VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2 H2 H2 10.223.51.3 PS2 cluster primary storage C2 - H3C2 - H3 10.223.51.4 PS3 cluster primary storage PS1 zone primary storage PSZ4 zone primary storage 2. H310.223.51.4 has SSVM CPVM and VMs i-2-8i-2-6 VRs and other guest VMs were on Hosts H1 and H3 3. Put H3 in maintenance mode. Result: VMs i-2-6-VM and i-2-8-VM went into STOP state. Try to start both VMs. These remain in 'Starting' state . New SSVM s-14-VM created.. Old SSVM s-10-VM remained in expunging and disconnected state CPVM v-11-VM remain in STOP and disconnected state. Cannot be started 4. Host H3 cancel maintenance mode. Old SSVM s-10-VM remained in expunging and disconnected state CPVM v-11-VM go to running state Old SSVM s-10-VM remained in expunging and disconnected state VMs i-2-6-VM and i-2-8-VM were in STOP state. Unable to restart both guest VMs - deployment failed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4462) [Automation][vmware] Failed to find vmdk filed during deployment; and deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-4462:
Assignee: Kelven Yang (was: Venkata Siva Vijayendra Bhamidipati)
[Automation][vmware] Failed to find vmdk filed during deployment; and
deployment failed
Key: CLOUDSTACK-4462
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4462
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, VMware
Affects Versions: 4.2.0
Environment: Automation
vmware
found with 4.2.0-forward branch
Reporter: Rayees Namathponnan
Assignee: Kelven Yang
Priority: Critical
Fix For: 4.2.1
Attachments: CLOUDSTACK-4462.rar
During automation run, MS unable to find vmdk file and deployment failed.
Observed below error in MS
2013-08-22 11:55:51,779 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.223.240.195 -- GET
signature=RPK2DwAB3%2FQ8uWNzeyn%2Fp72Ffcw%3DapiKey=9QzLLT5rIGDi6assUgBQ6s-cdRtyblucm14vV5seHyG6NijTFPH
y-4vU2HOoE157MdQOo8GjwghoBcQdhwZyBAcommand=queryAsyncJobResultresponse=jsonjobid=8c43beaf-fcf6-4440-90a8-9da05b0312d3
2013-08-22 11:55:51,798 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-15:null) SeqA 7-8020: Sending Seq 7-8020: { Ans: ,
MgmtId: 90928106758026, via: 7, Ver: v1, Flags: 100010, [{com.cloud.agent.a
pi.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-22 11:55:53,014 INFO [vmware.resource.VmwareResource]
(DirectAgent-169:10.223.250.131) Trying to connect to 10.223.250.185
2013-08-22 11:55:53,015 INFO [vmware.resource.VmwareResource]
(DirectAgent-169:10.223.250.131) Could not connect to 10.223.250.185 due to
java.net.ConnectException: Connection refused
2013-08-22 11:55:53,454 WARN [vmware.resource.VmwareResource]
(DirectAgent-306:10.223.250.130) StartCommand failed due to Exception:
java.lang.RuntimeException
Message: File [4faf04c26dd83025b43f65d32cc49d02] ROOT-421.vmdk was not found
java.lang.RuntimeException: File [4faf04c26dd83025b43f65d32cc49d02]
ROOT-421.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
at
com.cloud.hypervisor.vmware.mo.DatastoreMO.moveDatastoreFile(DatastoreMO.java:235)
at
com.cloud.storage.resource.VmwareStorageLayoutHelper.syncVolumeToVmDefaultFolder(VmwareStorageLayoutHelper.java:133)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2880)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2013-08-22 11:55:53,465 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-306:null) Seq 2-542512498: Cancelling because one of the answers
is false and it is stop on error.
2013-08-22 11:55:53,465 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-306:null) Seq 2-542512498: Response Received:
2013-08-22 11:55:53,466 DEBUG [agent.transport.Request]
(DirectAgent-306:null) Seq 2-542512498: Processing: { Ans: , MgmtId:
90928106758026, via: 2, Ver: v1, Flags: 110,
[{com.cloud.agent.api.StartAnswer:{vm:{id:421,name:r-421-TestVM,bootloader:HVM,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,hostName:r-421-TestVM,arch:i686,os:Debian
GNU/Linux 5.0 (32-bit),bootArgs: vpccidr=10.1.1.1/16
domain=test.domain.org dns1=8.8.8.8 template=domP name=r-421-TestVM
eth0ip=10.223.250.178 eth0mask=255.255.255.192 mgmtcidr=10.223.49.192/26
localgw=10.223.250.129 type=vpcrouter disable_rp_filter=true extra_pubnics=2
[jira] [Commented] (CLOUDSTACK-4513) [Vmware] new mapping vmware datacenter cloudstack zone - Host in second cluster in DC put in maintenance mode, CPVM and guest VMs that were migrated failed to com
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751942#comment-13751942 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4513: - In the logs, migration is constantly being retried and is failing because of insufficient capacity for VM migration. Excerpt of one such failure from the log: 2013-08-26 11:35:12,124 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:3 2013-08-26 11:35:12,128 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-6-Routing]] 2013-08-26 11:35:12,130 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-6-Routing]] 2013-08-26 11:35:12,130 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator) Looking for speed=100Mhz, Ram=512 2013-08-26 11:35:12,130 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator) Host name: 10.223.51.4, hostId: 6 is in avoid set, skipping this and trying other available hosts 2013-08-26 11:35:12,130 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts 2013-08-26 11:35:12,130 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (HA-Worker-0:work-1) No suitable hosts found 2013-08-26 11:35:12,130 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (HA-Worker-0:work-1) No suitable hosts found under this Cluster: 3 2013-08-26 11:35:12,132 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (HA-Worker-0:work-1) Could not find suitable Deployment Destination for this VM under any clusters, returning. 2013-08-26 11:35:12,132 DEBUG [cloud.deploy.FirstFitPlanner] (HA-Worker-0:work-1) Searching resources only under specified Cluster: 3 2013-08-26 11:35:12,133 DEBUG [cloud.deploy.FirstFitPlanner] (HA-Worker-0:work-1) The specified cluster is in avoid set, returning. 2013-08-26 11:35:12,133 DEBUG [cloud.vm.VirtualMachineManagerImpl] (HA-Worker-0:work-1) Unable to find destination for migrating the vm VM[User|z1vpc1G1adminV6] 2013-08-26 11:35:12,133 WARN [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-0:work-1) Insufficient capacity for migrating a VM. 2013-08-26 11:35:12,134 DEBUG [cloud.resource.ResourceManagerImpl] (HA-Worker-0:work-1) No next resource state for host 6 while current state is Enabled with event UnableToMigrate com.cloud.utils.fsm.NoTransitionException: No next resource state found for current state =Enabled event =UnableToMigrate at com.cloud.resource.ResourceManagerImpl.resourceStateTransitTo(ResourceManagerImpl.java:1173) at com.cloud.resource.ResourceManagerImpl.maintenanceFailed(ResourceManagerImpl.java:2285) at com.cloud.ha.HighAvailabilityManagerImpl.migrate(HighAvailabilityManagerImpl.java:581) at com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:829) 2013-08-26 11:35:12,134 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-0:work-1) Rescheduling HAWork[1-Migration-5-Running-Migrating] to try again at Mon Aug 26 11:37:14 PDT 2013 Angie, it looks like you are running into a capacity problem - can you retry this after adding a third host in C1 to increase host capacity? Or, you could try using a smaller service offering for the system/user VMs to see if this occurs with those. [Vmware] new mapping vmware datacenter cloudstack zone - Host in second cluster in DC put in maintenance mode, CPVM and guest VMs that were migrated failed to come up --- Key: CLOUDSTACK-4513 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4513 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: MS10.223.195.52 build 479 host ESXi 5.0 Reporter: angeline shen Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.1 Attachments: management-server.log.gz, management-server.log.gz, Screenshot-CloudPlatform™ - Mozilla Firefox-1.png, Screenshot-CloudPlatform™ - Mozilla Firefox-2.png, Screenshot-CloudPlatform™ - Mozilla Firefox-9.png, Screenshot-CloudPlatform™ - Mozilla Firefox.png 1. Vcenter CPP 4.2. VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2
[jira] [Assigned] (CLOUDSTACK-1872) Do not accept OVAs with multiple VMDKs for uploaded volumes or templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-1872: --- Assignee: Venkata Siva Vijayendra Bhamidipati Do not accept OVAs with multiple VMDKs for uploaded volumes or templates Key: CLOUDSTACK-1872 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1872 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template, VMware, Volumes Affects Versions: 4.0.1 Reporter: Kirk Kosinski Assignee: Venkata Siva Vijayendra Bhamidipati CloudStack volumes and templates are meant to be one single virtual disk. This is always the case with KVM and XenServer/XCP since the files used for volumes and templates are virtual disks (QCOW2, VHD). However, VMware volumes and templates are in OVA format, which are archives that can contain a complete VM including multiple VMDKs and other files such as ISOs. Currently, CloudStack will accept an OVA with an invalid configuration, extract it to secondary storage, and allow end-users to use it. This can cause unintended behavior or possibly failures when an end-user does try to use it. At the very least, it wastes space on secondary and possibly primary storage. For example, here is a uploaded volume that contained two VMDKs on secondary storage: # ll /mnt/secondary/volumes/12/ total 332 -rw-rw-rw- 1 root root 146944 Apr 1 16:38 3ab61094-8170-3139-a6b4-8edd2b4942ef.ova -rw-r--r-- 1 root root 68608 Apr 1 16:35 blankvm2-disk1.vmdk -rw-r--r-- 1 root root 68608 Apr 1 16:35 blankvm2-disk2.vmdk -rw-r--r-- 1 root root200 Apr 1 16:35 blankvm2.mf -rw-r--r-- 1 root root 5930 Apr 1 16:35 blankvm2.ovf -rw-rw-rw- 1 root root328 Apr 1 16:38 volume.properties Attaching this volume to a VM will result in both VMDKs being copied to primary storage, but only one will be attached to the VM. CloudStack should verify whether or not an OVA contains a supported configuration, and should give an error and reject the OVA if it is not supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4462) [Automation][vmware] Failed to find vmdk filed during deployment; and deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750376#comment-13750376
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4462:
-
I haven't been able to reproduce this on my setup. However, looking at the logs
attached, the signature is just like one of the exception signatures we saw in
CLOUDSTACK-3568, where waitForTask() after a moveDatastoreFile() encounters an
error. Also, this seems to have happened once in about 400 creation attempts of
VMs. Kelven, can you please take a look at this? Is it possible that there are
still corner cases in the refactored vmware context pool code?
[Automation][vmware] Failed to find vmdk filed during deployment; and
deployment failed
Key: CLOUDSTACK-4462
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4462
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, VMware
Affects Versions: 4.2.0
Environment: Automation
vmware
found with 4.2.0-forward branch
Reporter: Rayees Namathponnan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.1
Attachments: CLOUDSTACK-4462.rar
During automation run, MS unable to find vmdk file and deployment failed.
Observed below error in MS
2013-08-22 11:55:51,779 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.223.240.195 -- GET
signature=RPK2DwAB3%2FQ8uWNzeyn%2Fp72Ffcw%3DapiKey=9QzLLT5rIGDi6assUgBQ6s-cdRtyblucm14vV5seHyG6NijTFPH
y-4vU2HOoE157MdQOo8GjwghoBcQdhwZyBAcommand=queryAsyncJobResultresponse=jsonjobid=8c43beaf-fcf6-4440-90a8-9da05b0312d3
2013-08-22 11:55:51,798 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-15:null) SeqA 7-8020: Sending Seq 7-8020: { Ans: ,
MgmtId: 90928106758026, via: 7, Ver: v1, Flags: 100010, [{com.cloud.agent.a
pi.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-22 11:55:53,014 INFO [vmware.resource.VmwareResource]
(DirectAgent-169:10.223.250.131) Trying to connect to 10.223.250.185
2013-08-22 11:55:53,015 INFO [vmware.resource.VmwareResource]
(DirectAgent-169:10.223.250.131) Could not connect to 10.223.250.185 due to
java.net.ConnectException: Connection refused
2013-08-22 11:55:53,454 WARN [vmware.resource.VmwareResource]
(DirectAgent-306:10.223.250.130) StartCommand failed due to Exception:
java.lang.RuntimeException
Message: File [4faf04c26dd83025b43f65d32cc49d02] ROOT-421.vmdk was not found
java.lang.RuntimeException: File [4faf04c26dd83025b43f65d32cc49d02]
ROOT-421.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
at
com.cloud.hypervisor.vmware.mo.DatastoreMO.moveDatastoreFile(DatastoreMO.java:235)
at
com.cloud.storage.resource.VmwareStorageLayoutHelper.syncVolumeToVmDefaultFolder(VmwareStorageLayoutHelper.java:133)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2880)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2013-08-22 11:55:53,465 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-306:null) Seq 2-542512498: Cancelling because one of the answers
is false and it is stop on error.
2013-08-22 11:55:53,465 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-306:null) Seq 2-542512498: Response Received:
2013-08-22 11:55:53,466 DEBUG [agent.transport.Request]
(DirectAgent-306:null) Seq 2-542512498: Processing: { Ans: , MgmtId:
90928106758026, via: 2, Ver: v1, Flags: 110,
[jira] [Assigned] (CLOUDSTACK-4458) [VMWare] Failed to create Snapshot on Data Disk because of backup snapshot exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4458: --- Assignee: Venkata Siva Vijayendra Bhamidipati [VMWare] Failed to create Snapshot on Data Disk because of backup snapshot exception Key: CLOUDSTACK-4458 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4458 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.1 == Steps to Reproduce the Bug: == 1. Deploy a VM using the default CentOS Template 2. Create and attach a volume to the deployed VM as its data disk. 3. Create File System on it and generate few files on the data disk. 4. Stop the VM. 5. Take the Snapshot of the Data disk. = Observation on Management Server Logs: = 2013-08-22 11:37:53,960 DEBUG [storage.snapshot.SnapshotManagerImpl] (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Failed to create snapshot com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception: Exception: java.lang.RuntimeException Message: File []/vmfs/volumes/f9418bb5-7dc9164d/3fbe5d8cd5e64c1984984b4d4bf6e02f.vmdk was not found at org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:281) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:137) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:256) at com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1004) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1280) at com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2703) at org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-08-22 11:37:53,970 DEBUG [storage.volume.VolumeServiceImpl] (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Take snapshot: 28 failed com.cloud.utils.exception.CloudRuntimeException: Failed to create snapshot at com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1029) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1280) at com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2703) at org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception: Exception: java.lang.RuntimeException Message: File []/vmfs/volumes/f9418bb5-7dc9164d/3fbe5d8cd5e64c1984984b4d4bf6e02f.vmdk was not found at org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:281) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:137)
[jira] [Assigned] (CLOUDSTACK-4462) [Automation][vmware] Failed to find vmdk filed during deployment; and deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4462:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
[Automation][vmware] Failed to find vmdk filed during deployment; and
deployment failed
Key: CLOUDSTACK-4462
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4462
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, VMware
Affects Versions: 4.2.0
Environment: Automation
vmware
found with 4.2.0-forward branch
Reporter: Rayees Namathponnan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.1
Attachments: CLOUDSTACK-4462.rar
During automation run, MS unable to find vmdk file and deployment failed.
Observed below error in MS
2013-08-22 11:55:51,779 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.223.240.195 -- GET
signature=RPK2DwAB3%2FQ8uWNzeyn%2Fp72Ffcw%3DapiKey=9QzLLT5rIGDi6assUgBQ6s-cdRtyblucm14vV5seHyG6NijTFPH
y-4vU2HOoE157MdQOo8GjwghoBcQdhwZyBAcommand=queryAsyncJobResultresponse=jsonjobid=8c43beaf-fcf6-4440-90a8-9da05b0312d3
2013-08-22 11:55:51,798 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-15:null) SeqA 7-8020: Sending Seq 7-8020: { Ans: ,
MgmtId: 90928106758026, via: 7, Ver: v1, Flags: 100010, [{com.cloud.agent.a
pi.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-22 11:55:53,014 INFO [vmware.resource.VmwareResource]
(DirectAgent-169:10.223.250.131) Trying to connect to 10.223.250.185
2013-08-22 11:55:53,015 INFO [vmware.resource.VmwareResource]
(DirectAgent-169:10.223.250.131) Could not connect to 10.223.250.185 due to
java.net.ConnectException: Connection refused
2013-08-22 11:55:53,454 WARN [vmware.resource.VmwareResource]
(DirectAgent-306:10.223.250.130) StartCommand failed due to Exception:
java.lang.RuntimeException
Message: File [4faf04c26dd83025b43f65d32cc49d02] ROOT-421.vmdk was not found
java.lang.RuntimeException: File [4faf04c26dd83025b43f65d32cc49d02]
ROOT-421.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
at
com.cloud.hypervisor.vmware.mo.DatastoreMO.moveDatastoreFile(DatastoreMO.java:235)
at
com.cloud.storage.resource.VmwareStorageLayoutHelper.syncVolumeToVmDefaultFolder(VmwareStorageLayoutHelper.java:133)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2880)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2013-08-22 11:55:53,465 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-306:null) Seq 2-542512498: Cancelling because one of the answers
is false and it is stop on error.
2013-08-22 11:55:53,465 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-306:null) Seq 2-542512498: Response Received:
2013-08-22 11:55:53,466 DEBUG [agent.transport.Request]
(DirectAgent-306:null) Seq 2-542512498: Processing: { Ans: , MgmtId:
90928106758026, via: 2, Ver: v1, Flags: 110,
[{com.cloud.agent.api.StartAnswer:{vm:{id:421,name:r-421-TestVM,bootloader:HVM,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,hostName:r-421-TestVM,arch:i686,os:Debian
GNU/Linux 5.0 (32-bit),bootArgs: vpccidr=10.1.1.1/16
domain=test.domain.org dns1=8.8.8.8 template=domP name=r-421-TestVM
eth0ip=10.223.250.178 eth0mask=255.255.255.192 mgmtcidr=10.223.49.192/26
localgw=10.223.250.129 type=vpcrouter disable_rp_filter=true extra_pubnics=2
[jira] [Commented] (CLOUDSTACK-3010) [VMWare] [SharedNetworkWithServices] router VM deployment fails with error Message: Invalid configuration for device '2'.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744635#comment-13744635 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3010: - This happens only on shared networks, when the firewall and source NAT options are enabled using Virtual Router in the custom network offering. The mgmt layer isn't supplying a mac address to the guest network's NicVO. The db entry shows up like this: mysql select * from nics where id=37\G; *** 1. row *** id: 37 uuid: 095616df-e95b-479b-a9f9-591a5db72b12 instance_id: 16 mac_address: NULL ip4_address: 10.8.1.1 netmask: 255.255.255.128 gateway: NULL ip_type: NULL broadcast_uri: vlan://2418 network_id: 209 mode: Dhcp state: Allocated strategy: Create reserver_name: DirectNetworkGuru reservation_id: NULL device_id: 0 update_time: 2013-08-19 12:54:37 isolation_uri: vlan://2418 ip6_address: NULL default_nic: 0 vm_type: DomainRouter created: 2013-08-19 16:06:10 removed: NULL ip6_gateway: NULL ip6_cidr: NULL secondary_ip: 0 display_nic: 1 1 row in set (0.00 sec) ERROR: No query specified mysql The above NIC entries are made in allocateNic() in NetworkManagerImpl.java. This seems to be called when the guest VM is being setup/created, but not when the router VM is being created. Not clear where or why the guest mac address isn't being allocated for the router VM. This doesn't seem to be a vmware specific issue because it's all happening in the mgmt layers and afai can see, outside the vmware guru. [VMWare] [SharedNetworkWithServices] router VM deployment fails with error Message: Invalid configuration for device '2'. --- Key: CLOUDSTACK-3010 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3010 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Environment: commit # 971c40d98e07ab6cddb8e6db5095c1acea935815 Reporter: venkata swamybabu budumuru Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 Attachments: logs.setup1.tgz, logs.setup2.tgz, logs.tgz Steps to reproduce : 1. Have latest CloudStack setup with advanced zone using VMware cluster (1 host added to the cluster) 2. create a shared network with all services enabled mysql select * from network_offerings where id=14\G *** 1. row *** id: 14 name: CustomSharedOffering uuid: dbee9234-e443-4f00-827e-e9258bb0c209 unique_name: CustomSharedOffering display_text: CustomSharedOffering nw_rate: NULL mc_rate: 10 traffic_type: Guest tags: NULL system_only: 0 specify_vlan: 1 service_offering_id: NULL conserve_mode: 0 created: 2013-06-14 14:34:10 removed: NULL default: 0 availability: Optional dedicated_lb_service: 1 shared_source_nat_service: 0 sort_key: 0 redundant_router_service: 0 state: Enabled guest_type: Shared elastic_ip_service: 0 eip_associate_public_ip: 0 elastic_lb_service: 0 specify_ip_ranges: 1 inline: 0 is_persistent: 0 internal_lb: 0 public_lb: 1 mysql select * from ntwk_offering_service_map where network_offering_id=14; ++-++---+-+ | id | network_offering_id | service| provider | created | ++-++---+-+ | 48 | 14 | Dhcp | VirtualRouter | 2013-06-14 14:34:10 | | 52 | 14 | Dns| VirtualRouter | 2013-06-14 14:34:10 | | 51 | 14 | Firewall | VirtualRouter | 2013-06-14 14:34:10 | | 49 | 14 | Lb | VirtualRouter | 2013-06-14 14:34:10 | | 53 | 14 | PortForwarding | VirtualRouter | 2013-06-14 14:34:10 | | 46 | 14 | SourceNat | VirtualRouter | 2013-06-14 14:34:10 | | 50 | 14 | StaticNat | VirtualRouter |
[jira] [Updated] (CLOUDSTACK-4139) [VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-4139:
Priority: Major (was: Critical)
[VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
Key: CLOUDSTACK-4139
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4139
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster with Zone wide primary storage
2. Deploy instance
3. Create snapshot from ROOT volume
4. Attach the volume to an instance
5. Tried to resize the volume from 2 GB to 5 GB .
Observation:
1. It Failed to resize the volumes which are created from snapshot .
2. Task notification says resize is completed from UI but it failed and no
resize happened for this volume
3. I could resize the DATA volumes which are added by using the disk offering
and attached to the instance.
2013-08-07 16:37:31,370 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-785: Sending Seq 3-785: { Ans: ,
MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-07 16:37:33,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,296 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-21:null) submit async job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ], details: AsyncJobVO {id:49, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:480c853c-e70a-46a0-a6d6-ae74b416f318,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375873540089,ctxAccountId:3,diskofferingid:34443d4d-f29c-4d3f-8bb6-f6ae76e34b0d,ctxStartEventId:182},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 16:37:33,301 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,342 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]
2013-08-07 16:37:33,488 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Access to
Vol[35|vm=16|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Sending { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Executing: { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,557 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-32:null) Seq 2-1287389738: Executing request
[jira] [Commented] (CLOUDSTACK-4139) [VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743071#comment-13743071
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4139:
-
Since we have a workaround, which is to detach the volume created from a
snapshot and resize it, and then reattach it to the VM, downgrading the
priority of this bug from critical to major.
[VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
Key: CLOUDSTACK-4139
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4139
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster with Zone wide primary storage
2. Deploy instance
3. Create snapshot from ROOT volume
4. Attach the volume to an instance
5. Tried to resize the volume from 2 GB to 5 GB .
Observation:
1. It Failed to resize the volumes which are created from snapshot .
2. Task notification says resize is completed from UI but it failed and no
resize happened for this volume
3. I could resize the DATA volumes which are added by using the disk offering
and attached to the instance.
2013-08-07 16:37:31,370 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-785: Sending Seq 3-785: { Ans: ,
MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-07 16:37:33,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,296 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-21:null) submit async job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ], details: AsyncJobVO {id:49, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:480c853c-e70a-46a0-a6d6-ae74b416f318,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375873540089,ctxAccountId:3,diskofferingid:34443d4d-f29c-4d3f-8bb6-f6ae76e34b0d,ctxStartEventId:182},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 16:37:33,301 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,342 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]
2013-08-07 16:37:33,488 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Access to
Vol[35|vm=16|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Sending { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Executing: { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[jira] [Commented] (CLOUDSTACK-4139) [VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741606#comment-13741606
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4139:
-
The root cause is that vmware's vi sdk API importVApp() creates a VM with an
IDE disk. I tried deploying the ovf created from a cloudstack generated
snapshot of the volume to confirm this and the VM that got created had an IDE
disk instead of SCSI.
Looked to see if there is a way to tell importVApp() to create a SCSI disk
instead of IDE but haven't found one yet. If there is no way to do this, the
fix would be to edit the vmdk file after the importVApp() successfully creates
the volume and CS detaches it from the worker VM.
[VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
Key: CLOUDSTACK-4139
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4139
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster with Zone wide primary storage
2. Deploy instance
3. Create snapshot from ROOT volume
4. Attach the volume to an instance
5. Tried to resize the volume from 2 GB to 5 GB .
Observation:
1. It Failed to resize the volumes which are created from snapshot .
2. Task notification says resize is completed from UI but it failed and no
resize happened for this volume
3. I could resize the DATA volumes which are added by using the disk offering
and attached to the instance.
2013-08-07 16:37:31,370 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-785: Sending Seq 3-785: { Ans: ,
MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-07 16:37:33,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,296 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-21:null) submit async job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ], details: AsyncJobVO {id:49, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:480c853c-e70a-46a0-a6d6-ae74b416f318,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375873540089,ctxAccountId:3,diskofferingid:34443d4d-f29c-4d3f-8bb6-f6ae76e34b0d,ctxStartEventId:182},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 16:37:33,301 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,342 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]
2013-08-07 16:37:33,488 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Access to
Vol[35|vm=16|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Sending { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 =
[jira] [Commented] (CLOUDSTACK-4194) Failed to detach volume after it got resized
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739380#comment-13739380
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4194:
-
Hi Sailaja,
Sure, I will mark this as resolved instead. Please reopen if you run into it
with the latest builds.
Regards,
Vijay
Failed to detach volume after it got resized
Key: CLOUDSTACK-4194
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4194
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Upgrade, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Labels: integration-test
Fix For: 4.2.0
Attachments: apilog.log, db.dmp, management-server.log
Setup : Upgraded from 2.2.14 to 4.2
1. Configure Adv Zone with VMWARE cluster of 4.1 hosts
2. Upgrade from 2.2.14 to 4.2
3. Create DATA volume with small disk offering
4. Attach the volume to an instance
5. Resize the volume from 5 GB to 20 GB
6. Tried to detach after it for resized
Observation:
Failed to detach volume after it got resized
2013-08-08 22:18:16,003 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,031 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-5:null) submit async job-107 = [
a29ebaae-b392-4ffc-be29-184d7233d0e4 ], details: AsyncJobVO {id:107, userId:
2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 1153,
cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,sessionkey:AHzQuwtysq/QRF50wMgI/7ukyrU\u003d,cmdEventType:VOLUME.DETACH,ctxUserId:2,httpmethod:GET,_:1375980069954,ctxAccountId:2,ctxStartEventId:391},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90310994128556,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-08 22:18:16,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,035 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ])
Executing org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for
job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Sending { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1, Flags:
100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Executing: { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,072 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-230:null) Seq 1-475268002: Executing request
2013-08-08 22:18:16,072 DEBUG [vmware.mo.HostMO]
[jira] [Resolved] (CLOUDSTACK-4194) Failed to detach volume after it got resized
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4194.
-
Resolution: Fixed
Failed to detach volume after it got resized
Key: CLOUDSTACK-4194
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4194
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Upgrade, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Labels: integration-test
Fix For: 4.2.0
Attachments: apilog.log, db.dmp, management-server.log
Setup : Upgraded from 2.2.14 to 4.2
1. Configure Adv Zone with VMWARE cluster of 4.1 hosts
2. Upgrade from 2.2.14 to 4.2
3. Create DATA volume with small disk offering
4. Attach the volume to an instance
5. Resize the volume from 5 GB to 20 GB
6. Tried to detach after it for resized
Observation:
Failed to detach volume after it got resized
2013-08-08 22:18:16,003 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,031 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-5:null) submit async job-107 = [
a29ebaae-b392-4ffc-be29-184d7233d0e4 ], details: AsyncJobVO {id:107, userId:
2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 1153,
cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,sessionkey:AHzQuwtysq/QRF50wMgI/7ukyrU\u003d,cmdEventType:VOLUME.DETACH,ctxUserId:2,httpmethod:GET,_:1375980069954,ctxAccountId:2,ctxStartEventId:391},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90310994128556,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-08 22:18:16,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,035 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ])
Executing org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for
job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Sending { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1, Flags:
100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Executing: { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,072 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-230:null) Seq 1-475268002: Executing request
2013-08-08 22:18:16,072 DEBUG [vmware.mo.HostMO]
(DirectAgent-230:10.102.192.17) find VM i-2-1131-VM on host
2013-08-08 22:18:16,072 INFO [vmware.mo.HostMO]
(DirectAgent-230:10.102.192.17) VM i-2-1131-VM not found in
[jira] [Commented] (CLOUDSTACK-4139) [VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740548#comment-13740548
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4139:
-
I see this happening with volumes that are created from snapshots of either
root or data volumes.
Was speaking with Kelven regarding this issue and observed that this is what is
happening:
1) We create a data volume, a directory gets created in secondary storage. No
vmdk gets deployed yet.
2) We then attach the volume to a VM, and that is when the volume gets created
on primary. Its vmdk shows the disk controller as scsi:
.
.ddb.thinProvisioned = 1
ddb.adapterType = lsilogic
3) Then we create a snapshot from this volume. The snapshot gets created on
secondary storage as expected, and its vmdk also shows the controller type as
scsi:
.
.
# The Disk Data Base
#DDB
ddb.adapterType = lsilogic
ddb.geometry.cylinders = 652
.
.
So far, all is good.
4) Create a volume from the snapshot. This will create the volume on the
primary, but then its disk controller type is getting set to IDE instead of
SCSI:
.
.
# The Disk Data Base
#DDB
ddb.adapterType = ide
ddb.thinProvisioned = 1
ddb.geometry.sectors = 63
.
.
This IDE setting is causing the invalid disk backing info exception. vCenter
expects this to be a SCSI disk.
If I detach the volume from the VM, and then resize it, it uses a worker VM
that doesn't pass in the controller type in the backing info and so the disk
resize passes through fine. The disk can then be attached to the original VM.
This is a workaround.
As of now, am not sure why the disk controller is getting set to IDE. The
restoreVolumeFromSecStorage() function in VmwareStorageProcessor.java is the
exact point where this volume is created from a snapshot. Need to dig into
where in this code path the controller setting is getting changed. The metadata
files are copied over in moveAllVmDiskFiles(), so probably the problem lies
somewhere in there.
[VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
Key: CLOUDSTACK-4139
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4139
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster with Zone wide primary storage
2. Deploy instance
3. Create snapshot from ROOT volume
4. Attach the volume to an instance
5. Tried to resize the volume from 2 GB to 5 GB .
Observation:
1. It Failed to resize the volumes which are created from snapshot .
2. Task notification says resize is completed from UI but it failed and no
resize happened for this volume
3. I could resize the DATA volumes which are added by using the disk offering
and attached to the instance.
2013-08-07 16:37:31,370 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-785: Sending Seq 3-785: { Ans: ,
MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-07 16:37:33,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,296 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-21:null) submit async job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ], details: AsyncJobVO {id:49, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:480c853c-e70a-46a0-a6d6-ae74b416f318,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375873540089,ctxAccountId:3,diskofferingid:34443d4d-f29c-4d3f-8bb6-f6ae76e34b0d,ctxStartEventId:182},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 16:37:33,301 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===END=== 10.144.6.19 -- GET
[jira] [Commented] (CLOUDSTACK-4139) [VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740549#comment-13740549
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4139:
-
Also, Anthony pointed out that this line in the log excerpt:
Disk backing : [004a6f4c232c3a099013e47fe47da3fb]
e9166262ee514a398028c04bf21d80b7.vmdk matches == scsi0:0
should be looked at closer, because why is that disk's numbering 0:0 ? It
should be 0:1 since it's an additional volume for an existing VM.
[VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
Key: CLOUDSTACK-4139
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4139
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster with Zone wide primary storage
2. Deploy instance
3. Create snapshot from ROOT volume
4. Attach the volume to an instance
5. Tried to resize the volume from 2 GB to 5 GB .
Observation:
1. It Failed to resize the volumes which are created from snapshot .
2. Task notification says resize is completed from UI but it failed and no
resize happened for this volume
3. I could resize the DATA volumes which are added by using the disk offering
and attached to the instance.
2013-08-07 16:37:31,370 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-785: Sending Seq 3-785: { Ans: ,
MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-07 16:37:33,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,296 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-21:null) submit async job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ], details: AsyncJobVO {id:49, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:480c853c-e70a-46a0-a6d6-ae74b416f318,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375873540089,ctxAccountId:3,diskofferingid:34443d4d-f29c-4d3f-8bb6-f6ae76e34b0d,ctxStartEventId:182},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 16:37:33,301 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,342 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]
2013-08-07 16:37:33,488 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Access to
Vol[35|vm=16|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Sending { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Executing: { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[jira] [Commented] (CLOUDSTACK-4194) Failed to detach volume after it got resized
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738943#comment-13738943
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4194:
-
I don't see this issue on the latest 4.2 branch - Kelven had checked in changes
for datastore organization and those changes probably fixed this issue. Marking
as could not reproduce. Please reopen if you see it happening on latest builds.
The 4.2 tree I tested this with is on commit #
36cd824ba721ddbbee3f405a15d53702b22a113e
Failed to detach volume after it got resized
Key: CLOUDSTACK-4194
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4194
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Upgrade, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Labels: integration-test
Fix For: 4.2.0
Attachments: apilog.log, db.dmp, management-server.log
Setup : Upgraded from 2.2.14 to 4.2
1. Configure Adv Zone with VMWARE cluster of 4.1 hosts
2. Upgrade from 2.2.14 to 4.2
3. Create DATA volume with small disk offering
4. Attach the volume to an instance
5. Resize the volume from 5 GB to 20 GB
6. Tried to detach after it for resized
Observation:
Failed to detach volume after it got resized
2013-08-08 22:18:16,003 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,031 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-5:null) submit async job-107 = [
a29ebaae-b392-4ffc-be29-184d7233d0e4 ], details: AsyncJobVO {id:107, userId:
2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 1153,
cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,sessionkey:AHzQuwtysq/QRF50wMgI/7ukyrU\u003d,cmdEventType:VOLUME.DETACH,ctxUserId:2,httpmethod:GET,_:1375980069954,ctxAccountId:2,ctxStartEventId:391},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90310994128556,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-08 22:18:16,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,035 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ])
Executing org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for
job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Sending { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1, Flags:
100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Executing: { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1,
Flags: 100011,
[jira] [Resolved] (CLOUDSTACK-4194) Failed to detach volume after it got resized
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4194.
-
Resolution: Cannot Reproduce
Failed to detach volume after it got resized
Key: CLOUDSTACK-4194
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4194
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Upgrade, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Labels: integration-test
Fix For: 4.2.0
Attachments: apilog.log, db.dmp, management-server.log
Setup : Upgraded from 2.2.14 to 4.2
1. Configure Adv Zone with VMWARE cluster of 4.1 hosts
2. Upgrade from 2.2.14 to 4.2
3. Create DATA volume with small disk offering
4. Attach the volume to an instance
5. Resize the volume from 5 GB to 20 GB
6. Tried to detach after it for resized
Observation:
Failed to detach volume after it got resized
2013-08-08 22:18:16,003 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,031 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-5:null) submit async job-107 = [
a29ebaae-b392-4ffc-be29-184d7233d0e4 ], details: AsyncJobVO {id:107, userId:
2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 1153,
cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,sessionkey:AHzQuwtysq/QRF50wMgI/7ukyrU\u003d,cmdEventType:VOLUME.DETACH,ctxUserId:2,httpmethod:GET,_:1375980069954,ctxAccountId:2,ctxStartEventId:391},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90310994128556,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-08 22:18:16,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,035 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ])
Executing org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for
job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Sending { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1, Flags:
100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Executing: { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,072 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-230:null) Seq 1-475268002: Executing request
2013-08-08 22:18:16,072 DEBUG [vmware.mo.HostMO]
(DirectAgent-230:10.102.192.17) find VM i-2-1131-VM on host
2013-08-08 22:18:16,072 INFO [vmware.mo.HostMO]
(DirectAgent-230:10.102.192.17) VM i-2-1131-VM not
[jira] [Resolved] (CLOUDSTACK-4143) [VMWARE] Resize request sent for the volumes which are not attached to the instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4143.
-
Resolution: Fixed
[VMWARE] Resize request sent for the volumes which are not attached to the
instance
Key: CLOUDSTACK-4143
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4143
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster
2. Deploy instance
3. Add Data disk with 5 GB offering and attach to the instance
4. Resize works fine when it is attached to the instance
5. Detach the DATA volume
6. State of the DATA volume is ready and VM ID is none for this volume.
7. From UI i get to see resize option for this detached volume
8. Try to resize this volume from 5 GB to 20 GB.
Notes :Even for Volumes which are created from snapshots would be in
ready state . I think we are letting resize to be sent if the state of the
volume is Ready. We should sent the request only if the volume has VM ID .
It failed as :
2013-08-07 17:55:19,878 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=98b2a53b-1475-4658-a874-cf5c911e0fafshrinkok=falsediskofferingid=ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88size=27response=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375878539230
2013-08-07 17:55:19,913 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-1:null) submit async job-81 = [
7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ], details: AsyncJobVO {id:81, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:98b2a53b-1475-4658-a874-cf5c911e0faf,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375878539230,ctxAccountId:3,diskofferingid:ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88,ctxStartEventId:286,size:27},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 17:55:19,916 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=98b2a53b-1475-4658-a874-cf5c911e0fafshrinkok=falsediskofferingid=ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88size=27response=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375878539230
2013-08-07 17:55:19,918 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-81 = [
7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]
2013-08-07 17:55:19,949 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Access to
Vol[38|vm=null|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 17:55:20,103 DEBUG [agent.transport.Request]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq
1-1575617095: Sending { Cmd , MgmtId: 187767034175903, via: 1, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:6344e3d83b6541ec863aaa6cd19fd66b,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:none,newSize:28991029248,currentSize:27917287424,shrinkOk:false,wait:0}}]
}
2013-08-07 17:55:20,104 DEBUG [agent.transport.Request]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq
1-1575617095: Executing: { Cmd , MgmtId: 187767034175903, via: 1, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:6344e3d83b6541ec863aaa6cd19fd66b,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:none,newSize:28991029248,currentSize:27917287424,shrinkOk:false,wait:0}}]
}
2013-08-07 17:55:20,110 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-148:null) Seq 1-1575617095: Executing request
2013-08-07 17:55:20,146 ERROR [vmware.resource.VmwareResource]
(DirectAgent-148:10.102.192.23) VM
[jira] [Commented] (CLOUDSTACK-4143) [VMWARE] Resize request sent for the volumes which are not attached to the instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739157#comment-13739157
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4143:
-
Fix committed to 4.2 in commit :
Commit c850f0a0e3749090fe5ed7d5c410bf10d06b2281 in branch refs/heads/4.2 from
[~vijayendrabvs]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c850f0a ]
CLOUDSTACK-4139: [VMWARE][ZWPS] Failed to resize the volumes which are created
from snapshot
Description:
Support offline volume resize on ESX by creating a worker VM
to attach the unattached volume to and then resize it.
I entered the wrong bug ID in the commit message - will mention this in a
future commit when fixing 4139, apologies.
[VMWARE] Resize request sent for the volumes which are not attached to the
instance
Key: CLOUDSTACK-4143
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4143
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster
2. Deploy instance
3. Add Data disk with 5 GB offering and attach to the instance
4. Resize works fine when it is attached to the instance
5. Detach the DATA volume
6. State of the DATA volume is ready and VM ID is none for this volume.
7. From UI i get to see resize option for this detached volume
8. Try to resize this volume from 5 GB to 20 GB.
Notes :Even for Volumes which are created from snapshots would be in
ready state . I think we are letting resize to be sent if the state of the
volume is Ready. We should sent the request only if the volume has VM ID .
It failed as :
2013-08-07 17:55:19,878 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=98b2a53b-1475-4658-a874-cf5c911e0fafshrinkok=falsediskofferingid=ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88size=27response=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375878539230
2013-08-07 17:55:19,913 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-1:null) submit async job-81 = [
7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ], details: AsyncJobVO {id:81, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:98b2a53b-1475-4658-a874-cf5c911e0faf,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375878539230,ctxAccountId:3,diskofferingid:ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88,ctxStartEventId:286,size:27},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 17:55:19,916 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=98b2a53b-1475-4658-a874-cf5c911e0fafshrinkok=falsediskofferingid=ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88size=27response=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375878539230
2013-08-07 17:55:19,918 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-81 = [
7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]
2013-08-07 17:55:19,949 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Access to
Vol[38|vm=null|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 17:55:20,103 DEBUG [agent.transport.Request]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq
1-1575617095: Sending { Cmd , MgmtId: 187767034175903, via: 1, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:6344e3d83b6541ec863aaa6cd19fd66b,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:none,newSize:28991029248,currentSize:27917287424,shrinkOk:false,wait:0}}]
}
2013-08-07 17:55:20,104 DEBUG [agent.transport.Request]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq
1-1575617095: Executing: { Cmd ,
[jira] [Assigned] (CLOUDSTACK-4194) Failed to detach volume after it got resized
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4194:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
Failed to detach volume after it got resized
Key: CLOUDSTACK-4194
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4194
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Upgrade, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Labels: integration-test
Fix For: 4.2.0
Attachments: apilog.log, db.dmp, management-server.log
Setup : Upgraded from 2.2.14 to 4.2
1. Configure Adv Zone with VMWARE cluster of 4.1 hosts
2. Upgrade from 2.2.14 to 4.2
3. Create DATA volume with small disk offering
4. Attach the volume to an instance
5. Resize the volume from 5 GB to 20 GB
6. Tried to detach after it for resized
Observation:
Failed to detach volume after it got resized
2013-08-08 22:18:16,003 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,031 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-5:null) submit async job-107 = [
a29ebaae-b392-4ffc-be29-184d7233d0e4 ], details: AsyncJobVO {id:107, userId:
2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 1153,
cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,sessionkey:AHzQuwtysq/QRF50wMgI/7ukyrU\u003d,cmdEventType:VOLUME.DETACH,ctxUserId:2,httpmethod:GET,_:1375980069954,ctxAccountId:2,ctxStartEventId:391},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90310994128556,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-08 22:18:16,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.104.255.13 -- GET
command=detachVolumeid=2f7e7b87-30c2-4677-a5db-ed0aafdb49ebresponse=jsonsessionkey=AHzQuwtysq%2FQRF50wMgI%2F7ukyrU%3D_=1375980069954
2013-08-08 22:18:16,035 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ])
Executing org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for
job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Sending { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1, Flags:
100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,071 DEBUG [agent.transport.Request]
(Job-Executor-25:job-107 = [ a29ebaae-b392-4ffc-be29-184d7233d0e4 ]) Seq
1-475268002: Executing: { Cmd , MgmtId: 90310994128556, via: 1, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DettachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:2f7e7b87-30c2-4677-a5db-ed0aafdb49eb,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:3f4c460a-1634-3db0-8b1f-60fe7b17a264,id:202,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/esx-pri2,port:2049}},name:newsailaja3,size:6442450944,path:daa2d8dac9b8467abd5b670b2559ed46,volumeId:1153,vmName:i-2-1131-VM,accountId:2,format:OVA,id:1153,hypervisorType:VMware}},diskSeq:7,type:DATADISK},vmName:i-2-1131-VM,_managed:false,_storageHost:10.102.192.100,_storagePort:2049,wait:0}}]
}
2013-08-08 22:18:16,072 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-230:null) Seq 1-475268002: Executing request
2013-08-08 22:18:16,072 DEBUG [vmware.mo.HostMO]
(DirectAgent-230:10.102.192.17) find VM i-2-1131-VM on host
2013-08-08 22:18:16,072 INFO [vmware.mo.HostMO]
[jira] [Assigned] (CLOUDSTACK-4143) [VMWARE] Resize request sent for the volumes which are not attached to the instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4143:
---
Assignee: Venkata Siva Vijayendra Bhamidipati (was: Sateesh Chodapuneedi)
[VMWARE] Resize request sent for the volumes which are not attached to the
instance
Key: CLOUDSTACK-4143
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4143
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster
2. Deploy instance
3. Add Data disk with 5 GB offering and attach to the instance
4. Resize works fine when it is attached to the instance
5. Detach the DATA volume
6. State of the DATA volume is ready and VM ID is none for this volume.
7. From UI i get to see resize option for this detached volume
8. Try to resize this volume from 5 GB to 20 GB.
Notes :Even for Volumes which are created from snapshots would be in
ready state . I think we are letting resize to be sent if the state of the
volume is Ready. We should sent the request only if the volume has VM ID .
It failed as :
2013-08-07 17:55:19,878 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=98b2a53b-1475-4658-a874-cf5c911e0fafshrinkok=falsediskofferingid=ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88size=27response=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375878539230
2013-08-07 17:55:19,913 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-1:null) submit async job-81 = [
7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ], details: AsyncJobVO {id:81, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:98b2a53b-1475-4658-a874-cf5c911e0faf,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375878539230,ctxAccountId:3,diskofferingid:ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88,ctxStartEventId:286,size:27},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 17:55:19,916 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=98b2a53b-1475-4658-a874-cf5c911e0fafshrinkok=falsediskofferingid=ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88size=27response=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375878539230
2013-08-07 17:55:19,918 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-81 = [
7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]
2013-08-07 17:55:19,949 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Access to
Vol[38|vm=null|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 17:55:20,103 DEBUG [agent.transport.Request]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq
1-1575617095: Sending { Cmd , MgmtId: 187767034175903, via: 1, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:6344e3d83b6541ec863aaa6cd19fd66b,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:none,newSize:28991029248,currentSize:27917287424,shrinkOk:false,wait:0}}]
}
2013-08-07 17:55:20,104 DEBUG [agent.transport.Request]
(Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq
1-1575617095: Executing: { Cmd , MgmtId: 187767034175903, via: 1, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:6344e3d83b6541ec863aaa6cd19fd66b,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:none,newSize:28991029248,currentSize:27917287424,shrinkOk:false,wait:0}}]
}
2013-08-07 17:55:20,110 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-148:null) Seq 1-1575617095: Executing request
2013-08-07 17:55:20,146 ERROR
[jira] [Assigned] (CLOUDSTACK-4139) [VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4139:
---
Assignee: Venkata Siva Vijayendra Bhamidipati (was: Sateesh Chodapuneedi)
[VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot
Key: CLOUDSTACK-4139
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4139
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster with Zone wide primary storage
2. Deploy instance
3. Create snapshot from ROOT volume
4. Attach the volume to an instance
5. Tried to resize the volume from 2 GB to 5 GB .
Observation:
1. It Failed to resize the volumes which are created from snapshot .
2. Task notification says resize is completed from UI but it failed and no
resize happened for this volume
3. I could resize the DATA volumes which are added by using the disk offering
and attached to the instance.
2013-08-07 16:37:31,370 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-785: Sending Seq 3-785: { Ans: ,
MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-07 16:37:33,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,296 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-21:null) submit async job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ], details: AsyncJobVO {id:49, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:480c853c-e70a-46a0-a6d6-ae74b416f318,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375873540089,ctxAccountId:3,diskofferingid:34443d4d-f29c-4d3f-8bb6-f6ae76e34b0d,ctxStartEventId:182},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 16:37:33,301 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,342 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]
2013-08-07 16:37:33,488 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Access to
Vol[35|vm=16|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Sending { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Executing: { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,557 DEBUG
[jira] [Commented] (CLOUDSTACK-2535) Cleanup port-profiles that gets created on Nexus switch as part of network cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735625#comment-13735625 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2535: - Cleaning up port profiles isn't a high priority in cloud orchestration. Infact keeping them around is probably time saving during orchestration. Having port profiles on a vSwitch or a VEM or VSS doesn't consume resources - it's only when a vNIC is associated with a port profile that ports are used up on the switching modules. I don't think this is a critical issue, even if we were to clean up the profiles. Cleanup port-profiles that gets created on Nexus switch as part of network cleanup -- Key: CLOUDSTACK-2535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: pre-4.0.0, 4.0.0 Environment: Vmware Reporter: Koushik Das Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.2.0 Port profiles are not cleaned up when a guest network using it gets removed. As part of network shutdown all port profiles that got created on the Nexus switch should be removed. The same problem is also there for vSwitch and dvSwitch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2535) Cleanup port-profiles that gets created on Nexus switch as part of network cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-2535: Priority: Minor (was: Critical) Cleanup port-profiles that gets created on Nexus switch as part of network cleanup -- Key: CLOUDSTACK-2535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: pre-4.0.0, 4.0.0 Environment: Vmware Reporter: Koushik Das Assignee: Sateesh Chodapuneedi Priority: Minor Fix For: 4.2.0 Port profiles are not cleaned up when a guest network using it gets removed. As part of network shutdown all port profiles that got created on the Nexus switch should be removed. The same problem is also there for vSwitch and dvSwitch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4167) Put in upgrade paths in master for 4.1.2 and 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4167. - Resolution: Fixed Put in upgrade paths in master for 4.1.2 and 4.2 Key: CLOUDSTACK-4167 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4167 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Minor In 4.1 branch, the latest version is 4.1.2. So the upgrade path on 4.1 now will go thus: 4.0.0 - 4.1.0 - 4.1.1 - 4.1.2. Now, on the 4.2 branch, it goes thus: 4.0.0 - 4.1.0 - 4.2.0 At this point in time, neither 4.2.0 nor 4.1.2 have been released. It is unclear which will get released first. If 4.1.2 gets released before 4.2.0, we'll need to define an empty upgrade path from 4.1.0 to 4.1.2 first, and then another empty upgrade path from 4.1.2 to 4.2.0. If 4.2.0 gets released before 4.1.2, we will need to define an upgrade path from 4.2.0 to 4.1.2 and then another path from 4.1.2 to 4.2.0. Again there won't really be any SQL operations to do in these two paths. Putting in these upgrade paths tells us which version got released after which. In case there are any SQL changes that need to be made, we must put those in as well. In any case, the final version when upgrading to 4.2.0 will end up at 4.2.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3609) ASF 4.1 to 4.2 Upgrade: Invalid Global Configuration parameters are present on the Upgraded Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3609. - Resolution: Fixed ASF 4.1 to 4.2 Upgrade: Invalid Global Configuration parameters are present on the Upgraded Setup - Key: CLOUDSTACK-3609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3609 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: Chandan Purushothama Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 Attachments: DBCapture-3.PNG Attached the screenshot of the invalid global parameters to the bug report. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731698#comment-13731698 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4055: - If this bug has to be kept open, I'll mark the priority downward to minor for now, for there is little we can do from cloudstack's perspective. Windows Server 2012 (64-Bit) being deployed as 'Other OS' type -- Key: CLOUDSTACK-4055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Ahmad Emneina Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 Attachments: win2012_other_os.png Registered a Windows Server 2012 64-bit template in ACS and made sure Windows Server 2012 (64-Bit) was selected as the OS type when registering the template, however when we build an instance in CS it creates the OS type in VMware as Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS type is an available option in VMware. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-4055: Priority: Minor (was: Critical) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type -- Key: CLOUDSTACK-4055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Ahmad Emneina Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Minor Fix For: 4.2.0 Attachments: win2012_other_os.png Registered a Windows Server 2012 64-bit template in ACS and made sure Windows Server 2012 (64-Bit) was selected as the OS type when registering the template, however when we build an instance in CS it creates the OS type in VMware as Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS type is an available option in VMware. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4155) [VMWARE] Failed to deploy VM with NPE when vmware.nested.virtualization is enabled to true
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4155:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
[VMWARE] Failed to deploy VM with NPE when vmware.nested.virtualization is
enabled to true
---
Key: CLOUDSTACK-4155
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4155
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv Zone with VMWARE ESXi cluster
2. Enable global config vmware.nested.virtualization to true
3. Tried to deploy VM.
Observation:
Failed to deploy VM with NPE when vmware.nested.virtualization is enabled
to true
2013-08-07 21:34:22,613 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.104.255.13 -- GET
command=queryAsyncJobResultjobId=1888c4da-c2ef-44c4-aa54-2b161cc512cbresponse=jsonsessionkey=4wP3DoqOfQnbpv7fDOUY9C8LFmc%3D_=1375891672478
2013-08-07 21:34:22,637 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.104.255.13 -- GET
command=queryAsyncJobResultjobId=1888c4da-c2ef-44c4-aa54-2b161cc512cbresponse=jsonsessionkey=4wP3DoqOfQnbpv7fDOUY9C8LFmc%3D_=1375891672478
2013-08-07 21:34:22,766 DEBUG [vmware.mo.HostMO]
(DirectAgent-49:10.102.192.23) find VM i-3-22-VM on host
2013-08-07 21:34:22,766 DEBUG [vmware.mo.HostMO]
(DirectAgent-49:10.102.192.23) load VM cache on host
2013-08-07 21:34:23,129 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-12:null) SeqA 3-3012: Processing Seq 3-3012: { Cmd ,
MgmtId: -1, via: 3, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:15,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2013-08-07 21:34:23,142 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-12:null) SeqA 3-3012: Sending Seq 3-3012: { Ans: ,
MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-07 21:34:23,156 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-49:10.102.192.23) Nested Virtualization enabled in
configuration, checking hypervisor capability
2013-08-07 21:34:23,180 WARN [vmware.resource.VmwareResource]
(DirectAgent-49:10.102.192.23) StartCommand failed due to Exception:
java.lang.NullPointerException
Message: null
java.lang.NullPointerException
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2683)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:518)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-08-07 21:34:23,182 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-49:null) Seq 1-1674641481: Response Received:
2013-08-07 21:34:23,184 DEBUG [agent.transport.Request] (DirectAgent-49:null)
Seq 1-1674641481: Processing: { Ans: , MgmtId: 187767034175903, via: 1, Ver:
v1, Flags: 10,
[{com.cloud.agent.api.StartAnswer:{vm:{id:22,name:i-3-22-VM,bootloader:HVM,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:536870912,maxRam:536870912,arch:x86_64,os:CentOS
5.3
[jira] [Resolved] (CLOUDSTACK-3886) VM name on vCenter not getting set correctly when vm.instancename.flag is set to true
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3886. - Resolution: Fixed VM name on vCenter not getting set correctly when vm.instancename.flag is set to true - Key: CLOUDSTACK-3886 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3886 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Vmware deployment in cloudstack. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 In a vmware deployment on cloudstack, if the vm.instancename.flag is set to true, and a displayname is supplied during VM creation, the displayname simply gets appended to the internal name i-x-y of that VM in vCenter. The expected behaviour is this: If the vm.instancename.flag is set to false (default), there is no change in current behavior: 1. If hostname isn't supplied, it is set to the uuid. 2. If displayname is supplied, it shows up in the GUI. If not, it is set to the internal VM name i-x-y-VM. If the vm.instancename.flag is set to true: 1. If hostname is not supplied, and displayname is supplied, set hostname to displayname, and set the instance name as it appears on vCenter also, to the displayname. 2. If hostname is not supplied, and displayname is also not supplied, set hostname to uuid, but set internal name of the VM as it appears on vCenter to i-x-y-VM as is done currently. 3. If hostname is supplied, set the instance name as it appears on vCenter to this hostname. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4091) 4.1 fresh install doesn't work in dev environment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4091. - Resolution: Fixed 4.1 fresh install doesn't work in dev environment -- Key: CLOUDSTACK-4091 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4091 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.1 Environment: This is a fresh installation of the mgmt server in a dev environment on top of the latest 4.1 branch. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.1.1 The compilation goes through, but the mgmt server fails to come up with the following error: . . INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker encryptionSecretKeyChecker INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseIntegrityChecker INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to check for database integrity. INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database integrity check INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker managementServerNode INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseUpgradeChecker INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to check for database upgrade. INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 Code Version = 4.1.2-SNAPSHOT INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must be performed from 4.0.0 to 4.1.2-SNAPSHOT ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade version is actually at 4.1.1 but our management server code version is at 4.1.2-SNAPSHOT ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check failed. Refuse to startup 2013-08-02 09:40:39.356:INFO::Shutdown hook executing 2013-08-02 09:40:39.357:INFO::Stopped SelectChannelConnector@0.0.0.0:8080 2013-08-02 09:40:39.862:INFO:/client:Closing Spring root WebApplicationContext . . mysql select * from db_version; ERROR 1146 (42S02): Table 'cloud.db_version' doesn't exist mysql select * from version; ++-+-+--+ | id | version | updated | step | ++-+-+--+ | 1 | 4.0.0 | 2013-08-02 09:38:16 | Complete | ++-+-+--+ 1 row in set (0.01 sec) mysql -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-4167) Put in upgrade paths in master for 4.1.2 and 4.2
Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-4167: --- Summary: Put in upgrade paths in master for 4.1.2 and 4.2 Key: CLOUDSTACK-4167 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4167 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Minor In 4.1 branch, the latest version is 4.1.2. So the upgrade path on 4.1 now will go thus: 4.0.0 - 4.1.0 - 4.1.1 - 4.1.2. Now, on the 4.2 branch, it goes thus: 4.0.0 - 4.1.0 - 4.2.0 At this point in time, neither 4.2.0 nor 4.1.2 have been released. It is unclear which will get released first. If 4.1.2 gets released before 4.2.0, we'll need to define an empty upgrade path from 4.1.0 to 4.1.2 first, and then another empty upgrade path from 4.1.2 to 4.2.0. If 4.2.0 gets released before 4.1.2, we will need to define an upgrade path from 4.2.0 to 4.1.2 and then another path from 4.1.2 to 4.2.0. Again there won't really be any SQL operations to do in these two paths. Putting in these upgrade paths tells us which version got released after which. In case there are any SQL changes that need to be made, we must put those in as well. In any case, the final version when upgrading to 4.2.0 will end up at 4.2.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-4055: Fix Version/s: (was: 4.2.0) Future Windows Server 2012 (64-Bit) being deployed as 'Other OS' type -- Key: CLOUDSTACK-4055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Ahmad Emneina Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Minor Fix For: Future Attachments: win2012_other_os.png Registered a Windows Server 2012 64-bit template in ACS and made sure Windows Server 2012 (64-Bit) was selected as the OS type when registering the template, however when we build an instance in CS it creates the OS type in VMware as Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS type is an available option in VMware. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3609) ASF 4.1 to 4.2 Upgrade: Invalid Global Configuration parameters are present on the Upgraded Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3609: Status: Ready To Review (was: In Progress) ASF 4.1 to 4.2 Upgrade: Invalid Global Configuration parameters are present on the Upgraded Setup - Key: CLOUDSTACK-3609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3609 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: Chandan Purushothama Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 Attachments: DBCapture-3.PNG Attached the screenshot of the invalid global parameters to the bug report. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3609) ASF 4.1 to 4.2 Upgrade: Invalid Global Configuration parameters are present on the Upgraded Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733089#comment-13733089 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3609: - Patch posted at https://reviews.apache.org/r/13404/ . The patch for 4167 has been posted to the same review request for 4091 : https://reviews.apache.org/r/13298/ ASF 4.1 to 4.2 Upgrade: Invalid Global Configuration parameters are present on the Upgraded Setup - Key: CLOUDSTACK-3609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3609 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: Chandan Purushothama Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 Attachments: DBCapture-3.PNG Attached the screenshot of the invalid global parameters to the bug report. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4167) Put in upgrade paths in master for 4.1.2 and 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-4167: Status: Ready To Review (was: In Progress) Put in upgrade paths in master for 4.1.2 and 4.2 Key: CLOUDSTACK-4167 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4167 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Minor In 4.1 branch, the latest version is 4.1.2. So the upgrade path on 4.1 now will go thus: 4.0.0 - 4.1.0 - 4.1.1 - 4.1.2. Now, on the 4.2 branch, it goes thus: 4.0.0 - 4.1.0 - 4.2.0 At this point in time, neither 4.2.0 nor 4.1.2 have been released. It is unclear which will get released first. If 4.1.2 gets released before 4.2.0, we'll need to define an empty upgrade path from 4.1.0 to 4.1.2 first, and then another empty upgrade path from 4.1.2 to 4.2.0. If 4.2.0 gets released before 4.1.2, we will need to define an upgrade path from 4.2.0 to 4.1.2 and then another path from 4.1.2 to 4.2.0. Again there won't really be any SQL operations to do in these two paths. Putting in these upgrade paths tells us which version got released after which. In case there are any SQL changes that need to be made, we must put those in as well. In any case, the final version when upgrading to 4.2.0 will end up at 4.2.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4167) Put in upgrade paths in master for 4.1.2 and 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733090#comment-13733090 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4167: - Patch posted for review at https://reviews.apache.org/r/13298/ Put in upgrade paths in master for 4.1.2 and 4.2 Key: CLOUDSTACK-4167 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4167 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Minor In 4.1 branch, the latest version is 4.1.2. So the upgrade path on 4.1 now will go thus: 4.0.0 - 4.1.0 - 4.1.1 - 4.1.2. Now, on the 4.2 branch, it goes thus: 4.0.0 - 4.1.0 - 4.2.0 At this point in time, neither 4.2.0 nor 4.1.2 have been released. It is unclear which will get released first. If 4.1.2 gets released before 4.2.0, we'll need to define an empty upgrade path from 4.1.0 to 4.1.2 first, and then another empty upgrade path from 4.1.2 to 4.2.0. If 4.2.0 gets released before 4.1.2, we will need to define an upgrade path from 4.2.0 to 4.1.2 and then another path from 4.1.2 to 4.2.0. Again there won't really be any SQL operations to do in these two paths. Putting in these upgrade paths tells us which version got released after which. In case there are any SQL changes that need to be made, we must put those in as well. In any case, the final version when upgrading to 4.2.0 will end up at 4.2.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4091) 4.1 fresh install doesn't work in dev environment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-4091: Status: Ready To Review (was: In Progress) 4.1 fresh install doesn't work in dev environment -- Key: CLOUDSTACK-4091 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4091 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.1 Environment: This is a fresh installation of the mgmt server in a dev environment on top of the latest 4.1 branch. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.1.1 The compilation goes through, but the mgmt server fails to come up with the following error: . . INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker encryptionSecretKeyChecker INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseIntegrityChecker INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to check for database integrity. INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database integrity check INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker managementServerNode INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseUpgradeChecker INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to check for database upgrade. INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 Code Version = 4.1.2-SNAPSHOT INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must be performed from 4.0.0 to 4.1.2-SNAPSHOT ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade version is actually at 4.1.1 but our management server code version is at 4.1.2-SNAPSHOT ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check failed. Refuse to startup 2013-08-02 09:40:39.356:INFO::Shutdown hook executing 2013-08-02 09:40:39.357:INFO::Stopped SelectChannelConnector@0.0.0.0:8080 2013-08-02 09:40:39.862:INFO:/client:Closing Spring root WebApplicationContext . . mysql select * from db_version; ERROR 1146 (42S02): Table 'cloud.db_version' doesn't exist mysql select * from version; ++-+-+--+ | id | version | updated | step | ++-+-+--+ | 1 | 4.0.0 | 2013-08-02 09:38:16 | Complete | ++-+-+--+ 1 row in set (0.01 sec) mysql -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4091) 4.1 fresh install doesn't work in dev environment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729955#comment-13729955 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4091: - Patch posted for review at https://reviews.apache.org/r/13298/ 4.1 fresh install doesn't work in dev environment -- Key: CLOUDSTACK-4091 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4091 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.1 Environment: This is a fresh installation of the mgmt server in a dev environment on top of the latest 4.1 branch. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.1.1 The compilation goes through, but the mgmt server fails to come up with the following error: . . INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker encryptionSecretKeyChecker INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseIntegrityChecker INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to check for database integrity. INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database integrity check INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker managementServerNode INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseUpgradeChecker INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to check for database upgrade. INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 Code Version = 4.1.2-SNAPSHOT INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must be performed from 4.0.0 to 4.1.2-SNAPSHOT ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade version is actually at 4.1.1 but our management server code version is at 4.1.2-SNAPSHOT ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check failed. Refuse to startup 2013-08-02 09:40:39.356:INFO::Shutdown hook executing 2013-08-02 09:40:39.357:INFO::Stopped SelectChannelConnector@0.0.0.0:8080 2013-08-02 09:40:39.862:INFO:/client:Closing Spring root WebApplicationContext . . mysql select * from db_version; ERROR 1146 (42S02): Table 'cloud.db_version' doesn't exist mysql select * from version; ++-+-+--+ | id | version | updated | step | ++-+-+--+ | 1 | 4.0.0 | 2013-08-02 09:38:16 | Complete | ++-+-+--+ 1 row in set (0.01 sec) mysql -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3905) [VMWARE]Can not add Standard/DVSwitch when Nexus global config is set to true
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728166#comment-13728166 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3905: - The usage of nexus 1000v and vmware dvs are each controlled by their global configuration flags vmware.use.nexus.vswitch and vmware.use.dvswitch respectively. If one is set, the other cannot be used. If both are set, it pretty much boils down to the code that checks for one flag before the other. Currently, the mgmt server doesn't have a way to specify mutual exclusivity between global flags. Either we should put this in, or move these flags from a global config level to the zone level, where explicit code checks can be put in to disallow both flags to be set. [VMWARE]Can not add Standard/DVSwitch when Nexus global config is set to true - Key: CLOUDSTACK-3905 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3905 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.2.0 Steps: 1. Set below Global config parameters to true : vmware.use.dvswitch Enable/Disable Nexus/Vmware dvSwitch in VMware environment true vmware.use.nexus.vswitch Enable/Disable Cisco Nexus 1000v vSwitch in VMware environment true 2. Tried to add Standard vSwitch/DVSwitch Cluster : Observations: 1. Nexus 1000v Switch configuration details are mandatory to add cluster 2. It will not let to add new cluster with DVS/Standard vSwitch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-4055: --- Assignee: Venkata Siva Vijayendra Bhamidipati Windows Server 2012 (64-Bit) being deployed as 'Other OS' type -- Key: CLOUDSTACK-4055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Ahmad Emneina Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 Attachments: win2012_other_os.png Registered a Windows Server 2012 64-bit template in ACS and made sure Windows Server 2012 (64-Bit) was selected as the OS type when registering the template, however when we build an instance in CS it creates the OS type in VMware as Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS type is an available option in VMware. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4055. - Resolution: Won't Fix Windows Server 2012 (64-Bit) being deployed as 'Other OS' type -- Key: CLOUDSTACK-4055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Ahmad Emneina Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 Attachments: win2012_other_os.png Registered a Windows Server 2012 64-bit template in ACS and made sure Windows Server 2012 (64-Bit) was selected as the OS type when registering the template, however when we build an instance in CS it creates the OS type in VMware as Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS type is an available option in VMware. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728268#comment-13728268 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4055: - This bug cannot be fixed at present with the latest version of vi sdk (which Min had updated cloudstack to use) because vi sdk doesn't yet include Windows 2012 in its list of supported guest OSes. This cannot be fixed until the next vi sdk version is released with the guest OS description list getting a new enum for Windows 2012 Server. Until then, the OS description will show up as Other (64-bit). This list of guest OS flavors supported by vi sdk can be gleaned from the following link for VirtualMachineGuestOsIdentifier enum list : http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.vm.GuestOsDescriptor.GuestOsIdentifier.html It looks like Windows 2012 was added to the guest OS list for all hypervisors other than vmware as part of this commit: commit c11dbad9c9ba7a876243ec02e90215906cfd9115 Author: Nitin Mehta nitin.me...@citrix.com Date: Sat May 11 15:28:43 2013 +0530 The commit cannot however work for VMWare deployments due to the reason stated above. After vi sdk introduces the enum for Windows 2012, this enum should be entered into the file VmwareGuestOSMapper.java in the cloudstack code. This file contains all the mappings of the Guest OS strings to be returned against OS flavors, and currently this list contains Windows 8 64 bit, but not Windows 2012. This bug can be resolved as of now. Will mark as cannot fix. Windows Server 2012 (64-Bit) being deployed as 'Other OS' type -- Key: CLOUDSTACK-4055 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Ahmad Emneina Priority: Critical Fix For: 4.2.0 Attachments: win2012_other_os.png Registered a Windows Server 2012 64-bit template in ACS and made sure Windows Server 2012 (64-Bit) was selected as the OS type when registering the template, however when we build an instance in CS it creates the OS type in VMware as Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS type is an available option in VMware. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725844#comment-13725844 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3568: - Was speaking with Kelven and Prachi regarding another issue with a similar problem with waitForTask() and Kelven pointed out that waitForTask() isn't quite a vmware API but it's a wrapper written in VmwareClient.java - I had missed that earlier. It could be possible that we're incorrectly returning success in that function without waiting for the task to progress to 100% completion. Will update the review request with this input, and look into waitForTask()'s implementation. [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand. - Key: CLOUDSTACK-3568 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3568 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, VMware Affects Versions: 4.2.0 Environment: Build from 4.2 Reporter: Sangeetha Hariharan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: management-server.log Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand. Steps to reproduce the problem: Set up - Advanced zone with Vmware ESXI, 5.0.0 host. Deploy 30 Vms in parallel in a network that is already implemented (router is already running). Only 9 vms were successfully deployed. ~15 Vms failed in org.apache.cloudstack.storage.command.CopyCommand because of ROOT-106-104/ROOT-106-104.vmdk was not found error. mysql select count(*),state,type from vm_instance where name like hello% group by state,type ; +--+-+--+ | count(*) | state | type | +--+-+--+ | 42 | Error | User | |9 | Running | User | +--+-+--+ 2 rows in set (0.00 sec) Following exception seen in management server logs: 2013-07-16 15:47:55,099 ERROR [storage.resource.VmwareStorageProcessor] (DirectAgent-71:10.223.57.66) CreateCommand failed due to Exception: java.lang.RuntimeException Message: File [7caed722555d3f71879476c5e8d8d5ad] ROOT-106-104/ROOT-106-104.vmdk was not found java.lang.RuntimeException: File [7caed722555d3f71879476c5e8d8d5ad] ROOT-106-104/ROOT-106-104.vmdk was not found at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290) at com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:57) at com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:78) at com.cloud.hypervisor.vmware.mo.DatastoreMO.folderExists(DatastoreMO.java:319) at com.cloud.storage.resource.VmwareStorageProcessor.createVMLinkedClone(VmwareStorageProcessor.java:279) at com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:393) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:73) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:565) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-16 15:47:55,100 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-71:null) Seq 1-227737729: Response Received: 2013-07-16 15:47:55,100 DEBUG [agent.transport.Request]
[jira] [Updated] (CLOUDSTACK-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3568:
Status: Ready To Review (was: In Progress)
[Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms ,
we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
-
Key: CLOUDSTACK-3568
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3568
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, VMware
Affects Versions: 4.2.0
Environment: Build from 4.2
Reporter: Sangeetha Hariharan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.log
Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15
Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
Steps to reproduce the problem:
Set up - Advanced zone with Vmware ESXI, 5.0.0 host.
Deploy 30 Vms in parallel in a network that is already implemented (router is
already running).
Only 9 vms were successfully deployed.
~15 Vms failed in org.apache.cloudstack.storage.command.CopyCommand because
of ROOT-106-104/ROOT-106-104.vmdk was not found error.
mysql select count(*),state,type from vm_instance where name like hello%
group by state,type ;
+--+-+--+
| count(*) | state | type |
+--+-+--+
| 42 | Error | User |
|9 | Running | User |
+--+-+--+
2 rows in set (0.00 sec)
Following exception seen in management server logs:
2013-07-16 15:47:55,099 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-71:10.223.57.66) CreateCommand failed due to Exception:
java.lang.RuntimeException
Message: File [7caed722555d3f71879476c5e8d8d5ad]
ROOT-106-104/ROOT-106-104.vmdk was not found
java.lang.RuntimeException: File [7caed722555d3f71879476c5e8d8d5ad]
ROOT-106-104/ROOT-106-104.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:57)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:78)
at
com.cloud.hypervisor.vmware.mo.DatastoreMO.folderExists(DatastoreMO.java:319)
at
com.cloud.storage.resource.VmwareStorageProcessor.createVMLinkedClone(VmwareStorageProcessor.java:279)
at
com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:393)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:73)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:565)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-16 15:47:55,100 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-71:null) Seq 1-227737729: Response Received:
2013-07-16 15:47:55,100 DEBUG [agent.transport.Request] (DirectAgent-71:null)
Seq 1-227737729: Processing: { Ans: , MgmtId: 7647994577963, via: 1, Ver:
v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:java.lang.RuntimeException:
File [7caed722555d3f71879476c5e8d8d5ad] ROOT-106-104/ROOT-106-104.vmdk was
not found,wait:0}}] }
2013-07-16 15:47:55,100 DEBUG [agent.transport.Request]
(Job-Executor-8:job-101 = [ cad3c4ea-3d40-46f4-bce5-26d60d4af7c1 ]) Seq
1-227737729: Received: { Ans: , MgmtId: 7647994577963,
[jira] [Commented] (CLOUDSTACK-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724675#comment-13724675
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3568:
-
A few other file asynchronous task related issues were also seen in the logs
and a patch to fix all these issues has been submitted at
https://reviews.apache.org/r/13093/
[Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms ,
we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
-
Key: CLOUDSTACK-3568
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3568
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, VMware
Affects Versions: 4.2.0
Environment: Build from 4.2
Reporter: Sangeetha Hariharan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.log
Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15
Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
Steps to reproduce the problem:
Set up - Advanced zone with Vmware ESXI, 5.0.0 host.
Deploy 30 Vms in parallel in a network that is already implemented (router is
already running).
Only 9 vms were successfully deployed.
~15 Vms failed in org.apache.cloudstack.storage.command.CopyCommand because
of ROOT-106-104/ROOT-106-104.vmdk was not found error.
mysql select count(*),state,type from vm_instance where name like hello%
group by state,type ;
+--+-+--+
| count(*) | state | type |
+--+-+--+
| 42 | Error | User |
|9 | Running | User |
+--+-+--+
2 rows in set (0.00 sec)
Following exception seen in management server logs:
2013-07-16 15:47:55,099 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-71:10.223.57.66) CreateCommand failed due to Exception:
java.lang.RuntimeException
Message: File [7caed722555d3f71879476c5e8d8d5ad]
ROOT-106-104/ROOT-106-104.vmdk was not found
java.lang.RuntimeException: File [7caed722555d3f71879476c5e8d8d5ad]
ROOT-106-104/ROOT-106-104.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:57)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:78)
at
com.cloud.hypervisor.vmware.mo.DatastoreMO.folderExists(DatastoreMO.java:319)
at
com.cloud.storage.resource.VmwareStorageProcessor.createVMLinkedClone(VmwareStorageProcessor.java:279)
at
com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:393)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:73)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:565)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-16 15:47:55,100 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-71:null) Seq 1-227737729: Response Received:
2013-07-16 15:47:55,100 DEBUG [agent.transport.Request] (DirectAgent-71:null)
Seq 1-227737729: Processing: { Ans: , MgmtId: 7647994577963, via: 1, Ver:
v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:java.lang.RuntimeException:
File [7caed722555d3f71879476c5e8d8d5ad] ROOT-106-104/ROOT-106-104.vmdk was
not found,wait:0}}] }
[jira] [Commented] (CLOUDSTACK-3781) Unable to resize disk on VmWare with Zone wide storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723125#comment-13723125 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3781: - Hongtu, can you please take a look at this issue? It seems to be a special case of a volume resize on zone wide primary storage. Unable to resize disk on VmWare with Zone wide storage -- Key: CLOUDSTACK-3781 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3781 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Volumes Affects Versions: 4.2.0 Environment: Management Server: CentOS6.2 with latest 4.2 cloudstack build Hypervisor: Vmware Esxi 5.1 Storage: NFS for both primary and secondary Reporter: Pavan Kumar Bandarupally Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: MS Log.rar When we create an instance on vmware and try to resize the data disk , it gives an error saying Can't resize a volume that has never been attached, not sure which hypervisor type. Recreate volume to resize An InvalidParameterValueException is being thrown as the hypervisor is getting selected as none. The problem is when the storage is added at zone level. The cluster_id is getting selected as NULL in this case. If the storage is added at cluster level, things work fine. Please see the db query below: mysql SELECT c.hypervisor_type from volumes v, storage_pool s, cluster c where v.pool_id = s.id and s.cluster_id = c.id and v.id = 9; Empty set (0.00 sec) mysql select * from storage_pool; ++-+--+---+--++++---++--+---++-+-+-++---+---++-+---+ | id | name| uuid | pool_type | port | data_center_id | pod_id | cluster_id | used_bytes| capacity_bytes | host_address | user_info | path | created | removed | update_time | status | storage_provider_name | scope | hypervisor | managed | capacity_iops | ++-+--+---+--++++---++--+---++-+-+-++---+---++-+---+ | 1 | TeamStorage | 0f658e18-7e6a-3442-9c36-de5c56926e26 | NetworkFilesystem | 2049 | 1 | NULL | NULL | 2001531498496 | 590228480 | 10.147.28.7 | NULL | /export/home/pavan/primary | 2013-07-24 15:53:00 | NULL| NULL| Up | DefaultPrimary | ZONE | VMware | 0 | NULL | ++-+--+---+--++++---++--+---++-+-+-++---+---++-+---+ 1 row in set (0.00 sec) mysql select * from storage_pool\G *** 1. row *** id: 1 name: TeamStorage uuid: 0f658e18-7e6a-3442-9c36-de5c56926e26 pool_type: NetworkFilesystem port: 2049 data_center_id: 1 pod_id: NULL cluster_id: NULL used_bytes: 2001531498496 capacity_bytes: 590228480 host_address: 10.147.28.7 user_info: NULL path: /export/home/pavan/primary created: 2013-07-24 15:53:00 removed: NULL update_time: NULL status: Up storage_provider_name: DefaultPrimary scope: ZONE hypervisor: VMware managed: 0 capacity_iops: NULL 1 row in set (0.00 sec) Repro Steps: Create an instance with a data disk attached. Go to the data disk and try to resize (increase) it. An error will be thrown. Note: Marking it as a blocker as we can't test Disk Re-size feature on VmWare because of this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information
[jira] [Commented] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone(showing SG enabled to true eventhough zone created with sharednetwork)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723130#comment-13723130
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2730:
-
Will take a look at this at the earliest opportunity. However, we don't
officially support basic zones on vmware, so will downgrade this to major for
now.
vmware:addcluster failed in basiczone(showing SG enabled to true eventhough
zone created with sharednetwork)
Key: CLOUDSTACK-2730
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Attachments: management-server.log
In case of vmware ,when i try to configure basic zone with shared
network.addcluster failed with
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone even though
i select the bassic and shared network.
1.select the zone type as basic
2.select the network type as shared
3.provide pod ,guest details and configure primary and secondary detaisl
4.click on finish to create basic zone with shared network mode
Actual result:
even though i select shared network in basic zone,it sends security group
enble to true internally. due to this addcluster failed .
It throws following error:
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone
mysql select * from data_center where id=2\G;
*** 1. row ***
id: 2
name: zone1
uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
description: NULL
dns1: 10.103.128.16
dns2: NULL
internal_dns1: 10.103.128.16
internal_dns2: NULL
gateway: NULL
netmask: NULL
router_mac_address: 02:00:00:00:00:01
mac_address: 23
guest_network_cidr: NULL
domain: NULL
domain_id: NULL
networktype: Basic
dns_provider: VirtualRouter
gateway_provider: NULL
firewall_provider: NULL
dhcp_provider: VirtualRouter
lb_provider: ElasticLoadBalancerVm
vpn_provider: NULL
userdata_provider: VirtualRouter
allocation_state: Disabled
zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
is_security_group_enabled: 1
is_local_storage_enabled: 0
removed: NULL
owner: NULL
created: NULL
lastUpdated: NULL
engine_state: Disabled
ip6_dns1: NULL
ip6_dns2: NULL
1 row in set (0.00 sec)
mysql select * from networks where id=209\G;
*** 1. row ***
id: 209
name: defaultGuestNetwork
uuid: eca88272-2ad4-47a8-ab90-442393b6d034
display_text: defaultGuestNetwork
traffic_type: Guest
broadcast_domain_type: Native
broadcast_uri: vlan://untagged
gateway: NULL
cidr: NULL
mode: Dhcp
network_offering_id: 7
physical_network_id: 201
data_center_id: 2
guru_name: DirectPodBasedNetworkGuru
state: Setup
related: 209
domain_id: 1
account_id: 1
dns1: NULL
dns2: NULL
guru_data: NULL
set_fields: 0
acl_type: Domain
network_domain: cs1cloud.internal
reservation_id: NULL
guest_type: Shared
restart_required: 0
created: 2013-05-29 12:21:04
removed: NULL
specify_ip_ranges: 1
vpc_id: NULL
ip6_gateway: NULL
ip6_cidr: NULL
network_cidr: NULL
display_network: 1
network_acl_id: NULL
1 row in set (0.00 sec)
http://10.147.59.83:8080/client/api?command=createZonenetworktype=Basicname=zone1dns1=10.103.128.16internaldns1=10.103.128.16response=jsonsessionkey=6%2BUi17Y6gpixRBAR9s4yhQCQkhs%3D_=1369810303912
{ createzoneresponse : { zone :
[jira] [Updated] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone(showing SG enabled to true eventhough zone created with sharednetwork)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-2730:
Priority: Major (was: Critical)
vmware:addcluster failed in basiczone(showing SG enabled to true eventhough
zone created with sharednetwork)
Key: CLOUDSTACK-2730
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Venkata Siva Vijayendra Bhamidipati
Attachments: management-server.log
In case of vmware ,when i try to configure basic zone with shared
network.addcluster failed with
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone even though
i select the bassic and shared network.
1.select the zone type as basic
2.select the network type as shared
3.provide pod ,guest details and configure primary and secondary detaisl
4.click on finish to create basic zone with shared network mode
Actual result:
even though i select shared network in basic zone,it sends security group
enble to true internally. due to this addcluster failed .
It throws following error:
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone
mysql select * from data_center where id=2\G;
*** 1. row ***
id: 2
name: zone1
uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
description: NULL
dns1: 10.103.128.16
dns2: NULL
internal_dns1: 10.103.128.16
internal_dns2: NULL
gateway: NULL
netmask: NULL
router_mac_address: 02:00:00:00:00:01
mac_address: 23
guest_network_cidr: NULL
domain: NULL
domain_id: NULL
networktype: Basic
dns_provider: VirtualRouter
gateway_provider: NULL
firewall_provider: NULL
dhcp_provider: VirtualRouter
lb_provider: ElasticLoadBalancerVm
vpn_provider: NULL
userdata_provider: VirtualRouter
allocation_state: Disabled
zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
is_security_group_enabled: 1
is_local_storage_enabled: 0
removed: NULL
owner: NULL
created: NULL
lastUpdated: NULL
engine_state: Disabled
ip6_dns1: NULL
ip6_dns2: NULL
1 row in set (0.00 sec)
mysql select * from networks where id=209\G;
*** 1. row ***
id: 209
name: defaultGuestNetwork
uuid: eca88272-2ad4-47a8-ab90-442393b6d034
display_text: defaultGuestNetwork
traffic_type: Guest
broadcast_domain_type: Native
broadcast_uri: vlan://untagged
gateway: NULL
cidr: NULL
mode: Dhcp
network_offering_id: 7
physical_network_id: 201
data_center_id: 2
guru_name: DirectPodBasedNetworkGuru
state: Setup
related: 209
domain_id: 1
account_id: 1
dns1: NULL
dns2: NULL
guru_data: NULL
set_fields: 0
acl_type: Domain
network_domain: cs1cloud.internal
reservation_id: NULL
guest_type: Shared
restart_required: 0
created: 2013-05-29 12:21:04
removed: NULL
specify_ip_ranges: 1
vpc_id: NULL
ip6_gateway: NULL
ip6_cidr: NULL
network_cidr: NULL
display_network: 1
network_acl_id: NULL
1 row in set (0.00 sec)
http://10.147.59.83:8080/client/api?command=createZonenetworktype=Basicname=zone1dns1=10.103.128.16internaldns1=10.103.128.16response=jsonsessionkey=6%2BUi17Y6gpixRBAR9s4yhQCQkhs%3D_=1369810303912
{ createzoneresponse : { zone :
{id:c642382d-8587-4cd7-a1e9-5a488bb47da7,name:zone1,dns1:10.103.128.16,internaldns1:10.103.128.16,networktype:Basic,securitygroupsenabled:true,allocationstate:Disabled,zonetoken:68de3ddf-3a08-3371-9506-a57a4a0a8af5,dhcpprovider:VirtualRouter,localstorageenabled:false}
} }
[jira] [Created] (CLOUDSTACK-3886) VM name on vCenter not getting set correctly when vm.instancename.flag is set to true
Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-3886: --- Summary: VM name on vCenter not getting set correctly when vm.instancename.flag is set to true Key: CLOUDSTACK-3886 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3886 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Vmware deployment in cloudstack. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 In a vmware deployment on cloudstack, if the vm.instancename.flag is set to true, and a displayname is supplied during VM creation, the displayname simply gets appended to the internal name i-x-y of that VM in vCenter. The expected behaviour is this: If the vm.instancename.flag is set to false (default), there is no change in current behavior: 1. If hostname isn't supplied, it is set to the uuid. 2. If displayname is supplied, it shows up in the GUI. If not, it is set to the internal VM name i-x-y-VM. If the vm.instancename.flag is set to true: 1. If hostname is not supplied, and displayname is supplied, set hostname to displayname, and set the instance name as it appears on vCenter also, to the displayname. 2. If hostname is not supplied, and displayname is also not supplied, set hostname to uuid, but set internal name of the VM as it appears on vCenter to i-x-y-VM as is done currently. 3. If hostname is supplied, set the instance name as it appears on vCenter to this hostname. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3886) VM name on vCenter not getting set correctly when vm.instancename.flag is set to true
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3886: Status: Ready To Review (was: In Progress) VM name on vCenter not getting set correctly when vm.instancename.flag is set to true - Key: CLOUDSTACK-3886 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3886 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Vmware deployment in cloudstack. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 In a vmware deployment on cloudstack, if the vm.instancename.flag is set to true, and a displayname is supplied during VM creation, the displayname simply gets appended to the internal name i-x-y of that VM in vCenter. The expected behaviour is this: If the vm.instancename.flag is set to false (default), there is no change in current behavior: 1. If hostname isn't supplied, it is set to the uuid. 2. If displayname is supplied, it shows up in the GUI. If not, it is set to the internal VM name i-x-y-VM. If the vm.instancename.flag is set to true: 1. If hostname is not supplied, and displayname is supplied, set hostname to displayname, and set the instance name as it appears on vCenter also, to the displayname. 2. If hostname is not supplied, and displayname is also not supplied, set hostname to uuid, but set internal name of the VM as it appears on vCenter to i-x-y-VM as is done currently. 3. If hostname is supplied, set the instance name as it appears on vCenter to this hostname. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3886) VM name on vCenter not getting set correctly when vm.instancename.flag is set to true
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722110#comment-13722110 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3886: - Patch posted for review at https://reviews.apache.org/r/13008/ VM name on vCenter not getting set correctly when vm.instancename.flag is set to true - Key: CLOUDSTACK-3886 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3886 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Vmware deployment in cloudstack. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 In a vmware deployment on cloudstack, if the vm.instancename.flag is set to true, and a displayname is supplied during VM creation, the displayname simply gets appended to the internal name i-x-y of that VM in vCenter. The expected behaviour is this: If the vm.instancename.flag is set to false (default), there is no change in current behavior: 1. If hostname isn't supplied, it is set to the uuid. 2. If displayname is supplied, it shows up in the GUI. If not, it is set to the internal VM name i-x-y-VM. If the vm.instancename.flag is set to true: 1. If hostname is not supplied, and displayname is supplied, set hostname to displayname, and set the instance name as it appears on vCenter also, to the displayname. 2. If hostname is not supplied, and displayname is also not supplied, set hostname to uuid, but set internal name of the VM as it appears on vCenter to i-x-y-VM as is done currently. 3. If hostname is supplied, set the instance name as it appears on vCenter to this hostname. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3781) Unable to resize disk on VmWare with Zone wide storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3781: --- Assignee: Venkata Siva Vijayendra Bhamidipati Unable to resize disk on VmWare with Zone wide storage -- Key: CLOUDSTACK-3781 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3781 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Volumes Affects Versions: 4.2.0 Environment: Management Server: CentOS6.2 with latest 4.2 cloudstack build Hypervisor: Vmware Esxi 5.1 Storage: NFS for both primary and secondary Reporter: Pavan Kumar Bandarupally Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: MS Log.rar When we create an instance on vmware and try to resize the data disk , it gives an error saying Can't resize a volume that has never been attached, not sure which hypervisor type. Recreate volume to resize An InvalidParameterValueException is being thrown as the hypervisor is getting selected as none. The problem is when the storage is added at zone level. The cluster_id is getting selected as NULL in this case. If the storage is added at cluster level, things work fine. Please see the db query below: mysql SELECT c.hypervisor_type from volumes v, storage_pool s, cluster c where v.pool_id = s.id and s.cluster_id = c.id and v.id = 9; Empty set (0.00 sec) mysql select * from storage_pool; ++-+--+---+--++++---++--+---++-+-+-++---+---++-+---+ | id | name| uuid | pool_type | port | data_center_id | pod_id | cluster_id | used_bytes| capacity_bytes | host_address | user_info | path | created | removed | update_time | status | storage_provider_name | scope | hypervisor | managed | capacity_iops | ++-+--+---+--++++---++--+---++-+-+-++---+---++-+---+ | 1 | TeamStorage | 0f658e18-7e6a-3442-9c36-de5c56926e26 | NetworkFilesystem | 2049 | 1 | NULL | NULL | 2001531498496 | 590228480 | 10.147.28.7 | NULL | /export/home/pavan/primary | 2013-07-24 15:53:00 | NULL| NULL| Up | DefaultPrimary | ZONE | VMware | 0 | NULL | ++-+--+---+--++++---++--+---++-+-+-++---+---++-+---+ 1 row in set (0.00 sec) mysql select * from storage_pool\G *** 1. row *** id: 1 name: TeamStorage uuid: 0f658e18-7e6a-3442-9c36-de5c56926e26 pool_type: NetworkFilesystem port: 2049 data_center_id: 1 pod_id: NULL cluster_id: NULL used_bytes: 2001531498496 capacity_bytes: 590228480 host_address: 10.147.28.7 user_info: NULL path: /export/home/pavan/primary created: 2013-07-24 15:53:00 removed: NULL update_time: NULL status: Up storage_provider_name: DefaultPrimary scope: ZONE hypervisor: VMware managed: 0 capacity_iops: NULL 1 row in set (0.00 sec) Repro Steps: Create an instance with a data disk attached. Go to the data disk and try to resize (increase) it. An error will be thrown. Note: Marking it as a blocker as we can't test Disk Re-size feature on VmWare because of this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-1510) NPE when primary storage is added with wrong path
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-1510.
-
Resolution: Fixed
NPE when primary storage is added with wrong path
--
Key: CLOUDSTACK-1510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Minor
Fix For: 4.2.0
Attachments: apilog.log, management-server.log
Steps :
1. Configure Advanced zone
2. Tried to add second nfs primary storage with wrong path.
Observation: It failed with NPE
2013-03-05 15:02:16,535 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:203,uuid:40e80e79-ac1b-31d1-a067-1ec03e7bc67b,host:10.102.192.100,path:/cpg_vol/sailaja/priamry,port:2049,type:NetworkFilesystem},localPath:/mnt//40e80e79-ac1b-31d1-a067-1ec03e7bc67b,wait:0}}]
}
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 1-16676: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\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,wait:0}}] }
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Received: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-03-05 15:02:16,702 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-25:null) Details from executing class
com.cloud.agent.api.ModifyStoragePoolCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-03-05 15:02:16,708 WARN [cloud.storage.StorageManagerImpl]
(catalina-exec-25:null) Unable to establish a connection between
Host[-1-Routing] and Pool[203|NetworkFilesystem]
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203]
is unreachable: Unable establish connection from storage head to storage pool
203 due to java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
[jira] [Commented] (CLOUDSTACK-1510) NPE when primary storage is added with wrong path
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721178#comment-13721178
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-1510:
-
Hi Sailaja,
When I tested the code during submission of the patch the exception was
correctly propagated, so something must've changed. This is minor, so let's
track the notification issue in a different bug. I will mark this bug as
resolved.
Regards,
Vijay
NPE when primary storage is added with wrong path
--
Key: CLOUDSTACK-1510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Minor
Fix For: 4.2.0
Attachments: apilog.log, management-server.log
Steps :
1. Configure Advanced zone
2. Tried to add second nfs primary storage with wrong path.
Observation: It failed with NPE
2013-03-05 15:02:16,535 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:203,uuid:40e80e79-ac1b-31d1-a067-1ec03e7bc67b,host:10.102.192.100,path:/cpg_vol/sailaja/priamry,port:2049,type:NetworkFilesystem},localPath:/mnt//40e80e79-ac1b-31d1-a067-1ec03e7bc67b,wait:0}}]
}
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 1-16676: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\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,wait:0}}] }
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Received: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-03-05 15:02:16,702 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-25:null) Details from executing class
com.cloud.agent.api.ModifyStoragePoolCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-03-05 15:02:16,708 WARN [cloud.storage.StorageManagerImpl]
(catalina-exec-25:null) Unable to establish a connection between
Host[-1-Routing] and Pool[203|NetworkFilesystem]
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203]
is unreachable: Unable establish connection from storage head to storage pool
203 due to java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
[jira] [Commented] (CLOUDSTACK-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719169#comment-13719169
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3568:
-
Went through the logs and looked at Sangeetha's setup (primary storage).
Let's take an example failure in the logs and trace the events:
2013-07-16 15:47:48,631 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-68:10.223.57.66) creating linked clone from template
2013-07-16 15:47:49,316 DEBUG [storage.motion.AncientDataMotionStrategy]
(Job-Executor-9:job-102 = [ 1b0c2fa4-2326-4fd2-921b-98d19ca17d38 ]) copyAsync
inspecting src type TEMPLATE copyAsync inspecting dest type VOLUME
2013-07-16 15:47:49,323 DEBUG [agent.transport.Request] (Job-Executor-9:job-102
= [ 1b0c2fa4-2326-4fd2-921b-98d19ca17d38 ]) Seq 1-227737728: Sending { Cmd ,
MgmtId: 7647994577963, via: 1, Ver: v1, Flags: 100011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:6343361f88b73f178855d62eb1c3a698,origUrl:http://nfs1.lab.vmops.com/templates/passwordssh/CentOS5.3-x86_64.ova,uuid:1c3517c1-0226-47a7-90b3-96b7de70fc64,id:202,format:OVA,accountId:2,checksum:f6f881b7f2292948d8494db837fe0f47,hvm:true,displayText:test,imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:7caed722-555d-3f71-8794-76c5e8d8d5ad,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/master-vmware/primary,port:2049}},name:202-2-5806a2dd-c8ea-3a15-9b1a-af7098ec5de5}},destTO:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:7a3a4484-346a-4d83-903a-59e5dd7d2dff,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:7caed722-555d-3f71-8794-76c5e8d8d5ad,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/master-vmware/primary,port:2049}},name:ROOT-106,size:0,volumeId:104,vmName:i-4-106-VM,accountId:4,format:OVA,id:104}},executeInSequence:false,wait:0}}]
}
2013-07-16 15:47:49,324 DEBUG [agent.transport.Request] (Job-Executor-9:job-102
= [ 1b0c2fa4-2326-4fd2-921b-98d19ca17d38 ]) Seq 1-227737728: Executing: { Cmd
, MgmtId: 7647994577963, via: 1, Ver: v1, Flags: 100011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:6343361f88b73f178855d62eb1c3a698,origUrl:http://nfs1.lab.vmops.com/templates/passwordssh/CentOS5.3-x86_64.ova,uuid:1c3517c1-0226-47a7-90b3-96b7de70fc64,id:202,format:OVA,accountId:2,checksum:f6f881b7f2292948d8494db837fe0f47,hvm:true,displayText:test,imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:7caed722-555d-3f71-8794-76c5e8d8d5ad,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/master-vmware/primary,port:2049}},name:202-2-5806a2dd-c8ea-3a15-9b1a-af7098ec5de5}},destTO:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:7a3a4484-346a-4d83-903a-59e5dd7d2dff,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:7caed722-555d-3f71-8794-76c5e8d8d5ad,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/master-vmware/primary,port:2049}},name:ROOT-106,size:0,volumeId:104,vmName:i-4-106-VM,accountId:4,format:OVA,id:104}},executeInSequence:false,wait:0}}]
}
.
.
.
2013-07-16 15:47:50,229 INFO [vmware.mo.DatastoreMO]
(DirectAgent-70:10.223.57.66) Folder ROOT-106-104 does not exist on datastore
2013-07-16 15:47:51,025 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-70:10.223.57.66) creating linked clone from template
.
.
2013-07-16 15:47:53,917 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-70:10.223.57.66) Move volume out of volume-wrapper VM
2013-07-16 15:47:53,927 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-68:10.223.57.66) Move volume out of volume-wrapper VM
2013-07-16 15:47:55,099 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-71:10.223.57.66) CreateCommand failed due to Exception:
java.lang.RuntimeException
Message: File [7caed722555d3f71879476c5e8d8d5ad] ROOT-106-104/ROOT-106-104.vmdk
was not found
java.lang.RuntimeException: File [7caed722555d3f71879476c5e8d8d5ad]
ROOT-106-104/ROOT-106-104.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:57)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:78)
at
com.cloud.hypervisor.vmware.mo.DatastoreMO.folderExists(DatastoreMO.java:319)
at
com.cloud.storage.resource.VmwareStorageProcessor.createVMLinkedClone(VmwareStorageProcessor.java:279)
at
[jira] [Assigned] (CLOUDSTACK-3647) 3.0.6 to ASF 4.2 Upgrade: guest_os table has duplicate Windows 8 64-bit OS mappings on the Upgraded Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3647: --- Assignee: Venkata Siva Vijayendra Bhamidipati 3.0.6 to ASF 4.2 Upgrade: guest_os table has duplicate Windows 8 64-bit OS mappings on the Upgraded Setup --- Key: CLOUDSTACK-3647 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3647 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: Chandan Purushothama Assignee: Venkata Siva Vijayendra Bhamidipati Fix For: 4.2.0 mysql select * from guest_os where display_name like Windows 8%; +-+-+--+--++ | id | category_id | name | uuid | display_name | +-+-+--+--++ | 165 | 6 | NULL | 67b38d28-ed85-11e2-a76b-0649e40006c6 | Windows 8 (32-bit) | | 166 | 6 | NULL | 67b3a362-ed85-11e2-a76b-0649e40006c6 | Windows 8 (64-bit) | | 206 | 6 | NULL | 206 | Windows 8(64-bit) | +-+-+--+--++ 3 rows in set (0.00 sec) mysql -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3568:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
[Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms ,
we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
-
Key: CLOUDSTACK-3568
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3568
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Build from 4.2
Reporter: Sangeetha Hariharan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.log
Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15
Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
Steps to reproduce the problem:
Set up - Advanced zone with Vmware ESXI, 5.0.0 host.
Deploy 30 Vms in parallel in a network that is already implemented (router is
already running).
Only 9 vms were successfully deployed.
~15 Vms failed in org.apache.cloudstack.storage.command.CopyCommand because
of ROOT-106-104/ROOT-106-104.vmdk was not found error.
mysql select count(*),state,type from vm_instance where name like hello%
group by state,type ;
+--+-+--+
| count(*) | state | type |
+--+-+--+
| 42 | Error | User |
|9 | Running | User |
+--+-+--+
2 rows in set (0.00 sec)
Following exception seen in management server logs:
2013-07-16 15:47:55,099 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-71:10.223.57.66) CreateCommand failed due to Exception:
java.lang.RuntimeException
Message: File [7caed722555d3f71879476c5e8d8d5ad]
ROOT-106-104/ROOT-106-104.vmdk was not found
java.lang.RuntimeException: File [7caed722555d3f71879476c5e8d8d5ad]
ROOT-106-104/ROOT-106-104.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:57)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:78)
at
com.cloud.hypervisor.vmware.mo.DatastoreMO.folderExists(DatastoreMO.java:319)
at
com.cloud.storage.resource.VmwareStorageProcessor.createVMLinkedClone(VmwareStorageProcessor.java:279)
at
com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:393)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:73)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:565)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-16 15:47:55,100 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-71:null) Seq 1-227737729: Response Received:
2013-07-16 15:47:55,100 DEBUG [agent.transport.Request] (DirectAgent-71:null)
Seq 1-227737729: Processing: { Ans: , MgmtId: 7647994577963, via: 1, Ver:
v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:java.lang.RuntimeException:
File [7caed722555d3f71879476c5e8d8d5ad] ROOT-106-104/ROOT-106-104.vmdk was
not found,wait:0}}] }
2013-07-16 15:47:55,100 DEBUG [agent.transport.Request]
(Job-Executor-8:job-101 = [ cad3c4ea-3d40-46f4-bce5-26d60d4af7c1 ]) Seq
1-227737729: Received: { Ans: , MgmtId: 7647994577963,
[jira] [Resolved] (CLOUDSTACK-3598) [Automation] NullPointerException observed while connecting agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3598. - Resolution: Fixed https://reviews.apache.org/r/12716/ [Automation] NullPointerException observed while connecting agent -- Key: CLOUDSTACK-3598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3598 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Environment: Vmware build 4.2 Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3598.rar Observed below NPE in management server log INFO [storage.secondary.SecondaryStorageListener] (AgentConnectTaskPool-34:) Received a host startup notification com.cloud.agent.api.StartupSecondaryStorageCommand INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-34:) Received a host startup notification INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-34:) Template Sync found centos53-x64 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-34:) Template Sync found routing-8 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-34:) Template Sync found 204-17-be1f9cd1-6d30-378c-868d-301cc0429a25 already in the image store ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-34:) Monitor DownloadListener says there is an error in the connect process for 11 due to null java.lang.NullPointerException at com.cloud.configuration.dao.ResourceCountDaoImpl.setResourceCount(ResourceCountDaoImpl.java:101) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:847) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:342) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1086) at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:144) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-34:) Host 11 is disconnecting with event AgentDisconnected -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3598) [Automation] NullPointerException observed while connecting agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3598: Status: Ready To Review (was: In Progress) [Automation] NullPointerException observed while connecting agent -- Key: CLOUDSTACK-3598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3598 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Environment: Vmware build 4.2 Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3598.rar Observed below NPE in management server log INFO [storage.secondary.SecondaryStorageListener] (AgentConnectTaskPool-34:) Received a host startup notification com.cloud.agent.api.StartupSecondaryStorageCommand INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-34:) Received a host startup notification INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-34:) Template Sync found centos53-x64 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-34:) Template Sync found routing-8 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-34:) Template Sync found 204-17-be1f9cd1-6d30-378c-868d-301cc0429a25 already in the image store ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-34:) Monitor DownloadListener says there is an error in the connect process for 11 due to null java.lang.NullPointerException at com.cloud.configuration.dao.ResourceCountDaoImpl.setResourceCount(ResourceCountDaoImpl.java:101) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:847) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:342) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1086) at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:144) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-34:) Host 11 is disconnecting with event AgentDisconnected -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone(showing SG enabled to true eventhough zone created with sharednetwork)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-2730:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
vmware:addcluster failed in basiczone(showing SG enabled to true eventhough
zone created with sharednetwork)
Key: CLOUDSTACK-2730
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Attachments: management-server.log
In case of vmware ,when i try to configure basic zone with shared
network.addcluster failed with
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone even though
i select the bassic and shared network.
1.select the zone type as basic
2.select the network type as shared
3.provide pod ,guest details and configure primary and secondary detaisl
4.click on finish to create basic zone with shared network mode
Actual result:
even though i select shared network in basic zone,it sends security group
enble to true internally. due to this addcluster failed .
It throws following error:
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone
mysql select * from data_center where id=2\G;
*** 1. row ***
id: 2
name: zone1
uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
description: NULL
dns1: 10.103.128.16
dns2: NULL
internal_dns1: 10.103.128.16
internal_dns2: NULL
gateway: NULL
netmask: NULL
router_mac_address: 02:00:00:00:00:01
mac_address: 23
guest_network_cidr: NULL
domain: NULL
domain_id: NULL
networktype: Basic
dns_provider: VirtualRouter
gateway_provider: NULL
firewall_provider: NULL
dhcp_provider: VirtualRouter
lb_provider: ElasticLoadBalancerVm
vpn_provider: NULL
userdata_provider: VirtualRouter
allocation_state: Disabled
zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
is_security_group_enabled: 1
is_local_storage_enabled: 0
removed: NULL
owner: NULL
created: NULL
lastUpdated: NULL
engine_state: Disabled
ip6_dns1: NULL
ip6_dns2: NULL
1 row in set (0.00 sec)
mysql select * from networks where id=209\G;
*** 1. row ***
id: 209
name: defaultGuestNetwork
uuid: eca88272-2ad4-47a8-ab90-442393b6d034
display_text: defaultGuestNetwork
traffic_type: Guest
broadcast_domain_type: Native
broadcast_uri: vlan://untagged
gateway: NULL
cidr: NULL
mode: Dhcp
network_offering_id: 7
physical_network_id: 201
data_center_id: 2
guru_name: DirectPodBasedNetworkGuru
state: Setup
related: 209
domain_id: 1
account_id: 1
dns1: NULL
dns2: NULL
guru_data: NULL
set_fields: 0
acl_type: Domain
network_domain: cs1cloud.internal
reservation_id: NULL
guest_type: Shared
restart_required: 0
created: 2013-05-29 12:21:04
removed: NULL
specify_ip_ranges: 1
vpc_id: NULL
ip6_gateway: NULL
ip6_cidr: NULL
network_cidr: NULL
display_network: 1
network_acl_id: NULL
1 row in set (0.00 sec)
http://10.147.59.83:8080/client/api?command=createZonenetworktype=Basicname=zone1dns1=10.103.128.16internaldns1=10.103.128.16response=jsonsessionkey=6%2BUi17Y6gpixRBAR9s4yhQCQkhs%3D_=1369810303912
{ createzoneresponse : { zone :
[jira] [Assigned] (CLOUDSTACK-3574) Vmware - java.lang.NumberFormatException encountered when executing NetworkUsageCommand.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3574: --- Assignee: Venkata Siva Vijayendra Bhamidipati Vmware - java.lang.NumberFormatException encountered when executing NetworkUsageCommand. - Key: CLOUDSTACK-3574 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3574 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Build from 4.2 Reporter: Sangeetha Hariharan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Critical Fix For: 4.2.0 Set up: Advanced zone set up with vmware ESXI 5.0 host. Deploy few Vms. Following exception is seen every 5 minutes when executing NetworkUsageCommand. 2013-07-16 15:37:46,837 INFO [vmware.resource.VmwareResource] (DirectAgent-10:10.223.57.66) Executing resource NetworkUsageCommand 2013-07-16 15:37:46,841 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-11:null) Seq 1-227737619: Executing request 2013-07-16 15:37:46,841 INFO [vmware.resource.VmwareResource] (DirectAgent-11:10.223.57.66) Executing resource NetworkUsageCommand 2013-07-16 15:37:47,502 WARN [vmware.resource.VmwareResource] (DirectAgent-10:10.223.57.66) Unable to parse return from script return of network usage command: java.lang.NumberFormatException: For input string: iptables java.lang.NumberFormatException: For input string: iptables at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Long.parseLong(Long.java:438) at java.lang.Long.init(Long.java:690) at com.cloud.hypervisor.vmware.resource.VmwareResource.getNetworkStats(VmwareResource.java:6006) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:682) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:517) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-16 15:37:47,579 WARN [vmware.resource.VmwareResource] (DirectAgent-11:10.223.57.66) Unable to parse return from script return of network usage command: java.lang.NumberFormatException: For input string: iptables java.lang.NumberFormatException: For input string: iptables at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Long.parseLong(Long.java:438) at java.lang.Long.init(Long.java:690) at com.cloud.hypervisor.vmware.resource.VmwareResource.getNetworkStats(VmwareResource.java:6006) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:682) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:517) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-16 15:37:47,705 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-11:null) Seq 1-227737619: Response Received: 2013-07-16 15:37:47,705 DEBUG [agent.transport.Request]
[jira] [Assigned] (CLOUDSTACK-3602) [Automation] [BVT] Registering iso failed; observed NullPointerException during API call TemplateManagerImpl.registerIso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3602: --- Assignee: Venkata Siva Vijayendra Bhamidipati [Automation] [BVT] Registering iso failed; observed NullPointerException during API call TemplateManagerImpl.registerIso - Key: CLOUDSTACK-3602 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3602 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: ISO, VMware Affects Versions: 4.2.0 Environment: Vmware branch 4.2 Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3602.rar BVT test case /cloudstack/test/integration/smoke/test_vm_life_cycle.py, line 715, in test_10_attachAndDetach_iso failed in vmware Observed below NullPointerException, INFO [vmware.mo.HypervisorHostHelper] (DirectAgent-18:10.223.250.130) Waiting for network cloud.guest.3189.200.1-vSwitch0 to be ready ERROR [cloud.api.ApiServer] (catalina-exec-15:) unhandled exception executing api command: registerIso java.lang.NullPointerException at org.apache.cloudstack.storage.LocalHostEndpoint.init(LocalHostEndpoint.java:49) at org.apache.cloudstack.storage.endpoint.DefaultEndPointSelector.findEndpointForImageStorage(DefaultEndPointSelector.java:194) at org.apache.cloudstack.storage.endpoint.DefaultEndPointSelector.select(DefaultEndPointSelector.java:228) at org.apache.cloudstack.storage.endpoint.DefaultEndPointSelector.select(DefaultEndPointSelector.java:216) at com.cloud.storage.download.DownloadMonitorImpl.initiateTemplateDownload(DownloadMonitorImpl.java:173) at com.cloud.storage.download.DownloadMonitorImpl.downloadTemplateToStorage(DownloadMonitorImpl.java:215) at org.apache.cloudstack.storage.image.BaseImageStoreDriverImpl.createAsync(BaseImageStoreDriverImpl.java:116) at org.apache.cloudstack.storage.image.TemplateServiceImpl.createTemplateAsync(TemplateServiceImpl.java:173) at com.cloud.template.HypervisorTemplateAdapter.create(HypervisorTemplateAdapter.java:163) at com.cloud.template.TemplateManagerImpl.registerIso(TemplateManagerImpl.java:323) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.iso.RegisterIsoCmd.execute(RegisterIsoCmd.java:180) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:529) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO [cloud.template.HypervisorTemplateAdapter] (Job-Executor-111:job-343 = [
[jira] [Commented] (CLOUDSTACK-3514) [Automation] Vmware - Failed to download default template for first zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711634#comment-13711634 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3514: - Update from Rayees: Issue not found in latest runs. Marking as resolved. [Automation] Vmware - Failed to download default template for first zone - Key: CLOUDSTACK-3514 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3514 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, VMware Affects Versions: 4.2.0 Environment: 4.2 branch build VMware Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3514.rar, CLOUDSTACK-3514.rar Steps to reproduce Create Vmware advanced zone with 2 zones Result 2 Zones created sucessfully but failed download default template for first zone mysql select name, data_center_name from template_view where hypervisor_type = 'VMware' and state = 'Ready'; +-+--+ | name| data_center_name | +-+--+ | SystemVM Template (vSphere) | Adv-VMware-Zone1 | | SystemVM Template (vSphere) | Adv-VMware-Zone2 | | CentOS 5.3(64-bit) no GUI (vSphere) | Adv-VMware-Zone2 | +-+--+ 3 rows in set (0.00 sec) Please see the attached catalina.out, seems system vmware (ssv name : v9) created for the second zone (Adv-VMware-Zone2) first then (ssvm name : vm20) second zone (Adv-VMware-Zone1), also observed below massage, to skip download template INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Secondary storage vm s-20-VM is started INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) Primary secondary storage is not even started, wait until next turn INFO [storage.secondary.SecondaryStorageListener] (AgentConnectTaskPool-19:) Received a host startup notification com.cloud.agent.api.StartupSecondaryStorageCommand INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-19:) Received a host startup notification INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found routing-8 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 203-14-8d8b9015-3688-3cd7-8970-15ad1b8a1e8a already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 211-82-e0654140-451e-3a67-bf52-0a4fe4e178ed already in the image store ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Monitor DownloadListener says there is an error in the connect process for 17 due to null java.lang.NullPointerException at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:342) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1086) at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:144) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Host 17 is disconnecting with event AgentDisconnected Pattern not found (press RETURN) Attaching DB Dump for your reference -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3514) [Automation] Vmware - Failed to download default template for first zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3514. - Resolution: Fixed [Automation] Vmware - Failed to download default template for first zone - Key: CLOUDSTACK-3514 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3514 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, VMware Affects Versions: 4.2.0 Environment: 4.2 branch build VMware Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3514.rar, CLOUDSTACK-3514.rar Steps to reproduce Create Vmware advanced zone with 2 zones Result 2 Zones created sucessfully but failed download default template for first zone mysql select name, data_center_name from template_view where hypervisor_type = 'VMware' and state = 'Ready'; +-+--+ | name| data_center_name | +-+--+ | SystemVM Template (vSphere) | Adv-VMware-Zone1 | | SystemVM Template (vSphere) | Adv-VMware-Zone2 | | CentOS 5.3(64-bit) no GUI (vSphere) | Adv-VMware-Zone2 | +-+--+ 3 rows in set (0.00 sec) Please see the attached catalina.out, seems system vmware (ssv name : v9) created for the second zone (Adv-VMware-Zone2) first then (ssvm name : vm20) second zone (Adv-VMware-Zone1), also observed below massage, to skip download template INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Secondary storage vm s-20-VM is started INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) Primary secondary storage is not even started, wait until next turn INFO [storage.secondary.SecondaryStorageListener] (AgentConnectTaskPool-19:) Received a host startup notification com.cloud.agent.api.StartupSecondaryStorageCommand INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-19:) Received a host startup notification INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found routing-8 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 203-14-8d8b9015-3688-3cd7-8970-15ad1b8a1e8a already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 211-82-e0654140-451e-3a67-bf52-0a4fe4e178ed already in the image store ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Monitor DownloadListener says there is an error in the connect process for 17 due to null java.lang.NullPointerException at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:342) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1086) at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:144) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Host 17 is disconnecting with event AgentDisconnected Pattern not found (press RETURN) Attaching DB Dump for your reference -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3514) [Automation] Vmware - Failed to download default template for first zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3514: Status: Ready To Review (was: In Progress) [Automation] Vmware - Failed to download default template for first zone - Key: CLOUDSTACK-3514 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3514 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, VMware Affects Versions: 4.2.0 Environment: 4.2 branch build VMware Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3514.rar, CLOUDSTACK-3514.rar Steps to reproduce Create Vmware advanced zone with 2 zones Result 2 Zones created sucessfully but failed download default template for first zone mysql select name, data_center_name from template_view where hypervisor_type = 'VMware' and state = 'Ready'; +-+--+ | name| data_center_name | +-+--+ | SystemVM Template (vSphere) | Adv-VMware-Zone1 | | SystemVM Template (vSphere) | Adv-VMware-Zone2 | | CentOS 5.3(64-bit) no GUI (vSphere) | Adv-VMware-Zone2 | +-+--+ 3 rows in set (0.00 sec) Please see the attached catalina.out, seems system vmware (ssv name : v9) created for the second zone (Adv-VMware-Zone2) first then (ssvm name : vm20) second zone (Adv-VMware-Zone1), also observed below massage, to skip download template INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Secondary storage vm s-20-VM is started INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) Primary secondary storage is not even started, wait until next turn INFO [storage.secondary.SecondaryStorageListener] (AgentConnectTaskPool-19:) Received a host startup notification com.cloud.agent.api.StartupSecondaryStorageCommand INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-19:) Received a host startup notification INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found routing-8 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 203-14-8d8b9015-3688-3cd7-8970-15ad1b8a1e8a already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 211-82-e0654140-451e-3a67-bf52-0a4fe4e178ed already in the image store ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Monitor DownloadListener says there is an error in the connect process for 17 due to null java.lang.NullPointerException at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:342) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1086) at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:144) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Host 17 is disconnecting with event AgentDisconnected Pattern not found (press RETURN) Attaching DB Dump for your reference -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2867) Cannot add multiple vmware zones in vCenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati closed CLOUDSTACK-2867. --- Cannot add multiple vmware zones in vCenter --- Key: CLOUDSTACK-2867 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2867 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: VMWare cloudstack deployment. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Sateesh Chodapuneedi Create a datacenter in vmware, say dc1, add a cluster to it, say cluster1, add one or more hosts to cluster1. Add a zone in cloudstack, and provide dc1/cluster1 info for it. It'll go through fine. Next, create dc2, cluster2 in vCenter with new host(s). Attempt to add a new zone in cloudstack providing dc2/cluster2 info. It will fail with the following exception: INFO [cloud.configuration.ConfigurationManagerImpl] (94321089@qtp-1454176402-24:) adding a new subnet to the network 209 WARN [admin.zone.AddVmwareDcCmd] (1538955034@qtp-1454176402-23:) Exception: com.cloud.exception.ResourceInUseException: This DC is already part of other CloudStack zone(s). Cannot add this DC to more zones. at com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.addVmwareDatacenter(VmwareManagerImpl.java:952) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.admin.zone.AddVmwareDcCmd.execute(AddVmwareDcCmd.java:97) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) INFO [cloud.api.ApiServer] (1538955034@qtp-1454176402-23:) This DC is already part of other CloudStack zone(s). Cannot add this DC to more zones. INFO [vmware.resource.VmwareResource] (DirectAgent-100:10.223.74.132) Executing resource NetworkUsageCommand It looks like the CustomFieldDef[] cloud.zone key is getting defined globally for all DCs. So once it's set to true, it's probably getting read as true for new DCs as well. Or probably it's just that we're reading it wrongly in the mgmt server (doesn't look like that's the case though). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2969) Exception when creating vlan ip range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati closed CLOUDSTACK-2969. --- Verified. Exception when creating vlan ip range - Key: CLOUDSTACK-2969 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2969 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployment in cloudstack Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Labels: automation, integration-tests Fix For: 4.2.0 When creating an advanced zone configuration in the GUI using the zone config wizard, this exception is encountered: 135endIp=10.223.74.165response=jsonsessionkey=Uc2mmfyGUdrKCo7hDfiTMEwk8sU%3D_=1371065885754 2013-06-12 06:14:29,530 DEBUG [cloud.api.ApiServlet] (324500051@qtp-2127994111-6:null) ===START=== 10.217.252.54 -- GET command=createVlanIpRangezoneId=3bc75416-c576-4456-8e38-0cabc0f4ee3evlan=541gateway=10.223.154.129netmask=255.255.255.128startip=10.223.154.135endip=10.223.154.165forVirtualNetwork=trueresponse=jsonsessionkey=Uc2mmfyGUdrKCo7hDfiTMEwk8sU%3D_=1371065885983 2013-06-12 06:14:29,577 ERROR [cloud.api.ApiServer] (324500051@qtp-2127994111-6:null) unhandled exception executing api command: createVlanIpRange java.lang.NullPointerException at com.cloud.configuration.ConfigurationManagerImpl.createVlanAndPublicIpRange(ConfigurationManagerImpl.java:2531) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.admin.vlan.CreateVlanIpRangeCmd.execute(CreateVlanIpRangeCmd.java:211) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2771) Unable to create guest VM in basic zone: Zone is dedicated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati closed CLOUDSTACK-2771. --- Verified that the fix works. Unable to create guest VM in basic zone: Zone is dedicated -- Key: CLOUDSTACK-2771 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2771 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: 4.2.0, vmware setup (haven't checked if this issue is seen in non-vmware cloudstack deployments). Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Prachi Damle Fix For: 4.2.0 1) Create a basic zone in cloudstack using the zone wizard, with hypervisor type set to vmware. Select DefaultSharedNetworkOffering as the network offering. 2) Attempt to create a guest VM using the instance wizard. The operation fails with the following exception seen in the logs: WARN [apache.cloudstack.alerts] (Job-Executor-9:job-9) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-9) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM. Zone bzone1 is dedicated. at com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:454) at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:213) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3268) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2807) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2793) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3554) NPE while attaching VMWARE Tools ISO to the instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3554.
-
Resolution: Fixed
NPE while attaching VMWARE Tools ISO to the instance
-
Key: CLOUDSTACK-3554
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3554
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Fix For: 4.2.0
Attachments: apilog.log, management-server.log
Steps:
1. Configure Adv Zone with VMWARE
2. Deploy instance with newly added account
3. Tried to attach VMWARE tools iso to this instance
Observation:
It failed with NPE:
2013-07-16 17:22:43,089 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===START=== 10.144.6.19 -- GET
command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
2013-07-16 17:22:43,146 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-18:null) submit async job-77 = [
24362d6b-4eb7-48d0-893a-2ac61fa84d5e ], details: AsyncJobVO {id:77, userId:
8, accountId: 8, sessionKey: null, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.user.iso.AttachIsoCmd, cmdOriginator: null,
cmdInfo:
{id:e09209bc-4731-4aac-b65e-00aed3540993,response:json,sessionkey:5vYbKOzqMAqkmN9vVQ/695HcVDs\u003d,virtualmachineid:0f7b7a84-2325-4100-817a-e63e216c2b75,cmdEventType:ISO.ATTACH,ctxUserId:8,httpmethod:GET,_:1373975773858,ctxAccountId:8,ctxStartEventId:299},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-07-16 17:22:43,149 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 10.144.6.19 -- GET
command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
2013-07-16 17:22:43,152 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Executing
org.apache.cloudstack.api.command.user.iso.AttachIsoCmd for job-77 = [
24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]
2013-07-16 17:22:43,186 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to
Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,188 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to
VM[User|dc2user1i1] granted to Acct[8-dc2user1] by
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to
Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,194 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to
VM[User|dc2user1i1] granted to Acct[8-dc2user1] by
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,209 DEBUG [agent.transport.Request]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq
4-1669464340: Sending { Cmd , MgmtId: 187767034175903, via: 4, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
Tools Installer
ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
}
2013-07-16 17:22:43,210 DEBUG [agent.transport.Request]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq
4-1669464340: Executing: { Cmd , MgmtId: 187767034175903, via: 4, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
Tools Installer
ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
}
2013-07-16 17:22:43,211 DEBUG [agent.manager.DirectAgentAttache]
[jira] [Commented] (CLOUDSTACK-3600) [Automation][BVT] Failed to delete and extract ISO in vmware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711920#comment-13711920 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3600: - I just tried these two operations on the latest 4.2 branch. The ExtractIsoCmd API fired when we attempt to download an uploaded ISO works fine for me. I am not sure why the above NPE showed up in the above run. It is possible that the issue might have been fixed in later commits on 4.2. Next, when I attempt to delete a template created from a root volume, I don't run into an exception, though I run into a failure. The first time, the UI gives a failure message, probably because when it does a list templates, it still finds the template there. However, the logs show this: INFO [cloud.template.HypervisorTemplateAdapter] (Job-Executor-5:job-36 = [ 552300c6-ec62-49db-a74e-3531dbb1ec9c ]) Delete template from image store: s1 WARN [cloud.template.HypervisorTemplateAdapter] (Job-Executor-5:job-36 = [ 552300c6-ec62-49db-a74e-3531dbb1ec9c ]) Failed to delete the template Tmpl[206-OVA-2cb7e13c2-3c44-36d0-b8cd-a9017e073ec0 from the image store: s1 due to: Unable to delete file template under Template path 2cb7e13c2-3c44-36d0-b8cd-a9017e073ec0 INFO [cloud.template.HypervisorTemplateAdapter] (Job-Executor-6:job-37 = [ 23075f1f-06aa-4870-be35-41b73ebee6ef ]) Unable to find image store still having template: vm1template1, so just mark the template removed INFO [cloud.template.HypervisorTemplateAdapter] (Job-Executor-6:job-37 = [ 23075f1f-06aa-4870-be35-41b73ebee6ef ]) Delete template from template table The template is marked removed, so if I retry the same operation a second time, the template is deleted. But it still seems to be resident on secondary storage: [root@nfs2 tmpl]# find . | grep -i 2cb7e ./2/206/2cb7e13c2-3c44-36d0-b8cd-a9017e073ec0.ovf ./2/206/2cb7e13c2-3c44-36d0-b8cd-a9017e073ec0.ova ./2/206/2cb7e13c2-3c44-36d0-b8cd-a9017e073ec0-disk0.vmdk [root@nfs2 tmpl]# Need to investigate further to see why the template is not being found. Looks like the template path isn't being built correctly - probably the imagestore isn't being set correctly? I think this issue can be made critical/major instead of a blocker since I don't run into the above exceptions with the latest master. [Automation][BVT] Failed to delete and extract ISO in vmware --- Key: CLOUDSTACK-3600 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3600 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: ISO Affects Versions: 4.2.0 Environment: VMware Build 4.2 Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 BVT failure integration.smoke.test_iso.TestISO.test_03_delete_iso Unaable to delete iso observed below error in MS log INFO [cloud.template.HypervisorTemplateAdapter] (Job-Executor-15:job-1591 = [ 903c440e-7f7c-4151-9258-88fa82c1d05c ]) Delete template from image store: nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-15:job-1591 = [ 903c440e-7f7c-4151-9258-88fa82c1d05c ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.template.DeleteTemplateCmd com.cloud.utils.exception.CloudRuntimeException: Failed to update state at org.apache.cloudstack.storage.image.store.TemplateObject.processEvent(TemplateObject.java:164) at org.apache.cloudstack.storage.image.TemplateServiceImpl.deleteTemplateAsync(TemplateServiceImpl.java:513) at com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:242) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.template.TemplateManagerImpl.deleteTemplate(TemplateManagerImpl.java:1063) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.template.DeleteTemplateCmd.execute(DeleteTemplateCmd.java:112) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166)
[jira] [Assigned] (CLOUDSTACK-3554) NPE while attaching VMWARE Tools ISO to the instance
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3554:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
NPE while attaching VMWARE Tools ISO to the instance
-
Key: CLOUDSTACK-3554
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3554
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Fix For: 4.2.0
Attachments: apilog.log, management-server.log
Steps:
1. Configure Adv Zone with VMWARE
2. Deploy instance with newly added account
3. Tried to attach VMWARE tools iso to this instance
Observation:
It failed with NPE:
2013-07-16 17:22:43,089 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===START=== 10.144.6.19 -- GET
command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
2013-07-16 17:22:43,146 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-18:null) submit async job-77 = [
24362d6b-4eb7-48d0-893a-2ac61fa84d5e ], details: AsyncJobVO {id:77, userId:
8, accountId: 8, sessionKey: null, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.user.iso.AttachIsoCmd, cmdOriginator: null,
cmdInfo:
{id:e09209bc-4731-4aac-b65e-00aed3540993,response:json,sessionkey:5vYbKOzqMAqkmN9vVQ/695HcVDs\u003d,virtualmachineid:0f7b7a84-2325-4100-817a-e63e216c2b75,cmdEventType:ISO.ATTACH,ctxUserId:8,httpmethod:GET,_:1373975773858,ctxAccountId:8,ctxStartEventId:299},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-07-16 17:22:43,149 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 10.144.6.19 -- GET
command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
2013-07-16 17:22:43,152 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Executing
org.apache.cloudstack.api.command.user.iso.AttachIsoCmd for job-77 = [
24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]
2013-07-16 17:22:43,186 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to
Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,188 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to
VM[User|dc2user1i1] granted to Acct[8-dc2user1] by
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to
Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,194 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to
VM[User|dc2user1i1] granted to Acct[8-dc2user1] by
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,209 DEBUG [agent.transport.Request]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq
4-1669464340: Sending { Cmd , MgmtId: 187767034175903, via: 4, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
Tools Installer
ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
}
2013-07-16 17:22:43,210 DEBUG [agent.transport.Request]
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq
4-1669464340: Executing: { Cmd , MgmtId: 187767034175903, via: 4, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
Tools Installer
ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
}
2013-07-16 17:22:43,211 DEBUG
[jira] [Assigned] (CLOUDSTACK-3514) [Automation] Vmware - Failed to download default template for first zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3514: --- Assignee: Venkata Siva Vijayendra Bhamidipati [Automation] Vmware - Failed to download default template for first zone - Key: CLOUDSTACK-3514 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3514 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, VMware Affects Versions: 4.2.0 Environment: 4.2 branch build VMware Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3514.rar Steps to reproduce Create Vmware advanced zone with 2 zones Result 2 Zones created sucessfully but failed download default template for first zone mysql select name, data_center_name from template_view where hypervisor_type = 'VMware' and state = 'Ready'; +-+--+ | name| data_center_name | +-+--+ | SystemVM Template (vSphere) | Adv-VMware-Zone1 | | SystemVM Template (vSphere) | Adv-VMware-Zone2 | | CentOS 5.3(64-bit) no GUI (vSphere) | Adv-VMware-Zone2 | +-+--+ 3 rows in set (0.00 sec) Please see the attached catalina.out, seems system vmware (ssv name : v9) created for the second zone (Adv-VMware-Zone2) first then (ssvm name : vm20) second zone (Adv-VMware-Zone1), also observed below massage, to skip download template INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Secondary storage vm s-20-VM is started INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) Primary secondary storage is not even started, wait until next turn INFO [storage.secondary.SecondaryStorageListener] (AgentConnectTaskPool-19:) Received a host startup notification com.cloud.agent.api.StartupSecondaryStorageCommand INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-19:) Received a host startup notification INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found routing-8 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 203-14-8d8b9015-3688-3cd7-8970-15ad1b8a1e8a already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 211-82-e0654140-451e-3a67-bf52-0a4fe4e178ed already in the image store ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Monitor DownloadListener says there is an error in the connect process for 17 due to null java.lang.NullPointerException at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:342) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1086) at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:144) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Host 17 is disconnecting with event AgentDisconnected Pattern not found (press RETURN) Attaching DB Dump for your reference -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3311) PVLAN - vmware dvswitch - stop/start nd reboot Virtual router FAIL
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3311.
-
Resolution: Fixed
PVLAN - vmware dvswitch - stop/start nd reboot Virtual router FAIL
---
Key: CLOUDSTACK-3311
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3311
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: MS 10.223.195.113
CloudPlatform-4.2-129-rhel6.3.tar.gz
hostESXi 5.0
Reporter: angeline shen
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.log.gz
1. advance zone. pvlan guest network.create domain admin and user
accounts.
2. login as domain admin. Deploy VMs. login as user. Deploy VMs
3. stop VR. start VR fail.reboot VR fail.due to:
2013-07-01 11:04:00,772 WARN [vmware.resource.VmwareResource]
(DirectAgent-22:10.223.81.41) StartCommand failed due to Exception:
java.lang.Exception
Message: PVLAN ID 1612 is already in use as a promiscuous VLAN in the DVSwitch
java.lang.Exception: PVLAN ID 1612 is already in use as a promiscuous VLAN in
the DVSwitch
MS log:
2013-07-01 11:04:00,752 INFO [vmware.resource.VmwareResource]
(DirectAgent-22:10.223.81.41) Prepare network on vmwaredvs
P[dvSwitch2:untagged] with name prefix: cloud.guest
2013-07-01 11:04:00,767 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-22:10.223.81.41) Found distributed vSwitch
com.vmware.vim25.ManagedObjectReference@7a2ae54d
2013-07-01 11:04:00,772 ERROR [vmware.mo.HypervisorHostHelper]
(DirectAgent-22:10.223.81.41) PVLAN ID 1612 is already in use as a
promiscuous VLAN in the DVSwitch
2013-07-01 11:04:00,772 WARN [vmware.resource.VmwareResource]
(DirectAgent-22:10.223.81.41) StartCommand failed due to Exception:
java.lang.Exception
Message: PVLAN ID 1612 is already in use as a promiscuous VLAN in the DVSwitch
java.lang.Exception: PVLAN ID 1612 is already in use as a promiscuous VLAN in
the DVSwitch
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:512)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2926)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2675)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:476)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-01 11:04:00,774 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-22:null) Seq 2-2101805090: Cancelling because one of the answers
is false and it is stop on error.
2013-07-01 11:04:00,774 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-22:null) Seq 2-2101805090: Response Received:
2013-07-01 11:04:00,775 DEBUG [agent.transport.Request] (DirectAgent-22:null)
Seq 2-2101805090: Processing: { Ans: , MgmtId: 6655051826959, via: 2, Ver:
v1, Flags: 10, [{StartAnswer:{vm:{id:4,name:r-4-VM,bootload
er:HVM,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,arch:i686,os:Debian
GNU/Linux 5.0 (32-bit),bootArgs: template=domP name=r-4-VM
eth0ip=10.223.161.141 eth
0mask=255.255.255.192 gateway=10.223.161.129 domain=cs1cloud.internal
dhcprange=10.223.161.129 eth1ip=10.223.81.48 eth1mask=255.255.255.192
mgmtcidr=10.223.195.0/24 localgw=10.223.81.1 type=dhcpsrvr
disable_rp_filter=true ex
tra_pubnics=2 dns1=10.223.110.254
nic_macs=06:d1:0e:00:00:15|02:00:6e:b1:00:14,rebootOnCrash:false,enableHA:true,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:64e0048090cecfd7,params:{nicAdapte
[jira] [Commented] (CLOUDSTACK-3514) [Automation] Vmware - Failed to download default template for first zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709240#comment-13709240 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3514: - Tried reproducing this on my setup with master and 4.2, but wasn't able to. System VMs and guest VMs came up fine. I created two advanced zones and separately enabled both in quick succession. However, the code itself has an unprotected reference that leads to the NPE and that must be fixed. I'll put up a patch for review. Not sure what causes the above condition, but with the fix in place the mgmt server will proceed since it won't hit the above NPE. [Automation] Vmware - Failed to download default template for first zone - Key: CLOUDSTACK-3514 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3514 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, VMware Affects Versions: 4.2.0 Environment: 4.2 branch build VMware Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3514.rar, CLOUDSTACK-3514.rar Steps to reproduce Create Vmware advanced zone with 2 zones Result 2 Zones created sucessfully but failed download default template for first zone mysql select name, data_center_name from template_view where hypervisor_type = 'VMware' and state = 'Ready'; +-+--+ | name| data_center_name | +-+--+ | SystemVM Template (vSphere) | Adv-VMware-Zone1 | | SystemVM Template (vSphere) | Adv-VMware-Zone2 | | CentOS 5.3(64-bit) no GUI (vSphere) | Adv-VMware-Zone2 | +-+--+ 3 rows in set (0.00 sec) Please see the attached catalina.out, seems system vmware (ssv name : v9) created for the second zone (Adv-VMware-Zone2) first then (ssvm name : vm20) second zone (Adv-VMware-Zone1), also observed below massage, to skip download template INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Secondary storage vm s-20-VM is started INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) Primary secondary storage is not even started, wait until next turn INFO [storage.secondary.SecondaryStorageListener] (AgentConnectTaskPool-19:) Received a host startup notification com.cloud.agent.api.StartupSecondaryStorageCommand INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-19:) Received a host startup notification INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found routing-8 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 203-14-8d8b9015-3688-3cd7-8970-15ad1b8a1e8a already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 211-82-e0654140-451e-3a67-bf52-0a4fe4e178ed already in the image store ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Monitor DownloadListener says there is an error in the connect process for 17 due to null java.lang.NullPointerException at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:342) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1086) at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:144) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO
[jira] [Commented] (CLOUDSTACK-3514) [Automation] Vmware - Failed to download default template for first zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709348#comment-13709348 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3514: - Patch posted for review at https://reviews.apache.org/r/12566/ [Automation] Vmware - Failed to download default template for first zone - Key: CLOUDSTACK-3514 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3514 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, VMware Affects Versions: 4.2.0 Environment: 4.2 branch build VMware Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-3514.rar, CLOUDSTACK-3514.rar Steps to reproduce Create Vmware advanced zone with 2 zones Result 2 Zones created sucessfully but failed download default template for first zone mysql select name, data_center_name from template_view where hypervisor_type = 'VMware' and state = 'Ready'; +-+--+ | name| data_center_name | +-+--+ | SystemVM Template (vSphere) | Adv-VMware-Zone1 | | SystemVM Template (vSphere) | Adv-VMware-Zone2 | | CentOS 5.3(64-bit) no GUI (vSphere) | Adv-VMware-Zone2 | +-+--+ 3 rows in set (0.00 sec) Please see the attached catalina.out, seems system vmware (ssv name : v9) created for the second zone (Adv-VMware-Zone2) first then (ssvm name : vm20) second zone (Adv-VMware-Zone1), also observed below massage, to skip download template INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Secondary storage vm s-20-VM is started INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) Primary secondary storage is not even started, wait until next turn INFO [storage.secondary.SecondaryStorageListener] (AgentConnectTaskPool-19:) Received a host startup notification com.cloud.agent.api.StartupSecondaryStorageCommand INFO [network.security.SecurityGroupListener] (AgentConnectTaskPool-19:) Received a host startup notification INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found routing-8 already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 203-14-8d8b9015-3688-3cd7-8970-15ad1b8a1e8a already in the image store INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-19:) Template Sync found 211-82-e0654140-451e-3a67-bf52-0a4fe4e178ed already in the image store ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Monitor DownloadListener says there is an error in the connect process for 17 due to null java.lang.NullPointerException at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:342) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:586) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1086) at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:144) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) INFO [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-19:) Host 17 is disconnecting with event AgentDisconnected Pattern not found (press RETURN) Attaching DB Dump for your reference -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3311) PVLAN - vmware dvswitch - stop/start nd reboot Virtual router FAIL
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707221#comment-13707221
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3311:
-
Patch for fix posted for review at https://reviews.apache.org/r/12517/
PVLAN - vmware dvswitch - stop/start nd reboot Virtual router FAIL
---
Key: CLOUDSTACK-3311
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3311
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: MS 10.223.195.113
CloudPlatform-4.2-129-rhel6.3.tar.gz
hostESXi 5.0
Reporter: angeline shen
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.log.gz
1. advance zone. pvlan guest network.create domain admin and user
accounts.
2. login as domain admin. Deploy VMs. login as user. Deploy VMs
3. stop VR. start VR fail.reboot VR fail.due to:
2013-07-01 11:04:00,772 WARN [vmware.resource.VmwareResource]
(DirectAgent-22:10.223.81.41) StartCommand failed due to Exception:
java.lang.Exception
Message: PVLAN ID 1612 is already in use as a promiscuous VLAN in the DVSwitch
java.lang.Exception: PVLAN ID 1612 is already in use as a promiscuous VLAN in
the DVSwitch
MS log:
2013-07-01 11:04:00,752 INFO [vmware.resource.VmwareResource]
(DirectAgent-22:10.223.81.41) Prepare network on vmwaredvs
P[dvSwitch2:untagged] with name prefix: cloud.guest
2013-07-01 11:04:00,767 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-22:10.223.81.41) Found distributed vSwitch
com.vmware.vim25.ManagedObjectReference@7a2ae54d
2013-07-01 11:04:00,772 ERROR [vmware.mo.HypervisorHostHelper]
(DirectAgent-22:10.223.81.41) PVLAN ID 1612 is already in use as a
promiscuous VLAN in the DVSwitch
2013-07-01 11:04:00,772 WARN [vmware.resource.VmwareResource]
(DirectAgent-22:10.223.81.41) StartCommand failed due to Exception:
java.lang.Exception
Message: PVLAN ID 1612 is already in use as a promiscuous VLAN in the DVSwitch
java.lang.Exception: PVLAN ID 1612 is already in use as a promiscuous VLAN in
the DVSwitch
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:512)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2926)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2675)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:476)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-01 11:04:00,774 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-22:null) Seq 2-2101805090: Cancelling because one of the answers
is false and it is stop on error.
2013-07-01 11:04:00,774 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-22:null) Seq 2-2101805090: Response Received:
2013-07-01 11:04:00,775 DEBUG [agent.transport.Request] (DirectAgent-22:null)
Seq 2-2101805090: Processing: { Ans: , MgmtId: 6655051826959, via: 2, Ver:
v1, Flags: 10, [{StartAnswer:{vm:{id:4,name:r-4-VM,bootload
er:HVM,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,arch:i686,os:Debian
GNU/Linux 5.0 (32-bit),bootArgs: template=domP name=r-4-VM
eth0ip=10.223.161.141 eth
0mask=255.255.255.192 gateway=10.223.161.129 domain=cs1cloud.internal
dhcprange=10.223.161.129 eth1ip=10.223.81.48 eth1mask=255.255.255.192
mgmtcidr=10.223.195.0/24 localgw=10.223.81.1 type=dhcpsrvr
disable_rp_filter=true ex
tra_pubnics=2 dns1=10.223.110.254
[jira] [Commented] (CLOUDSTACK-644) Resize volumes feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707357#comment-13707357 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-644: Marcus has checked in all the code related to this feature in commits 4f274d0b8ed9ad57bd9621bb0c9fc46c10990534, 975021dda1aeee24c8729407e323a5e884e9ad31 and c5185c09efd8747f22e1ed4268cea3d037d6fde6. The code submitted in the review link provided above by Talluri went into commit# c5185c09efd8747f22e1ed4268cea3d037d6fde6. However, as part of commit # a22403edcd656562e2e71613fd11cf8e69554be8, Edison reorganized code from StorageManagerImpl to VolumeManagerImpl and some code from commit # c5185c09efd8747f22e1ed4268cea3d037d6fde6 was missed out, resulting in resize volume not getting kicked off for vmware. I'll log a separate bug to track this and provide a patch containing the missing code. I've tested master with the patch and am confirming that volume resize works for vmware. Resize volumes feature -- Key: CLOUDSTACK-644 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-644 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.1.0 Time Spent: 4h Remaining Estimate: 0h We would like the ability to resize root/data volumes in order to accomodate hybrid/traditional server loads. We've got some code that provides a resizeVolume API call, but we need to coordinate with the storage refactor, as well as making sure that the implementation is satisfactory. It's possible that we'll want to reimplement it within the new volume service. Or maybe we can implement this existing code/api call server side and the new storage services can build off of it. Would like so me input on the proper way to proceed. Release Planning: Dev list discussion: http://markmail.org/message/ptihqdglplndrqqn Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Resize+Data+Volumes Feature branch: reviewboard -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3509) Put in missing code to kick off non root volume resize operations in vmware deployments
Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-3509: --- Summary: Put in missing code to kick off non root volume resize operations in vmware deployments Key: CLOUDSTACK-3509 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3509 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployments in cloudstack 4.2. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Currently, on master, issuing a volume resize operation on a non-root volume of a guest VM resident on ESX hypervisor throws the following exception: ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-3:job-23 = [ 8f455c05-6b91-4eb0-aa95-a80993263769 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd com.cloud.exception.InvalidParameterValueException: Cloudstack currently only supports volumes marked as KVM or XenServer hypervisor for resize at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:1127) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:189) at org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd.execute(ResizeVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:532) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) The volume resize code for XS, KVM and VMWare was checked in by Marcus on behalf of Hongtu, but a small part of that code was inadvertently overwritten in a later commit, resulting in the above loss of functionality. Creating this bug to track the re-checkin of that missing hypervisor check in VolumeManagerImpl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3509) Put in missing code to kick off non root volume resize operations in vmware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3509: Description: Currently, on master, issuing a volume resize operation on a non-root volume of a guest VM resident on ESX hypervisor throws the following exception: ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-3:job-23 = [ 8f455c05-6b91-4eb0-aa95-a80993263769 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd com.cloud.exception.InvalidParameterValueException: Cloudstack currently only supports volumes marked as KVM or XenServer hypervisor for resize at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:1127) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:189) at org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd.execute(ResizeVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:532) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) The volume resize code for XS, KVM and VMWare was checked in by Marcus on behalf of Hongtu, but a small part of that code was inadvertently overwritten in a later commit, resulting in the above loss of functionality. Creating this bug to track the re-checkin of that missing hypervisor check in VolumeManagerImpl. The original ticket tracking the volume resize feature is CLOUDSTACK-644 (https://issues.apache.org/jira/browse/CLOUDSTACK-644). was: Currently, on master, issuing a volume resize operation on a non-root volume of a guest VM resident on ESX hypervisor throws the following exception: ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-3:job-23 = [ 8f455c05-6b91-4eb0-aa95-a80993263769 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd com.cloud.exception.InvalidParameterValueException: Cloudstack currently only supports volumes marked as KVM or XenServer hypervisor for resize at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:1127) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:189) at org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd.execute(ResizeVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:532) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) The volume resize code for XS, KVM and VMWare was checked in by Marcus on behalf of Hongtu, but a small part of that code was inadvertently overwritten in a later commit, resulting in the above loss of functionality. Creating this bug to track the re-checkin of that missing hypervisor check in VolumeManagerImpl. Put in missing code to kick off non root volume resize operations in vmware deployments --- Key: CLOUDSTACK-3509 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3509 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployments in cloudstack 4.2. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Currently, on master, issuing a volume resize operation on a non-root volume of a guest VM resident on ESX hypervisor throws
[jira] [Commented] (CLOUDSTACK-3509) Put in missing code to kick off non root volume resize operations in vmware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707367#comment-13707367 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3509: - Patch posted to https://reviews.apache.org/r/12521/ Put in missing code to kick off non root volume resize operations in vmware deployments --- Key: CLOUDSTACK-3509 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3509 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployments in cloudstack 4.2. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Currently, on master, issuing a volume resize operation on a non-root volume of a guest VM resident on ESX hypervisor throws the following exception: ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-3:job-23 = [ 8f455c05-6b91-4eb0-aa95-a80993263769 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd com.cloud.exception.InvalidParameterValueException: Cloudstack currently only supports volumes marked as KVM or XenServer hypervisor for resize at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:1127) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:189) at org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd.execute(ResizeVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:532) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) The volume resize code for XS, KVM and VMWare was checked in by Marcus on behalf of Hongtu, but a small part of that code was inadvertently overwritten in a later commit, resulting in the above loss of functionality. Creating this bug to track the re-checkin of that missing hypervisor check in VolumeManagerImpl. The original ticket tracking the volume resize feature is CLOUDSTACK-644 (https://issues.apache.org/jira/browse/CLOUDSTACK-644). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-644) Resize volumes feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707366#comment-13707366 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-644: https://issues.apache.org/jira/browse/CLOUDSTACK-3509 Resize volumes feature -- Key: CLOUDSTACK-644 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-644 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.1.0 Time Spent: 4h Remaining Estimate: 0h We would like the ability to resize root/data volumes in order to accomodate hybrid/traditional server loads. We've got some code that provides a resizeVolume API call, but we need to coordinate with the storage refactor, as well as making sure that the implementation is satisfactory. It's possible that we'll want to reimplement it within the new volume service. Or maybe we can implement this existing code/api call server side and the new storage services can build off of it. Would like so me input on the proper way to proceed. Release Planning: Dev list discussion: http://markmail.org/message/ptihqdglplndrqqn Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Resize+Data+Volumes Feature branch: reviewboard -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3490) [VMware]Router VM failed to start with VMware hypervisor .
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3490. - Resolution: Duplicate Assignee: Venkata Siva Vijayendra Bhamidipati Closing as a dup of CLOUDSTACK-3425. Manasa, after the fix for CLOUDSTACK-3425 is committed to master, if you still see this issue, please reopen this bug. [VMware]Router VM failed to start with VMware hypervisor . --- Key: CLOUDSTACK-3490 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3490 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: 4.2 stable build Reporter: manasaveloori Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Attachments: management-server.zip Steps: 1.Have CS with VMware hypervisor. 2.Create primary storage –local .Secondary storage-NFS. 3.Deploy a user VM. Observations: Observed that the Router VM fails to start with following exception 2013-07-12 18:25:49,696 DEBUG [vmware.mo.HostMO] (DirectAgent-16:10.147.40.29) VM r-18-VM found in host cache 2013-07-12 18:25:49,766 INFO [vmware.resource.VmwareResource] (DirectAgent-16:10.147.40.29) Configure VNC port for VM r-18-VM, port: 5926, host: 10.147.40.29 2013-07-12 18:25:50,224 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM 2013-07-12 18:25:50,265 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2 is ready to launch secondary storage VM 2013-07-12 18:25:50,626 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy 2013-07-12 18:25:50,643 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 2 is ready to launch console proxy 2013-07-12 18:25:51,048 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) ===START=== 10.252.192.69 -- GET command=queryAsyncJobResultjobId=c5e0d5a6-f41f-4014-86f7-41f0d6d6c43aresponse=jsonsessionkey=B2dkl66uTrHsb5xkAC2urfO%2F7xo%3D_=1373614297789 2013-07-12 18:25:51,087 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) ===END=== 10.252.192.69 -- GET command=queryAsyncJobResultjobId=c5e0d5a6-f41f-4014-86f7-41f0d6d6c43aresponse=jsonsessionkey=B2dkl66uTrHsb5xkAC2urfO%2F7xo%3D_=1373614297789 2013-07-12 18:25:51,693 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 3 routers to update status. 2013-07-12 18:25:51,696 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. 2013-07-12 18:25:51,808 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 3 routers to update status. 2013-07-12 18:25:51,811 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. 2013-07-12 18:25:53,411 WARN [vmware.resource.VmwareResource] (DirectAgent-16:10.147.40.29) StartCommand failed due to Exception: java.lang.RuntimeException Message: A specified parameter was not correct. java.lang.RuntimeException: A specified parameter was not correct. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:835) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2834) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:507) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-12 18:25:53,419 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-16:null) Seq
[jira] [Updated] (CLOUDSTACK-3509) Put in missing code to kick off non root volume resize operations in vmware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3509: Status: Ready To Review (was: In Progress) Put in missing code to kick off non root volume resize operations in vmware deployments --- Key: CLOUDSTACK-3509 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3509 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployments in cloudstack 4.2. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Currently, on master, issuing a volume resize operation on a non-root volume of a guest VM resident on ESX hypervisor throws the following exception: ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-3:job-23 = [ 8f455c05-6b91-4eb0-aa95-a80993263769 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd com.cloud.exception.InvalidParameterValueException: Cloudstack currently only supports volumes marked as KVM or XenServer hypervisor for resize at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:1127) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:189) at org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd.execute(ResizeVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:532) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) The volume resize code for XS, KVM and VMWare was checked in by Marcus on behalf of Hongtu, but a small part of that code was inadvertently overwritten in a later commit, resulting in the above loss of functionality. Creating this bug to track the re-checkin of that missing hypervisor check in VolumeManagerImpl. The original ticket tracking the volume resize feature is CLOUDSTACK-644 (https://issues.apache.org/jira/browse/CLOUDSTACK-644). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3509) Put in missing code to kick off non root volume resize operations in vmware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3509. - Resolution: Fixed Put in missing code to kick off non root volume resize operations in vmware deployments --- Key: CLOUDSTACK-3509 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3509 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployments in cloudstack 4.2. Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Venkata Siva Vijayendra Bhamidipati Currently, on master, issuing a volume resize operation on a non-root volume of a guest VM resident on ESX hypervisor throws the following exception: ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-3:job-23 = [ 8f455c05-6b91-4eb0-aa95-a80993263769 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd com.cloud.exception.InvalidParameterValueException: Cloudstack currently only supports volumes marked as KVM or XenServer hypervisor for resize at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:1127) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:189) at org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd.execute(ResizeVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:532) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) The volume resize code for XS, KVM and VMWare was checked in by Marcus on behalf of Hongtu, but a small part of that code was inadvertently overwritten in a later commit, resulting in the above loss of functionality. Creating this bug to track the re-checkin of that missing hypervisor check in VolumeManagerImpl. The original ticket tracking the volume resize feature is CLOUDSTACK-644 (https://issues.apache.org/jira/browse/CLOUDSTACK-644). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3264) [ZWPS]NPE while finding storage pools for migration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-3264. - Resolution: Fixed [ZWPS]NPE while finding storage pools for migration --- Key: CLOUDSTACK-3264 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3264 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployment , esxi 5.1 Reporter: Srikanteswararao Talluri Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Steps to reproduce: = Issue findStoragePoolsForMigration API for a volume ===START=== 10.252.192.7 -- GET command=findStoragePoolsForMigrationid=02e0e77b-59dd-4bc4-a3b8-ba3914212883response=jsonsessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D_=1372404084373 2013-06-28 18:16:45,204 ERROR [cloud.api.ApiServer] (catalina-exec-16:null) unhandled exception executing api command: findStoragePoolsForMigration java.lang.NullPointerException at com.cloud.server.ManagementServerImpl.listStoragePoolsForMigrationOfVolume(ManagementServerImpl.java:1336) at org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-06-28 18:16:45,207 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) ===END=== 10.252.192.7 -- GET command=findStoragePoolsForMigrationid=02e0e77b-59dd-4bc4-a3b8-ba3914212883response=jsonsessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D_=1372404084373 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-1510) NPE when primary storage is added with wrong path
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-1510.
-
Resolution: Fixed
NPE when primary storage is added with wrong path
--
Key: CLOUDSTACK-1510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Minor
Fix For: 4.2.0
Steps :
1. Configure Advanced zone
2. Tried to add second nfs primary storage with wrong path.
Observation: It failed with NPE
2013-03-05 15:02:16,535 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:203,uuid:40e80e79-ac1b-31d1-a067-1ec03e7bc67b,host:10.102.192.100,path:/cpg_vol/sailaja/priamry,port:2049,type:NetworkFilesystem},localPath:/mnt//40e80e79-ac1b-31d1-a067-1ec03e7bc67b,wait:0}}]
}
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 1-16676: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\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,wait:0}}] }
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Received: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-03-05 15:02:16,702 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-25:null) Details from executing class
com.cloud.agent.api.ModifyStoragePoolCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-03-05 15:02:16,708 WARN [cloud.storage.StorageManagerImpl]
(catalina-exec-25:null) Unable to establish a connection between
Host[-1-Routing] and Pool[203|NetworkFilesystem]
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203]
is unreachable: Unable establish connection from storage head to storage pool
203 due to java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
[jira] [Assigned] (CLOUDSTACK-3425) Vmware - Not able to deploy VM - Router Vm fails to start.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3425:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
Vmware - Not able to deploy VM - Router Vm fails to start.
--
Key: CLOUDSTACK-3425
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3425
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Build from 4.2
Reporter: Sangeetha Hariharan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.log
Vmware - Not able to deploy VM - Router Vm fails to start.
Steps to reproduce the problem:
Advanced zone set up with vmware 5.0 host.
Once the zone is configured and enabled , system Vms come up successfully.
Default template gets downloaded.
Try to deploy a new VM.
VM deployment fails because of the router VM not being able to start
successfully.
Router is in stopped state.
Trying to start the router manually also fails.
Following exception seen when start command is issued for Router :
2013-07-09 10:40:15,805 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-158:10.223.57.66) Network cloud.public.1371.0.1-vSwitch0 is
ready on vSwitch vSwitch0
2013-07-09 10:40:15,854 INFO [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Preparing NIC device on network
cloud.public.1371.0.1-vSwitch0
2013-07-09 10:40:15,855 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Prepare NIC at new device
{operation:ADD,device:{addressType:Manual,macAddress:02:00:0e:fc:00:04,key:-7,backing:{network:{value:network-30877,type:Network},deviceName:cloud.public.1371.0.1-vSwitch0},connectable:{startConnected:true,allowGuestControl:true,connected:true},unitNumber:4}}
2013-07-09 10:40:15,855 DEBUG [vmware.mo.HostMO]
(DirectAgent-158:10.223.57.66) find VM r-4-VM on host
2013-07-09 10:40:15,855 DEBUG [vmware.mo.HostMO]
(DirectAgent-158:10.223.57.66) VM r-4-VM found in host cache
2013-07-09 10:40:15,871 INFO [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Configure VNC port for VM r-4-VM, port: 5962,
host: 10.223.57.66
2013-07-09 10:40:15,949 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-14:null) Ping from 2
2013-07-09 10:40:16,452 WARN [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) StartCommand failed due to Exception:
java.lang.RuntimeException
Message: Invalid configuration for device '0'.
java.lang.RuntimeException: Invalid configuration for device '0'.
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:833)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2842)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:508)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-09 10:40:16,454 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-158:null) Seq 1-397543353: Cancelling because one of the answers
is false and it is stop on error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3425) Vmware - Not able to deploy VM - Router Vm fails to start.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703753#comment-13703753
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3425:
-
Patch posted for review at https://reviews.apache.org/r/12369/
Vmware - Not able to deploy VM - Router Vm fails to start.
--
Key: CLOUDSTACK-3425
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3425
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Build from 4.2
Reporter: Sangeetha Hariharan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.log
Vmware - Not able to deploy VM - Router Vm fails to start.
Steps to reproduce the problem:
Advanced zone set up with vmware 5.0 host.
Once the zone is configured and enabled , system Vms come up successfully.
Default template gets downloaded.
Try to deploy a new VM.
VM deployment fails because of the router VM not being able to start
successfully.
Router is in stopped state.
Trying to start the router manually also fails.
Following exception seen when start command is issued for Router :
2013-07-09 10:40:15,805 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-158:10.223.57.66) Network cloud.public.1371.0.1-vSwitch0 is
ready on vSwitch vSwitch0
2013-07-09 10:40:15,854 INFO [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Preparing NIC device on network
cloud.public.1371.0.1-vSwitch0
2013-07-09 10:40:15,855 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Prepare NIC at new device
{operation:ADD,device:{addressType:Manual,macAddress:02:00:0e:fc:00:04,key:-7,backing:{network:{value:network-30877,type:Network},deviceName:cloud.public.1371.0.1-vSwitch0},connectable:{startConnected:true,allowGuestControl:true,connected:true},unitNumber:4}}
2013-07-09 10:40:15,855 DEBUG [vmware.mo.HostMO]
(DirectAgent-158:10.223.57.66) find VM r-4-VM on host
2013-07-09 10:40:15,855 DEBUG [vmware.mo.HostMO]
(DirectAgent-158:10.223.57.66) VM r-4-VM found in host cache
2013-07-09 10:40:15,871 INFO [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Configure VNC port for VM r-4-VM, port: 5962,
host: 10.223.57.66
2013-07-09 10:40:15,949 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-14:null) Ping from 2
2013-07-09 10:40:16,452 WARN [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) StartCommand failed due to Exception:
java.lang.RuntimeException
Message: Invalid configuration for device '0'.
java.lang.RuntimeException: Invalid configuration for device '0'.
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:833)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2842)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:508)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-09 10:40:16,454 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-158:null) Seq 1-397543353: Cancelling because one of the answers
is false and it is stop on error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3425) Vmware - Not able to deploy VM - Router Vm fails to start.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3425:
Status: Ready To Review (was: In Progress)
Vmware - Not able to deploy VM - Router Vm fails to start.
--
Key: CLOUDSTACK-3425
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3425
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Build from 4.2
Reporter: Sangeetha Hariharan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.log
Vmware - Not able to deploy VM - Router Vm fails to start.
Steps to reproduce the problem:
Advanced zone set up with vmware 5.0 host.
Once the zone is configured and enabled , system Vms come up successfully.
Default template gets downloaded.
Try to deploy a new VM.
VM deployment fails because of the router VM not being able to start
successfully.
Router is in stopped state.
Trying to start the router manually also fails.
Following exception seen when start command is issued for Router :
2013-07-09 10:40:15,805 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-158:10.223.57.66) Network cloud.public.1371.0.1-vSwitch0 is
ready on vSwitch vSwitch0
2013-07-09 10:40:15,854 INFO [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Preparing NIC device on network
cloud.public.1371.0.1-vSwitch0
2013-07-09 10:40:15,855 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Prepare NIC at new device
{operation:ADD,device:{addressType:Manual,macAddress:02:00:0e:fc:00:04,key:-7,backing:{network:{value:network-30877,type:Network},deviceName:cloud.public.1371.0.1-vSwitch0},connectable:{startConnected:true,allowGuestControl:true,connected:true},unitNumber:4}}
2013-07-09 10:40:15,855 DEBUG [vmware.mo.HostMO]
(DirectAgent-158:10.223.57.66) find VM r-4-VM on host
2013-07-09 10:40:15,855 DEBUG [vmware.mo.HostMO]
(DirectAgent-158:10.223.57.66) VM r-4-VM found in host cache
2013-07-09 10:40:15,871 INFO [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) Configure VNC port for VM r-4-VM, port: 5962,
host: 10.223.57.66
2013-07-09 10:40:15,949 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-14:null) Ping from 2
2013-07-09 10:40:16,452 WARN [vmware.resource.VmwareResource]
(DirectAgent-158:10.223.57.66) StartCommand failed due to Exception:
java.lang.RuntimeException
Message: Invalid configuration for device '0'.
java.lang.RuntimeException: Invalid configuration for device '0'.
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:833)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2842)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:508)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-09 10:40:16,454 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-158:null) Seq 1-397543353: Cancelling because one of the answers
is false and it is stop on error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3301) [ZWPS] Unable to deploy vm(user,systemvm using ZWPS in kvm/vmware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703841#comment-13703841 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3301: - Can someone push this fix into master for Rajesh? This fix is needed for the fix for CLOUDSTACK-3264 to work. [ZWPS] Unable to deploy vm(user,systemvm using ZWPS in kvm/vmware - Key: CLOUDSTACK-3301 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3301 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Storage Controller Affects Versions: 4.2.0 Reporter: Rajesh Battala Assignee: Rajesh Battala Priority: Blocker Fix For: 4.2.0 while creation VM on KVM with ZWPS deploy VM is failing with the below NPE exception log. reason: == from the code pool capacity iops is getting set only for solidfire storage type not for nfs. Need to handle the case for it. 2013-07-01 15:45:42,224 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-7:job-19) VM state transitted from :Stopped to Error with event: OperationFailedToErrorvm's original host id: null new host id: null host id before state transition: null 2013-07-01 15:45:42,232 WARN [apache.cloudstack.alerts] (Job-Executor-7:job-19) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 10, on Host with Id: null 2013-07-01 15:45:42,276 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-7:job-19) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd java.lang.NullPointerException at com.cloud.storage.StorageManagerImpl.storagePoolHasEnoughIops(StorageManagerImpl.java:1518) at org.apache.cloudstack.storage.allocator.ZoneWideStoragePoolAllocator.filter(ZoneWideStoragePoolAllocator.java:53) at org.apache.cloudstack.storage.allocator.ZoneWideStoragePoolAllocator.select(ZoneWideStoragePoolAllocator.java:96) at org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.allocateToPool(AbstractStoragePoolAllocator.java:109) at com.cloud.deploy.DeploymentPlanningManagerImpl.findSuitablePoolsForVolumes(DeploymentPlanningManagerImpl.java:1123) at com.cloud.deploy.DeploymentPlanningManagerImpl.checkClustersforDestination(DeploymentPlanningManagerImpl.java:847) at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:404) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3307) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2868) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2854) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3264) [ZWPS]NPE while finding storage pools for migration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703904#comment-13703904 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3264: - Patch for master branch posted as diff version 2 on https://reviews.apache.org/r/12348/ [ZWPS]NPE while finding storage pools for migration --- Key: CLOUDSTACK-3264 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3264 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployment , esxi 5.1 Reporter: Srikanteswararao Talluri Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Steps to reproduce: = Issue findStoragePoolsForMigration API for a volume ===START=== 10.252.192.7 -- GET command=findStoragePoolsForMigrationid=02e0e77b-59dd-4bc4-a3b8-ba3914212883response=jsonsessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D_=1372404084373 2013-06-28 18:16:45,204 ERROR [cloud.api.ApiServer] (catalina-exec-16:null) unhandled exception executing api command: findStoragePoolsForMigration java.lang.NullPointerException at com.cloud.server.ManagementServerImpl.listStoragePoolsForMigrationOfVolume(ManagementServerImpl.java:1336) at org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-06-28 18:16:45,207 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) ===END=== 10.252.192.7 -- GET command=findStoragePoolsForMigrationid=02e0e77b-59dd-4bc4-a3b8-ba3914212883response=jsonsessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D_=1372404084373 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3264) [ZWPS]NPE while finding storage pools for migration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-3264: --- Assignee: Venkata Siva Vijayendra Bhamidipati (was: Sateesh Chodapuneedi) [ZWPS]NPE while finding storage pools for migration --- Key: CLOUDSTACK-3264 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3264 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: vmware deployment , esxi 5.1 Reporter: Srikanteswararao Talluri Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.2.0 Steps to reproduce: = Issue findStoragePoolsForMigration API for a volume ===START=== 10.252.192.7 -- GET command=findStoragePoolsForMigrationid=02e0e77b-59dd-4bc4-a3b8-ba3914212883response=jsonsessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D_=1372404084373 2013-06-28 18:16:45,204 ERROR [cloud.api.ApiServer] (catalina-exec-16:null) unhandled exception executing api command: findStoragePoolsForMigration java.lang.NullPointerException at com.cloud.server.ManagementServerImpl.listStoragePoolsForMigrationOfVolume(ManagementServerImpl.java:1336) at org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-06-28 18:16:45,207 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) ===END=== 10.252.192.7 -- GET command=findStoragePoolsForMigrationid=02e0e77b-59dd-4bc4-a3b8-ba3914212883response=jsonsessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D_=1372404084373 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
