from:"Ram Ganesh \(JIRA\)"

[jira] [Updated] (CLOUDSTACK-5482) Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind snaphots in CreatedOnPri

2014-11-15 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5482:
---
Assignee: edison su  (was: Sateesh Chodapuneedi)

 Vmware - When nfs was down for about 1 hour , when snapshots were in progress 
 , snapshot job failed when nfs was brought up leaving behind  snaphots in 
 CreatedOnPrimary state.
 -

 Key: CLOUDSTACK-5482
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5482
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Build from 4.3
Reporter: Sangeetha Hariharan
Assignee: edison su
 Fix For: 4.4.0, 4.5.0

 Attachments: nfs12down.rar, vmware.rar, vmware.rar


 Set up :
 Advanced Zone with 2 5.1 ESXI hosts.
 Steps to reproduce the problem:
 1. Deploy 5 Vms in each of the hosts , so we start with 11 Vms.
 2. Start concurrent snapshots for ROOT volumes of all the Vms.
 3. Shutdown the Secondary storage server when the snapshots are in the 
 progress.
 4. Bring the Secondary storage server up after 1 hour.
 When the secondary storage was down , 2 of the  snapshots were already 
 completed. 5 of them were in progress and the other 4 had not started yet.
 Once the secondary store was brought up , I see the snapshots that were in 
 progress actually continue to download to secondary and succeed. But the 
 other 4 snapshots error out. 
 mysql select volume_id,status,created from snapshots;
 +---+--+-+
 | volume_id | status   | created |
 +---+--+-+
 |22 | BackedUp | 2013-12-12 23:24:13 |
 |21 | Destroyed| 2013-12-12 23:24:13 |
 |20 | BackedUp | 2013-12-12 23:24:14 |
 |19 | Destroyed| 2013-12-12 23:24:14 |
 |18 | BackedUp | 2013-12-12 23:24:14 |
 |17 | BackedUp | 2013-12-12 23:24:14 |
 |16 | BackedUp | 2013-12-12 23:24:14 |
 |14 | BackedUp | 2013-12-12 23:24:15 |
 |25 | BackedUp | 2013-12-12 23:24:15 |
 |24 | BackedUp | 2013-12-12 23:24:15 |
 |23 | BackedUp | 2013-12-12 23:24:15 |
 |22 | CreatedOnPrimary | 2013-12-12 23:53:38 |
 |21 | BackedUp | 2013-12-12 23:53:38 |
 |20 | BackedUp | 2013-12-12 23:53:38 |
 |19 | BackedUp | 2013-12-12 23:53:39 |
 |18 | CreatedOnPrimary | 2013-12-12 23:53:39 |
 |17 | CreatedOnPrimary | 2013-12-12 23:53:40 |
 |16 | CreatedOnPrimary | 2013-12-12 23:53:40 |
 |14 | BackedUp | 2013-12-12 23:53:40 |
 |25 | BackedUp | 2013-12-12 23:53:41 |
 |24 | BackedUp | 2013-12-12 23:53:41 |
 |23 | BackedUp | 2013-12-12 23:53:42 |
 |21 | BackedUp | 2013-12-13 00:53:37 |
 |19 | BackedUp | 2013-12-13 00:53:38 |
 +---+--+-+
 24 rows in set (0.00 sec)
 This leaves behind incomplete snapshots. The directory does not have a ovf 
 file and has incomplete vmdk file.
 [root@Rack3Host8 18]# ls -ltR
 .:
 total 12
 drwxr-xr-x. 2 root root 4096 Dec 12 22:56 36d7964c-e545-41d7-b303-96359a88dcef
 drwxr-xr-x. 2 root root 4096 Dec 12 22:30 68802f5f-84b1-42ad-8dca-4de7e83324e2
 ./36d7964c-e545-41d7-b303-96359a88dcef:
 total 403256
 -rw-r--r--. 1 root root 412524288 Dec 13 00:20 
 36d7964c-e545-41d7-b303-96359a88dcef-disk0.vmdk
 ./68802f5f-84b1-42ad-8dca-4de7e83324e2:
 total 448860
 -rw-r--r--. 1 root root 459168256 Dec 12 22:30 
 68802f5f-84b1-42ad-8dca-4de7e83324e2-disk0.vmdk
 -rw-r--r--. 1 root root  6454 Dec 12 22:30 
 68802f5f-84b1-42ad-8dca-4de7e83324e2.ovf
 [root@Rack3Host8 18]#
 Following exception seen in the management server logs:
 2013-12-12 20:23:13,021 DEBUG [c.c.a.t.Request] (AgentManager-Handler-2:null) 
 Seq 5-813367309: Processing:  { Ans: , MgmtId: 95307354844397, via: 5, Ver: 
 v1, Flags: 10, 
 [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:backup
  snapshot exception: Exception: java.lang.Exception\nMessage: Unable to 
 finish the whole process to package as a OVA file\n,wait:0}}] }
 2013-12-12 20:23:13,022 DEBUG [c.c.a.t.Request] (Job-Executor-1:ctx-83fb69a5 
 ctx-51e56052) Seq 5-813367309: Received:  { Ans: , MgmtId: 95307354844397, 
 via: 5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
 2013-12-12 20:23:13,041 DEBUG [c.c.s.s.SnapshotManagerImpl] 
 (Job-Executor-1:ctx-83fb69a5 ctx-51e56052) Failed to

[jira] [Updated] (CLOUDSTACK-245) VPC ACLs are not stored and programmed consistently

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-245:
--
Assignee: Kishan Kavala

 VPC ACLs are not stored and programmed consistently
 ---

 Key: CLOUDSTACK-245
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-245
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: pre-4.0.0
Reporter: David Noland
Assignee: Kishan Kavala
Priority: Minor
 Fix For: 4.4.0, 4.5.0


 If user specifies 1.2.3.4/24 as the CIDR for an ACL the firewall rule is 
 being programmed as 1.2.3.0/24. Both CIDRs are correct, but it's inconsistent 
 to store one thing in the database and program the firewall using another 
 rule. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-3607) guest_os_hypervisor table has values that are not registered in guest_os table

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-3607:
---
Assignee: Chandan Purushothama

 guest_os_hypervisor table has values that are not registered in guest_os 
 table
 --

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


 mysql select * from guest_os_hypervisor where guest_os_id not in (select id 
 from guest_os);
 +-+-++-+
 | id  | hypervisor_type | guest_os_name  | guest_os_id |
 +-+-++-+
 | 128 | VmWare  | Red Hat Enterprise Linux 6(32-bit) | 204 |
 | 129 | VmWare  | Red Hat Enterprise Linux 6(64-bit) | 205 |
 +-+-++-+
 2 rows in set (0.07 sec)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-315) Infrastructure view does not show capacity values

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-315:
--
Fix Version/s: 4.5.0

 Infrastructure view does not show capacity values
 -

 Key: CLOUDSTACK-315
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-315
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.1.0, 4.2.0
 Environment: master branch
Reporter: Rohit Yadav
Assignee: Min Chen
Priority: Minor
 Fix For: 4.4.0, 4.5.0


 Goto Infrastructure, it won't post a GET request to get list of capacities, 
 no. of hosts, zones, routers etc.; and fails to show any capacity values.
 This was observed on master branch, 
 head=16fa74b7293039db75fdc6851c35e194b33f2135.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 - 4.3.0 OVS provider should be inserted to the physical network

2014-11-05 Thread Ram Ganesh (JIRA)

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

Ram Ganesh updated CLOUDSTACK-6320:
---
Assignee: Kishan Kavala

Upgrade 4.1.1 - 4.3.0 OVS provider should be inserted to the physical network
--

Key: CLOUDSTACK-6320
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.3.0
Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver
6.1.0
Advanced zone with GRE isolation is configured before upgrade.
Reporter: Florin Dumitrascu
Assignee: Kishan Kavala
Fix For: 4.4.0, 4.5.0

When you create an Advanced zone in 4.3 code, server-side will
automatically add OVS provider to its physical network.
However, since your zone was created in 4.1 code and upgraded to 4.3,
server-side won't automatically add OVS provider to its physical network.
Full message thread:
-Original Message-
From: Alena Prokharchyk
Sent: Friday, March 21, 2014 4:18 PM
To: Jessica Wang; Florin Dumitrascu; Murali Reddy
Cc: Nguyen Anh Tu (t...@apache.org); d...@cloudstack.apache.org
Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is your
zone an Advanced zone or Basic zone? (2)
Then its a DB upgrade bug. If the GRE isolation is supported on the network
in 4.1.1, DB upgrade should have inserted the provider to physical network.
On 3/21/14, 3:51 PM, Jessica Wang jessica.w...@citrix.com wrote:
[Alena] Not exactly like that.
[Alena] None of the providers are added to the physical network by
default if execute createPhysicalNetwork call via API.
[Alena] Our CS UI does this job - adding the providers to the network
- for you by calling addNetworkServiceProvider call.

Actually, OVS provider is an exception.
UI doesn't do the job because server-side already does the job.
When you create an Advanced zone in 4.3 code, server-side will
automatically add OVS provider to its physical network.
However, since your zone was created in 4.1 code and upgraded to 4.3,
server-side won't automatically add OVS provider to its physical network.

Murali, please confirm.

-Original Message-
From: Alena Prokharchyk
Sent: Friday, March 21, 2014 2:44 PM
To: Florin Dumitrascu; Jessica Wang; Murali Reddy; Florin Dumitrascu
Cc: Nguyen Anh Tu (t...@apache.org); d...@cloudstack.apache.org
Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) -
Is your zone an Advanced zone or Basic zone? (2)

On 3/21/14, 2:34 PM, Florin Dumitrascu
florin.dumitra...@intunenetworks.com wrote:

Hi,

Alena, my assumption is that the Ovs provider is created when you
create the physical network with GRE isolation (if someone can confirm ...).
When I configured CS RC8 from scratch, I could see the provider and
enable it in the GUI.

Not exactly like that. None of the providers are added to the physical
network by default if execute createPhysicalNetwork call via API. Our
CS UI does this job - adding the providers to the network - for you by
calling addNetworkServiceProvider call.

But when I have upgraded from CS 4.1.1 to 4.3.0 RC9, I have preserved
the existing configuration with the existing physical network.
So my assumption is that the physical network was not updated with the
OVS provider (such a provider was not needed in CS 4.1.1).

So while you were on 4.1.1, GRE isolation was disabled? Did you enable
it on 4.3? If there is a way to enable new isolation on the physical
network, on my opinion - the UI should perform the background call and
add all the providers associated with this option, to the physical
network. So it would be a UI issue.

Or the case was the following - the GRE isolation was enabled on your
network while on 4.1.1, but new provider - OVS - was added in 4.3. And
this provider wasn't added to existing physical networks during the
upgrade. Then its a database upgrade bug.

Please confirm which one from the above is correct.

Jessica, I am building CentOS RPM packages from the RC source, using
package.sh script in the source packaging folder. Not aware about
the difference between oss and noredist.
Also, my setup is for an advanced zone.

Kind Regards,
Florin

-Original Message-
From: Jessica Wang [mailto:jessica.w...@citrix.com]
Sent: Friday, March 21, 2014 8:28 PM
To: Florin Dumitrascu; Murali Reddy
Cc: Nguyen Anh Tu (t...@apache.org); d...@cloudstack.apache.org; Alena
Prokharchyk
Subject: RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) -
Is your zone an Advanced zone or Basic zone?

[jira] [Updated] (CLOUDSTACK-3607) guest_os_hypervisor table has values that are not registered in guest_os table

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-3607:
---
Fix Version/s: 4.5.0

 guest_os_hypervisor table has values that are not registered in guest_os 
 table
 --

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


 mysql select * from guest_os_hypervisor where guest_os_id not in (select id 
 from guest_os);
 +-+-++-+
 | id  | hypervisor_type | guest_os_name  | guest_os_id |
 +-+-++-+
 | 128 | VmWare  | Red Hat Enterprise Linux 6(32-bit) | 204 |
 | 129 | VmWare  | Red Hat Enterprise Linux 6(64-bit) | 205 |
 +-+-++-+
 2 rows in set (0.07 sec)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 - 4.3.0 OVS provider should be inserted to the physical network

2014-11-05 Thread Ram Ganesh (JIRA)

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

Ram Ganesh updated CLOUDSTACK-6320:
---
Fix Version/s: 4.5.0

Upgrade 4.1.1 - 4.3.0 OVS provider should be inserted to the physical network
--

Murali, please confirm.

On 3/21/14, 2:34 PM, Florin Dumitrascu
florin.dumitra...@intunenetworks.com wrote:

Hi,

Please confirm which one from the above is correct.

Kind Regards,
Florin

[jira] [Updated] (CLOUDSTACK-5836) When tried to reverting back to (disk attached)quiesced vm snapshot, got error at logs

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5836:
---
Fix Version/s: 4.5.0

 When tried to reverting back to (disk attached)quiesced vm snapshot, got 
 error at logs
 --

 Key: CLOUDSTACK-5836
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5836
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Snapshot
Affects Versions: 4.3.0
 Environment: cloudstack 4.3,vm snapshot
Reporter: rashid
Assignee: edison su
 Fix For: 4.4.0, 4.5.0


 Environment: There is a vm with attached disk. When tried to revert back to 
 older vm snapshot then I saw the below error message in log 
 • VM did not stop
 • At notification it says “successfull”  No GUI error message
 Manually powered off and powered on the vm and verified that Vm has been 
 successfully reverted.
 But , why vm did not get powered off by itself?
 PLease check the below logs 
 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-41:ctx-5711a5dd) Add job-93 
 into job monitoring INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-42:ctx-b7e47685) Add job-94 into job monitoring INFO  
 [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-43:ctx-7c2d7cd2) Add job-93 into 
 job monitoring INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-42:ctx-b7e47685) Remove job-94 from job monitoring WARN  
 [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-43:ctx-7c2d7cd2) job-93 is 
 scheduled for wakeup run, but there is no joining info anymore ERROR 
 [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-43:ctx-7c2d7cd2) Unable to 
 find a wakeup dispatcher from the joined job: AsyncJobVO {id:93, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd, 
 cmdInfo: 
 {response:json,sessionkey:LAwQEgGPTl8PlWexb67vz8P8SoU\u003d,cmdEventType:VMSNAPSHOT.REVERTTO,ctxUserId:2,httpmethod:GET,vmsnapshotid:4b1ea7b0-7274-4d35-bfd8-d1f151eabe3e,_:1389095290252,ctxAccountId:2,ctxStartEventId:119},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 345052565034, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Tue Jan 07 06:48:10 EST 2014} INFO  
 [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-43:ctx-7c2d7cd2) Remove job-93 
 from job monitoring INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-41:ctx-5711a5dd) Remove job-93 from job monitoring INFO  
 [c.c.h.HighAvailabilityManagerImpl] (HA-2:ctx-943a466a) checking health of 
 usage server



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-5800) While creating a VM from template (which is created based on existing newly created vm) getting error as Unable to deploy vm base on template due to of insufficient

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5800:
---
Assignee: edison su

 While creating a VM from template (which is created based on existing newly 
 created  vm) getting error as Unable to deploy vm base on template due to of 
 insufficient server capicity
 -

 Key: CLOUDSTACK-5800
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5800
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Template, XenServer
Affects Versions: 4.3.0
 Environment: CENTOS 6.4,WIN2012,ACS 4.3.0,
Reporter: rashid
Assignee: edison su
 Fix For: 4.4.0, 4.5.0


 While creating a vm from template 
 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-5:ctx-c259052d) Add job-46 
 into job monitoring
 INFO  [o.a.c.s.v.VolumeServiceImpl] (Job-Executor-5:ctx-c259052d 
 ctx-506ea49e) lock is acquired for VMTemplateStoragePool 7
 WARN  [o.a.c.alerts] (CapacityChecker:ctx-374c70b5)  alertType:: 24 // 
 dataCenterId:: 1 // podId:: null // clusterId:: null // message:: System 
 Alert: Number of unallocated shared network IPs is low in availability zone 
 NEWZONE
 WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-32c31ce6) Task (job-45) has 
 been pending for 104 seconds
 WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-32c31ce6) Task (job-46) has 
 been pending for 103 seconds
 WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-92c2ed53) Task (job-45) has 
 been pending for 164 seconds
 WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-92c2ed53) Task (job-46) has 
 been pending for 163 seconds
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-4:ctx-f87acd3c) 
 destoryVDIbyNameLabel failed due to there are 0 VDIs with name 
 cloud-377c12f4-a8e9-491a-8cba-34b9532455f8
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-4:ctx-f87acd3c) 
 failed to set hidden to 0  
 /var/run/sr-mount/ab820f54-badd-db21-f758-0abcb47ea4d7/b0246f72-9bda-4f29-981f-548f4b7a9f6c.vhd
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-4:ctx-f87acd3c) 
 Catch Exception com.cloud.utils.exception.CloudRuntimeException for template 
 +  due to com.cloud.utils.exception.CloudRuntimeException: failed to set 
 hidden to 0  
 /var/run/sr-mount/ab820f54-badd-db21-f758-0abcb47ea4d7/b0246f72-9bda-4f29-981f-548f4b7a9f6c.vhd
 com.cloud.utils.exception.CloudRuntimeException: failed to set hidden to 0  
 /var/run/sr-mount/ab820f54-badd-db21-f758-0abcb47ea4d7/b0246f72-9bda-4f29-981f-548f4b7a9f6c.vhd
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:858)
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:928)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:75)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:50)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:609)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:106)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)

[jira] [Updated] (CLOUDSTACK-5800) While creating a VM from template (which is created based on existing newly created vm) getting error as Unable to deploy vm base on template due to of insufficient

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5800:
---
Fix Version/s: 4.5.0

 While creating a VM from template (which is created based on existing newly 
 created  vm) getting error as Unable to deploy vm base on template due to of 
 insufficient server capicity
 -

 Key: CLOUDSTACK-5800
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5800
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Template, XenServer
Affects Versions: 4.3.0
 Environment: CENTOS 6.4,WIN2012,ACS 4.3.0,
Reporter: rashid
Assignee: edison su
 Fix For: 4.4.0, 4.5.0


 While creating a vm from template 
 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-5:ctx-c259052d) Add job-46 
 into job monitoring
 INFO  [o.a.c.s.v.VolumeServiceImpl] (Job-Executor-5:ctx-c259052d 
 ctx-506ea49e) lock is acquired for VMTemplateStoragePool 7
 WARN  [o.a.c.alerts] (CapacityChecker:ctx-374c70b5)  alertType:: 24 // 
 dataCenterId:: 1 // podId:: null // clusterId:: null // message:: System 
 Alert: Number of unallocated shared network IPs is low in availability zone 
 NEWZONE
 WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-32c31ce6) Task (job-45) has 
 been pending for 104 seconds
 WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-32c31ce6) Task (job-46) has 
 been pending for 103 seconds
 WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-92c2ed53) Task (job-45) has 
 been pending for 164 seconds
 WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-2:ctx-92c2ed53) Task (job-46) has 
 been pending for 163 seconds
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-4:ctx-f87acd3c) 
 destoryVDIbyNameLabel failed due to there are 0 VDIs with name 
 cloud-377c12f4-a8e9-491a-8cba-34b9532455f8
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-4:ctx-f87acd3c) 
 failed to set hidden to 0  
 /var/run/sr-mount/ab820f54-badd-db21-f758-0abcb47ea4d7/b0246f72-9bda-4f29-981f-548f4b7a9f6c.vhd
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-4:ctx-f87acd3c) 
 Catch Exception com.cloud.utils.exception.CloudRuntimeException for template 
 +  due to com.cloud.utils.exception.CloudRuntimeException: failed to set 
 hidden to 0  
 /var/run/sr-mount/ab820f54-badd-db21-f758-0abcb47ea4d7/b0246f72-9bda-4f29-981f-548f4b7a9f6c.vhd
 com.cloud.utils.exception.CloudRuntimeException: failed to set hidden to 0  
 /var/run/sr-mount/ab820f54-badd-db21-f758-0abcb47ea4d7/b0246f72-9bda-4f29-981f-548f4b7a9f6c.vhd
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:858)
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:928)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:75)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:50)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:609)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:106)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)

[jira] [Updated] (CLOUDSTACK-5836) When tried to reverting back to (disk attached)quiesced vm snapshot, got error at logs

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5836:
---
Assignee: edison su

 When tried to reverting back to (disk attached)quiesced vm snapshot, got 
 error at logs
 --

 Key: CLOUDSTACK-5836
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5836
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Snapshot
Affects Versions: 4.3.0
 Environment: cloudstack 4.3,vm snapshot
Reporter: rashid
Assignee: edison su
 Fix For: 4.4.0, 4.5.0


 Environment: There is a vm with attached disk. When tried to revert back to 
 older vm snapshot then I saw the below error message in log 
 • VM did not stop
 • At notification it says “successfull”  No GUI error message
 Manually powered off and powered on the vm and verified that Vm has been 
 successfully reverted.
 But , why vm did not get powered off by itself?
 PLease check the below logs 
 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-41:ctx-5711a5dd) Add job-93 
 into job monitoring INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-42:ctx-b7e47685) Add job-94 into job monitoring INFO  
 [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-43:ctx-7c2d7cd2) Add job-93 into 
 job monitoring INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-42:ctx-b7e47685) Remove job-94 from job monitoring WARN  
 [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-43:ctx-7c2d7cd2) job-93 is 
 scheduled for wakeup run, but there is no joining info anymore ERROR 
 [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-43:ctx-7c2d7cd2) Unable to 
 find a wakeup dispatcher from the joined job: AsyncJobVO {id:93, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd, 
 cmdInfo: 
 {response:json,sessionkey:LAwQEgGPTl8PlWexb67vz8P8SoU\u003d,cmdEventType:VMSNAPSHOT.REVERTTO,ctxUserId:2,httpmethod:GET,vmsnapshotid:4b1ea7b0-7274-4d35-bfd8-d1f151eabe3e,_:1389095290252,ctxAccountId:2,ctxStartEventId:119},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 345052565034, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Tue Jan 07 06:48:10 EST 2014} INFO  
 [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-43:ctx-7c2d7cd2) Remove job-93 
 from job monitoring INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-41:ctx-5711a5dd) Remove job-93 from job monitoring INFO  
 [c.c.h.HighAvailabilityManagerImpl] (HA-2:ctx-943a466a) checking health of 
 usage server



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-5583) vmopsSnapshot plug-in (XenServer) does not return an error when it should

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5583:
---
Fix Version/s: 4.5.0

 vmopsSnapshot plug-in (XenServer) does not return an error when it should
 -

 Key: CLOUDSTACK-5583
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5583
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Snapshot, Xen
Affects Versions: 4.3.0
 Environment: XenServer 6.1
Reporter: Mike Tutkowski
Assignee: Anthony Xu
 Fix For: 4.4.0, 4.5.0


 I tried to revert a VM snapshot and one of my storage repositories had an 
 insufficient amount of space. The plug-in did not return an error message (it 
 returned 0).
 From the XenServer vmopsSnapshot plug-in's revert_memory_snapshot method:
 [root@XenServer-6 ~]# xe snapshot-revert 
 snapshot-uuid=82e33f6d-59f3-a26d-4171-d51cd58716d8
 Error code: SR_BACKEND_FAILURE_44
 Error parameters: , There is insufficient space, 
 An error should be returned from the plug-in instead of 0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-5583) vmopsSnapshot plug-in (XenServer) does not return an error when it should

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5583:
---
Assignee: Anthony Xu

 vmopsSnapshot plug-in (XenServer) does not return an error when it should
 -

 Key: CLOUDSTACK-5583
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5583
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Snapshot, Xen
Affects Versions: 4.3.0
 Environment: XenServer 6.1
Reporter: Mike Tutkowski
Assignee: Anthony Xu
 Fix For: 4.4.0, 4.5.0


 I tried to revert a VM snapshot and one of my storage repositories had an 
 insufficient amount of space. The plug-in did not return an error message (it 
 returned 0).
 From the XenServer vmopsSnapshot plug-in's revert_memory_snapshot method:
 [root@XenServer-6 ~]# xe snapshot-revert 
 snapshot-uuid=82e33f6d-59f3-a26d-4171-d51cd58716d8
 Error code: SR_BACKEND_FAILURE_44
 Error parameters: , There is insufficient space, 
 An error should be returned from the plug-in instead of 0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-315) Infrastructure view does not show capacity values

2014-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-315:
--
Assignee: Min Chen

 Infrastructure view does not show capacity values
 -

 Key: CLOUDSTACK-315
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-315
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.1.0, 4.2.0
 Environment: master branch
Reporter: Rohit Yadav
Assignee: Min Chen
Priority: Minor
 Fix For: 4.4.0, 4.5.0


 Goto Infrastructure, it won't post a GET request to get list of capacities, 
 no. of hosts, zones, routers etc.; and fails to show any capacity values.
 This was observed on master branch, 
 head=16fa74b7293039db75fdc6851c35e194b33f2135.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-5807) Problem with shared datastore in VMware cluster with only one host

2014-11-04 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5807:
---
Assignee: Likitha Shetty

 Problem with shared datastore in VMware cluster with only one host
 --

 Key: CLOUDSTACK-5807
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5807
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.3.0
 Environment: ESX 5.1
Reporter: Mike Tutkowski
Assignee: Likitha Shetty
 Fix For: 4.4.0


 I created a volume on a SAN and connected my one and only ESX host in the 
 cluster to it via CHAP. The iSCSI target was detected and I was able to 
 create a datastore with it (manually through vSphere Client).
 The problem is that the VMware server resource detects this new datastore and 
 automatically introduces it to CloudStack as host-based primary storage.
 This is a problem because it should really be cluster-based primary storage.
 If I were to add another ESX host to this cluster, I don't think it could 
 access this primary storage as it is currently configured in CloudStack.
 The logic to detect if a datastore on an ESX host is local must be somewhat 
 flawed.
 I believe if I had two or more hosts in my cluster and performed this 
 datastore operation that it would not have detected this as host-based 
 primary storage and I would have been able to manually add the datastore to 
 CloudStack as cluster-based primary storage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-4587) VM is failing to deploy on a Legacy zone after adding zone wide primary storage and moving cluster wide primary storage to maintenance mode

2014-07-23 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-4587:
---

Assignee: Likitha Shetty

 VM is failing to deploy on a Legacy zone after adding zone wide primary 
 storage and moving cluster wide primary storage to maintenance  mode
 

 Key: CLOUDSTACK-4587
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4587
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.1
Reporter: Sailaja Mada
Assignee: Likitha Shetty
 Fix For: 4.4.0

 Attachments: failureloigs.rar, logs.rar, vmdeploylogs.rar


 Steps:
 1. Upgraded from 307 to 4.2 using VMWARE Cluster with Cluster level primary 
 storage 
 2. Add Zone wide primary storage after upgrade 
 3. Move the cluster level scope storage to Maintenance mode 
 4. Try to deploy new VM. 
 Observation:
 VM is failing to deploy on a Legacy zone after adding zone wide primary 
 storage and moving cluster wide primary storage to maintenance mode
 2013-09-01 14:21:10,323 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) Network 
 id=207 is already implemented
 2013-09-01 14:21:10,354 DEBUG [network.guru.PodBasedNetworkGuru] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) 
 Allocated a nic 
 NicProfile[119-35-4a8f547b-7bff-4b3f-ba10-b0146af4d1bb-10.102.195.111-null 
 for VM[DomainRouter|r-35-VM]
 2013-09-01 14:21:10,390 DEBUG [cloud.storage.VolumeManagerImpl] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) 
 Checking if we need to prepare 1 volumes for VM[DomainRouter|r-35-VM]
 2013-09-01 14:21:10,400 DEBUG [storage.image.TemplateDataFactoryImpl] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) 
 template 203 is already in store:2, type:Image
 2013-09-01 14:21:10,409 DEBUG [storage.image.TemplateDataFactoryImpl] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) 
 template 203 is already in store:203, type:Primary
 2013-09-01 14:21:10,410 DEBUG [storage.volume.VolumeServiceImpl] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) Found 
 template 203-2-3cfe22ca-3a33-39a0-bf5e-0dab154869fd in storage pool 203 with 
 VMTemplateStoragePool id: 11
 2013-09-01 14:21:10,421 DEBUG [storage.volume.VolumeServiceImpl] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) Acquire 
 lock on VMTemplateStoragePool 11 with timeout 3600 seconds
 2013-09-01 14:21:10,423 INFO  [storage.volume.VolumeServiceImpl] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) lock is 
 acquired for VMTemplateStoragePool 11
 2013-09-01 14:21:10,431 DEBUG [storage.motion.AncientDataMotionStrategy] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) 
 copyAsync inspecting src type TEMPLATE copyAsync inspecting dest type TEMPLATE
 2013-09-01 14:21:10,519 DEBUG [storage.motion.AncientDataMotionStrategy] 
 (Job-Executor-119:job-199 = [ 4837d9ec-d365-4653-960c-83fa1dc4fa87 ]) copy 
 object failed:
 java.lang.NullPointerException
 at 
 org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyObject(AncientDataMotionStrategy.java:210)
 at 
 org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:411)
 at 
 org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:55)
 at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:440)
 at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:569)
 at 
 com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2536)
 at 
 com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2592)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2740)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1872)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouters(VirtualNetworkApplianceManagerImpl.java:1972)
 at

[jira] [Commented] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs

2014-07-14 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-7012:


Sateesh

Should we resolve this ticket so that QA can pick this up for resolution?

 [Atomation] Vcenter Hang during 4.4 automation runs
 ---

 Key: CLOUDSTACK-7012
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.4.0
 Environment: VCenter 5.0
 Exi 5.0
Reporter: Rayees Namathponnan
Assignee: Sateesh Chodapuneedi
Priority: Critical
 Fix For: 4.4.0

 Attachments: catalina.rar


 This issue observed with 4.4 automation run with Vcenter 5.0,  during BVT run 
 VM deployment fail,  if you try to connect VCenter from console gets below 
 error 
 Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 
 10.223.52.12 failed.
 I was using same VCenter more 1.5 year, i never faced this issue earlier, 
 then i tried to run automation with 4.2 and 4.3 build last week i didnt 
 observe this issue,  i think some of the changes in CS 4.4 causing VCenter to 
 hang 
 Observed below error in MS Log
 INFO  [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New 
 VmwareContext object, current outstanding count: 451
 INFO  [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan 
 hung worker VM to recycle
 INFO  [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) 
 New VmwareContext object, current outstanding count: 452



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

[jira] [Updated] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs

2014-07-10 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-7012:
---

Assignee: Sateesh Chodapuneedi  (was: Kelven Yang)

 [Atomation] Vcenter Hang during 4.4 automation runs
 ---

 Key: CLOUDSTACK-7012
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.4.0
 Environment: VCenter 5.0
 Exi 5.0
Reporter: Rayees Namathponnan
Assignee: Sateesh Chodapuneedi
Priority: Critical
 Fix For: 4.4.0

 Attachments: catalina.rar


 This issue observed with 4.4 automation run with Vcenter 5.0,  during BVT run 
 VM deployment fail,  if you try to connect VCenter from console gets below 
 error 
 Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 
 10.223.52.12 failed.
 I was using same VCenter more 1.5 year, i never faced this issue earlier, 
 then i tried to run automation with 4.2 and 4.3 build last week i didnt 
 observe this issue,  i think some of the changes in CS 4.4 causing VCenter to 
 hang 
 Observed below error in MS Log
 INFO  [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New 
 VmwareContext object, current outstanding count: 451
 INFO  [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan 
 hung worker VM to recycle
 INFO  [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) 
 New VmwareContext object, current outstanding count: 452



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

[jira] [Updated] (CLOUDSTACK-6261) remove the forceful timeout setting when login to NetScaler

2014-06-16 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-6261:
---

Assignee: Rajesh Battala

 remove the forceful timeout setting when login to NetScaler
 ---

 Key: CLOUDSTACK-6261
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6261
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Devices
Affects Versions: 4.4.0
 Environment: NetScaler VPX/MPX 10.5+ (code does not force timeout 
 when login to SDX)
Reporter: Vijay Venkatachalam
Assignee: Rajesh Battala
Priority: Minor
  Labels: patch
 Fix For: 4.4.0

   Original Estimate: 2h
  Remaining Estimate: 2h

 Today, the NetScaler Resource forces a idle timeout of 100,000 seconds (~1 
 day and 4 hours) during login. The request is to remove forcing the timeout 
 to a specific value.
 Also, future versions of NetScaler is planning to have a cap of 1 day for 
 this setting.
 It is best to leave it to the system default which is 30 mins. This should be 
 enough, anyway there are threads for monitoring of member status, and 
 statistics collections  that keeps the session alive and it is unlikely to 
 gather idle time.
 The NetScaler resource already handles timeout expiry using retries so there 
 should not be any see side effects by leaving the idle time out to be the 
 default value 30 mins.. 



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

[jira] [Assigned] (CLOUDSTACK-6804) [Automation] Add host fails in KVM

2014-06-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh reassigned CLOUDSTACK-6804:
--

Assignee: Ram Ganesh

 [Automation] Add host fails in KVM 
 ---

 Key: CLOUDSTACK-6804
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6804
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.4.0
 Environment: RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: Ram Ganesh
Priority: Blocker
 Fix For: 4.4.0


 Add host failing in in KVM with RHEL 6.3
 2014-05-29 11:09:24,951 INFO  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Trying to add a new 
 host
 at http://10.223.250.194 in data center 1
 2014-05-29 11:09:25,211 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: 
 lsmod|grep kvm
 2014-05-29 11:09:26,454 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: 
 lsmod|grep kvm
 2014-05-29 11:09:27,512 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: 
 lsmod|grep kvm
 2014-05-29 11:09:28,568 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) It's not a KVM 
 enabled machine
 2014-05-29 11:09:28,571 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Unable to find the 
 server resources at http://10.223.250.194
 2014-05-29 11:09:28,574 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Could not find 
 exception: com.cloud.exception.DiscoveryException in error code list for 
 exceptions
 2014-05-29 11:09:28,574 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy146.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:683)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:506)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330)
 at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77)
 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)

[jira] [Updated] (CLOUDSTACK-6804) [Automation] Add host fails in KVM

2014-06-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-6804:
---

Assignee: Kishan Kavala  (was: Ram Ganesh)

 [Automation] Add host fails in KVM 
 ---

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


 Add host failing in in KVM with RHEL 6.3
 2014-05-29 11:09:24,951 INFO  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Trying to add a new 
 host
 at http://10.223.250.194 in data center 1
 2014-05-29 11:09:25,211 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: 
 lsmod|grep kvm
 2014-05-29 11:09:26,454 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: 
 lsmod|grep kvm
 2014-05-29 11:09:27,512 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: 
 lsmod|grep kvm
 2014-05-29 11:09:28,568 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) It's not a KVM 
 enabled machine
 2014-05-29 11:09:28,571 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Unable to find the 
 server resources at http://10.223.250.194
 2014-05-29 11:09:28,574 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Could not find 
 exception: com.cloud.exception.DiscoveryException in error code list for 
 exceptions
 2014-05-29 11:09:28,574 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy146.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:683)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:506)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330)
 at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77)
 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

[jira] [Commented] (CLOUDSTACK-6084) [Automation] Failed to create private gateway

2014-05-11 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-6084:


So this should be assigned to Daan then?

 [Automation] Failed to create private gateway
 -

 Key: CLOUDSTACK-6084
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6084
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
 Environment: xenserver 6.2 ,advanced zone
Reporter: Srikanteswararao Talluri
Assignee: Jayapal Reddy
Priority: Critical
 Fix For: 4.4.0


 Steps to reproduce:
 = 
# 1) Create VPC
 self.createVPC()
 # 2) Create ACl
 self.createACL()
 # 3) Create ACl Item
 self.createACLItem()
 # 4) Create network with ACL
 self.createNetwork()
 # 5) create private gw
 self.createPvtGw()
 Logs can be found here : 
 http://jenkins.buildacloud.org/view/cloudstack-qa-master/job/test-matrix-master/3/distro=centos63,hypervisor=xen,profile=xen62/artifact/3.tar.bz2
 ===START===  10.208.8.5 -- GET  
 physicalnetworkid=200vpcid=e1f5910c-1352-4274-9326-f8413f41d4bfsourcenatsupported=trueaclid=bdca388c-c6cf-4757-b72d-c07e22ff9fa5vlan=30response=jsonnetmask=255.255.255.0apiKey=ZVang0oygdXeY5o3XEz4X3i60YHJj5nVE8gN6hR_zlBWzIoxby09FIxK_a-UlWl_jzLen_4I8oXgmQLppn3ikwcommand=createPrivateGatewaysignature=2Z89SOGldeUm9Lfg10R8rcx%2FRZ0%3Dipaddress=10.147.30.200gateway=10.147.30.1
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,779 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-335:ctx-48012a52) Ping from 1(apache-81-3)
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,808 DEBUG [network.vpc.VpcManagerImpl] (catalina-exec-3:ctx-d5a8de3b 
 ctx-fa9b0854 ctx-5b785c5e) Creating Private gateway for VPC [VPC [6-new vpc]
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,808 INFO  [network.vpc.VpcManagerImpl] (catalina-exec-3:ctx-d5a8de3b 
 ctx-fa9b0854 ctx-5b785c5e) creating new network for vpc [VPC [6-new vpc] 
 using broadcast uri: 30
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,834 DEBUG [contrail.management.ContrailGuru] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design 
 this network
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,834 DEBUG [network.guru.MidoNetGuestNetworkGuru] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) design called
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,835 DEBUG [network.guru.MidoNetGuestNetworkGuru] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design 
 this network, the physical isolation type is not MIDO
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,835 DEBUG [network.guru.NiciraNvpGuestNetworkGuru] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design 
 this network
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,840 DEBUG [network.opendaylight.OpendaylightGuestNetworkGuru] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design 
 this network
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,841 DEBUG [network.guru.OvsGuestNetworkGuru] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Refusing to design 
 this network
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,857 DEBUG [network.guru.SspGuestNetworkGuru] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) SSP not configured 
 to be active
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,858 DEBUG [engine.orchestration.NetworkOrchestrator] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Releasing lock for 
 Acct[bcbb718a-93c7-11e3-af4f-b6c8db337241-system]
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,858 DEBUG [cloud.network.NetworkServiceImpl] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Created private 
 network Ntwk[230|Guest|5]
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,864 DEBUG [cloud.network.NetworkServiceImpl] 
 (catalina-exec-3:ctx-d5a8de3b ctx-fa9b0854 ctx-5b785c5e) Private network 
 Ntwk[230|Guest|5] is created
 Feb 12 02:23:49 cloudstack-centos63.fmt.vmops.com local0: 2014-02-12 
 10:23:49,891 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-310:ctx-dca6e64d) Ping from 2(apache-81-2)
 Feb 12

[jira] [Commented] (CLOUDSTACK-6570) API breakage of the UpdateUser API call

2014-05-07 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-6570:


Can this bug's status be moved to resolved since I see commits ?

 API breakage of the UpdateUser API call
 ---

 Key: CLOUDSTACK-6570
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6570
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: Any, the UpdateUser API call is environment independent
Reporter: Ove Ewerlid
Priority: Blocker
  Labels: easyfix
 Fix For: 4.4.0, 4.5.0


 44 adds USER_API_KEY in ./api/src/org/apache/cloudstack/api/ApiConstants.java 
 and changes the value of API_KEY. Since API_KEY value is exposed in the 
 UpdateUser API, the API breaks.  Up until 4.3, KEYs to UpdateUser were passed 
 via parameters;
   * userapikey
   * usersecretkey
 with 44 this changes to;
   * apikey
   * usersecretkey
   



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

[jira] [Updated] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers

2014-05-07 Thread Ram Ganesh (JIRA)

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

Ram Ganesh updated CLOUDSTACK-6453:
---

Priority: Critical (was: Blocker)

[GPU] Windows 2012 Server instance created with vGPU offering is not coming
up after installing PV drivers
--

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

Attachments: SMlog, gpulogs.zip

Steps:
1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2
2. Create Service Offering using K2 - K200 profile of vGPU
3. Deploy windows 2012 instance with ISO using K200 vGPU profile offering
4. Install Windows 2012 instance and install PV drivers
5. During PV driver installation Windows 2012 server went for reboot.
Observation:
1. After reboot, Windows 2012 Server instance created with vGPU offering is
not coming up after installing PV drivers
2. It remained in stopped state.
3. Tried to start instance manually , Cloudstack says Instance started and
instance moved to running state. But XenServer failed to start the instance.
4. Later Cloudstack also marked the instance in stopped state.
Attached detailed logs

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

[jira] [Commented] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers

2014-05-07 Thread Ram Ganesh (JIRA)

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

Ram Ganesh commented on CLOUDSTACK-6453:

reducing the severity of the bug to critical since this bug does not block
majority of the GPU uses cases.

[GPU] Windows 2012 Server instance created with vGPU offering is not coming
up after installing PV drivers
--

Attachments: SMlog, gpulogs.zip

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

[jira] [Updated] (CLOUDSTACK-6333) [Automation] NPE observed while deleting account

2014-05-04 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-6333:
---

Assignee: Sanjay Tripathi

 [Automation] NPE observed while deleting account
 

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

 Attachments: management-server.rar


 This issue observed in automation run, there are many account clean up 
 failures with NPE
 Also In Log observed VM state transitted from :Expunging to Expunging, why 
 we are changing state Expunging to Expunging
 2014-04-02 17:19:45,664 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (AccountChecker-1:ctx-633521d3) Cleaning up NICS
 2014-04-02 17:19:45,664 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-633521d3) Cleaning network for vm: 455
 2014-04-02 17:19:45,665 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (AccountChecker-1:ctx-633521d3) Cleaning up hypervisor data s
 tructures (ex. SRs in XenServer) for managed storage
 2014-04-02 17:19:45,669 WARN  [c.c.u.AccountManagerImpl] 
 (AccountChecker-1:ctx-633521d3) Failed to cleanup account Acct[10b43
 b95-f6e0-445f-acff-9c5cc450f59b-test-TestBaseImageUpdate-6JJ7ST] due to
 java.lang.NullPointerException
 at 
 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.disconnectVolumesFromHost(VolumeOrchestrator.java:867)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:527)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:463)
 at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1654)
 at sun.reflect.GeneratedMethodAccessor555.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy205.expunge(Unknown Source)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:651)
 at 
 com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1575)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)



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

[jira] [Updated] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN

2014-04-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-6444:
---

Assignee: Anthony Xu

 [Automation] test_01_primary_storage_iscsi  failed on 
 test_primary_storage.py - Wrong iscsi path format - it should be 
 /targetIQN/LUN 
 

 Key: CLOUDSTACK-6444
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 Error Message:
 Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
   begin captured logging  
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 STARTED : TC: test_01_primary_storage_iscsi :::
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listZones {}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
  HTTP/1.1 200 735
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
  Response: { listzonesresponse : { count:2 ,zone : [  
 {id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
  
 {id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
  ] } }
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listPods {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  HTTP/1.1 200 314
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  Response: { listpodsresponse : { count:1 ,pod : [  
 {id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
  ] } }
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listClusters {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET

[jira] [Updated] (CLOUDSTACK-5342) [Automation] Add NIC to virtual machine fails in KVM

2014-04-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5342:
---

Assignee: Saksham Srivastava

 [Automation] Add NIC to virtual machine fails in KVM
 

 Key: CLOUDSTACK-5342
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.3.0
 Environment: KVM advanced
Reporter: Gaurav Aradhye
Assignee: Saksham Srivastava
 Fix For: 4.4.0


 Add network to VM test cases fail in KVM with following error.
 Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : 
 u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
 The same test cases execute successfully on XenServer. As per the feature 
 specification (see 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
  Add network to VM feature should be supported on KVM too.



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

[jira] [Commented] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers

2014-04-28 Thread Ram Ganesh (JIRA)

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

Ram Ganesh commented on CLOUDSTACK-6453:

a specific scenario is not working so not sure if we should still flag it as
blocker.

Sailaja : Can you confirm?

[GPU] Windows 2012 Server instance created with vGPU offering is not coming
up after installing PV drivers
--

Attachments: SMlog, gpulogs.zip

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

[jira] [Commented] (CLOUDSTACK-6295) Management server cannot start because Java 7 missing

2014-04-28 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-6295:


Paul

is your observation same as CLOUDSTACK-6351?

 Management server cannot start because Java 7 missing
 -

 Key: CLOUDSTACK-6295
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6295
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.4.0
 Environment: centos 6.5
Reporter: Paul Angus
Priority: Blocker

 Management server cannot start because java 7 is not installed. Java 7 
 package dependency needs to be added into installation.



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

[jira] [Updated] (CLOUDSTACK-6338) [Automation] Failed to NetScaler Device with error un.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertathB

2014-04-23 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-6338:
---

Assignee: Rajesh Battala

 [Automation]  Failed to NetScaler Device with error 
 un.security.validator.ValidatorException: PKIX path building failed: 
 sun.security.provider.certpath.SunCertathBuilderException: unable to find 
 valid certification path to requested target} 
 

 Key: CLOUDSTACK-6338
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6338
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
 Environment: KVM EIP/ELB (RHEL 6.3)
Reporter: Rayees Namathponnan
Assignee: Rajesh Battala
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management.rar


 Failed to add Netscaler during EIP/ELB configuration 
 2014-04-03 21:29:46,460 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-18:ctx-72880204 ctx-2d222b87 ctx-c9a147a3) ===END===  
 10.223.240
 .193 -- GET  
 username=nsrootphysicalnetworkid=94c18f72-8a9c-4d0a-ba43-9a24606f3391url=http%3A%2F%2F10.223.240.177%3Fusername%3
 Dnsroot%26publicinterface%3D1%2F1%26hostname%3D10.223.240.177%26privateinterface%3D1%2F1%26lbdevicecapacity%3D50%26networkdevice
 type%3DNetscalerVPXLoadBalancer%26lbdevicededicated%3Dfalse%26numretries%3D2networkdevicetype=NetscalerVPXLoadBalancerapiKey=K
 BeoHDz29tjADzbpQ5OEQNgVZ6xYCRE1XDzb4UmfdG_K86pHhU2AYqFZzF8ii8RFKCbu6Yik21VURn8uYrgScgcommand=addNetscalerLoadBalancersignature
 =PeFY913bQNNkKk5NjxxXzL%2BAEHQ%3Dresponse=json
 2014-04-03 21:29:46,462 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-9:job-13) Add job-13 into job monitoring
 2014-04-03 21:29:46,463 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-9:job-13) Executing AsyncJobVO {id:13, userId:
  2, accountId: 2, instanceType: None, instanceId: null, cmd: 
 com.cloud.api.commands.AddNetscalerLoadBalancerCmd, cmdInfo: {phys
 icalnetworkid:94c18f72-8a9c-4d0a-ba43-9a24606f3391,response:json,username:nsroot,cmdEventType:PHYSICAL.LOADBALANCE
 R.ADD,ctxUserId:2,networkdevicetype:NetscalerVPXLoadBalancer,httpmethod:GET,ctxAccountId:2,ctxStartEventId:5
 2,password:nsroot,apiKey:KBeoHDz29tjADzbpQ5OEQNgVZ6xYCRE1XDzb4UmfdG_K86pHhU2AYqFZzF8ii8RFKCbu6Yik21VURn8uYrgScg,signat
 ure:PeFY913bQNNkKk5NjxxXzL+AEHQ\u003d,url:http://10.223.240.177?username\u003dnsroot\u0026publicinterface\u003d1/1\u0026ho
 stname\u003d10.223.240.177\u0026privateinterface\u003d1/1\u0026lbdevicecapacity\u003d50\u0026networkdevicetype\u003dNetscalerVPX
 LoadBalancer\u0026lbdevicededicated\u003dfalse\u0026password\u003dnsroot\u0026numretries\u003d2},
  cmdVersion: 0, status: IN_PRO
 GRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 
 73187150500751, completeMsid: null, lastUpdated: null, lastPolle
 d: null, created: null}
 2014-04-03 21:29:46,464 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-e2bcddac) ===START===  10.223.240.193 -- GET  
 signature=%
 2FNYT%2FQGLpRKIHiBiILgVLOgSoFU%3DapiKey=KBeoHDz29tjADzbpQ5OEQNgVZ6xYCRE1XDzb4UmfdG_K86pHhU2AYqFZzF8ii8RFKCbu6Yik21VURn8uYrgScg
 command=queryAsyncJobResultresponse=jsonjobid=6f3a6915-6ed5-4b52-b467-7e0cfa30e2cf
 2014-04-03 21:29:46,483 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-9:job-13 ctx-39a38b39) Received unknown p
 arameters for command addNetscalerLoadBalancer. Unknown parameters : 
 ctxstarteventid
 2014-04-03 21:29:46,552 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-e2bcddac ctx-96d05190 ctx-6ab9c015) ===END===  
 10.223.240
 .193 -- GET  
 signature=%2FNYT%2FQGLpRKIHiBiILgVLOgSoFU%3DapiKey=KBeoHDz29tjADzbpQ5OEQNgVZ6xYCRE1XDzb4UmfdG_K86pHhU2AYqFZzF8ii8R
 FKCbu6Yik21VURn8uYrgScgcommand=queryAsyncJobResultresponse=jsonjobid=6f3a6915-6ed5-4b52-b467-7e0cfa30e2cf
 2014-04-03 21:29:47,589 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-9:job-13) Complete async job-13, jobStatus: FAILED, 
 resultCode: 530, result: 
 org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
  to log in to Netscaler device at 10.223.240.177 due to 
 sun.security.validator.ValidatorException: PKIX path building failed: 
 sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
 valid certification path to requested target}



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

[jira] [Updated] (CLOUDSTACK-6475) [Automation] communication between cloudstack agent and MS disconnecting continuously

2014-04-23 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-6475:
---

Assignee: Kishan Kavala

 [Automation] communication between cloudstack agent and MS disconnecting 
 continuously  
 ---

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

 Attachments: Agent_log.rar, management-server.rar


 This issue is observed during automation, run.
 communication between cloudstack agent and ms getting disconnected 
 continuously;  observed below error in agent log
  2014-04-22 04:08:47,867 INFO  [cloud.agent.Agent] (AgentShutdownThread:null) 
 Stopping the agent: Reason = sig.kill
 2014-04-22 04:10:41,456 INFO  [cloud.agent.AgentShell] (main:null) Agent 
 started
 2014-04-22 04:10:41,500 INFO  [cloud.agent.AgentShell] (main:null) 
 Implementation Version is 4.4.0-SNAPSHOT
 2014-04-22 04:10:41,502 INFO  [cloud.agent.AgentShell] (main:null) 
 agent.properties found at /etc/cloudstack/agent/agent.properties
 2014-04-22 04:10:41,551 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
 to using properties file for storage
 2014-04-22 04:10:41,552 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
 to the constant time backoff algorithm
 2014-04-22 04:10:41,572 INFO  [cloud.utils.LogUtils] (main:null) log4j 
 configuration found at /etc/cloudstack/agent/log4j-cloud.xml
 2014-04-22 04:10:41,722 INFO  [cloud.agent.Agent] (main:null) id is 0
 2014-04-22 04:10:42,501 INFO  [kvm.resource.LibvirtComputingResource] 
 (main:null) No libvirt.vif.driver specified. Defaults to BridgeVifDriver.
 2014-04-22 04:10:42,590 INFO  [cloud.agent.Agent] (main:null) Agent [id = 0 : 
 type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : host = 
 10.223.49.195 : port = 8250
 2014-04-22 04:10:42,664 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 Connecting to 10.223.49.195:8250
 2014-04-22 04:10:42,920 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 SSL: Handshake done
 2014-04-22 04:10:42,920 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 Connected to 10.223.49.195:8250
 2014-04-22 04:10:42,941 WARN  [kvm.resource.LibvirtComputingResource] 
 (Agent-Handler-1:null) Could not read cpuinfo_max_freq
 2014-04-22 04:10:43,158 INFO  [cloud.serializer.GsonHelper] 
 (Agent-Handler-1:null) Default Builder inited.
 2014-04-22 04:10:43,227 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
 Proccess agent startup answer, agent id = 0
 2014-04-22 04:10:43,227 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) Set 
 agent id 0
 2014-04-22 04:10:43,233 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
 Startup Response Received: agent id = 0
 2014-04-22 04:11:40,925 INFO  [cloud.agent.Agent] (Agent-Handler-1:null) Lost 
 connection to the server. Dealing with the remaining commands...
 2014-04-22 04:11:42,352 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 0
 2014-04-22 04:11:42,368 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 1
 2014-04-22 04:11:42,383 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 2
 2014-04-22 04:11:42,398 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 3
 2014-04-22 04:11:42,413 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 4
 2014-04-22 04:11:42,414 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error; reboot the host
 2014-04-22 04:11:42,472 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error:

[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic

2014-04-15 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-6317:


Sateesh is testing the fix. Should have an update in another couple of days.

 [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
 --

 Key: CLOUDSTACK-6317
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6317
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.3.0, 4.4.0
 Environment: VMware vCenter 5.1, ESXi 5.0 hosts
 MS with ACS 4.3.0
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
Priority: Critical
 Fix For: 4.4.0, 4.3.1


 Prior to ACS 4.3.0 CloudStack used to support tagged VLAN for management / 
 storage / control traffic via traffic label, where admin would specify the 
 VLAN in comma separated string of vmware network traffic label. E.g. 
 vSwitch0,100 - This means management traffic would use standard vSwitch port 
 group tagged with VLAN 100 which sits on vSwitch0 existing on ESXi host.
 This is functionality was broken since below commit in ACS 4.3 branch,
 Commit 7c4831df9292115466fb9e01fcba952a5dad31c1 in branch refs/heads/4.3 from 
 Hugo Trippaers
 [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7c4831d ]
 This commit overwrites the parsed vSwitch name, from traffic label, with 
 traffic label specified by admin resulting into below error during deployment 
 of SSVM (or any VM that needs management/storage traffic)
 2014-04-01 08:23:19,866 DEBUG [c.c.h.v.r.VmwareResource] 
 (DirectAgent-9:ctx-862d86ff 10.102.192.3) VM v-2-VM will be started with NIC 
 device type: E1000
 2014-04-01 08:23:19,866 INFO  [c.c.h.v.r.VmwareResource] 
 (DirectAgent-9:ctx-862d86ff 10.102.192.3) Prepare NIC device based on NicTO: 
 {deviceId:0,networkRateMbps:-1,defaultNic:false,uuid:07c38800-6da3-4596-b0ea-09047d45970e,mac:02:00:63:46:00:02,broadcastType:LinkLocal,type:Control,isSecurityGroupEnabled:false,name:vSwitch0,100}
 2014-04-01 08:23:21,150 ERROR [c.c.h.v.m.HypervisorHostHelper] 
 (DirectAgent-6:ctx-a6062e05 10.102.192.3) Unable to find vSwitchvSwitch0,100
 2014-04-01 08:23:21,151 WARN  [c.c.h.v.r.VmwareResource] 
 (DirectAgent-6:ctx-a6062e05 10.102.192.3) StartCommand failed due to 
 Exception: java.lang.Exception
 Message: Unable to find vSwitchvSwitch0,100



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

[jira] [Updated] (CLOUDSTACK-5974) [Automation] Adding persistent network (with All services through VpcVirtualRouter) to VPC failing with Failed to add VPC router VM to guest network

2014-04-08 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5974:
---

Assignee: Likitha Shetty

 [Automation] Adding persistent network (with All services through 
 VpcVirtualRouter) to VPC failing with Failed to add VPC router VM to guest 
 network
 --

 Key: CLOUDSTACK-5974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5974
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.4.0
 Environment: Observed on KVM and VMware
Reporter: Gaurav Aradhye
Assignee: Likitha Shetty
  Labels: automation
 Fix For: 4.4.0

 Attachments: Mgt-Server-Log-PN.txt


 1. Create a VPC network with cidr 10.1.1.1/16
 2. Create a persistent network offering with all services through 
 VpcVirtualRouter (Dhcp,Dns,SourceNat,PortForwarding,Vpn,Lb,UserData,StaticNat)
 3. Try to add tier to VPC with this network offering
 4. Operation fails with error Failed to add VPC router VM to guest network
 Mgt-Server Log attached.
 Please note that if Persistent flag is unchecked in the service offering 
 keeping everything same, it works.



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

[jira] [Updated] (CLOUDSTACK-6239) [Automation] jasypt decryption error is thrown after restarting console proxy VM

2014-03-27 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-6239:
---

Assignee: Rajesh Battala

 [Automation] jasypt decryption error is thrown after restarting console proxy 
 VM
 

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


 STEPS TO REPRODUCE:
 
 1. create a zone and let SSVM and CPVM come up.
 2. restart CPVM.
 i am hitting the following error while CPVM is being restarted.
 2014-03-14 05:48:55,917 DEBUG [cloud.resource.ResourceState] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Resource state update: [id = 8; 
 name = v-6-VM; old state = Creating; event = InternalCreated; new state = 
 Enabled]
 2014-03-14 05:48:55,917 DEBUG [cloud.host.Status] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Transition:[Resource state = 
 Enabled, Agent event = AgentConnected, Host id = 8, name = v-6-VM]
 2014-03-14 05:48:55,922 DEBUG [cloud.host.Status] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Agent status update: [id = 8; name 
 = v-6-VM; old status = Creating; event = AgentConnected; new status = 
 Connecting; old update count = 0; new update count = 1]
 2014-03-14 05:48:55,922 DEBUG [agent.manager.ClusteredAgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) create ClusteredAgentAttache for 8
 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 XcpServerDiscoverer
 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 HypervServerDiscoverer
 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 DeploymentPlanningManagerImpl
 2014-03-14 05:48:55,923 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 ClusteredVirtualMachineManagerImpl
 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 NetworkOrchestrator
 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 StoragePoolMonitor
 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 SecurityGroupListener
 2014-03-14 05:48:55,924 INFO  [network.security.SecurityGroupListener] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Received a host startup notification
 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 SecondaryStorageListener
 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 UploadListener
 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 BehindOnPingListener
 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 DirectNetworkStatsListener
 2014-03-14 05:48:55,924 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Sending Connect to listener: 
 ConsoleProxyListener
 2014-03-14 05:48:55,928 DEBUG [utils.crypt.DBEncryptionUtil] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Error while decrypting: 
 A1i0Flrc5LPgCsx3V7cOVQ
 2014-03-14 05:48:55,929 ERROR [agent.manager.AgentManagerImpl] 
 (AgentConnectTaskPool-11423:ctx-abee3e50) Monitor ConsoleProxyListener says 
 there is an error in the connect process for 8 due to null
 org.jasypt.exceptions.EncryptionOperationNotPossibleException
   at 
 org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:981)
   at 
 org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725)
   at 
 com.cloud.utils.crypt.DBEncryptionUtil.decrypt(DBEncryptionUtil.java:63)
   at 
 org.apache.cloudstack.framework.config.impl.ConfigurationVO.getValue(ConfigurationVO.java:125)
   at 
 org.apache.cloudstack.framework.config.ConfigKey.value(ConfigKey.java:136)
   at

[jira] [Updated] (CLOUDSTACK-6092) Storage OverProvisioning as a Per Primary Basis

2014-02-20 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-6092:
---

Description: 
The current scenario is to set the global parameter 
storage.overprovisioning.factor that is inherently applicable for any qualified 
primary store to leverage over provision of the underlying storage. 
Cloud Deployments can have different combinations of primary storage either for 
different vendors or from the same vendor but different products
Depending on the storage capability, CloudStack admins need the flexibility to 
determine what the over-provisioning factor should be for each primary storage.

FS link - 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+OverProvisioning+as+Per+Primary+Basis

  was:
The current scenario is to set the global parameter 
storage.overprovisioning.factor that is inherently applicable for any qualified 
primary store to leverage over provision of the underlying storage. 
Cloud Deployments can have different combinations of primary storage either for 
different vendors or from the same vendor but different products
Depending on the storage capability, CloudStack admins need the flexibility to 
determine what the over-provisioning factor should be for each primary storage.




 Storage OverProvisioning as a Per Primary Basis
 ---

 Key: CLOUDSTACK-6092
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6092
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Storage Controller
Affects Versions: 4.4.0
Reporter: Saksham Srivastava
Assignee: Saksham Srivastava
  Labels: Storage
 Fix For: 4.4.0


 The current scenario is to set the global parameter 
 storage.overprovisioning.factor that is inherently applicable for any 
 qualified primary store to leverage over provision of the underlying storage. 
 Cloud Deployments can have different combinations of primary storage either 
 for different vendors or from the same vendor but different products
 Depending on the storage capability, CloudStack admins need the flexibility 
 to determine what the over-provisioning factor should be for each primary 
 storage.
 FS link - 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+OverProvisioning+as+Per+Primary+Basis



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CLOUDSTACK-5964) [Automation] Assigning virtual machine (belonging to persistent network) to other account, creates a non persistent network instead of persistent one

2014-01-28 Thread Ram Ganesh (JIRA)

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

Ram Ganesh commented on CLOUDSTACK-5964:

Whether a network is persistent or not is a property of network and NOT of a
VM isn't? So above use is valid - VM should not dictate if the network should
be persistent or not.

I am resolving this bug as as-design. Please re-open if you disagree and you
have a use case

[Automation] Assigning virtual machine (belonging to persistent network) to
other account, creates a non persistent network instead of persistent one
-

Key: CLOUDSTACK-5964
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5964
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.4.0
Environment: Observed on VMware yet
Reporter: Gaurav Aradhye
Labels: automation
Fix For: 4.4.0

Steps to reproduce:
1. Create an account (account-1), create a persistent network in it
2. Deploy VM in this persistent network
3. Create another account (account-2) and assign the VM to this account
4. Check the network created in account-2
5. The network created should be persistent, but instead non persistent
network is created
I have not attached any logs as there are no exceptions or anything to debug.
Please let me know in case you need some specific data from logs.

--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CLOUDSTACK-5964) [Automation] Assigning virtual machine (belonging to persistent network) to other account, creates a non persistent network instead of persistent one

2014-01-28 Thread Ram Ganesh (JIRA)


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

Ram Ganesh resolved CLOUDSTACK-5964.


Resolution: Won't Fix

 [Automation] Assigning virtual machine (belonging to persistent network) to 
 other account, creates a non persistent network instead of persistent one
 -

 Key: CLOUDSTACK-5964
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5964
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.4.0
 Environment: Observed on VMware yet
Reporter: Gaurav Aradhye
  Labels: automation
 Fix For: 4.4.0


 Steps to reproduce:
 1. Create an account (account-1), create a persistent network in it
 2. Deploy VM in this persistent network
 3. Create another account (account-2) and assign the VM to this account
 4. Check the network created in account-2
 5. The network created should be persistent, but instead non persistent 
 network is created
 I have not attached any logs as there are no exceptions or anything to debug.
 Please let me know in case you need some specific data from logs.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CLOUDSTACK-5944) listNetworkACLs unexpectedly returns all ACL's

2014-01-24 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5944:


is this same as https://issues.apache.org/jira/browse/CLOUDSTACK-5145?

 listNetworkACLs unexpectedly returns all ACL's
 --

 Key: CLOUDSTACK-5944
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5944
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.1
Reporter: Rutger te Nijenhuis
Priority: Minor

 There is some unexpected behavior in the listNetworkACLs call.
 If a valid VPCs networkid is provided, listNetworkACLs returns only the acl's 
 belonging to the VPC network. However listNetworkACLs returns all ACLs within 
 an account when a valid networkid is given which does not belong to a VPC 
 network. The networkid can be from any non-VPC network, also outside the 
 account.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CLOUDSTACK-5903) CLONE - OVA files exist for templates created from volumes

2014-01-18 Thread Ram Ganesh (JIRA)

Ram Ganesh created CLOUDSTACK-5903:
--

 Summary: CLONE - OVA files exist for templates created from volumes
 Key: CLOUDSTACK-5903
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5903
 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
Reporter: Ram Ganesh
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.3.0


With the fix provided for 
[https://issues.apache.org/jira/browse/CLOUDSTACK-671], CS is not supposed not 
to keep OVA file with a template and snapshots. 
There is no OVA saved and kept with a snapshot. But there is inconsistent 
behavior with regards to templates. Templates that are created from snapshots 
don't have OVA file whereas templates created from volumes have OVA file that 
consumes storage and causes longer template creation.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CLOUDSTACK-5903) CLONE - OVA files exist for templates created from volumes

2014-01-18 Thread Ram Ganesh (JIRA)


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

Ram Ganesh resolved CLOUDSTACK-5903.


Resolution: Invalid

Sorry. By mistake I cloned this bug. Resolving it as invalid

 CLONE - OVA files exist for templates created from volumes
 --

 Key: CLOUDSTACK-5903
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5903
 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
Reporter: Ram Ganesh
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.3.0


 With the fix provided for 
 [https://issues.apache.org/jira/browse/CLOUDSTACK-671], CS is not supposed 
 not to keep OVA file with a template and snapshots. 
 There is no OVA saved and kept with a snapshot. But there is inconsistent 
 behavior with regards to templates. Templates that are created from snapshots 
 don't have OVA file whereas templates created from volumes have OVA file that 
 consumes storage and causes longer template creation.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5815) [Hyper-v] Two SNAT rules for one isolated network if acquired ip is from different vlan

2014-01-14 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5815:
---

Assignee: Rajesh Battala

 [Hyper-v] Two SNAT rules for one isolated network if acquired ip is from 
 different vlan
 ---

 Key: CLOUDSTACK-5815
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5815
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Network Controller
Affects Versions: 4.3.0
 Environment: Latest build from 4.3 branch with 
 commit:6f309b8a87d3376950a60234d399c6e3749ad1c7
Reporter: Sanjeev N
Assignee: Rajesh Battala
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.3.0


 [Hyper-v] Two SNAT rules for one isolated network if acquired ip is from 
 different vlan
 Steps to Reproduce:
 =
 1.Bring up CS in advanced zone with hyper-v cluster
 2.Create isolated guest network and deploy few vms in the network
 3.Exhaust all the public IP addresses present in the zone (in user_ip_address 
 table set the allocated=now())
 4.Add new public IP range in new vlan and new subnet
 5.Acquire one ip address from the new ip range and configure PF and assign 
 one vm deployed at step2 
 Expected Result:
 ==
 In isolated network there is only one SNAT ip address for the entire network. 
 So even the acquired IP address is from different vlan, new SNAT rule should 
 not be configured with the acquired ip address.
 Actual Result:
 
 Since the ip address acquired at step5 is from new vlan and is the ip address 
 from that vlan additional SNAT rule got configured on VR with the acquired ip 
 address.
 Following is the output from iptables on VR:
 root@r-4-VM:~# iptables -t nat -L -nv
 Chain PREROUTING (policy ACCEPT 279 packets, 28169 bytes)
  pkts bytes target prot opt in out source   
 destination
 0 0 DNAT   tcp  --  eth2   *   0.0.0.0/0
 10.147.31.240tcp dpt:22 to:10.1.1.26:22
 0 0 DNAT   tcp  --  eth0   *   0.0.0.0/0
 10.147.31.240tcp dpt:22 to:10.1.1.26:22
 Chain INPUT (policy ACCEPT 4 packets, 240 bytes)
  pkts bytes target prot opt in out source   
 destination
 Chain OUTPUT (policy ACCEPT 4 packets, 304 bytes)
  pkts bytes target prot opt in out source   
 destination
 0 0 DNAT   tcp  --  *  *   0.0.0.0/0
 10.147.31.240tcp dpt:22 to:10.1.1.26:22
 Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
  pkts bytes target prot opt in out source   
 destination
 0 0 SNAT   tcp  --  *  eth010.1.1.0/24  10.1.1.26 
tcp dpt:22 to:10.1.1.1
 4   304 SNAT   all  --  *  eth20.0.0.0/00.0.0.0/0 
to:10.147.48.5
 0 0 SNAT   all  --  *  eth20.0.0.0/00.0.0.0/0 
to:10.147.31.240
 ip address configuration on eth2 as follows:
 root@r-4-VM:~# ip addr show eth2
 4: eth2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP 
 qlen 1000
 link/ether 06:78:3c:00:00:17 brd ff:ff:ff:ff:ff:ff
 inet 10.147.48.5/24 brd 10.147.48.255 scope global eth2
 inet 10.147.31.240/24 brd 10.147.31.255 scope global eth2
 inet6 fe80::478:3cff:fe00:17/64 scope link
valid_lft forever preferred_lft forever
 Following is the IpAssocCmd got executed after configuring PF rule on the 
 acquired ip address:
 2014-01-07 11:30:39,274 DEBUG [c.c.a.t.Request] (Job-Executor-31:ctx-26e587af 
 ctx-d423299a) Seq 4-2034961238: Sending  { Cmd , MgmtId: 132129494109518, 
 via: 4(10.147.40.31), Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.routing.IpAssocCommand:{ipAddresses:[{accountId:2,publicIp:10.147.48.5,sourceNat:true,add:true,oneToOneNat:false,firstIP:true,broadcastUri:vlan://48,vlanGateway:10.147.48.1,vlanNetmask:255.255.255.0,vifMacAddress:06:88:76:00:00:17,networkRate:200,trafficType:Public}],accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:10.147.40.230,router.name:r-4-VM},wait:0}},{com.cloud.agent.api.routing.IpAssocCommand:{ipAddresses:[{accountId:2,publicIp:10.147.31.240,sourceNat:true,add:true,oneToOneNat:false,firstIP:true,broadcastUri:vlan://31,vlanGateway:10.147.31.1,vlanNetmask:255.255.255.0,vifMacAddress:06:78:3e:00:00:17,networkRate:200,trafficType:Public}],accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:10.147.40.230,router.name:r-4-VM},wait:0}}]
  }
 2014-01-07 11:30:39,275 DEBUG [c.c.a.t.Request] (Job-Executor-31:ctx-26e587af 
 ctx-d423299a) Seq 4-2034961238: Executing:

[jira] [Updated] (CLOUDSTACK-5795) [Hyper-V] When a Template is created from volume the db.properties file is not created, due to which when we restart management server, The DB entry for that Templa

2014-01-06 Thread Ram Ganesh (JIRA)

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

Ram Ganesh updated CLOUDSTACK-5795:
---

Assignee: Devdeep Singh

[Hyper-V] When a Template is created from volume the db.properties file is
not created, due to which when we restart management server, The DB entry
for that Template is deleted from template_store_ref table and template
becomes inaccessible
--

Key: CLOUDSTACK-5795
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5795
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
Environment: Hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.3.0

Attachments: CS-5795.jpg, CS-5795.zip

Steps :
===
1. Deploy an advanced zone setup of CS 4.3 with Hyper-V as the hypervisor
type.
2. Create a VM.
3. Stop the VM and create a Template from it's ROOT volume.
But when the template is created, we can see in our secondary storage that
the template.properties file doesn't get created
4. Now Deploy a VM from the template created in step 3 .
VM deployment goes fine.
5. Now restart the management server.
After management server restart we find that the DB entry for that template
in template_store_ref is gone.
Attaching management server logs , snapshot and DB dump.

--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5794) [Hyper-v] Specify username and domain name together in the username field while adding host in Hyper-v cluster

2014-01-06 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5794:
---

Assignee: Devdeep Singh

 [Hyper-v] Specify username and domain name together in the username field 
 while adding host in Hyper-v cluster
 --

 Key: CLOUDSTACK-5794
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5794
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, Hypervisor Controller
Affects Versions: 4.3.0
 Environment: Hyper-v cluster
Reporter: Sanjeev N
Assignee: Devdeep Singh
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.3.0

 Attachments: hyprv-host.PNG


 In Hyper-v all the hosts are domain joined hosts. So while adding a host in 
 hyper-v cluster Admin should pass the domain name and username using username 
 parameter itself. 
 Pass the username parameter as below:
 username=BLR\sanjeev



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5752) Persistent network fails to implement

2014-01-03 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5752:
---

Assignee: Likitha Shetty

 Persistent network fails to implement 
 --

 Key: CLOUDSTACK-5752
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5752
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.3.0
 Environment: Advanced zone, any hypervisor
Reporter: Sowmya Krishnan
Assignee: Likitha Shetty
Priority: Blocker
 Fix For: 4.3.0

 Attachments: ms.log


 Latest build fails to implement a persistent network.
 Steps:
 Create isolated network offering with persistent = true
 Launch a network with this offering.
 Logs simply say that it fails to implement the network and router fails to 
 launch and throws an NPE:
 2014-01-03 14:02:36,344 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Starting router 
 VM[DomainRouter|r-34-VM]
 2014-01-03 14:02:36,344 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Cleaning up because we're unable 
 to implement the network Ntwk[219|Guest|22]
 2014-01-03 14:02:36,349 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Lock is acquired for network 
 Ntwk[219|Guest|22] as a part of network shutdown
 2014-01-03 14:02:36,355 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 port forwarding rules 
 for network id=219 as a part of shutdownNetworkRu
 les
 2014-01-03 14:02:36,355 DEBUG [c.c.n.f.FirewallManagerImpl] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to 
 the network elements
 2014-01-03 14:02:36,356 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Releasing 0 static nat rules for 
 network id=219 as a part of shutdownNetworkRules
 2014-01-03 14:02:36,356 DEBUG [c.c.n.f.FirewallManagerImpl] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) There are no rules to forward to 
 the network elements
 2014-01-03 14:02:36,357 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Revoking 0 Public load balancing 
 rules for network id=219
 ...
 ...
 2014-01-03 14:02:36,383 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Sending network shutdown to 
 VirtualRouter
 2014-01-03 14:02:36,384 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Stopping router 
 VM[DomainRouter|r-34-VM]
 2014-01-03 14:02:36,384 WARN  [o.a.c.e.o.NetworkOrchestrator] 
 (catalina-exec-9:ctx-e1417c9c ctx-499be25e) Unable to complete shutdown of 
 the network elements due to element: VirtualRouter
 java.lang.NullPointerException
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1268)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2702)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy240.stop(Unknown Source)
 at 
 com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:665)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2052)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:1965)
 at

[jira] [Updated] (CLOUDSTACK-5739) [vmware] Vcenter 5.5 host ESXi 5.5 host maintenance mode some VMs in stop state not migrated

2014-01-03 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5739:
---

Assignee: Likitha Shetty

 [vmware] Vcenter 5.5  host ESXi 5.5  host maintenance mode some VMs in stop 
 state not migrated
 --

 Key: CLOUDSTACK-5739
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5739
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: MS4.3   build  1/2/2014
 vcenter  5.5host1   host2 ESXi 5.5
Reporter: angeline shen
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.3.0

 Attachments: management-server.log.gz, vm43.png, vm431.png, 
 vm432.png, vm5131.png, vm5132.png, vm5133.png, vm5134.png, vm5135.png, 
 vm5136.png


 1. advance zone, create VMs
 2. Put host1 in maintenance mode.
 3. 1 guest VM remain in stop state , not migrated
  VRs remain in stop state, not migrated
  host remain in PrepareForMaintenance mode



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5743) [Hyper-V] Download ROOT Volume when the VM is in stopped state is failing with Forbidden You don't have permission to access /userdata/e914903a-070b-4ee3-b217-f07d

2014-01-03 Thread Ram Ganesh (JIRA)

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

Ram Ganesh updated CLOUDSTACK-5743:
---

Assignee: Devdeep Singh

[Hyper-V] Download ROOT Volume when the VM is in stopped state is failing
with Forbidden You don't have permission to access
/userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server
--

Key: CLOUDSTACK-5743
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5743
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.3.0
Environment: 4.3, Hyper-V
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
Labels: hyper-V,, hyper-v, hyperv
Fix For: 4.3.0

Steps :

1. Create an advanced zone setup with hyper-v as the host hypervisor type and
shared CIFS storage for primary storage
2. Deploy a VM
3. stop the VM
4. Goto the ROOT/Data volume of the VM and try to download it.
Expected behaviour :
=
The volume should be successfully downloaded .
Observed behaviour :
=
ROOT volume download fails with the following message in the UI :
Forbidden
You don't have permission to access
/userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server
There is nothing in the MS log or Agent logs.
NOTE : Tried the same operation on VMware and it is working fine.
In case of Hyperv also, template download is going through but volume
download is failing.

--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CLOUDSTACK-5707) Hitting multiple exceptions when the Vsphere client is upgraded to 5.5 from 5.1

2014-01-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5707:


Likitha

Can you please look into this one?

 Hitting multiple exceptions when the Vsphere client is upgraded to 5.5 from 
 5.1
 ---

 Key: CLOUDSTACK-5707
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5707
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.3.0
 Environment: Upgraded the CS 4.2.1 to 4.3 with ESXi5.1 using Vsphere 
 client 5.1
 Upgraded the Vsphere client to 5.5
Reporter: manasaveloori
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.3.0

 Attachments: management-server.rar


 Steps followed:
 1.Deployed CS 4.2.1 GA build with  ESXi5.1(using Vsphere 5.1 client)
 2.Deployed some VMs.
 3.Upgraded the CS to 4.3.
 4.Now unmanaged the cluster, kept the host in maintenance .
 5.Upgraded the Vsphere client to 5.5 
 (http://www.vmadmin.co.uk/vmware/36-virtualcenter/284-vsphere4to5upgradevcenter41to5)
 6.Manage the cluster and cancelled the maintenance mode on host.
 7.Host is connected.
 Observing the following exceptions in Ms logs:
 014-01-01 20:03:35,467 DEBUG [c.c.s.StatsCollector] 
 (StatsCollector-3:ctx-a4d2e607) StorageCollector is running...
 2014-01-01 20:03:35,497 INFO  [c.c.a.m.AgentAttache] 
 (StatsCollector-3:ctx-a4d2e607) Seq 2-1062210638: Unable to send due to 
 Resource [Host:2] is unreachable: Host 2: Channel is closed
 2014-01-01 20:03:35,497 DEBUG [c.c.a.m.AgentAttache] 
 (StatsCollector-3:ctx-a4d2e607) Seq 2-1062210638: Cancelling.
 2014-01-01 20:03:35,498 DEBUG [o.a.c.s.RemoteHostEndPoint] 
 (StatsCollector-3:ctx-a4d2e607) Failed to send command, due to Agent:2, 
 com.cloud.exception.AgentUnavailableException: Resource [Host:2] is 
 unreachable: Host 2: Channel is closed
 2014-01-01 20:03:35,498 ERROR [c.c.s.StatsCollector] 
 (StatsCollector-3:ctx-a4d2e607) Error trying to retrieve storage stats
 com.cloud.utils.exception.CloudRuntimeException: Failed to send command, due 
 to Agent:2, com.cloud.exception.AgentUnavailableException: Resource [Host:2] 
 is unreachable: Host 2: Channel is closed
 at 
 org.apache.cloudstack.storage.RemoteHostEndPoint.sendMessage(RemoteHostEndPoint.java:116)
 at 
 com.cloud.server.StatsCollector$StorageCollector.runInContext(StatsCollector.java:550)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 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)
 2014-01-01 20:03:35,506 DEBUG [c.c.s.StatsCollector] 
 (StatsCollector-1:ctx-df84e56c) HostStatsCollector is running...
 2014-01-01 20:03:35,534 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-374:ctx-c3b00e50) Seq 4-378077280: Executing request
 2014-01-01 20:03:35,638 ERROR [c.c.h.v.r.VmwareResource] 
 (DirectAgent-374:ctx-c3b00e50 10.147.40.28) Unable to execute 
 GetHostStatsCommand due to Exception: javax.xml.ws.soap.SOAPFaultException
 Message: The session is not authenticated.
 javax.xml.ws.soap.SOAPFaultException: The session is not authenticated.
 at 
 com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
 at 
 com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119)
 at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)

[jira] [Updated] (CLOUDSTACK-5707) Hitting multiple exceptions when the Vsphere client is upgraded to 5.5 from 5.1

2014-01-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5707:
---

Assignee: Likitha Shetty

 Hitting multiple exceptions when the Vsphere client is upgraded to 5.5 from 
 5.1
 ---

 Key: CLOUDSTACK-5707
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5707
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.3.0
 Environment: Upgraded the CS 4.2.1 to 4.3 with ESXi5.1 using Vsphere 
 client 5.1
 Upgraded the Vsphere client to 5.5
Reporter: manasaveloori
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.3.0

 Attachments: management-server.rar


 Steps followed:
 1.Deployed CS 4.2.1 GA build with  ESXi5.1(using Vsphere 5.1 client)
 2.Deployed some VMs.
 3.Upgraded the CS to 4.3.
 4.Now unmanaged the cluster, kept the host in maintenance .
 5.Upgraded the Vsphere client to 5.5 
 (http://www.vmadmin.co.uk/vmware/36-virtualcenter/284-vsphere4to5upgradevcenter41to5)
 6.Manage the cluster and cancelled the maintenance mode on host.
 7.Host is connected.
 Observing the following exceptions in Ms logs:
 014-01-01 20:03:35,467 DEBUG [c.c.s.StatsCollector] 
 (StatsCollector-3:ctx-a4d2e607) StorageCollector is running...
 2014-01-01 20:03:35,497 INFO  [c.c.a.m.AgentAttache] 
 (StatsCollector-3:ctx-a4d2e607) Seq 2-1062210638: Unable to send due to 
 Resource [Host:2] is unreachable: Host 2: Channel is closed
 2014-01-01 20:03:35,497 DEBUG [c.c.a.m.AgentAttache] 
 (StatsCollector-3:ctx-a4d2e607) Seq 2-1062210638: Cancelling.
 2014-01-01 20:03:35,498 DEBUG [o.a.c.s.RemoteHostEndPoint] 
 (StatsCollector-3:ctx-a4d2e607) Failed to send command, due to Agent:2, 
 com.cloud.exception.AgentUnavailableException: Resource [Host:2] is 
 unreachable: Host 2: Channel is closed
 2014-01-01 20:03:35,498 ERROR [c.c.s.StatsCollector] 
 (StatsCollector-3:ctx-a4d2e607) Error trying to retrieve storage stats
 com.cloud.utils.exception.CloudRuntimeException: Failed to send command, due 
 to Agent:2, com.cloud.exception.AgentUnavailableException: Resource [Host:2] 
 is unreachable: Host 2: Channel is closed
 at 
 org.apache.cloudstack.storage.RemoteHostEndPoint.sendMessage(RemoteHostEndPoint.java:116)
 at 
 com.cloud.server.StatsCollector$StorageCollector.runInContext(StatsCollector.java:550)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 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)
 2014-01-01 20:03:35,506 DEBUG [c.c.s.StatsCollector] 
 (StatsCollector-1:ctx-df84e56c) HostStatsCollector is running...
 2014-01-01 20:03:35,534 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-374:ctx-c3b00e50) Seq 4-378077280: Executing request
 2014-01-01 20:03:35,638 ERROR [c.c.h.v.r.VmwareResource] 
 (DirectAgent-374:ctx-c3b00e50 10.147.40.28) Unable to execute 
 GetHostStatsCommand due to Exception: javax.xml.ws.soap.SOAPFaultException
 Message: The session is not authenticated.
 javax.xml.ws.soap.SOAPFaultException: The session is not authenticated.
 at 
 com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
 at 
 com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119)
 at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
 at

[jira] [Commented] (CLOUDSTACK-5716) [Hyper-v] Can't type Special character in console view

2014-01-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5716:


Anshul,

Can you please look into this one?

 [Hyper-v] Can't type Special character in console view
 --

 Key: CLOUDSTACK-5716
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5716
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.3.0
 Environment: Latest build from 4.3 branch with 
 commit:95b6a7b96dab1c77e25987d6fe6003b4447281f1
Reporter: Sanjeev N
Assignee: Anshul Gangwar
Priority: Critical
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.3.0


 [Hyper-v] Can't type Special character in console view
 Steps to Reproduce:
 
 1.Bring up CS with Hyperv cluster
 2.Wait for the CPVM to come up
 3.Deploy guest vm with default cent os template
 4.Try accessing the system/guest vms console from CS
 5.Login and try to type special characters
 Result:
 =
 Can't type the special characters(Shift+(1-9,0)) and also other characters 
 like below:
 ~
 `
 {
 }
 |
 
 
 ?
 :
 
 +
 _
 -
 =



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5716) [Hyper-v] Can't type Special character in console view

2014-01-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5716:
---

Assignee: Anshul Gangwar

 [Hyper-v] Can't type Special character in console view
 --

 Key: CLOUDSTACK-5716
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5716
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.3.0
 Environment: Latest build from 4.3 branch with 
 commit:95b6a7b96dab1c77e25987d6fe6003b4447281f1
Reporter: Sanjeev N
Assignee: Anshul Gangwar
Priority: Critical
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.3.0


 [Hyper-v] Can't type Special character in console view
 Steps to Reproduce:
 
 1.Bring up CS with Hyperv cluster
 2.Wait for the CPVM to come up
 3.Deploy guest vm with default cent os template
 4.Try accessing the system/guest vms console from CS
 5.Login and try to type special characters
 Result:
 =
 Can't type the special characters(Shift+(1-9,0)) and also other characters 
 like below:
 ~
 `
 {
 }
 |
 
 
 ?
 :
 
 +
 _
 -
 =



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CLOUDSTACK-5721) [Automation] ROOT /Data Volume migration failing with error Volume need to detached from VM

2014-01-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh resolved CLOUDSTACK-5721.


Resolution: Duplicate

This is the new behaviour starting 4.3. Sateesh commented about it in 
CLOUDSTACK-5008. Please have a look at the comments.

 [Automation] ROOT /Data Volume migration failing with error Volume need to 
 detached from VM
 -

 Key: CLOUDSTACK-5721
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5721
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.3.0
 Environment: KVM and VMware
 branch 4.3
Reporter: Rayees Namathponnan
Assignee: Sateesh Chodapuneedi
Priority: Blocker
 Fix For: 4.3.0

 Attachments: management-server.rar


 Steps to reproduce 
 Step 1 : Create advanced zone in KVM or vmware with 2 primary storage
 Step 2 : Create new data volume
 Step 3 : Migrate date volume before attaching to any vm
 Result 
 Volume migration failed with error  Volume need to detached from VM 
 2014-01-02 08:31:08,642 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-13:ctx-d1293903 ctx-e4003189) ===END===  10.216.51.177 -- GET  
 command=migrateVolumelivemigrate=truestorageid=41b632b5-40b3-3024-a38b-ea259c72579fvolumeid=0ab09e30-fe24-4994-9921-c62759e0593aresponse=jsonsessionkey=8sDkkIHWYSBfmGVV%2B4Y6Stidoi4%3D_=1388680475046
 2014-01-02 08:31:08,653 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-16:ctx-6d2be4dd) Add job-4519 into job monitoring
 2014-01-02 08:31:08,653 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-16:ctx-6d2be4dd) Executing AsyncJobVO {id:4519, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd, cmdInfo: 
 {response:json,sessionkey:8sDkkIHWYSBfmGVV+4Y6Stidoi4\u003d,cmdEventType:VOLUME.MIGRATE,ctxUserId:2,storageid:41b632b5-40b3-3024-a38b-ea259c72579f,livemigrate:true,httpmethod:GET,volumeid:0ab09e30-fe24-4994-9921-c62759e0593a,_:1388680475046,ctxAccountId:2,ctxStartEventId:16885},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-01-02 08:31:08,660 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-16:ctx-6d2be4dd) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd
 com.cloud.exception.InvalidParameterValueException: Volume needs to be 
 detached from VM
 at 
 com.cloud.storage.VolumeApiServiceImpl.migrateVolume(VolumeApiServiceImpl.java:1555)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy195.migrateVolume(Unknown Source)
 at 
 org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd.execute(MigrateVolumeCmd.java:103)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
 at 
 com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
 at

[jira] [Updated] (CLOUDSTACK-5731) [Automation] VM deployment failed with ConcurrentOperationException in vmware

2014-01-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5731:
---

Assignee: Likitha Shetty

 [Automation] VM deployment failed with ConcurrentOperationException in vmware
 -

 Key: CLOUDSTACK-5731
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5731
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, VMware
Affects Versions: 4.3.0
 Environment: vmware 5.0
 branch 4.3
Reporter: Rayees Namathponnan
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.3.0

 Attachments: management-server.rar


 This issue observed in automation environment,  where mulpitple deployment 
 and delete operation happens parallel 
 Vew of the vm deployment failed with below error, i will attach complete log 
 with this defect 
 2014-01-02 13:24:29,612 WARN  [o.a.c.alerts] (Job-Executor-2:ctx-9e3b8e54 
 ctx-dd556c3f)  alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: 
 null // message:: Failed to deploy
  Vm with Id: 5, on Host with Id: null
 2014-01-02 13:24:29,653 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-2:ctx-9e3b8e54) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.DeployVMCmd
 com.cloud.utils.exception.CloudRuntimeException: Unable to serialize: 
 com.cloud.exception.AgentUnavailableException/{_scope:com.cloud.host.Host,_id:1,idList:[],csErrorCode:4285,detailMessage:Resource
  [Host:1] is unreachable: Host 1: Unable to start instance due to Unable to 
 transition to a new state from Running via 
 OperationFailed,cause:{class:com.cloud.exception.ConcurrentOperationException,msg:Unable
  to transition to a new state from Running via 
 OperationFailed},stackTrace:[{declaringClass:com.cloud.vm.VirtualMachineManagerImpl,methodName:orchestrateStart,fileName:VirtualMachineManagerImpl.java,lineNumber:1053},{declaringClass:com.cloud.vm.VirtualMachineManagerImpl,methodName:orchestrateStart,fileName:VirtualMachineManagerImpl.java,lineNumber:4736},{declaringClass:sun.reflect.NativeMethodAccessorImpl,methodName:invoke0,fileName:NativeMethodAccessorImpl.java,lineNumber:-2},{declaringClass:sun.reflect.NativeMethodAccessorImpl,methodName:invoke,fileName:NativeMethodAccessorImpl.java,lineNumber:57},{declaringClass:sun.reflect.DelegatingMethodAccessorImpl,methodName:invoke,fileName:DelegatingMethodAccessorImpl.java,lineNumber:43},{declaringClass:java.lang.reflect.Method,methodName:invoke,fileName:Method.java,lineNumber:606},{declaringClass:com.cloud.vm.VmWorkJobHandlerProxy,methodName:handleVmWorkJob,fileName:VmWorkJobHandlerProxy.java,lineNumber:107},{declaringClass:com.cloud.vm.VirtualMachineManagerImpl,methodName:handleVmWorkJob,fileName:VirtualMachineManagerImpl.java,lineNumber:4855},{declaringClass:com.cloud.vm.VmWorkJobDispatcher,methodName:runJob,fileName:VmWorkJobDispatcher.java,lineNumber:99},{declaringClass:org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5,methodName:runInContext,fileName:AsyncJobManagerImpl.java,lineNumber:522},{declaringClass:org.apache.cloudstack.managed.context.ManagedContextRunnable$1,methodName:run,fileName:ManagedContextRunnable.java,lineNumber:49},{declaringClass:org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1,methodName:call,fileName:DefaultManagedContext.java,lineNumber:56},{declaringClass:org.apache.cloudstack.managed.context.impl.DefaultManagedContext,methodName:callWithContext,fileName:DefaultManagedContext.java,lineNumber:103},{declaringClass:org.apache.cloudstack.managed.context.impl.DefaultManagedContext,methodName:runWithContext,fileName:DefaultManagedContext.java,lineNumber:53},{declaringClass:org.apache.cloudstack.managed.context.ManagedContextRunnable,methodName:run,fileName:ManagedContextRunnable.java,lineNumber:46},{declaringClass:java.util.concurrent.Executors$RunnableAdapter,methodName:call,fileName:Executors.java,lineNumber:471},{declaringClass:java.util.concurrent.FutureTask,methodName:run,fileName:FutureTask.java,lineNumber:262},{declaringClass:java.util.concurrent.ThreadPoolExecutor,methodName:runWorker,fileName:ThreadPoolExecutor.java,lineNumber:1145},{declaringClass:java.util.concurrent.ThreadPoolExecutor$Worker,methodName:run,fileName:ThreadPoolExecutor.java,lineNumber:615},{declaringClass:java.lang.Thread,methodName:run,fileName:Thread.java,lineNumber:744}],suppressedExceptions:[]}
 at 
 org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.fromObjectSerializedString(JobSerializerHelper.java:135)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl.unmarshallResultObject(AsyncJobManagerImpl.java:667)

[jira] [Updated] (CLOUDSTACK-5678) Cold Storage migration is failing

2014-01-01 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5678:
---

Assignee: Kelven Yang  (was: Devdeep Singh)

 Cold Storage migration is failing
 -

 Key: CLOUDSTACK-5678
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5678
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Kelven Yang
Priority: Blocker
  Labels: vmsync
 Fix For: 4.3.0


 Steps to Reproduce: 
  
 1.Bring up CS in advanced zone with 2 hosts in a hyper-v cluster using CIFS 
 for both primary and secondary storage 
 2.Deploy one or two guest vms using default cent os template. 
 3.Add one more primary storage (say primary2) to the cluster 
 4.Stop one of the vms deployed at step2 
 5.Migrate the storage from source primary to new primary storage primary2 
 Expected Result: 
 = 
 Storage migration should succeed when the vm is in stopped state 
 Actual Result: 
 === 
 013-12-30 17:21:03,163 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-6:ctx-9672ce4b) ===START===  10.144.7.20 -- GET  
 command=migrateVirtualMachinestorageid=d65ffa8c-fdd7-360a-b729-c0d9ba5df050virtualmachineid=9226ccd6-b409-4452-821f-5b33a24137a5response=jsonsessionkey=lIed4xLaMsDL4yCyAJYyUK0pAJk%3D_=1388403965445
 2013-12-30 17:21:03,194 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-6:ctx-9672ce4b ctx-5d353029) submit async job-129, details: 
 AsyncJobVO {id:129, userId: 2, accountId: 2, instanceType: None, instanceId: 
 null, cmd: org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,sessionkey:lIed4xLaMsDL4yCyAJYyUK0pAJk\u003d,virtualmachineid:9226ccd6-b409-4452-821f-5b33a24137a5,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:d65ffa8c-fdd7-360a-b729-c0d9ba5df050,httpmethod:GET,_:1388403965445,ctxAccountId:2,ctxStartEventId:274},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-30 17:21:03,194 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-6:ctx-9672ce4b ctx-5d353029) ===END===  10.144.7.20 -- GET  
 command=migrateVirtualMachinestorageid=d65ffa8c-fdd7-360a-b729-c0d9ba5df050virtualmachineid=9226ccd6-b409-4452-821f-5b33a24137a5response=jsonsessionkey=lIed4xLaMsDL4yCyAJYyUK0pAJk%3D_=1388403965445
 2013-12-30 17:21:03,196 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-48:ctx-46f6bd2b) Add job-129 into job monitoring
 2013-12-30 17:21:03,196 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-48:ctx-46f6bd2b) Executing AsyncJobVO {id:129, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,sessionkey:lIed4xLaMsDL4yCyAJYyUK0pAJk\u003d,virtualmachineid:9226ccd6-b409-4452-821f-5b33a24137a5,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:d65ffa8c-fdd7-360a-b729-c0d9ba5df050,httpmethod:GET,_:1388403965445,ctxAccountId:2,ctxStartEventId:274},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-30 17:21:03,212 DEBUG [c.c.u.d.T.Transaction] 
 (Job-Executor-48:ctx-46f6bd2b ctx-5d353029) Rolling back the transaction: 
 Time = 4 Name =  Job-Executor-48; called by 
 -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.migrateVmStorageThroughJobQueue:4475-VirtualMachineManagerImpl.storageMigration:1558-UserVmManagerImpl.vmStorageMigration:4069-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:57-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616
 2013-12-30 17:21:03,213 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-48:ctx-46f6bd2b) Unexpected exception while executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
 com.cloud.utils.exception.CloudRuntimeException: Unable to serialize: 
 com.cloud.vm.VmWorkStorageMigration@40df9e44
 at 
 org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
 at com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
 at 
 com.cloud.vm.VirtualMachineManagerImpl$9.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:4504)
 at 
 com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
 at

[jira] [Updated] (CLOUDSTACK-5675) Destory VM is failing with Unable to delete vm snapshots for VM

2014-01-01 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5675:
---

Assignee: Kelven Yang  (was: Devdeep Singh)

 Destory VM is failing with Unable to delete vm snapshots for VM 
 --

 Key: CLOUDSTACK-5675
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5675
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Kelven Yang
Priority: Blocker
  Labels: vmsync
 Fix For: 4.3.0


 Steps :
 ===
 1. Deploy a CS advanced zone setup with Hyper-V as hypervisor type
 2. Create a VM
 3. Destroy the VM
 Expected result:
 ==
 The VM should be created and destroyed successfully.
 Observed result :
 =
 Destroy VM fails with :
 2013-12-30 15:02:30,297 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-2:ctx-57d2f51b) ===START===  10.144.7.20 -- GET  
 command=destroyVirtualMachineresponse=jsonsessionkey=P7hUEU1kTW2jFEVpcBKYxFUSxx4%3Did=706fae35-94d2-414d-94da-8c7b21051eddexpunge=true_=1388396154899
 2013-12-30 15:02:30,344 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-2:ctx-57d2f51b ctx-03d0a162) submit async job-38, details: 
 AsyncJobVO {id:38, userId: 2, accountId: 2, instanceType: VirtualMachine, 
 instanceId: 6, cmd: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, 
 cmdInfo: 
 {response:json,id:706fae35-94d2-414d-94da-8c7b21051edd,sessionkey:P7hUEU1kTW2jFEVpcBKYxFUSxx4\u003d,cmdEventType:VM.DESTROY,ctxUserId:2,httpmethod:GET,_:1388396154899,ctxAccountId:2,expunge:true,ctxStartEventId:108},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-30 15:02:30,344 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-2:ctx-57d2f51b ctx-03d0a162) ===END===  10.144.7.20 -- GET  
 command=destroyVirtualMachineresponse=jsonsessionkey=P7hUEU1kTW2jFEVpcBKYxFUSxx4%3Did=706fae35-94d2-414d-94da-8c7b21051eddexpunge=true_=1388396154899
 2013-12-30 15:02:30,346 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-41:ctx-90d46ce0) Add job-38 into job monitoring
 2013-12-30 15:02:30,346 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-41:ctx-90d46ce0) Executing AsyncJobVO {id:38, userId: 2, 
 accountId: 2, instanceType: VirtualMachine, instanceId: 6, cmd: 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, cmdInfo: 
 {response:json,id:706fae35-94d2-414d-94da-8c7b21051edd,sessionkey:P7hUEU1kTW2jFEVpcBKYxFUSxx4\u003d,cmdEventType:VM.DESTROY,ctxUserId:2,httpmethod:GET,_:1388396154899,ctxAccountId:2,expunge:true,ctxStartEventId:108},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-30 15:02:30,371 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Destroying vm VM[User|av3]
 2013-12-30 15:02:30,372 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Stopped called on VM[User|av3] 
 but the state is Error
 2013-12-30 15:02:30,404 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Sync job-39 execution on object 
 VmWorkJobQueue.6
 2013-12-30 15:02:31,064 DEBUG [c.c.s.StatsCollector] 
 (StatsCollector-2:ctx-1f663345) StorageCollector is running...
 2013-12-30 15:02:31,125 DEBUG [c.c.a.t.Request] 
 (StatsCollector-2:ctx-1f663345) Seq 2-1575288891: Received:  { Ans: , MgmtId: 
 280320865129348, via: 2, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
 2013-12-30 15:02:31,127 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-15:ctx-9d56111c) Seq 1-2099445910: Executing request
 2013-12-30 15:02:31,128 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-15:ctx-9d56111c) POST request 
 tohttp://10.102.192.14:8250/api/HypervResource/com.cloud.agent.api.GetStorageStatsCommand
  with 
 contents{id:b183fb1d-c446-3a6f-b7ee-ec18507f39ae,localPath:/HYPERV-SMB/abhinav-hyperv-ps1?user\u003dabhinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR,pooltype:NetworkFilesystem,contextMap:{},wait:0}
 2013-12-30 15:02:31,128 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-15:ctx-9d56111c) Sending cmd to 
 http://10.102.192.14:8250/api/HypervResource/com.cloud.agent.api.GetStorageStatsCommand
  cmd

[jira] [Updated] (CLOUDSTACK-5676) Live migration of VM is failing with a NPE

2014-01-01 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5676:
---

Assignee: Kelven Yang  (was: Devdeep Singh)

 Live migration of VM is failing with a NPE
 --

 Key: CLOUDSTACK-5676
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5676
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Kelven Yang
Priority: Blocker
  Labels: vmsync
 Fix For: 4.3.0


 Steps to Reproduce: 
  
 1.Bring up CS in advanced zone with 2 hosts in a hyper-v cluster using CIFS 
 for both primary and secondary storage 
 2.Deploy one or two guest vms using default cent os template. 
 3.Migrate one of the VMs from Host1 to Host2
 Expected Behaviour: 
 = 
 Live VM migration should be successful
 Observed Behaviour: 
 === 
 Live VM migration fails with :
 013-12-30 16:41:29,564 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-1:ctx-2ba86ed3 ctx-ca0be041) Sync job-95 execution on object 
 VmWorkJobQueue.16
 2013-12-30 16:41:31,261 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (AsyncJobMgr-Heartbeat-1:ctx-c85fb697) Execute sync-queue item: 
 SyncQueueItemVO {id:30, queueId: 27, contentType: AsyncJob, contentId: 95, 
 lastProcessMsid: null, lastprocessNumber: null, lastProcessTime: null, 
 created: Mon Dec 30 16:41:29 IST 2013}
 2013-12-30 16:41:31,263 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (AsyncJobMgr-Heartbeat-1:ctx-c85fb697) Schedule queued job-95
 2013-12-30 16:41:31,277 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-2:ctx-ba975c56) Add job-95 into job monitoring
 2013-12-30 16:41:31,278 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-2:ctx-ba975c56) Executing AsyncJobVO {id:95, userId: 2, 
 accountId: 2, instanceType: null, instanceId: null, cmd: 
 com.cloud.vm.VmWorkMigrate, cmdInfo: 
 rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAEHQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwAEcQB-AAlwcQB-AAk,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Mon Dec 30 16:41:29 IST 2013}
 2013-12-30 16:41:31,279 DEBUG [c.c.v.VmWorkJobDispatcher] 
 (Job-Executor-2:ctx-ba975c56) Run VM work job: com.cloud.vm.VmWorkMigrate
 2013-12-30 16:41:31,287 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Job-Executor-2:ctx-ba975c56 ctx-ca0be041) Unable to complete AsyncJobVO 
 {id:95, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd: 
 com.cloud.vm.VmWorkMigrate, cmdInfo: 
 rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAEHQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwAEcQB-AAlwcQB-AAk,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Mon Dec 30 16:41:29 IST 2013}
 java.lang.NullPointerException
 at 
 com.cloud.vm.VmWorkMigrate.getDeployDestination(VmWorkMigrate.java:60)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4743)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at

[jira] [Updated] (CLOUDSTACK-5701) physical size is not getting updated in snapshot_store_ref table.

2014-01-01 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5701:
---

Priority: Critical  (was: Major)

 physical size is not getting updated in snapshot_store_ref table.
 -

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


 Physical size is not getting updated in snapshot_store_ref table. Because of 
 that, CS doesn't has any record of delta snapshots size created in XenServer.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5678) Cold Storage migration is failing

2013-12-31 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5678:
---

Labels: vmsync  (was: )

 Cold Storage migration is failing
 -

 Key: CLOUDSTACK-5678
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5678
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Blocker
  Labels: vmsync
 Fix For: 4.3.0


 Steps to Reproduce: 
  
 1.Bring up CS in advanced zone with 2 hosts in a hyper-v cluster using CIFS 
 for both primary and secondary storage 
 2.Deploy one or two guest vms using default cent os template. 
 3.Add one more primary storage (say primary2) to the cluster 
 4.Stop one of the vms deployed at step2 
 5.Migrate the storage from source primary to new primary storage primary2 
 Expected Result: 
 = 
 Storage migration should succeed when the vm is in stopped state 
 Actual Result: 
 === 
 013-12-30 17:21:03,163 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-6:ctx-9672ce4b) ===START===  10.144.7.20 -- GET  
 command=migrateVirtualMachinestorageid=d65ffa8c-fdd7-360a-b729-c0d9ba5df050virtualmachineid=9226ccd6-b409-4452-821f-5b33a24137a5response=jsonsessionkey=lIed4xLaMsDL4yCyAJYyUK0pAJk%3D_=1388403965445
 2013-12-30 17:21:03,194 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-6:ctx-9672ce4b ctx-5d353029) submit async job-129, details: 
 AsyncJobVO {id:129, userId: 2, accountId: 2, instanceType: None, instanceId: 
 null, cmd: org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,sessionkey:lIed4xLaMsDL4yCyAJYyUK0pAJk\u003d,virtualmachineid:9226ccd6-b409-4452-821f-5b33a24137a5,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:d65ffa8c-fdd7-360a-b729-c0d9ba5df050,httpmethod:GET,_:1388403965445,ctxAccountId:2,ctxStartEventId:274},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-30 17:21:03,194 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-6:ctx-9672ce4b ctx-5d353029) ===END===  10.144.7.20 -- GET  
 command=migrateVirtualMachinestorageid=d65ffa8c-fdd7-360a-b729-c0d9ba5df050virtualmachineid=9226ccd6-b409-4452-821f-5b33a24137a5response=jsonsessionkey=lIed4xLaMsDL4yCyAJYyUK0pAJk%3D_=1388403965445
 2013-12-30 17:21:03,196 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-48:ctx-46f6bd2b) Add job-129 into job monitoring
 2013-12-30 17:21:03,196 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-48:ctx-46f6bd2b) Executing AsyncJobVO {id:129, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,sessionkey:lIed4xLaMsDL4yCyAJYyUK0pAJk\u003d,virtualmachineid:9226ccd6-b409-4452-821f-5b33a24137a5,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:d65ffa8c-fdd7-360a-b729-c0d9ba5df050,httpmethod:GET,_:1388403965445,ctxAccountId:2,ctxStartEventId:274},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-30 17:21:03,212 DEBUG [c.c.u.d.T.Transaction] 
 (Job-Executor-48:ctx-46f6bd2b ctx-5d353029) Rolling back the transaction: 
 Time = 4 Name =  Job-Executor-48; called by 
 -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.migrateVmStorageThroughJobQueue:4475-VirtualMachineManagerImpl.storageMigration:1558-UserVmManagerImpl.vmStorageMigration:4069-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:57-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616
 2013-12-30 17:21:03,213 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-48:ctx-46f6bd2b) Unexpected exception while executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
 com.cloud.utils.exception.CloudRuntimeException: Unable to serialize: 
 com.cloud.vm.VmWorkStorageMigration@40df9e44
 at 
 org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
 at com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
 at 
 com.cloud.vm.VirtualMachineManagerImpl$9.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:4504)
 at 
 com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
 at

[jira] [Updated] (CLOUDSTACK-5676) Live migration of VM is failing with a NPE

2013-12-31 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5676:
---

Labels: vmsync  (was: )

 Live migration of VM is failing with a NPE
 --

 Key: CLOUDSTACK-5676
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5676
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Blocker
  Labels: vmsync
 Fix For: 4.3.0


 Steps to Reproduce: 
  
 1.Bring up CS in advanced zone with 2 hosts in a hyper-v cluster using CIFS 
 for both primary and secondary storage 
 2.Deploy one or two guest vms using default cent os template. 
 3.Migrate one of the VMs from Host1 to Host2
 Expected Behaviour: 
 = 
 Live VM migration should be successful
 Observed Behaviour: 
 === 
 Live VM migration fails with :
 013-12-30 16:41:29,564 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-1:ctx-2ba86ed3 ctx-ca0be041) Sync job-95 execution on object 
 VmWorkJobQueue.16
 2013-12-30 16:41:31,261 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (AsyncJobMgr-Heartbeat-1:ctx-c85fb697) Execute sync-queue item: 
 SyncQueueItemVO {id:30, queueId: 27, contentType: AsyncJob, contentId: 95, 
 lastProcessMsid: null, lastprocessNumber: null, lastProcessTime: null, 
 created: Mon Dec 30 16:41:29 IST 2013}
 2013-12-30 16:41:31,263 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (AsyncJobMgr-Heartbeat-1:ctx-c85fb697) Schedule queued job-95
 2013-12-30 16:41:31,277 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-2:ctx-ba975c56) Add job-95 into job monitoring
 2013-12-30 16:41:31,278 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-2:ctx-ba975c56) Executing AsyncJobVO {id:95, userId: 2, 
 accountId: 2, instanceType: null, instanceId: null, cmd: 
 com.cloud.vm.VmWorkMigrate, cmdInfo: 
 rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAEHQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwAEcQB-AAlwcQB-AAk,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Mon Dec 30 16:41:29 IST 2013}
 2013-12-30 16:41:31,279 DEBUG [c.c.v.VmWorkJobDispatcher] 
 (Job-Executor-2:ctx-ba975c56) Run VM work job: com.cloud.vm.VmWorkMigrate
 2013-12-30 16:41:31,287 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Job-Executor-2:ctx-ba975c56 ctx-ca0be041) Unable to complete AsyncJobVO 
 {id:95, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd: 
 com.cloud.vm.VmWorkMigrate, cmdInfo: 
 rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAEHQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwAEcQB-AAlwcQB-AAk,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Mon Dec 30 16:41:29 IST 2013}
 java.lang.NullPointerException
 at 
 com.cloud.vm.VmWorkMigrate.getDeployDestination(VmWorkMigrate.java:60)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4743)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at

[jira] [Updated] (CLOUDSTACK-5675) Destory VM is failing with Unable to delete vm snapshots for VM

2013-12-31 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5675:
---

Labels: vmsync  (was: )

 Destory VM is failing with Unable to delete vm snapshots for VM 
 --

 Key: CLOUDSTACK-5675
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5675
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Hyperv , 4.3
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Blocker
  Labels: vmsync
 Fix For: 4.3.0


 Steps :
 ===
 1. Deploy a CS advanced zone setup with Hyper-V as hypervisor type
 2. Create a VM
 3. Destroy the VM
 Expected result:
 ==
 The VM should be created and destroyed successfully.
 Observed result :
 =
 Destroy VM fails with :
 2013-12-30 15:02:30,297 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-2:ctx-57d2f51b) ===START===  10.144.7.20 -- GET  
 command=destroyVirtualMachineresponse=jsonsessionkey=P7hUEU1kTW2jFEVpcBKYxFUSxx4%3Did=706fae35-94d2-414d-94da-8c7b21051eddexpunge=true_=1388396154899
 2013-12-30 15:02:30,344 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-2:ctx-57d2f51b ctx-03d0a162) submit async job-38, details: 
 AsyncJobVO {id:38, userId: 2, accountId: 2, instanceType: VirtualMachine, 
 instanceId: 6, cmd: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, 
 cmdInfo: 
 {response:json,id:706fae35-94d2-414d-94da-8c7b21051edd,sessionkey:P7hUEU1kTW2jFEVpcBKYxFUSxx4\u003d,cmdEventType:VM.DESTROY,ctxUserId:2,httpmethod:GET,_:1388396154899,ctxAccountId:2,expunge:true,ctxStartEventId:108},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-30 15:02:30,344 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-2:ctx-57d2f51b ctx-03d0a162) ===END===  10.144.7.20 -- GET  
 command=destroyVirtualMachineresponse=jsonsessionkey=P7hUEU1kTW2jFEVpcBKYxFUSxx4%3Did=706fae35-94d2-414d-94da-8c7b21051eddexpunge=true_=1388396154899
 2013-12-30 15:02:30,346 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-41:ctx-90d46ce0) Add job-38 into job monitoring
 2013-12-30 15:02:30,346 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-41:ctx-90d46ce0) Executing AsyncJobVO {id:38, userId: 2, 
 accountId: 2, instanceType: VirtualMachine, instanceId: 6, cmd: 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, cmdInfo: 
 {response:json,id:706fae35-94d2-414d-94da-8c7b21051edd,sessionkey:P7hUEU1kTW2jFEVpcBKYxFUSxx4\u003d,cmdEventType:VM.DESTROY,ctxUserId:2,httpmethod:GET,_:1388396154899,ctxAccountId:2,expunge:true,ctxStartEventId:108},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-30 15:02:30,371 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Destroying vm VM[User|av3]
 2013-12-30 15:02:30,372 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Stopped called on VM[User|av3] 
 but the state is Error
 2013-12-30 15:02:30,404 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Sync job-39 execution on object 
 VmWorkJobQueue.6
 2013-12-30 15:02:31,064 DEBUG [c.c.s.StatsCollector] 
 (StatsCollector-2:ctx-1f663345) StorageCollector is running...
 2013-12-30 15:02:31,125 DEBUG [c.c.a.t.Request] 
 (StatsCollector-2:ctx-1f663345) Seq 2-1575288891: Received:  { Ans: , MgmtId: 
 280320865129348, via: 2, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
 2013-12-30 15:02:31,127 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-15:ctx-9d56111c) Seq 1-2099445910: Executing request
 2013-12-30 15:02:31,128 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-15:ctx-9d56111c) POST request 
 tohttp://10.102.192.14:8250/api/HypervResource/com.cloud.agent.api.GetStorageStatsCommand
  with 
 contents{id:b183fb1d-c446-3a6f-b7ee-ec18507f39ae,localPath:/HYPERV-SMB/abhinav-hyperv-ps1?user\u003dabhinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR,pooltype:NetworkFilesystem,contextMap:{},wait:0}
 2013-12-30 15:02:31,128 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-15:ctx-9d56111c) Sending cmd to 
 http://10.102.192.14:8250/api/HypervResource/com.cloud.agent.api.GetStorageStatsCommand
  cmd

[jira] [Updated] (CLOUDSTACK-5672) [Automation]Failed to add new nic to vm; error Unable to serialize observed

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5672:
---

Assignee: Saksham Srivastava

 [Automation]Failed to add new nic to vm;  error Unable to serialize 
 observed 
 ---

 Key: CLOUDSTACK-5672
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5672
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Network Controller
Affects Versions: 4.3.0
 Environment: KVM
 branch 4.3
Reporter: Rayees Namathponnan
Assignee: Saksham Srivastava
Priority: Blocker
 Fix For: 4.3.0


 Steps to reproduce 
 Step 1 : Create advanced zone 
 Step 2 : Depoy and vm VM-QA1
 Step 3 : Create new network 
 Step 4 : Add new nic to VM-QA1
 Result 
 Failed to add new nic to the vm, below error observed 
 nstanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd, cmdInfo: 
 {response:json,sessionkey:ZZ4QXAUZwIPe83MSDipOFbHVpwo\u003d,virtualmachineid:751ac91a-9a63-4d75-9700-70e269b539a4,cmdEventType:NIC.CREATE,ctxUserId:2,httpmethod:GET,_:1388332341748,ctxAccountId:2,networkid:ac35a773-08d1-4f55-9a57-bf0b78111698,ctxStartEventId:16101},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-29 07:49:06,291 DEBUG [c.c.u.d.T.Transaction] 
 (Job-Executor-29:ctx-f5b59752 ctx-fbfc6d7f) Rolling back the transaction: 
 Time = 91 Name =  Job-Executor-29; called by 
 -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue:4525-VirtualMachineManagerImpl.addVmToNetwork:3112-UserVmManagerImpl.addNicToVirtualMachine:1038-GeneratedMethodAccessor813.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616-AopUtils.invokeJoinpointUsingReflection:317
 2013-12-29 07:49:06,324 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-29:ctx-f5b59752) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
 com.cloud.utils.exception.CloudRuntimeException: Unable to serialize: 
 com.cloud.vm.VmWorkAddVmToNetwork@57ca10b0
 at 
 org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
 at com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
 at 
 com.cloud.vm.VirtualMachineManagerImpl$10.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:4554)
 at 
 com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
 at 
 com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
 at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
 at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue(VirtualMachineManagerImpl.java:4525)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.addVmToNetwork(VirtualMachineManagerImpl.java:3112)
 at 
 com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:1038)
 at sun.reflect.GeneratedMethodAccessor813.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy169.addNicToVirtualMachine(Unknown Source)
 at 
 org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:110)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
 at 
 com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
 at

[jira] [Updated] (CLOUDSTACK-5591) [VMWare][64-bit template]Public network is not reachable by the System Vm's.

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5591:
---

Assignee: Jayapal Reddy  (was: Sateesh Chodapuneedi)

 [VMWare][64-bit template]Public network is not reachable by the System Vm's.
 

 Key: CLOUDSTACK-5591
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5591
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.3.0
Reporter: Kiran Koneti
Assignee: Jayapal Reddy
Priority: Blocker
 Fix For: 4.3.0


 The setup details are as follows:
 1)Installed the CS setup and changed the global setting to allow the download 
 from the internal sites.
 2)Created a Advanced Zone setup with Vmware 5.5 where the system Vm's came up.
 3)Then added one more cluster for the KVm and added a KVM host.
 4)After adding the KVM ost the system Vm template for the KVM was not ready 
 and it shows as connection timed out.
 5)Then logged into the SSVM and tried to ping the public network then the 
 network was not reachable,even the default gateway was not pingable.
 6)When stopped the IP tables the gateway was pingable.
 7)When tried to check the arp of the gw using arping the gatewayIP it says 
 the eth0 is down and when eth0 is made up the ping was successful and the 
 public network was reachable.
 8)Then tried to restart the SSVM again the situation is same that the public 
 network is not reachable.
 9)If we leave the stup for longer time without making any changes the Public 
 network will be reachable and when rebooted again the network will not be 
 reached again.
 The Iptables details are as below:
 iptables -L -nv
 Chain INPUT (policy DROP 4 packets, 312 bytes)
  pkts bytes target prot opt in out source   
 destination
 0 0 ACCEPT tcp  --  eth2   *   0.0.0.0/00.0.0.0/0 
state NEW tcp dpt:443
 0 0 ACCEPT tcp  --  eth2   *   0.0.0.0/00.0.0.0/0 
state NEW tcp dpt:80
 160 ACCEPT tcp  --  eth1   *   0.0.0.0/00.0.0.0/0 
state NEW tcp dpt:3922
 0 0 ACCEPT all  --  eth0   *   0.0.0.0/00.0.0.0/0 
state RELATED,ESTABLISHED
   547 95190 ACCEPT all  --  eth1   *   0.0.0.0/00.0.0.0/0 
state RELATED,ESTABLISHED
 2   262 ACCEPT all  --  eth2   *   0.0.0.0/00.0.0.0/0 
state RELATED,ESTABLISHED
 0 0 ACCEPT all  --  eth3   *   0.0.0.0/00.0.0.0/0 
state RELATED,ESTABLISHED
10   588 ACCEPT all  --  lo *   0.0.0.0/00.0.0.0/0
 0 0 DROP   icmp --  *  *   0.0.0.0/00.0.0.0/0 
icmptype 13
 0 0 ACCEPT icmp --  *  *   0.0.0.0/00.0.0.0/0
 0 0 ACCEPT tcp  --  eth1   *   0.0.0.0/00.0.0.0/0 
state NEW tcp dpt:3922
 Chain FORWARD (policy DROP 0 packets, 0 bytes)
  pkts bytes target prot opt in out source   
 destination
 Chain OUTPUT (policy ACCEPT 493 packets, 76135 bytes)
  pkts bytes target prot opt in out source   
 destination
 0 0 ACCEPT tcp  --  *  eth10.0.0.0/0
 10.147.28.0/24   state NEW tcp
 0 0 REJECT tcp  --  *  eth10.0.0.0/00.0.0.0/0 
state NEW tcp dpt:80 reject-with icmp-port-unreachable
 0 0 REJECT tcp  --  *  eth10.0.0.0/00.0.0.0/0 
state NEW tcp dpt:443 reject-with icmp-port-unreachable
 Chain HTTP (0 references)
  pkts bytes target prot opt in out source   
 destination
 The arping request is as below:
  arping 10.147.X.X
 Interface eth0 is down



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CLOUDSTACK-5591) [VMWare][64-bit template]Public network is not reachable by the System Vm's.

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5591:


Jayapal

Can you help root cause this issue and check if iptables is blocking the 
traffic?

 [VMWare][64-bit template]Public network is not reachable by the System Vm's.
 

 Key: CLOUDSTACK-5591
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5591
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.3.0
Reporter: Kiran Koneti
Assignee: Jayapal Reddy
Priority: Blocker
 Fix For: 4.3.0


 The setup details are as follows:
 1)Installed the CS setup and changed the global setting to allow the download 
 from the internal sites.
 2)Created a Advanced Zone setup with Vmware 5.5 where the system Vm's came up.
 3)Then added one more cluster for the KVm and added a KVM host.
 4)After adding the KVM ost the system Vm template for the KVM was not ready 
 and it shows as connection timed out.
 5)Then logged into the SSVM and tried to ping the public network then the 
 network was not reachable,even the default gateway was not pingable.
 6)When stopped the IP tables the gateway was pingable.
 7)When tried to check the arp of the gw using arping the gatewayIP it says 
 the eth0 is down and when eth0 is made up the ping was successful and the 
 public network was reachable.
 8)Then tried to restart the SSVM again the situation is same that the public 
 network is not reachable.
 9)If we leave the stup for longer time without making any changes the Public 
 network will be reachable and when rebooted again the network will not be 
 reached again.
 The Iptables details are as below:
 iptables -L -nv
 Chain INPUT (policy DROP 4 packets, 312 bytes)
  pkts bytes target prot opt in out source   
 destination
 0 0 ACCEPT tcp  --  eth2   *   0.0.0.0/00.0.0.0/0 
state NEW tcp dpt:443
 0 0 ACCEPT tcp  --  eth2   *   0.0.0.0/00.0.0.0/0 
state NEW tcp dpt:80
 160 ACCEPT tcp  --  eth1   *   0.0.0.0/00.0.0.0/0 
state NEW tcp dpt:3922
 0 0 ACCEPT all  --  eth0   *   0.0.0.0/00.0.0.0/0 
state RELATED,ESTABLISHED
   547 95190 ACCEPT all  --  eth1   *   0.0.0.0/00.0.0.0/0 
state RELATED,ESTABLISHED
 2   262 ACCEPT all  --  eth2   *   0.0.0.0/00.0.0.0/0 
state RELATED,ESTABLISHED
 0 0 ACCEPT all  --  eth3   *   0.0.0.0/00.0.0.0/0 
state RELATED,ESTABLISHED
10   588 ACCEPT all  --  lo *   0.0.0.0/00.0.0.0/0
 0 0 DROP   icmp --  *  *   0.0.0.0/00.0.0.0/0 
icmptype 13
 0 0 ACCEPT icmp --  *  *   0.0.0.0/00.0.0.0/0
 0 0 ACCEPT tcp  --  eth1   *   0.0.0.0/00.0.0.0/0 
state NEW tcp dpt:3922
 Chain FORWARD (policy DROP 0 packets, 0 bytes)
  pkts bytes target prot opt in out source   
 destination
 Chain OUTPUT (policy ACCEPT 493 packets, 76135 bytes)
  pkts bytes target prot opt in out source   
 destination
 0 0 ACCEPT tcp  --  *  eth10.0.0.0/0
 10.147.28.0/24   state NEW tcp
 0 0 REJECT tcp  --  *  eth10.0.0.0/00.0.0.0/0 
state NEW tcp dpt:80 reject-with icmp-port-unreachable
 0 0 REJECT tcp  --  *  eth10.0.0.0/00.0.0.0/0 
state NEW tcp dpt:443 reject-with icmp-port-unreachable
 Chain HTTP (0 references)
  pkts bytes target prot opt in out source   
 destination
 The arping request is as below:
  arping 10.147.X.X
 Interface eth0 is down



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-4492) [object_store_ref] Attaching volume to a vm is failing after upgrade if the volume was uploaded before upgrade

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-4492:
---

Assignee: edison su

 [object_store_ref] Attaching volume to a vm is failing after upgrade if the 
 volume was uploaded before upgrade 
 ---

 Key: CLOUDSTACK-4492
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4492
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller, Volumes
Affects Versions: 4.2.1
 Environment: Build is from commit 
 :a6bf80216466ada185de7e04d3e64be4e25c11a7
 Upgrade from 3.0.6 to 4.2 
Reporter: Sanjeev N
Assignee: edison su
Priority: Critical
  Labels: ReleaseNote
 Fix For: 4.3.0

 Attachments: cloud.dmp, cloud.dmp, management-server.rar, 
 management-server.rar


 Failing to attach a volume to a vm after upgrade if it was uploaded before 
 upgrade.
 Steps to Reproduce:
 
 1.Bring up CS with VMWare cluster using 3.0.6 GA build
 2.upload volume using API:
 http://10.147.59.126:8096/client/api?command=uploadVolumeformat=OVAname=cent53-upload-BUurl=http://10.147.28.7/templates/vmware/CentOS5.3-x86_64.ovazoneid=9076c21d-d0c4-4cee-9820-2a551b65616eaccount=admindomainid=1
 3.Upgrade to 4.2
 4.Deploy one vm with root disk
 5.Try to attach the volume uploaded at step2 to vm created above
 Result:
 =
 Attaching volume failed with InvalidParameterValueException
 Observations:
 ===
 Uploaded volume has state set to UploadOp in volumes table. However 
 AttachVolumeCmd is checking for volume state to be either in Allocated, Ready 
 or in Uploaded state. So attaching is failing.
 Following is the log snippet:
 2013-08-26 01:36:30,254 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) 
 ===START===  10.146.0.131 -- GET  
 command=attachVolumeid=55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7evirtualMachineId=ce3c8eb5-05f9-445b-ab74-68751e8a982aresponse=jsonsessionkey=u8uFWRNIgqqVZ%2B%2FBLCQbaSfZMCw%3D_=1377495389690
 2013-08-26 01:36:30,405 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-4:null) submit async job-189 = [ 
 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ], details: AsyncJobVO {id:189, userId: 
 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 20, cmd: 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator: 
 null, cmdInfo: 
 {response:json,id:55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7e,sessionkey:u8uFWRNIgqqVZ+/BLCQbaSfZMCw\u003d,cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:ce3c8eb5-05f9-445b-ab74-68751e8a982a,httpmethod:GET,_:1377495389690,ctxAccountId:2,ctxStartEventId:2015},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 6615759585382, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-08-26 01:36:30,408 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) 
 ===END===  10.146.0.131 -- GET  
 command=attachVolumeid=55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7evirtualMachineId=ce3c8eb5-05f9-445b-ab74-68751e8a982aresponse=jsonsessionkey=u8uFWRNIgqqVZ%2B%2FBLCQbaSfZMCw%3D_=1377495389690
 2013-08-26 01:36:30,410 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-157:job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ]) 
 Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for 
 job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ]
 2013-08-26 01:36:30,468 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-157:job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
 com.cloud.exception.InvalidParameterValueException: Volume state must be in 
 Allocated, Ready or in Uploaded state
 at 
 com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1807)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
 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

[jira] [Commented] (CLOUDSTACK-4492) [object_store_ref] Attaching volume to a vm is failing after upgrade if the volume was uploaded before upgrade

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-4492:


Assigning it to Edison as he made commits around these issue

 [object_store_ref] Attaching volume to a vm is failing after upgrade if the 
 volume was uploaded before upgrade 
 ---

 Key: CLOUDSTACK-4492
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4492
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller, Volumes
Affects Versions: 4.2.1
 Environment: Build is from commit 
 :a6bf80216466ada185de7e04d3e64be4e25c11a7
 Upgrade from 3.0.6 to 4.2 
Reporter: Sanjeev N
Assignee: edison su
Priority: Critical
  Labels: ReleaseNote
 Fix For: 4.3.0

 Attachments: cloud.dmp, cloud.dmp, management-server.rar, 
 management-server.rar


 Failing to attach a volume to a vm after upgrade if it was uploaded before 
 upgrade.
 Steps to Reproduce:
 
 1.Bring up CS with VMWare cluster using 3.0.6 GA build
 2.upload volume using API:
 http://10.147.59.126:8096/client/api?command=uploadVolumeformat=OVAname=cent53-upload-BUurl=http://10.147.28.7/templates/vmware/CentOS5.3-x86_64.ovazoneid=9076c21d-d0c4-4cee-9820-2a551b65616eaccount=admindomainid=1
 3.Upgrade to 4.2
 4.Deploy one vm with root disk
 5.Try to attach the volume uploaded at step2 to vm created above
 Result:
 =
 Attaching volume failed with InvalidParameterValueException
 Observations:
 ===
 Uploaded volume has state set to UploadOp in volumes table. However 
 AttachVolumeCmd is checking for volume state to be either in Allocated, Ready 
 or in Uploaded state. So attaching is failing.
 Following is the log snippet:
 2013-08-26 01:36:30,254 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) 
 ===START===  10.146.0.131 -- GET  
 command=attachVolumeid=55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7evirtualMachineId=ce3c8eb5-05f9-445b-ab74-68751e8a982aresponse=jsonsessionkey=u8uFWRNIgqqVZ%2B%2FBLCQbaSfZMCw%3D_=1377495389690
 2013-08-26 01:36:30,405 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-4:null) submit async job-189 = [ 
 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ], details: AsyncJobVO {id:189, userId: 
 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 20, cmd: 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator: 
 null, cmdInfo: 
 {response:json,id:55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7e,sessionkey:u8uFWRNIgqqVZ+/BLCQbaSfZMCw\u003d,cmdEventType:VOLUME.ATTACH,ctxUserId:2,virtualMachineId:ce3c8eb5-05f9-445b-ab74-68751e8a982a,httpmethod:GET,_:1377495389690,ctxAccountId:2,ctxStartEventId:2015},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 6615759585382, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-08-26 01:36:30,408 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) 
 ===END===  10.146.0.131 -- GET  
 command=attachVolumeid=55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7evirtualMachineId=ce3c8eb5-05f9-445b-ab74-68751e8a982aresponse=jsonsessionkey=u8uFWRNIgqqVZ%2B%2FBLCQbaSfZMCw%3D_=1377495389690
 2013-08-26 01:36:30,410 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-157:job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ]) 
 Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for 
 job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ]
 2013-08-26 01:36:30,468 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-157:job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
 com.cloud.exception.InvalidParameterValueException: Volume state must be in 
 Allocated, Ready or in Uploaded state
 at 
 com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1807)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
 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

[jira] [Updated] (CLOUDSTACK-5669) [Automation] Destroy VM failed with error Unable to delete vm snapshots for VM

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5669:
---

Assignee: Kishan Kavala

 [Automation] Destroy VM failed with error Unable to delete vm snapshots for 
 VM
 

 Key: CLOUDSTACK-5669
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5669
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: KVM (rhel 6.3)
 Branch 4.3
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.3.0

 Attachments: CLOUDSTACK-5669.rar, CLOUDSTACK-5669.rar


 Steps to reproduce this issue
 Step 1 : Create advanced zone in KVM
 Step 2 : Deploy a vm
 Step 3 : Destroy the VM 
 Actual Result 
 Destroy vm failed with below error 
 2013-12-28 22:27:25,773 DEBUG [c.c.v.s.VMSnapshotManagerImpl] 
 (Job-Executor-72:ctx-7f27a041 ctx-0e39c47b) Execute Delete-All-VM-Snapshot 
 within VM work job context. vmId: 685
 2013-12-28 22:27:25,773 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-72:ctx-7f27a041 ctx-0e39c47b) Complete async job-3495, 
 jobStatus: SUCCEEDED, resultCode: 0, result: 
 rO0ABXNyABFqYXZhLmxhbmcuQm9vbGVhbs0gcoDVnPruAgABWgAFdmFsdWV4cAE
 2013-12-28 22:27:25,782 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-132:ctx-cc2e347e) Add job-3494 into job monitoring
 2013-12-28 22:27:25,782 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-132:ctx-cc2e347e) Executing AsyncJobVO {id:3494, userId: 2, 
 accountId: 2, instanceType: VirtualMachine, instanceId: 685, cmd: 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, cmdInfo: 
 {id:751ac91a-9a63-4d75-9700-70e269b539a4,response:json,sessionkey:rpAfwAtIsmOkK0hrRyHNw+XC6Dc\u003d,cmdEventType:VM.DESTROY,ctxUserId:2,httpmethod:GET,_:1388298410496,ctxAccountId:2,ctxStartEventId:13788},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null, 
 lastPolled: Sat Dec 28 22:27:23 PST 2013, created: Sat Dec 28 22:26:50 PST 
 2013}
 2013-12-28 22:27:25,785 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-72:ctx-7f27a041) Done executing 
 com.cloud.vm.snapshot.VmWorkDeleteAllVMSnapshots for job-3495
 2013-12-28 22:27:25,788 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Job-Executor-151:ctx-7f1c4523 ctx-0e39c47b) Unable to delete all snapshots 
 for VM[User|ryzvm2]
 2013-12-28 22:27:25,792 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-151:ctx-7f1c4523) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
 com.cloud.utils.exception.CloudRuntimeException: Unable to delete vm 
 snapshots for VM[User|ryzvm2]
   at 
 com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1527)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:256)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.destroy(VirtualMachineEntityImpl.java:223)
   at com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3616)
   at com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:2085)
   at sun.reflect.GeneratedMethodAccessor747.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at $Proxy169.destroyVm(Unknown Source)
   at 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:112)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
   at

[jira] [Commented] (CLOUDSTACK-5669) [Automation] Destroy VM failed with error Unable to delete vm snapshots for VM

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5669:


Kishan

Can you help look into this issue?

 [Automation] Destroy VM failed with error Unable to delete vm snapshots for 
 VM
 

 Key: CLOUDSTACK-5669
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5669
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: KVM (rhel 6.3)
 Branch 4.3
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.3.0

 Attachments: CLOUDSTACK-5669.rar, CLOUDSTACK-5669.rar


 Steps to reproduce this issue
 Step 1 : Create advanced zone in KVM
 Step 2 : Deploy a vm
 Step 3 : Destroy the VM 
 Actual Result 
 Destroy vm failed with below error 
 2013-12-28 22:27:25,773 DEBUG [c.c.v.s.VMSnapshotManagerImpl] 
 (Job-Executor-72:ctx-7f27a041 ctx-0e39c47b) Execute Delete-All-VM-Snapshot 
 within VM work job context. vmId: 685
 2013-12-28 22:27:25,773 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-72:ctx-7f27a041 ctx-0e39c47b) Complete async job-3495, 
 jobStatus: SUCCEEDED, resultCode: 0, result: 
 rO0ABXNyABFqYXZhLmxhbmcuQm9vbGVhbs0gcoDVnPruAgABWgAFdmFsdWV4cAE
 2013-12-28 22:27:25,782 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-132:ctx-cc2e347e) Add job-3494 into job monitoring
 2013-12-28 22:27:25,782 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-132:ctx-cc2e347e) Executing AsyncJobVO {id:3494, userId: 2, 
 accountId: 2, instanceType: VirtualMachine, instanceId: 685, cmd: 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, cmdInfo: 
 {id:751ac91a-9a63-4d75-9700-70e269b539a4,response:json,sessionkey:rpAfwAtIsmOkK0hrRyHNw+XC6Dc\u003d,cmdEventType:VM.DESTROY,ctxUserId:2,httpmethod:GET,_:1388298410496,ctxAccountId:2,ctxStartEventId:13788},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null, 
 lastPolled: Sat Dec 28 22:27:23 PST 2013, created: Sat Dec 28 22:26:50 PST 
 2013}
 2013-12-28 22:27:25,785 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-72:ctx-7f27a041) Done executing 
 com.cloud.vm.snapshot.VmWorkDeleteAllVMSnapshots for job-3495
 2013-12-28 22:27:25,788 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Job-Executor-151:ctx-7f1c4523 ctx-0e39c47b) Unable to delete all snapshots 
 for VM[User|ryzvm2]
 2013-12-28 22:27:25,792 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-151:ctx-7f1c4523) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
 com.cloud.utils.exception.CloudRuntimeException: Unable to delete vm 
 snapshots for VM[User|ryzvm2]
   at 
 com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1527)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:256)
   at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.destroy(VirtualMachineEntityImpl.java:223)
   at com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3616)
   at com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:2085)
   at sun.reflect.GeneratedMethodAccessor747.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at $Proxy169.destroyVm(Unknown Source)
   at 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:112)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
   at

[jira] [Updated] (CLOUDSTACK-5670) [Automation] VirtualRouter failed to stop with NullPointerException

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5670:
---

Assignee: Kishan Kavala

 [Automation] VirtualRouter failed to stop with NullPointerException
 ---

 Key: CLOUDSTACK-5670
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5670
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.3.0
 Environment: KVM
 Branch 4.3
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.3.0


 Steps to reproduce 
 Step 1 : Create Advanced zone in kvm
 Step 2 : create an account
 Step  3 : deploy a   vm
 step 4 : make sure new router and vm got deployed
 step 5 : destroy the account 
 Expected result 
 account and corresponding router should be depleted 
 actual result 
 router delete failed with NPE
 2013-12-28 22:53:34,600 DEBUG [c.c.a.t.Request] 
 (StatsCollector-2:ctx-4c64000f) Seq 7-1306657158: Received:  { Ans: , MgmtId: 
 29066118877352, via: 7, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
 2013-12-28 22:53:34,758 DEBUG [c.c.a.t.Request] (AgentManager-Handler-3:null) 
 Seq 1-1538730432: Processing:  { Ans: , MgmtId: 29066118877352, via: 1, Ver: 
 v1, Flags: 0, 
 [{com.cloud.agent.api.routing.IpAssocAnswer:{results:[10.223.122.85 - 
 success],result:true,wait:0}}] }
 2013-12-28 22:53:34,758 DEBUG [c.c.a.t.Request] 
 (Network-Scavenger-1:ctx-2a427ae4) Seq 1-1538730432: Received:  { Ans: , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 0, { IpAssocAnswer } }
 2013-12-28 22:53:34,760 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (Network-Scavenger-1:ctx-2a427ae4) Sending network shutdown to VirtualRouter
 2013-12-28 22:53:34,762 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
 (Network-Scavenger-1:ctx-2a427ae4) Stopping router VM[DomainRouter|r-171-QA]
 2013-12-28 22:53:34,762 WARN  [o.a.c.e.o.NetworkOrchestrator] 
 (Network-Scavenger-1:ctx-2a427ae4) Unable to complete shutdown of the network 
 elements due to element: VirtualRouter
 java.lang.NullPointerException
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1263)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2698)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139)
 at sun.reflect.GeneratedMethodAccessor570.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy240.stop(Unknown Source)
 at 
 com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:665)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2052)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:1965)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.reallyRun(NetworkOrchestrator.java:2305)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.runInContext(NetworkOrchestrator.java:2248)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at

[jira] [Commented] (CLOUDSTACK-5670) [Automation] VirtualRouter failed to stop with NullPointerException

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5670:


Kishan

Can you help look into this issue?

 [Automation] VirtualRouter failed to stop with NullPointerException
 ---

 Key: CLOUDSTACK-5670
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5670
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.3.0
 Environment: KVM
 Branch 4.3
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.3.0


 Steps to reproduce 
 Step 1 : Create Advanced zone in kvm
 Step 2 : create an account
 Step  3 : deploy a   vm
 step 4 : make sure new router and vm got deployed
 step 5 : destroy the account 
 Expected result 
 account and corresponding router should be depleted 
 actual result 
 router delete failed with NPE
 2013-12-28 22:53:34,600 DEBUG [c.c.a.t.Request] 
 (StatsCollector-2:ctx-4c64000f) Seq 7-1306657158: Received:  { Ans: , MgmtId: 
 29066118877352, via: 7, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
 2013-12-28 22:53:34,758 DEBUG [c.c.a.t.Request] (AgentManager-Handler-3:null) 
 Seq 1-1538730432: Processing:  { Ans: , MgmtId: 29066118877352, via: 1, Ver: 
 v1, Flags: 0, 
 [{com.cloud.agent.api.routing.IpAssocAnswer:{results:[10.223.122.85 - 
 success],result:true,wait:0}}] }
 2013-12-28 22:53:34,758 DEBUG [c.c.a.t.Request] 
 (Network-Scavenger-1:ctx-2a427ae4) Seq 1-1538730432: Received:  { Ans: , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 0, { IpAssocAnswer } }
 2013-12-28 22:53:34,760 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (Network-Scavenger-1:ctx-2a427ae4) Sending network shutdown to VirtualRouter
 2013-12-28 22:53:34,762 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
 (Network-Scavenger-1:ctx-2a427ae4) Stopping router VM[DomainRouter|r-171-QA]
 2013-12-28 22:53:34,762 WARN  [o.a.c.e.o.NetworkOrchestrator] 
 (Network-Scavenger-1:ctx-2a427ae4) Unable to complete shutdown of the network 
 elements due to element: VirtualRouter
 java.lang.NullPointerException
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1263)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2698)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:139)
 at sun.reflect.GeneratedMethodAccessor570.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy240.stop(Unknown Source)
 at 
 com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:665)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2052)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:1965)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.reallyRun(NetworkOrchestrator.java:2305)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.runInContext(NetworkOrchestrator.java:2248)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at

[jira] [Commented] (CLOUDSTACK-5647) Adding F5 device to network service provider fails with NoClassDefFoundError

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5647:


Jayapal

Can you look into this one?

 Adding F5 device to network service provider fails with NoClassDefFoundError
 

 Key: CLOUDSTACK-5647
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5647
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller, Network Devices
Affects Versions: 4.3.0
 Environment: Latest build from 4.3 with commit : 
 4b2b6544255ee7fe12b4b4732cacd08e4ee6a1b7
 Network: Advanced
Reporter: Sanjeev N
Assignee: Jayapal Reddy
Priority: Blocker
 Fix For: 4.3.0

 Attachments: management-server.rar


 [Hyper-v] Adding F5 device to network service providers fails with 
 NoClassDefFoundError
 Steps to Reproduce:
 =
 1.Bring up CS in advanced zone with Hyper-v cluster 
 2.Go to Home-Infrastructure-Zones-Adv-Physical Network 1-Network Service 
 Providers from UI
 3.Try to add F5 device
 Result:
 ==
 Adding F5 device fails with following error:
 2013-12-26 12:08:02,144 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-24:ctx-7a6a5fed) ===START===  10.146.0.134 -- POST  
 command=addF5LoadBalancerphysicalnetworkid=9dbdb202-2f29-4d93-be19-20e70c4eb085username=adminnetworkdevicetype=F5BigIpLoadBalancerurl=https%3A%2F%2F10.147.40.192%3Fpublicinterface%3D1.1%26privateinterface%3D1.2%26numretries%3D2%26lbdevicededicated%3Dfalseresponse=jsonsessionkey=wNiOWZzu7DZ8g1onQ0P8HZkTmtw%3D
 2013-12-26 12:08:02,401 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-24:ctx-7a6a5fed ctx-2d9e9f38) submit async job-59, details: 
 AsyncJobVO {id:59, userId: 2, accountId: 2, instanceType: None, instanceId: 
 null, cmd: com.cloud.api.commands.AddF5LoadBalancerCmd, cmdInfo: 
 {physicalnetworkid:9dbdb202-2f29-4d93-be19-20e70c4eb085,response:json,sessionkey:wNiOWZzu7DZ8g1onQ0P8HZkTmtw\u003d,username:admin,cmdEventType:PHYSICAL.LOADBALANCER.ADD,ctxUserId:2,networkdevicetype:F5BigIpLoadBalancer,httpmethod:POST,ctxAccountId:2,ctxStartEventId:190,password:password,url:https://10.147.40.192?publicinterface\u003d1.1\u0026privateinterface\u003d1.2\u0026numretries\u003d2\u0026lbdevicededicated\u003dfalse},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 132129494109518, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-26 12:08:02,402 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-53:ctx-f2fca977) Add job-59 into job monitoring
 2013-12-26 12:08:02,403 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-53:ctx-f2fca977) Executing AsyncJobVO {id:59, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 com.cloud.api.commands.AddF5LoadBalancerCmd, cmdInfo: 
 {physicalnetworkid:9dbdb202-2f29-4d93-be19-20e70c4eb085,response:json,sessionkey:wNiOWZzu7DZ8g1onQ0P8HZkTmtw\u003d,username:admin,cmdEventType:PHYSICAL.LOADBALANCER.ADD,ctxUserId:2,networkdevicetype:F5BigIpLoadBalancer,httpmethod:POST,ctxAccountId:2,ctxStartEventId:190,password:password,url:https://10.147.40.192?publicinterface\u003d1.1\u0026privateinterface\u003d1.2\u0026numretries\u003d2\u0026lbdevicededicated\u003dfalse},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 132129494109518, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-26 12:08:02,403 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-24:ctx-7a6a5fed ctx-2d9e9f38) ===END===  10.146.0.134 -- POST  
 command=addF5LoadBalancerphysicalnetworkid=9dbdb202-2f29-4d93-be19-20e70c4eb085username=adminnetworkdevicetype=F5BigIpLoadBalancerurl=https%3A%2F%2F10.147.40.192%3Fpublicinterface%3D1.1%26privateinterface%3D1.2%26numretries%3D2%26lbdevicededicated%3Dfalseresponse=jsonsessionkey=wNiOWZzu7DZ8g1onQ0P8HZkTmtw%3D
 2013-12-26 12:08:02,529 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-53:ctx-f2fca977) Unexpected exception while executing 
 com.cloud.api.commands.AddF5LoadBalancerCmd
 java.lang.NoClassDefFoundError: 
 org/apache/commons/discovery/tools/DiscoverSingleton
 at 
 org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:45)
 at java.security.AccessController.doPrivileged(Native Method)
 at 
 org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:41)
 at 
 org.apache.axis.components.logger.LogFactory.clinit(LogFactory.java:33)
 at 
 org.apache.axis.handlers.BasicHandler.clinit(BasicHandler.java:43)
 at org.apache.axis.client.Service.getAxisClient(Service.java:104)

[jira] [Updated] (CLOUDSTACK-5647) Adding F5 device to network service provider fails with NoClassDefFoundError

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5647:
---

Assignee: Jayapal Reddy

 Adding F5 device to network service provider fails with NoClassDefFoundError
 

 Key: CLOUDSTACK-5647
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5647
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller, Network Devices
Affects Versions: 4.3.0
 Environment: Latest build from 4.3 with commit : 
 4b2b6544255ee7fe12b4b4732cacd08e4ee6a1b7
 Network: Advanced
Reporter: Sanjeev N
Assignee: Jayapal Reddy
Priority: Blocker
 Fix For: 4.3.0

 Attachments: management-server.rar


 [Hyper-v] Adding F5 device to network service providers fails with 
 NoClassDefFoundError
 Steps to Reproduce:
 =
 1.Bring up CS in advanced zone with Hyper-v cluster 
 2.Go to Home-Infrastructure-Zones-Adv-Physical Network 1-Network Service 
 Providers from UI
 3.Try to add F5 device
 Result:
 ==
 Adding F5 device fails with following error:
 2013-12-26 12:08:02,144 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-24:ctx-7a6a5fed) ===START===  10.146.0.134 -- POST  
 command=addF5LoadBalancerphysicalnetworkid=9dbdb202-2f29-4d93-be19-20e70c4eb085username=adminnetworkdevicetype=F5BigIpLoadBalancerurl=https%3A%2F%2F10.147.40.192%3Fpublicinterface%3D1.1%26privateinterface%3D1.2%26numretries%3D2%26lbdevicededicated%3Dfalseresponse=jsonsessionkey=wNiOWZzu7DZ8g1onQ0P8HZkTmtw%3D
 2013-12-26 12:08:02,401 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-24:ctx-7a6a5fed ctx-2d9e9f38) submit async job-59, details: 
 AsyncJobVO {id:59, userId: 2, accountId: 2, instanceType: None, instanceId: 
 null, cmd: com.cloud.api.commands.AddF5LoadBalancerCmd, cmdInfo: 
 {physicalnetworkid:9dbdb202-2f29-4d93-be19-20e70c4eb085,response:json,sessionkey:wNiOWZzu7DZ8g1onQ0P8HZkTmtw\u003d,username:admin,cmdEventType:PHYSICAL.LOADBALANCER.ADD,ctxUserId:2,networkdevicetype:F5BigIpLoadBalancer,httpmethod:POST,ctxAccountId:2,ctxStartEventId:190,password:password,url:https://10.147.40.192?publicinterface\u003d1.1\u0026privateinterface\u003d1.2\u0026numretries\u003d2\u0026lbdevicededicated\u003dfalse},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 132129494109518, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-26 12:08:02,402 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (Job-Executor-53:ctx-f2fca977) Add job-59 into job monitoring
 2013-12-26 12:08:02,403 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-53:ctx-f2fca977) Executing AsyncJobVO {id:59, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 com.cloud.api.commands.AddF5LoadBalancerCmd, cmdInfo: 
 {physicalnetworkid:9dbdb202-2f29-4d93-be19-20e70c4eb085,response:json,sessionkey:wNiOWZzu7DZ8g1onQ0P8HZkTmtw\u003d,username:admin,cmdEventType:PHYSICAL.LOADBALANCER.ADD,ctxUserId:2,networkdevicetype:F5BigIpLoadBalancer,httpmethod:POST,ctxAccountId:2,ctxStartEventId:190,password:password,url:https://10.147.40.192?publicinterface\u003d1.1\u0026privateinterface\u003d1.2\u0026numretries\u003d2\u0026lbdevicededicated\u003dfalse},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 132129494109518, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-26 12:08:02,403 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-24:ctx-7a6a5fed ctx-2d9e9f38) ===END===  10.146.0.134 -- POST  
 command=addF5LoadBalancerphysicalnetworkid=9dbdb202-2f29-4d93-be19-20e70c4eb085username=adminnetworkdevicetype=F5BigIpLoadBalancerurl=https%3A%2F%2F10.147.40.192%3Fpublicinterface%3D1.1%26privateinterface%3D1.2%26numretries%3D2%26lbdevicededicated%3Dfalseresponse=jsonsessionkey=wNiOWZzu7DZ8g1onQ0P8HZkTmtw%3D
 2013-12-26 12:08:02,529 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-53:ctx-f2fca977) Unexpected exception while executing 
 com.cloud.api.commands.AddF5LoadBalancerCmd
 java.lang.NoClassDefFoundError: 
 org/apache/commons/discovery/tools/DiscoverSingleton
 at 
 org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:45)
 at java.security.AccessController.doPrivileged(Native Method)
 at 
 org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:41)
 at 
 org.apache.axis.components.logger.LogFactory.clinit(LogFactory.java:33)
 at 
 org.apache.axis.handlers.BasicHandler.clinit(BasicHandler.java:43)
 at org.apache.axis.client.Service.getAxisClient(Service.java:104)
 at org.apache.axis.client.Service.init(Service.java:113)

[jira] [Updated] (CLOUDSTACK-5657) [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs with Local System Log On

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5657:
---

Assignee: Devdeep Singh

 [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs 
 with Local System Log On
 -

 Key: CLOUDSTACK-5657
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5657
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, Hypervisor Controller
Affects Versions: 4.3.0
 Environment: latest build from 4.3
 Hypervisor: Hyperv
 Storage: SMB for both primary and secondary
Reporter: Sanjeev N
Assignee: Devdeep Singh
Priority: Critical
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.3.0


 [Hyper-v] vm live migration does not work if the Cloudstack Hyper-v Agen runs 
 with Local System Log On
 CloudStack to communicate with Hyper-v server we run CloudStack-Hyperv Agent 
 as a service in Windows2012R2 (Hyperv) Server. By default this service would 
 run with Local System Log On. However vm live migration fails with 
 authentication issues if this service runs with Local System Log on. So we 
 need to stop this service and change the Log On account to domain user and 
 start the service for the live migration to work.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5556) [Automation] Failed to re-attach the volume in KVM

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5556:
---

Assignee: edison su

 [Automation] Failed to re-attach the volume in KVM
 --

 Key: CLOUDSTACK-5556
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5556
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.3.0
 Environment: KVM (RHEL 6.3)
 Branch 4.3
Reporter: Rayees Namathponnan
Assignee: edison su
 Fix For: 4.3.0


 Steps to reproduce 
 Step 1 : Create advanced zone in KVM
 Step 2 : Deploy a VM
 Step 3 : Add new Volume 
 Step 4 : Attach the volume to vm
 Step 5 : Remove volume from the vm
 Step 6 : attach the same volume again 
 Result 
 Failed to attach the volume second time, with error Failed to attach volume: 
 vol1 to VM: RYZ1; org.libvirt.LibvirtException: internal error unable to 
 execute QEMU command '__com.redhat_drive_add': Duplicate ID 
 'drive-virtio-disk1' for drive
 Observed below error in MS log
 2013-12-18 22:20:49,276 DEBUG [c.c.a.t.Request] (Job-Executor-51:ctx-98ec33fc 
 ctx-5303d6ac) Seq 1-1588070511: Sending  { Cmd , MgmtId: 29066118877352, via: 
 1(Rack2Host11.lab.vmops.com), Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:afcc7fa1-dd56-49cb-9246-2806d20dbcc4,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049,url:NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=PrimarySTOREUUID=fff90cb5-06dd-33b3-8815-d78c08ca01d9}},name:vol1,size:5368709120,path:afcc7fa1-dd56-49cb-9246-2806d20dbcc4,volumeId:484,accountId:2,format:QCOW2,id:484,hypervisorType:KVM}},diskSeq:1,path:afcc7fa1-dd56-49cb-9246-2806d20dbcc4,type:DATADISK,_details:{managed:false,storagePort:2049,storageHost:10.223.110.232,volumeSize:5368709120}},vmName:i-2-433-QA,wait:0}}]
  }
 2013-12-18 22:20:49,568 DEBUG [c.c.a.t.Request] (AgentManager-Handler-4:null) 
 Seq 1-1588070511: Processing:  { Ans: , MgmtId: 29066118877352, via: 1, Ver: 
 v1, Flags: 10, 
 [{org.apache.cloudstack.storage.command.AttachAnswer:{result:false,details:org.libvirt.LibvirtException:
  internal error unable to execute QEMU command '__com.redhat_drive_add': 
 Duplicate ID 'drive-virtio-disk1' for drive,wait:0}}] }
 2013-12-18 22:20:49,568 DEBUG [c.c.a.t.Request] (Job-Executor-51:ctx-98ec33fc 
 ctx-5303d6ac) Seq 1-1588070511: Received:  { Ans: , MgmtId: 29066118877352, 
 via: 1, Ver: v1, Flags: 10, { AttachAnswer } }
 2013-12-18 22:20:49,568 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-51:ctx-98ec33fc) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume: 
 vol1 to VM: RYZ1; org.libvirt.LibvirtException: internal error unable to 
 execute QEMU command '__com.redhat_drive_add': Duplicate ID 
 'drive-virtio-disk1' for drive
   at 
 com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:1879)
   at 
 com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1264)
   at 
 com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1088)
   at 
 com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1063)
   at sun.reflect.GeneratedMethodAccessor610.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at $Proxy193.attachVolumeToVM(Unknown Source)
   at 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123)
   at

[jira] [Updated] (CLOUDSTACK-5329) MigrateVMCmd on stopped VM is failing with NPE when trying to migrate to zone-wide-primary storage.

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5329:
---

Assignee: edison su

 MigrateVMCmd on stopped VM is failing with NPE when trying to migrate to 
 zone-wide-primary storage.
 ---

 Key: CLOUDSTACK-5329
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5329
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.3.0
Reporter: manasaveloori
Assignee: edison su
Priority: Critical
 Fix For: 4.3.0

 Attachments: management-server.rar


 Steps:
 1.Have a CS with multiple zone wide primary storage using KVM host.
 2.Deploy a VM and stop it.
 3.Now goto  Migrate VM.Drop down lists the available primary storage to 
 migrate.
 4.Now migrate the VM to another zone wide primary storage.
 Observation:
 Observed the following NPE:
 2013-12-02 21:16:04,537 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-49:ctx-63bbd88b) Executing AsyncJobVO {id:91, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,sessionkey:bETJCcI/wg7sd2gWxD7zzG5wotQ\u003d,virtualmachineid:d22ce820-339c-4c80-a16b-dd21bd7a8804,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:b01ec063-b9c5-3685-b5ea-c816554f1ffe,httpmethod:GET,_:1385979761075,ctxAccountId:2,ctxStartEventId:293},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 6758231703598, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-02 21:16:04,562 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-49:ctx-63bbd88b) Unexpected exception while executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
 java.lang.NullPointerException
 at 
 com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:3954)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy169.vmStorageMigration(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:150)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
 at 
 com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:520)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at

[jira] [Commented] (CLOUDSTACK-5329) MigrateVMCmd on stopped VM is failing with NPE when trying to migrate to zone-wide-primary storage.

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5329:


Edison

Can you please look into this one?

 MigrateVMCmd on stopped VM is failing with NPE when trying to migrate to 
 zone-wide-primary storage.
 ---

 Key: CLOUDSTACK-5329
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5329
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.3.0
Reporter: manasaveloori
Assignee: edison su
Priority: Critical
 Fix For: 4.3.0

 Attachments: management-server.rar


 Steps:
 1.Have a CS with multiple zone wide primary storage using KVM host.
 2.Deploy a VM and stop it.
 3.Now goto  Migrate VM.Drop down lists the available primary storage to 
 migrate.
 4.Now migrate the VM to another zone wide primary storage.
 Observation:
 Observed the following NPE:
 2013-12-02 21:16:04,537 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-49:ctx-63bbd88b) Executing AsyncJobVO {id:91, userId: 2, 
 accountId: 2, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo: 
 {response:json,sessionkey:bETJCcI/wg7sd2gWxD7zzG5wotQ\u003d,virtualmachineid:d22ce820-339c-4c80-a16b-dd21bd7a8804,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:b01ec063-b9c5-3685-b5ea-c816554f1ffe,httpmethod:GET,_:1385979761075,ctxAccountId:2,ctxStartEventId:293},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 6758231703598, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-12-02 21:16:04,562 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-49:ctx-63bbd88b) Unexpected exception while executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
 java.lang.NullPointerException
 at 
 com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:3954)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy169.vmStorageMigration(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:150)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
 at 
 com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:520)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at

[jira] [Updated] (CLOUDSTACK-5660) [Hyper-v] Migrate vm live migration succeeds but throws error as Failed to migrate the system vm

2013-12-30 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5660:
---

Assignee: Devdeep Singh

 [Hyper-v] Migrate vm live migration succeeds but throws error as Failed to 
 migrate the system vm
 

 Key: CLOUDSTACK-5660
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5660
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.3.0
 Environment: Latest build from 4.3 branch with commit:
 bf7601e9b86b7ea66026ac3ac94cd145e9912864
Reporter: Sanjeev N
Assignee: Devdeep Singh
  Labels: hyper-V,, hyper-v, hyperv
 Fix For: 4.3.0


 [Hyper-v] Migrate vm live migration succeeds but throws error as Failed to 
 migrate the system vm
 Steps to Reproduce:
 
 1.Bring up CS in advanced zone with at-least two hyper-v hosts in the cluster.
 2.Deploy one guest vm with default cent os template
 3.Live Migrate any vm (system /guest ) to another host.
 Result:
 ==
 VM Migration to another host succeeds but the migrate job retuns failure as 
 follows :2013-12-27 19:19:49,143 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-15:ctx-9065306c) Complete async job-19, jobStatus: FAILED, 
 resultCode: 530, result: 
 org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
  to migrate the system vm}
 2013-12-27 19:19:49,208 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (Job-Executor-15:ctx-9065306c) Done executing 
 org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd for 
 job-19
 Does not throw any exception but throws error in UI and MS log . This might 
 confuse the user.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5422) Changing XenServer Tools Version 6.1 + doesnt work

2013-12-29 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5422:
---

Assignee: Sanjay Tripathi  (was: Anshul Gangwar)

 Changing  XenServer Tools Version 6.1 + doesnt work 
 

 Key: CLOUDSTACK-5422
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5422
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.1
 Environment: CloudStack 4.2.1
Reporter: Tomasz Zieba
Assignee: Sanjay Tripathi
Priority: Blocker
 Fix For: 4.3.0


 The situation is very similar to CLOUDSTACK-3806
 and refers to the option XenServer Tools Version 6.1 + in Instances menu.
 Checking / unchecking this option when Instance does not affect the operation 
 of the system. The problem identical to CLOUDSTACK-3806.
 The database does not change the corresponding field.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CLOUDSTACK-5422) Changing XenServer Tools Version 6.1 + doesnt work

2013-12-29 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5422:


Sanjay

Can you help with this bug?

 Changing  XenServer Tools Version 6.1 + doesnt work 
 

 Key: CLOUDSTACK-5422
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5422
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.1
 Environment: CloudStack 4.2.1
Reporter: Tomasz Zieba
Assignee: Sanjay Tripathi
Priority: Blocker
 Fix For: 4.3.0


 The situation is very similar to CLOUDSTACK-3806
 and refers to the option XenServer Tools Version 6.1 + in Instances menu.
 Checking / unchecking this option when Instance does not affect the operation 
 of the system. The problem identical to CLOUDSTACK-3806.
 The database does not change the corresponding field.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5562) management-server.log file does not get created with cloud user hence logging fails

2013-12-23 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5562:
---

Assignee: Saksham Srivastava  (was: Devdeep Singh)

 management-server.log file does not get created with cloud user hence logging 
 fails
 ---

 Key: CLOUDSTACK-5562
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5562
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Latest build from 4.3 with commit 
 197ef921f7b3c80998359f376fe045b13558633c
Reporter: Sanjeev N
Assignee: Saksham Srivastava
Priority: Critical
 Fix For: 4.3.0


 management-server.log file does not get created with cloud user hence logging 
 fails
 Steps to Reproduce;
 
 1. Install management server with latest build
 2.Create zone
 We don't see any log messages inside management server log file since it got 
 created with root user and has the file permissions as follows:
 -rw-r--r--.1 root root 16899871 Dec 19 15:05 
 /var/log/cloudstack/management/management-server.log
 After changing the permissions I could see the messages getting logged in 
 inside that file.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (CLOUDSTACK-5403) Shared network - None of PF, LB rules work after router restart, firewall rules dropped from iptables post restart

2013-12-22 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5403:
---

Assignee: Jayapal Reddy

 Shared network - None of PF, LB rules work after router restart, firewall 
 rules dropped from iptables post restart
 --

 Key: CLOUDSTACK-5403
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5403
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Network Controller
Affects Versions: 4.3.0
 Environment: Advanced zone, shared network on Hyper-V
Reporter: Sowmya Krishnan
Assignee: Jayapal Reddy
Priority: Critical
 Fix For: 4.3.0

 Attachments: iptables_after_restart.gz, iptables_before_restart.gz, 
 restart_vr.log.gz, restart_vr_agent.log.log


 None of PF, LB or firewall rules work after router is restarted in shared 
 network, advanced zone
 Steps:
 Create a shared network in advanced zone
 Acquire IP
 Create PF and corresponding Firewall rule
 Acquire another IP
 Create LB and corresponding Firewall rule
 Ensure all the rules work
 Restart router
 Check all rules
 Result:
 None of PF or LB rules work after router restart
 I've tested this only in Hypev-V so far. I'll update the bug in case I am 
 able to test in any other hypervisor as well.
 The following rules are dropped from iptables FORWARD chain after restart:
 ACCEPT tcp  --  anywhere shareduser1vm1   state 
 RELATED,ESTABLISHED /* 10.102.196.239:888:888 */
 ACCEPT tcp  --  anywhere shareduser1vm1   tcp dpt:http 
 state NEW /* 10.102.196.239:888:888 */
 So also the firewall rules corresponding to the LB rule source ip
 The rules themselves exist in DB though:
 mysql select * from firewall_rules;
 ++--+---++--++--+++---++--+-+---+---+-+--++--+
 | id | uuid | ip_address_id | start_port | 
 end_port | state  | protocol | purpose| account_id | domain_id | 
 network_id | xid  | created | 
 icmp_code | icmp_type | related | type | vpc_id | traffic_type |
 ++--+---++--++--+++---++--+-+---+---+-+--++--+
 |  1 | b9082345-8a3d-4f6d-9b64-3d2d98e65d2d | 5 |888 |
   888 | Active | tcp  | Firewall   |  4 | 2 |
 205 | 5cf27b56-4d37-4ec1-bdf8-ede0407f0115 | 2013-12-06 06:51:40 |  NULL 
 |  NULL |NULL | User |   NULL | Ingress  |
 |  2 | 5b657e22-649a-4cd4-b23c-2416243f48ba | 5 |888 |
   888 | Active | tcp  | PortForwarding |  4 | 2 |
 205 | aad0e89d-f0df-4ee2-949d-39f129a1383a | 2013-12-06 06:52:13 |  NULL 
 |  NULL |NULL | User |   NULL | NULL |
 | 13 | 42f795f9-45e6-471f-9b17-4ce631a09531 | 6 |888 |
   888 | Active | tcp  | Firewall   |  4 | 2 |
 205 | 0802945b-23b8-4b95-9441-f6b89e66d806 | 2013-12-06 11:27:08 |  NULL 
 |  NULL |NULL | User |   NULL | Ingress  |
 | 14 | 9f5aa3dd-b8e9-4193-b635-c5fd7e188f35 | 6 |888 |
   888 | Active | tcp  | LoadBalancing  |  4 | 2 |
 205 | ef7067b9-38b3-4d42-b8ee-5bfe44a817fa | 2013-12-06 11:27:53 |  NULL 
 |  NULL |NULL | User |   NULL | NULL |
 ++--+---++--++--+++---++--+-+---+---+-+--++--+
 4 rows in set (0.00 sec)
 mysql select * from load_balancing_rules;
 ++--+-++--++---+--++-+
 | id | name | description | default_port_start | default_port_end | 
 algorithm  | source_ip_address | source_ip_address_network_id | scheme | 
 lb_protocol |
 ++--+-++--++---+--++-+
 | 14

[jira] [Commented] (CLOUDSTACK-5402) Shared network - LB Rule gets created with same IP in which PF and Firewall is configured, later fails to delete properly configured LB rules

2013-12-22 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5402:


Looks similar to 5403

 Shared network - LB Rule gets created with same IP in which PF and Firewall 
 is configured, later fails to delete properly configured LB rules
 -

 Key: CLOUDSTACK-5402
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5402
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Network Controller
Affects Versions: 4.3.0
 Environment: Advanced zone, shared n/w, hyper-v
Reporter: Sowmya Krishnan
Assignee: Jayapal Reddy
Priority: Critical
 Fix For: 4.3.0

 Attachments: mslog_CS5402.log


 LB rule gets created in the same IP as PF and Firewall rule in shared network.
 Later, the same exception is thrown for any operations done on other properly 
 configured LBs. Also, it fails to delete a properly configured LB rule
 The same issue is not found in case of isolated network.
 Steps:
 
 Create a shared network, conserve mode = OFF
 Acquire a Public IP
 Configure Firewall and PF rules
 Ensure PF and firewall rules working
 Configure LB rule with same IP
 Acquire another IP
 Create LB rule
 Try to delete this LB rule
 Result
 =
 Following exception is thrown while creating LB rule:
 Exception is thrown: com.cloud.utils.exception.CloudRuntimeException: Ip 
 10.102.196.239 is used by multiple services!
 But the LB rule gets configured anyway and VM gets added to the LB rule as 
 well.
 Later whenever LB related operations are invoked, it throws the same exception
 Also, unable to delete other LB rules after this.
 Expected result:
 ===
 LB rule shouldn't get added when PF and Firewall rules are already configured 
 with that IP. 
 Logs:
 2013-12-06 12:53:18,142 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-13:ctx-8c80cb07) Unexpected exception while executing 
 org.apache.cloudstack.api.com
 mand.user.loadbalancer.DeleteLoadBalancerRuleCmd
 com.cloud.utils.exception.CloudRuntimeException: Ip 10.102.196.239 is used by 
 multiple services!
 at 
 com.cloud.network.NetworkModelImpl.getProviderToIpList(NetworkModelImpl.java:473)
 at 
 com.cloud.network.IpAddressManagerImpl.applyIpAssociations(IpAddressManagerImpl.java:952)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:2285)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerRules(LoadBalancingRulesManagerImpl.java:1774)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerConfig(LoadBalancingRulesManagerImpl.java:1694)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.deleteLoadBalancerRule(LoadBalancingRulesManagerImpl.java:1432)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.deleteLoadBalancerRule(LoadBalancingRulesManagerImpl.java:1367)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy173.deleteLoadBalancerRule(Unknown Source)
 at 
 org.apache.cloudstack.api.command.user.loadbalancer.DeleteLoadBalancerRuleCmd.execute(DeleteLoadBalancerRuleCmd.java:91)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
 at

[jira] [Updated] (CLOUDSTACK-5402) Shared network - LB Rule gets created with same IP in which PF and Firewall is configured, later fails to delete properly configured LB rules

2013-12-22 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5402:
---

Assignee: Jayapal Reddy  (was: Devdeep Singh)

 Shared network - LB Rule gets created with same IP in which PF and Firewall 
 is configured, later fails to delete properly configured LB rules
 -

 Key: CLOUDSTACK-5402
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5402
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Network Controller
Affects Versions: 4.3.0
 Environment: Advanced zone, shared n/w, hyper-v
Reporter: Sowmya Krishnan
Assignee: Jayapal Reddy
Priority: Critical
 Fix For: 4.3.0

 Attachments: mslog_CS5402.log


 LB rule gets created in the same IP as PF and Firewall rule in shared network.
 Later, the same exception is thrown for any operations done on other properly 
 configured LBs. Also, it fails to delete a properly configured LB rule
 The same issue is not found in case of isolated network.
 Steps:
 
 Create a shared network, conserve mode = OFF
 Acquire a Public IP
 Configure Firewall and PF rules
 Ensure PF and firewall rules working
 Configure LB rule with same IP
 Acquire another IP
 Create LB rule
 Try to delete this LB rule
 Result
 =
 Following exception is thrown while creating LB rule:
 Exception is thrown: com.cloud.utils.exception.CloudRuntimeException: Ip 
 10.102.196.239 is used by multiple services!
 But the LB rule gets configured anyway and VM gets added to the LB rule as 
 well.
 Later whenever LB related operations are invoked, it throws the same exception
 Also, unable to delete other LB rules after this.
 Expected result:
 ===
 LB rule shouldn't get added when PF and Firewall rules are already configured 
 with that IP. 
 Logs:
 2013-12-06 12:53:18,142 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-13:ctx-8c80cb07) Unexpected exception while executing 
 org.apache.cloudstack.api.com
 mand.user.loadbalancer.DeleteLoadBalancerRuleCmd
 com.cloud.utils.exception.CloudRuntimeException: Ip 10.102.196.239 is used by 
 multiple services!
 at 
 com.cloud.network.NetworkModelImpl.getProviderToIpList(NetworkModelImpl.java:473)
 at 
 com.cloud.network.IpAddressManagerImpl.applyIpAssociations(IpAddressManagerImpl.java:952)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:2285)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerRules(LoadBalancingRulesManagerImpl.java:1774)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerConfig(LoadBalancingRulesManagerImpl.java:1694)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.deleteLoadBalancerRule(LoadBalancingRulesManagerImpl.java:1432)
 at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.deleteLoadBalancerRule(LoadBalancingRulesManagerImpl.java:1367)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy173.deleteLoadBalancerRule(Unknown Source)
 at 
 org.apache.cloudstack.api.command.user.loadbalancer.DeleteLoadBalancerRuleCmd.execute(DeleteLoadBalancerRuleCmd.java:91)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
 at

[jira] [Updated] (CLOUDSTACK-5592) ssh should run on eth1 interface in ssvm/cpvm running in HyperV

2013-12-20 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5592:
---

Assignee: Rajesh Battala

 ssh should run on eth1 interface in ssvm/cpvm running in HyperV
 ---

 Key: CLOUDSTACK-5592
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5592
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.3.0
Reporter: Rajesh Battala
Assignee: Rajesh Battala
Priority: Critical
  Labels: hyper-V,
 Fix For: 4.3.0


 currently ssh is getting configured to run on local link ip in ssvm/console 
 proxy. 
 Admin won't be able to login to the consoles and ssvm startup will fail.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

[jira] [Updated] (CLOUDSTACK-5442) Virtual Router does not start properly on Hyper-V for DefaultSharedNetworkOffering network

2013-12-11 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5442:
---

Affects Version/s: 4.3.0

 Virtual Router does not start properly on Hyper-V for 
 DefaultSharedNetworkOffering network
 --

 Key: CLOUDSTACK-5442
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5442
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.3.0
Reporter: Donal Lafferty
Priority: Blocker

 Create DefaultSharedNetworkOffering using the following settings:
 echo listNetworkOfferings name=DefaultSharedNetworkOffering
 apiresult=`cloudmonkey api listNetworkOfferings 
 name='DefaultSharedNetworkOffering' `
 echo
 echo listNetworkOfferings returned
 echo $apiresult
 echo
 qcNetOffId=`echo $apiresult | sed -e 's/^.*id: //; s/,.*$//'`
 echo cluster is
 echo $qcNetOffId
 echo
 # provides network but no ip ranges, those are populated on a pod by pod basis
 echo createNetwork zoneid=$zone networkofferingid=$qcNetOffId 
 physicalnetworkid=$physnetid name=CorporateNet displaytext=Limited Access
 apiresult=`cloudmonkey api createNetwork zoneid=$zone 
 networkofferingid=$qcNetOffId name=CorporateNet displaytext=Limited 
 Access `
 echo
 echo createNetwork returned
 echo $apiresult
 echo
 netId=`echo $apiresult | sed -e 's/^.*id: //; s/,.*$//'`
 echo network id is
 echo $netId
 echo
 ...
 echo createVlanIpRange networkid=$netId podid=$pod gateway='10.70.176.1' 
 netmask='255.255.240.0' startip='10.70.176.124' endip='10.70.176.144' 
 forvirtualnetwork='false'
 apiresult=`cloudmonkey api createVlanIpRange networkid=$netId podid=$pod 
 gateway='10.70.176.1' netmask='255.255.240.0' startip='10.70.176.124' 
 endip='10.70.176.144' forvirtualnetwork='false' `
 echo
 echo createVlanIpRange returned
 echo $apiresult
 echo
 When virtual router starts, it returns an invalid IP address as shown in this 
 log entry:
 2013-12-10 15:33:23,964 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) executeRequest received response 
 [{com.cloud.agent.api.StartAnswer:{vm:{id:4,name:r-4-VM,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,arch:i686,os:Debian
  GNU/Linux 5.0 (32-bit),bootArgs: template\u003ddomP name\u003dr-4-VM 
 eth0ip\u003d10.70.176.127 eth0mask\u003d255.255.240.0 
 gateway\u003d10.70.176.1 domain\u003dcs1cloud.internal 
 dhcprange\u003d10.70.176.1 eth1ip\u003d0.0.0.0 eth1mask\u003d0.0.0.0 
 type\u003ddhcpsrvr disable_rp_filter\u003dtrue 
 dns1\u003d4.4.4.4,rebootOnCrash:false,enableHA:true,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:2d49f38670916c19,params:{},uuid:fea15e5a-49ae-463c-a5b7-b30d2a9aae4f,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:9244f17c-e15e-4ffe-a0c5-af2c589ba84d,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource,id:1,poolType:Filesystem,host:10.70.176.29,path:E:\\CSHV3\\VHDXs\\,port:0,url:Filesystem://10.70.176.29/E:\\CSHV3\\VHDXs\\/?ROLE\u003dPrimary\u0026STOREUUID\u003d700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource}},name:ROOT-4,size:2101252608,volumeId:4,vmName:r-4-VM,accountId:1,id:4,deviceId:0,hypervisorType:Hyperv}},diskSeq:0,type:ROOT,_details:{managed:false,storagePort:0,storageHost:10.70.176.29,volumeSize:2101252608}}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:b099ba13-6f48-4e5c-8a2f-26db548766f3,ip:10.70.176.127,netmask:255.255.240.0,gateway:10.70.176.1,mac:06:3e:a2:00:00:0d,dns1:4.4.4.4,broadcastType:Native,type:Guest,broadcastUri:vlan://untagged,isolationUri:ec2://untagged,isSecurityGroupEnabled:false},{deviceId:1,networkRateMbps:-1,defaultNic:false,uuid:817d22a5-3c0a-403b-a5da-16ffa441e2b4,ip:0.0.0.0,netmask:0.0.0.0,gateway:0.0.0.0,mac:02:00:20:bb:00:01,broadcastType:LinkLocal,type:Control,isSecurityGroupEnabled:false}]},result:true,contextMap:{},wait:0}}]
 2013-12-10 15:33:23,964 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Ping command port, 0.0.0.0:3922
 2013-12-10 15:33:23,964 INFO  [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Trying to connect to 0.0.0.0
 2013-12-10 15:33:23,965 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Ping command port succeeded for vm r-4-VM
 2013-12-10 15:33:23,965 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Execute network usage setup command on r-4-VM
 2013-12-10 15:33:24,163 ERROR [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Unable to execute NetworkUsage command on DomR 
 (0.0.0.0), domR may not be ready yet. failure due to

[jira] [Updated] (CLOUDSTACK-5442) Virtual Router does not start properly on Hyper-V for DefaultSharedNetworkOffering network

2013-12-11 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5442:
---

Assignee: Rajesh Battala

 Virtual Router does not start properly on Hyper-V for 
 DefaultSharedNetworkOffering network
 --

 Key: CLOUDSTACK-5442
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5442
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.3.0
Reporter: Donal Lafferty
Assignee: Rajesh Battala
Priority: Blocker

 Create DefaultSharedNetworkOffering using the following settings:
 echo listNetworkOfferings name=DefaultSharedNetworkOffering
 apiresult=`cloudmonkey api listNetworkOfferings 
 name='DefaultSharedNetworkOffering' `
 echo
 echo listNetworkOfferings returned
 echo $apiresult
 echo
 qcNetOffId=`echo $apiresult | sed -e 's/^.*id: //; s/,.*$//'`
 echo cluster is
 echo $qcNetOffId
 echo
 # provides network but no ip ranges, those are populated on a pod by pod basis
 echo createNetwork zoneid=$zone networkofferingid=$qcNetOffId 
 physicalnetworkid=$physnetid name=CorporateNet displaytext=Limited Access
 apiresult=`cloudmonkey api createNetwork zoneid=$zone 
 networkofferingid=$qcNetOffId name=CorporateNet displaytext=Limited 
 Access `
 echo
 echo createNetwork returned
 echo $apiresult
 echo
 netId=`echo $apiresult | sed -e 's/^.*id: //; s/,.*$//'`
 echo network id is
 echo $netId
 echo
 ...
 echo createVlanIpRange networkid=$netId podid=$pod gateway='10.70.176.1' 
 netmask='255.255.240.0' startip='10.70.176.124' endip='10.70.176.144' 
 forvirtualnetwork='false'
 apiresult=`cloudmonkey api createVlanIpRange networkid=$netId podid=$pod 
 gateway='10.70.176.1' netmask='255.255.240.0' startip='10.70.176.124' 
 endip='10.70.176.144' forvirtualnetwork='false' `
 echo
 echo createVlanIpRange returned
 echo $apiresult
 echo
 When virtual router starts, it returns an invalid IP address as shown in this 
 log entry:
 2013-12-10 15:33:23,964 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) executeRequest received response 
 [{com.cloud.agent.api.StartAnswer:{vm:{id:4,name:r-4-VM,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,arch:i686,os:Debian
  GNU/Linux 5.0 (32-bit),bootArgs: template\u003ddomP name\u003dr-4-VM 
 eth0ip\u003d10.70.176.127 eth0mask\u003d255.255.240.0 
 gateway\u003d10.70.176.1 domain\u003dcs1cloud.internal 
 dhcprange\u003d10.70.176.1 eth1ip\u003d0.0.0.0 eth1mask\u003d0.0.0.0 
 type\u003ddhcpsrvr disable_rp_filter\u003dtrue 
 dns1\u003d4.4.4.4,rebootOnCrash:false,enableHA:true,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:2d49f38670916c19,params:{},uuid:fea15e5a-49ae-463c-a5b7-b30d2a9aae4f,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:9244f17c-e15e-4ffe-a0c5-af2c589ba84d,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource,id:1,poolType:Filesystem,host:10.70.176.29,path:E:\\CSHV3\\VHDXs\\,port:0,url:Filesystem://10.70.176.29/E:\\CSHV3\\VHDXs\\/?ROLE\u003dPrimary\u0026STOREUUID\u003d700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource}},name:ROOT-4,size:2101252608,volumeId:4,vmName:r-4-VM,accountId:1,id:4,deviceId:0,hypervisorType:Hyperv}},diskSeq:0,type:ROOT,_details:{managed:false,storagePort:0,storageHost:10.70.176.29,volumeSize:2101252608}}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:b099ba13-6f48-4e5c-8a2f-26db548766f3,ip:10.70.176.127,netmask:255.255.240.0,gateway:10.70.176.1,mac:06:3e:a2:00:00:0d,dns1:4.4.4.4,broadcastType:Native,type:Guest,broadcastUri:vlan://untagged,isolationUri:ec2://untagged,isSecurityGroupEnabled:false},{deviceId:1,networkRateMbps:-1,defaultNic:false,uuid:817d22a5-3c0a-403b-a5da-16ffa441e2b4,ip:0.0.0.0,netmask:0.0.0.0,gateway:0.0.0.0,mac:02:00:20:bb:00:01,broadcastType:LinkLocal,type:Control,isSecurityGroupEnabled:false}]},result:true,contextMap:{},wait:0}}]
 2013-12-10 15:33:23,964 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Ping command port, 0.0.0.0:3922
 2013-12-10 15:33:23,964 INFO  [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Trying to connect to 0.0.0.0
 2013-12-10 15:33:23,965 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Ping command port succeeded for vm r-4-VM
 2013-12-10 15:33:23,965 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Execute network usage setup command on r-4-VM
 2013-12-10 15:33:24,163 ERROR [c.c.h.h.r.HypervDirectConnectResource] 
 (DirectAgent-34:ctx-02a1939d) Unable to execute NetworkUsage command on DomR 
 (0.0.0.0), domR may

[jira] [Updated] (CLOUDSTACK-1527) Non-fatal POSTIN scriptlet failure in rpm package cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64

2013-12-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-1527:
---

Assignee: (was: Pradeep Soundararajan)

 Non-fatal POSTIN scriptlet failure in rpm package 
 cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
 -

 Key: CLOUDSTACK-1527
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1527
 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: venkata swamybabu budumuru
 Fix For: 4.3.0


 Steps to reproduce :
 (1) copy the latest MASTER build and try to install 
 wget 
 http:///releases/ASF/rhel/6.3/master/CloudStack-non-OSS-MASTER-101-rhel6.3.tar.gz
 Observations:
  Here is the snippet of the installation messages
 ./install.sh (option M)
 Running rpm_check_debug
 Running Transaction Test
 Transaction Test Succeeded
 Running Transaction
   Installing : cloudstack-common-4.2.0-SNAPSHOT.el6.x86_64
   
  
 1/2 
   Installing : cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
   
  
 2/2 
 Non-fatal POSTIN scriptlet failure in rpm package 
 cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
 Please download vhd-util from 
 http://download.cloud.com.s3.amazonaws.com/tools/vhd-util and put it in
 /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/
 warning: %post(cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64) scriptlet 
 failed, exit status 1
   Verifying  : cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
   
  
 1/2 
   Verifying  : cloudstack-common-4.2.0-SNAPSHOT.el6.x86_64
   
  
 2/2 
 Installed:
   cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el6   
   
   

 Dependency Installed:
   cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el6   
   
   

 Complete!
 Done



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-458) xen:snapshots:Storage gc fail to clean the failed snapshot images from secondarystorage

2013-12-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-458:
---

Assignee no longer active on CloudStack

 xen:snapshots:Storage gc fail to clean the failed snapshot images from 
 secondarystorage
 ---

 Key: CLOUDSTACK-458
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-458
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Snapshot
Affects Versions: 4.0.0
Reporter: deepti dohare
Priority: Minor
 Fix For: 4.3.0


 After storage cleanup still see the snapshot image oin the secondary storage 
 snapshot folder for the failure snapshots 
 In this case : next hourly snapshot was successful but previous snapshot was 
 stuck in backingupstate 
 Steps: 
 *** 
 1.Deploy a VM and set concurrent.snapshots.threshold.per host to 2 
 2.Once its successful,schedule the recurring snapshots hourly on the root 
 volume and also perform snapshot on other instance volumes 
 3.configure the storage.cleanup.interval to 150 and restart the 
 cloud-management service while hourly snapshot on root volume is in progress 
 4.check the secondary storage snapshot folder 
 5. after few hours,delete all the created snapshots from Cloudstack and check 
 the storage cleanup thread cleansup all the snapshots form the snapshot 
 folder or not. 
 Actual result: 
 step4:snapshots job failed and secondary storage has copied image file and 
 database shows snapshot job status as Backing UP 
 next hourly snapshot was successful. 
 Step5: 
 It cleans all the successful hourly snapshot images except the failed 
 snapshot image files 
 Expected result: 
 ** 
 Storage GC should clean all image files exists in the snapshot folder when we 
 delete the all the snapshots from Cloud stack. 
 also when previous hourly snapshot stuck in backing up state ,the next hourly 
 snapshot is successful,Cloudstack should intelligent enough to update the 
 status of failure jobs properly. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-458) xen:snapshots:Storage gc fail to clean the failed snapshot images from secondarystorage

2013-12-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-458:
--

Assignee: (was: deepti dohare)

 xen:snapshots:Storage gc fail to clean the failed snapshot images from 
 secondarystorage
 ---

 Key: CLOUDSTACK-458
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-458
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Snapshot
Affects Versions: 4.0.0
Reporter: deepti dohare
Priority: Minor
 Fix For: 4.3.0


 After storage cleanup still see the snapshot image oin the secondary storage 
 snapshot folder for the failure snapshots 
 In this case : next hourly snapshot was successful but previous snapshot was 
 stuck in backingupstate 
 Steps: 
 *** 
 1.Deploy a VM and set concurrent.snapshots.threshold.per host to 2 
 2.Once its successful,schedule the recurring snapshots hourly on the root 
 volume and also perform snapshot on other instance volumes 
 3.configure the storage.cleanup.interval to 150 and restart the 
 cloud-management service while hourly snapshot on root volume is in progress 
 4.check the secondary storage snapshot folder 
 5. after few hours,delete all the created snapshots from Cloudstack and check 
 the storage cleanup thread cleansup all the snapshots form the snapshot 
 folder or not. 
 Actual result: 
 step4:snapshots job failed and secondary storage has copied image file and 
 database shows snapshot job status as Backing UP 
 next hourly snapshot was successful. 
 Step5: 
 It cleans all the successful hourly snapshot images except the failed 
 snapshot image files 
 Expected result: 
 ** 
 Storage GC should clean all image files exists in the snapshot folder when we 
 delete the all the snapshots from Cloud stack. 
 also when previous hourly snapshot stuck in backing up state ,the next hourly 
 snapshot is successful,Cloudstack should intelligent enough to update the 
 status of failure jobs properly. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-1527) Non-fatal POSTIN scriptlet failure in rpm package cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64

2013-12-02 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-1527:


Assignee no longer active on CloudStack

 Non-fatal POSTIN scriptlet failure in rpm package 
 cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
 -

 Key: CLOUDSTACK-1527
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1527
 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: venkata swamybabu budumuru
 Fix For: 4.3.0


 Steps to reproduce :
 (1) copy the latest MASTER build and try to install 
 wget 
 http:///releases/ASF/rhel/6.3/master/CloudStack-non-OSS-MASTER-101-rhel6.3.tar.gz
 Observations:
  Here is the snippet of the installation messages
 ./install.sh (option M)
 Running rpm_check_debug
 Running Transaction Test
 Transaction Test Succeeded
 Running Transaction
   Installing : cloudstack-common-4.2.0-SNAPSHOT.el6.x86_64
   
  
 1/2 
   Installing : cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
   
  
 2/2 
 Non-fatal POSTIN scriptlet failure in rpm package 
 cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
 Please download vhd-util from 
 http://download.cloud.com.s3.amazonaws.com/tools/vhd-util and put it in
 /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/
 warning: %post(cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64) scriptlet 
 failed, exit status 1
   Verifying  : cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
   
  
 1/2 
   Verifying  : cloudstack-common-4.2.0-SNAPSHOT.el6.x86_64
   
  
 2/2 
 Installed:
   cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el6   
   
   

 Dependency Installed:
   cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el6   
   
   

 Complete!
 Done



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-3449) Configuration of Hyper-V System VMs Missing

2013-11-20 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-3449:
---

Affects Version/s: (was: Future)
   4.3.0

 Configuration of Hyper-V System VMs Missing
 ---

 Key: CLOUDSTACK-3449
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3449
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.3.0
 Environment: Hyper-V hypervisors
Reporter: Donal Lafferty
Assignee: Rajesh Battala
  Labels: bootargs, hyper-V,, systemvm,
 Fix For: 4.3.0


 Background:
 System VMs are passed their configuration details in the 'bootArgs' field of 
 the StartCommand used to create and start them.  For instance, with 
 XenServer, the vm.set_PV_args command is used.
 When the SystemVM is launched, the cloud-early-config script reads this 
 information and sets up the system VM accordingly.
 Problem:
 The current SystemVM does not process its configuration when running on a 
 Hyper-V hypervisor.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-3449) Configuration of Hyper-V System VMs Missing

2013-11-20 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-3449:
---

Fix Version/s: 4.3.0

 Configuration of Hyper-V System VMs Missing
 ---

 Key: CLOUDSTACK-3449
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3449
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.3.0
 Environment: Hyper-V hypervisors
Reporter: Donal Lafferty
Assignee: Rajesh Battala
  Labels: bootargs, hyper-V,, systemvm,
 Fix For: 4.3.0


 Background:
 System VMs are passed their configuration details in the 'bootArgs' field of 
 the StartCommand used to create and start them.  For instance, with 
 XenServer, the vm.set_PV_args command is used.
 When the SystemVM is launched, the cloud-early-config script reads this 
 information and sets up the system VM accordingly.
 Problem:
 The current SystemVM does not process its configuration when running on a 
 Hyper-V hypervisor.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-5069) Make VMware vCenter session timeout value configurable.

2013-11-07 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5069:
---

Priority: Critical  (was: Major)

 Make VMware vCenter session timeout value configurable.
 ---

 Key: CLOUDSTACK-5069
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5069
 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: Likitha Shetty
Priority: Critical
 Fix For: 4.3.0


 We see socket timeout errors in a VMware setup if a VMware task 
 (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes.
 Add a global config 'vmware.vcenter.session.timeout' to make the vCenter 
 session timeout value configurable.
 Note that VMware tasks like CloneVM_Task take longer if we use the default 
 full-clone mode and a slow storage.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-5069) Make VMware vCenter session timeout value configurable.

2013-11-07 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5069:


It is critical to make the session timeout configurable. so bumping up the 
severity.

 Make VMware vCenter session timeout value configurable.
 ---

 Key: CLOUDSTACK-5069
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5069
 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: Likitha Shetty
 Fix For: 4.3.0


 We see socket timeout errors in a VMware setup if a VMware task 
 (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes.
 Add a global config 'vmware.vcenter.session.timeout' to make the vCenter 
 session timeout value configurable.
 Note that VMware tasks like CloneVM_Task take longer if we use the default 
 full-clone mode and a slow storage.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-5069) Make VMware vCenter session timeout value configurable.

2013-11-07 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5069:
---

Assignee: Likitha Shetty

 Make VMware vCenter session timeout value configurable.
 ---

 Key: CLOUDSTACK-5069
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5069
 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: Likitha Shetty
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.3.0


 We see socket timeout errors in a VMware setup if a VMware task 
 (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes.
 Add a global config 'vmware.vcenter.session.timeout' to make the vCenter 
 session timeout value configurable.
 Note that VMware tasks like CloneVM_Task take longer if we use the default 
 full-clone mode and a slow storage.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-5089) updateResourceCount: updates resource count incorrectly for VPC

2013-11-07 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5089:


Alena

is this fixed in 4.2? Then fixVersion needs to be corrected to point to 4.2

 updateResourceCount: updates resource count incorrectly for VPC
 ---

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


 Steps to reproduce:
 1) Have 2 accounts in the system. Account1 owns 1 VPC, Account 2 doesnt own 
 any vpcs.
 2) Execute updateResourceCount for an account2. 
 Bug: resourceCount for VPC is reset to the total number of VPCs in the 
 system, although account doesn't own it. There is some bug in VPC dao that 
 leads to that.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4593) [VMWARE] [Upgrade]Livestorage Migration VM Snapshot features are not fully functional after upgrade

2013-11-06 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-4593:
---

Fix Version/s: 4.3.0

  [VMWARE] [Upgrade]Livestorage Migration  VM Snapshot features are not fully 
 functional after upgrade
 --

 Key: CLOUDSTACK-4593
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4593
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller, Upgrade, VMware
Affects Versions: 4.2.1
Reporter: Sailaja Mada
 Fix For: 4.3.0

 Attachments: apilogs.rar, clouddbback.dmp, mgmtlogs.rar


 Steps:
 Upgraded setup :
 307 Setup with 2 clusters ( Cluster1 – 2 ESXi 5.0 hosts , Cluster2 – Esxi 4.1 
 host) 
 1.11 Vm’s deployed with 2 VM’s in stopped state 
 2.VM’s with ROOT volume, 2 DATA volumes, 3 DATA volumes 
 3.Snapshots , Template / volumes from this snapshot 
 4.Detached volumes 
 5.Empty volumes which are not attached to any instance 
 6.Cluster with 2 primary storage's 
 Upgraded to 4.2  
 I got into below failures with VM Snapshot if tried without Stop/Start of the 
 VM Post upgrade :
 2013-09-02 21:35:36,733 WARN  [vmware.resource.VmwareResource] 
 (DirectAgent-320:10.102.192.23) StartCommand failed due to Exception: 
 java.lang.RuntimeException
 Message: File unspecified filename was not found
 java.lang.RuntimeException: File unspecified filename was not found
 at 
 com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
 at 
 com.cloud.hypervisor.vmware.mo.VirtualMachineMO.powerOn(VirtualMachineMO.java:188)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2966)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:519)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-09-02 21:35:36,742 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-320:null) Seq 6-949618439: Response Received:
 2013-09-02 21:35:43,972 INFO  [storage.volume.VolumeServiceImpl] 
 (Job-Executor-75:job-151 = [ 3e8e2327-7c56-45ea-a653-ee5b89d75d57 ]) Volume 
 52 is not referred anywhere, remove it from volumes table
 2013-09-02 21:35:43,981 ERROR [cloud.storage.VolumeManagerImpl] 
 (Job-Executor-75:job-151 = [ 3e8e2327-7c56-45ea-a653-ee5b89d75d57 ]) migrate 
 volume failed:copy volume from primary to secondary failed due to exception: 
 Exception: java.lang.Exception
 Message: Unable to find related disk device for volume. volume path: 
 ROOT-14-30-04
 2013-09-02 21:35:43,990 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-75:job-151 = [ 3e8e2327-7c56-45ea-a653-ee5b89d75d57 ]) Unable 
 to contact resource.
 com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203] 
 is unreachable: migrate volume failed: copy volume from primary to secondary 
 failed due to exception: Exception: java.lang.Exception
 Message: Unable to find related disk device for volume. volume path: 
 ROOT-14-30-04
 at 
 com.cloud.storage.VolumeManagerImpl.migrateVolume(VolumeManagerImpl.java:2254)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2590)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
 at

[jira] [Commented] (CLOUDSTACK-5041) [upgrade]VM deployment using the template registered before upgrade is failing with java.net.SocketTimeoutException

2013-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh commented on CLOUDSTACK-5041:


Does it work for templates registered post upgrade? Exception trace above looks 
like a  connectivity issue and generic in nature.

 [upgrade]VM deployment using the template registered before upgrade is 
 failing with java.net.SocketTimeoutException
 ---

 Key: CLOUDSTACK-5041
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5041
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Upgrade, VMware
Affects Versions: 4.2.1
 Environment: upgrade from 4.2 to 4.2.1 using VMware HV
Reporter: manasaveloori
Priority: Blocker
 Fix For: 4.2.1

 Attachments: management-server.log


 1. Have CS 4.2 with VMware HV.
 2. register a template centos.
 3. upgrade to 4.2.1
 4. Deploy a VM using the template registered before upgrade.
 Observation:
 Observed the following exception:
  ERROR [storage.resource.VmwareStorageProcessor] 
 (DirectAgent-95:10.147.40.28) clone volume from base image failed due to 
 Exception: javax.xml.ws.WebServiceException
 Message: java.net.SocketTimeoutException: Read timed out
 javax.xml.ws.WebServiceException: java.net.SocketTimeoutException: Read timed 
 out
 at 
 com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:196)
 at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:212)
 at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:203)
 at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:122)
 at 
 com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:95)
 at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:626)
 at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:585)
 at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:570)
 at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:467)
 at com.sun.xml.internal.ws.client.Stub.process(Stub.java:308)
 at 
 com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:146)
 at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
 at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
 at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:129)
 at $Proxy90.waitForUpdates(Unknown Source)
 at 
 com.cloud.hypervisor.vmware.util.VmwareClient.waitForValues(VmwareClient.java:462)
 at 
 com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:404)
 at 
 com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createFullClone(VirtualMachineMO.java:602)
 at 
 com.cloud.storage.resource.VmwareStorageProcessor.createVMFullClone(VmwareStorageProcessor.java:296)
 at 
 com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:382)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:73)
 at 
 com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:155)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:559)
 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)
 Caused by: java.net.SocketTimeoutException: Read timed

[jira] [Updated] (CLOUDSTACK-5051) [Automation] vmware - Copy template to primary storage failed with NPE, and vm deployment failed

2013-11-05 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5051:
---

Assignee: Likitha Shetty

 [Automation] vmware - Copy template to  primary storage failed with NPE, and 
 vm deployment failed 
 --

 Key: CLOUDSTACK-5051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Template, VMware
Affects Versions: 4.3.0
 Environment: vmware 5.0
 build : master 4.3.0
Reporter: Rayees Namathponnan
Assignee: Likitha Shetty
 Fix For: 4.3.0

 Attachments: CLOUDSTACK-5051.rar


 steps to reproduce 
 create build from master branch, create advance zone, then deploy VM
 Actual result
 During router deployment, failed to copy template from primary storage and 
 router deployment failed
 observed below NPE in ms log
 2013-11-05 17:55:32,867 DEBUG [c.c.a.t.Request] 
 (AgentManager-Handler-14:null) Seq 5-1852899341: Processing:  { Ans: , 
 MgmtId: 90928106758026, via: 5, Ver: v1, Flag
 s: 10, 
 [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:Unable
  to copy template to primary storage due to exception:Exception: jav
 a.lang.NullPointerException\nMessage: null\n,wait:0}}] }
 2013-11-05 17:55:32,867 DEBUG [c.c.a.t.Request] (Job-Executor-2:ctx-7de85510 
 ctx-e51fa7a1) Seq 5-1852899341: Received:  { Ans: , MgmtId: 90928106758026, 
 via: 5, Ver
 : v1, Flags: 10, { CopyCmdAnswer } }
 2013-11-05 17:55:32,878 INFO  [o.a.c.s.v.VolumeServiceImpl] 
 (Job-Executor-2:ctx-7de85510 ctx-e51fa7a1) releasing lock for 
 VMTemplateStoragePool 4
 2013-11-05 17:55:32,878 WARN  [c.c.u.d.Merovingian2] 
 (Job-Executor-2:ctx-7de85510 ctx-e51fa7a1) Was unable to find lock for the 
 key template_spool_ref4 and thread i
 d 2009240553
 2013-11-05 17:55:32,879 DEBUG [o.a.c.e.o.VolumeOrchestrator] 
 (Job-Executor-2:ctx-7de85510 ctx-e51fa7a1) Unable to create 
 Vol[5|vm=6|ROOT]:Unable to copy template to
  primary storage due to exception:Exception: java.lang.NullPointerException
 Message: null
 2013-11-05 17:55:32,879 INFO  [c.c.v.VirtualMachineManagerImpl] 
 (Job-Executor-2:ctx-7de85510 ctx-e51fa7a1) Unable to contact resource.
 com.cloud.exception.StorageUnavailableException: Resource [StoragePool:2] is 
 unreachable: Unable to create Vol[5|vm=6|ROOT]:Unable to copy template to 
 primary stora
 ge due to exception:Exception: java.lang.NullPointerException
 Message: null
 at 
 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1069)
 at 
 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:828)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:510)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3409)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2990)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2976)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 :



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-5016) Failed to reboot the VM which has VM Snapshots and Migrated Volumes

2013-11-04 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5016:
---

Assignee: Likitha Shetty

 Failed to reboot the VM which has VM Snapshots and Migrated Volumes
 ---

 Key: CLOUDSTACK-5016
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5016
 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.1
Reporter: Sailaja Mada
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.2.1

 Attachments: logsall.rar, startvm.png


 Steps:
 1. Configure Adv Zone with 2 zone wide primary storages using VMWARE 5.0 
 update2 Hypervisor
 2. Deploy VM using user account
 3. Create 2 VMsnapshots wo memory and 1 VM snapshot with Memory
 4.  Revert to VM Snap2 then to VM Snap1 
 5. Stop the VM and Migrate the Volume to second Primary Storage 
 7. Start the VM - It got started. 
 8. Tried to reboot the VM. 
 Observation: 
 It failed to start the VM .
 2013-10-31 20:17:28,495 WARN  [storage.resource.VmwareStorageLayoutHelper] 
 (DirectAgent-289:10.102.192.18) Unable to locate VMDK file: 
 a933eb3fa28a473ab5e28b99f5f2607e-delta.vmdk
 2013-10-31 20:17:28,496 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-289:null) Seq 9-894174187: Response Received:
 2013-10-31 20:17:28,497 DEBUG [agent.transport.Request] 
 (DirectAgent-289:null) Seq 9-894174187: Processing:  { Ans: , MgmtId: 
 94838926819810, via: 9, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.Answer:{result:true,details:Success,wait:0}}] 
 }
 2013-10-31 20:17:28,497 DEBUG [agent.transport.Request] 
 (Job-Executor-5:job-143 = [ 57e484cb-c0aa-47c8-b991-1aa7aed9b038 ]) Seq 
 9-894174187: Received:  { Ans: , MgmtId: 94838926819810, via: 9, Ver: v1, 
 Flags: 10, { Answer } }
 2013-10-31 20:17:28,507 INFO  [storage.volume.VolumeServiceImpl] 
 (Job-Executor-5:job-143 = [ 57e484cb-c0aa-47c8-b991-1aa7aed9b038 ]) Volume 39 
 is not referred anywhere, remove it from volumes table
 2013-10-31 20:17:28,513 ERROR [cloud.storage.VolumeManagerImpl] 
 (Job-Executor-5:job-143 = [ 57e484cb-c0aa-47c8-b991-1aa7aed9b038 ]) migrate 
 volume failed:copy volume from primary to secondary failed due to exception: 
 Exception: java.lang.RuntimeException
 Message: File [7f18caf5397a340a934ed37c558aee2b] i-5-24-VM/i-5-24-VM.vmx was 
 not found
 2013-10-31 20:17:28,519 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-5:job-143 = [ 57e484cb-c0aa-47c8-b991-1aa7aed9b038 ]) Unable to 
 contact resource.
 com.cloud.exception.StorageUnavailableException: Resource [StoragePool:5] is 
 unreachable: migrate volume failed: copy volume from primary to secondary 
 failed due to exception: Exception: java.lang.RuntimeException
 Message: File [7f18caf5397a340a934ed37c558aee2b] i-5-24-VM/i-5-24-VM.vmx was 
 not found
 2013-10-31 20:17:28,519 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-5:job-143 = [ 57e484cb-c0aa-47c8-b991-1aa7aed9b038 ]) Unable to 
 contact resource.
 com.cloud.exception.StorageUnavailableException: Resource [StoragePool:5] is 
 unreachable: migrate volume failed: copy volume from primary to secondary 
 failed due to exception: Exception: java.lang.RuntimeException
 Message: File [7f18caf5397a340a934ed37c558aee2b] i-5-24-VM/i-5-24-VM.vmx was 
 not found
 at 
 com.cloud.storage.VolumeManagerImpl.migrateVolume(VolumeManagerImpl.java:2278)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2629)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:570)
 at 
 com.cloud.vm.UserVmManagerImpl.restoreVMInternal(UserVmManagerImpl.java:4930)
 at 
 com.cloud.vm.UserVmManagerImpl.rebootVirtualMachine(UserVmManagerImpl.java:1971)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.vm.RebootVMCmd.execute(RebootVMCmd.java:99)
 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)

[jira] [Updated] (CLOUDSTACK-5027) [VMWARE] Failed to Deploy instance when primary storage of a different zone are in maintenance mode

2013-11-04 Thread Ram Ganesh (JIRA)


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

Ram Ganesh updated CLOUDSTACK-5027:
---

Assignee: Sateesh Chodapuneedi

 [VMWARE] Failed to Deploy instance when primary storage of a different zone 
 are in maintenance mode
 ---

 Key: CLOUDSTACK-5027
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5027
 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.1
Reporter: Sailaja Mada
Assignee: Sateesh Chodapuneedi
Priority: Critical
 Fix For: 4.2.1

 Attachments: failureloigs.rar


 Steps:
 1. Configure 2 vMWARE zones each with Zone wide primary storages
 2.  Moved Zone 1 primary storages into maintenance mode
 3. Tried to deploy VM on second VMWARE zone which has Primary storage up 
 state.
 Observation:
 [VMWARE] Failed to Deploy instance when primary storage of a different zone 
 are in maintenance mode
 2013-11-03 10:21:07,088 DEBUG [cloud.storage.VolumeManagerImpl] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) Checking 
 if we need to prepare 1 volumes for VM[DomainRouter|r-30-VM]
 2013-11-03 10:21:07,099 DEBUG [storage.image.TemplateDataFactoryImpl] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) template 
 8 is already in store:1, type:Image
 2013-11-03 10:21:07,104 DEBUG [storage.datastore.PrimaryDataStoreImpl] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) Not 
 found (templateId:8poolId:6) in template_spool_ref, persisting it
 2013-11-03 10:21:07,121 DEBUG [storage.image.TemplateDataFactoryImpl] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) template 
 8 is already in store:6, type:Primary
 2013-11-03 10:21:07,123 DEBUG [storage.volume.VolumeServiceImpl] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) Found 
 template routing-8 in storage pool 6 with VMTemplateStoragePool id: 28
 2013-11-03 10:21:07,187 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-3:null) SeqA 10-30340: Processing Seq 10-30340:  { Cmd 
 , MgmtId: -1, via: 10, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:17,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2013-11-03 10:21:07,331 DEBUG [storage.volume.VolumeServiceImpl] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) Acquire 
 lock on VMTemplateStoragePool 28 with timeout 3600 seconds
 2013-11-03 10:21:07,333 INFO  [storage.volume.VolumeServiceImpl] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) lock is 
 acquired for VMTemplateStoragePool 28
 2013-11-03 10:21:07,341 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-3:null) SeqA 10-30340: Sending Seq 10-30340:  { Ans: , 
 MgmtId: 94838926819810, via: 10, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2013-11-03 10:21:07,373 DEBUG [storage.motion.AncientDataMotionStrategy] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) 
 copyAsync inspecting src type TEMPLATE copyAsync inspecting dest type TEMPLATE
 2013-11-03 10:21:07,387 DEBUG [storage.motion.AncientDataMotionStrategy] 
 (Job-Executor-17:job-155 = [ d4cadcb1-7e06-4ee2-9d08-0585964fc934 ]) copy 
 object failed:
 java.lang.NullPointerException
 at 
 org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyObject(AncientDataMotionStrategy.java:210)
 at 
 org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:411)
 at 
 org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:58)
 at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:446)
 at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:575)
 at 
 com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2567)
 at 
 com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2631)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2764)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1896)
 at

1 2 3 >

1 - 100 of 213 matches

Mail list logo