date:20130716


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

Sailaja Mada updated CLOUDSTACK-3544:
-

Attachment: Xen61hosttags.png

 Xen 6.2 hosts are tagged with Xen 6.1 
 --

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


 Steps:
 1. Add Xenserver 6.2 to Cloudstack 
 Observation:
 Xen 6.2 hosts are tagged with Xen 6.1 .  In a way it is added as 6.1 host and 
 not 6.2 host. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3544) Xen 6.2 hosts are tagged with Xen 6.1

Sailaja Mada created CLOUDSTACK-3544:


 Summary: Xen 6.2 hosts are tagged with Xen 6.1 
 Key: CLOUDSTACK-3544
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3544
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: XenServer
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Critical
 Attachments: Xen61hosttags.png

Steps:

1. Add Xenserver 6.2 to Cloudstack 

Observation:
Xen 6.2 hosts are tagged with Xen 6.1 .  In a way it is added as 6.1 host and 
not 6.2 host. 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3544) Xen 6.2 hosts are tagged with Xen 6.1


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

Sailaja Mada updated CLOUDSTACK-3544:
-

Fix Version/s: 4.2.0

 Xen 6.2 hosts are tagged with Xen 6.1 
 --

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

 Attachments: Xen61hosttags.png


 Steps:
 1. Add Xenserver 6.2 to Cloudstack 
 Observation:
 Xen 6.2 hosts are tagged with Xen 6.1 .  In a way it is added as 6.1 host and 
 not 6.2 host. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-3544) Xen 6.2 hosts are tagged with Xen 6.1

2013-07-16 Thread ASF subversion and git services (JIRA)


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

Devdeep Singh reassigned CLOUDSTACK-3544:
-

Assignee: Devdeep Singh

 Xen 6.2 hosts are tagged with Xen 6.1 
 --

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

 Attachments: Xen61hosttags.png


 Steps:
 1. Add Xenserver 6.2 to Cloudstack 
 Observation:
 Xen 6.2 hosts are tagged with Xen 6.1 .  In a way it is added as 6.1 host and 
 not 6.2 host. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2119) Doc : Adding NICs to guest VMs on VMWare get IPs to the new nics if vm-tools are installed


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

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

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

CLOUDSTACK-2119


 Doc : Adding NICs to guest VMs on VMWare get IPs to the new nics if vm-tools 
 are installed 
 ---

 Key: CLOUDSTACK-2119
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2119
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, VMware
Affects Versions: 4.2.0
 Environment: VMWare
Reporter: Saksham Srivastava
Assignee: Radhika Nair
 Fix For: 4.2.0


 Add NIC API creates new NICs on the guest VM.
 If vm-tools are not present running dhclient does not result in IPs assigned 
 to the NICs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2119) Doc : Adding NICs to guest VMs on VMWare get IPs to the new nics if vm-tools are installed


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

Radhika Nair resolved CLOUDSTACK-2119.
--

Resolution: Fixed

 Doc : Adding NICs to guest VMs on VMWare get IPs to the new nics if vm-tools 
 are installed 
 ---

 Key: CLOUDSTACK-2119
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2119
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, VMware
Affects Versions: 4.2.0
 Environment: VMWare
Reporter: Saksham Srivastava
Assignee: Radhika Nair
 Fix For: 4.2.0


 Add NIC API creates new NICs on the guest VM.
 If vm-tools are not present running dhclient does not result in IPs assigned 
 to the NICs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2119) Doc : Adding NICs to guest VMs on VMWare get IPs to the new nics if vm-tools are installed


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

Radhika Nair commented on CLOUDSTACK-2119:
--

For adding or removing a NIC to work, ensure that vm-tools are running on the 
guest VMs on VMware host.

 Doc : Adding NICs to guest VMs on VMWare get IPs to the new nics if vm-tools 
 are installed 
 ---

 Key: CLOUDSTACK-2119
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2119
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, VMware
Affects Versions: 4.2.0
 Environment: VMWare
Reporter: Saksham Srivastava
Assignee: Radhika Nair
 Fix For: 4.2.0


 Add NIC API creates new NICs on the guest VM.
 If vm-tools are not present running dhclient does not result in IPs assigned 
 to the NICs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3545) NPE while listing the storage pools for migrating a volume

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

Devdeep Singh commented on CLOUDSTACK-3545:
---

Marking it blocker. It prevents a storage motion feature to be used/verified.
It is also a regression.

NPE while listing the storage pools for migrating a volume
--

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

1. Do a cloudstack setup with either XenServer 6.1 or 6.2 hosts.
2. Add multiple storage pools to the cluster.
3. Execute a findStoragePoolsForMigration api to list the storage pools
available for migrating a volume.
A NPE is generated. Stack trace looks as follows
ERROR [cloud.api.ApiServer] (catalina-exec-16:null) unhandled exception
executing api command: findStoragePoolsForMigration
java.lang.NullPointerException
at
com.cloud.server.ManagementServerImpl.listStoragePoolsForMigrationOfVolume(ManagementServerImpl.java:1336)

at
org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72)

at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3545) NPE while listing the storage pools for migrating a volume

Devdeep Singh created CLOUDSTACK-3545:
-

 Summary: NPE while listing the storage pools for migrating a volume
 Key: CLOUDSTACK-3545
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3545
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Reporter: Devdeep Singh
Assignee: Devdeep Singh
 Fix For: 4.2.0


1. Do a cloudstack setup with either XenServer 6.1 or 6.2 hosts.
2. Add multiple storage pools to the cluster.
3. Execute a findStoragePoolsForMigration api to list the storage pools 
available for migrating a volume.

A NPE is generated. Stack trace looks as follows
ERROR [cloud.api.ApiServer] (catalina-exec-16:null) unhandled exception 
executing api command: findStoragePoolsForMigration 
java.lang.NullPointerException 
at 
com.cloud.server.ManagementServerImpl.listStoragePoolsForMigrationOfVolume(ManagementServerImpl.java:1336)
 
at 
org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72)
 
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) 
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) 
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3545) NPE while listing the storage pools for migrating a volume


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

Devdeep Singh updated CLOUDSTACK-3545:
--

Priority: Blocker  (was: Major)

 NPE while listing the storage pools for migrating a volume
 --

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


 1. Do a cloudstack setup with either XenServer 6.1 or 6.2 hosts.
 2. Add multiple storage pools to the cluster.
 3. Execute a findStoragePoolsForMigration api to list the storage pools 
 available for migrating a volume.
 A NPE is generated. Stack trace looks as follows
 ERROR [cloud.api.ApiServer] (catalina-exec-16:null) unhandled exception 
 executing api command: findStoragePoolsForMigration 
 java.lang.NullPointerException 
 at 
 com.cloud.server.ManagementServerImpl.listStoragePoolsForMigrationOfVolume(ManagementServerImpl.java:1336)
  
 at 
 org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72)
  
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) 
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) 
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3545) NPE while listing the storage pools for migrating a volume

2013-07-16 Thread ASF subversion and git services (JIRA)

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

Devdeep Singh commented on CLOUDSTACK-3545:
---

The bug is similar to https://issues.apache.org/jira/browse/CLOUDSTACK-3264
which was filed for ZWPS. The fix was also made for ZWFS.

NPE while listing the storage pools for migrating a volume
--

at
org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72)

at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)

[jira] [Commented] (CLOUDSTACK-3545) NPE while listing the storage pools for migrating a volume

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

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

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

CLOUDSTACK-3545: NPE in listStoragePoolsForMigration api. The volume table no
longer holds
the pod id, the column is null now. Made a change to get the pod id from the
storage pool
on which the volume resides.

NPE while listing the storage pools for migrating a volume
--

at
org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72)

at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)

[jira] [Commented] (CLOUDSTACK-2725) [Automation] Re-attaching volume on VM failing in KVM

2013-07-16 Thread Marcus Sorensen (JIRA)


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

Marcus Sorensen commented on CLOUDSTACK-2725:
-

I'm so far unable to recreate the issue, RHEL 6.3, libvirt 0.10.2 (stock), with 
cloudstack 4.1. I created a VM on NFS storage, with a datadisk, attached two 
other data disks, and detached/reattached each one. I tried with 4.1 to try to 
verify whether or not it was libvirt, or how we are using libvirt in 4.2.  I 
will now try 4.2 and see if I can reproduce.

 [Automation] Re-attaching volume on VM failing in KVM
 -

 Key: CLOUDSTACK-2725
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.2.0
 Environment: Automation environment KVM 
 Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
Reporter: Rayees Namathponnan
Assignee: Fang Wang
Priority: Blocker
 Fix For: 4.2.0

 Attachments: CLOUDSTACK-2725.rar


 Below two test case failing from BVT 
 integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 
 integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume 
 Steps to reproduce 
 Step 1 : Create an account, service offering, create volume, create VM
 Step 2 : Attach volume to VM , 
 Step 3 : Detach volume
 Step 4 : Attach volume to VM  again 
 Actual result 
 Attachment failed with below error
 2013-05-28 13:45:39,101 DEBUG [agent.transport.Request] 
 (Job-Executor-98:job-1246) Seq 5-258539658: Rec
 eived:  { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, { 
 AttachAnswer } }
 2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-98:job-1246) Unexpected e
 xception while executing 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume: 
 TestDiskServ to VM: ce79edb6-
 a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error 
 unable to execute QEMU comman
 d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
 at 
 com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
 at 
 com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
 t(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
 22)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-05-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-98:job-1246) Complete asy
 nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error 
 text: Failed to attach volume
 : TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e; 
 org.libvirt.LibvirtException: internal erro

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2119) Doc : Adding NICs to guest VMs on VMWare get IPs to the new nics if vm-tools are installed

2013-07-16 Thread ASF subversion and git services (JIRA)


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

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

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

CLOUDSTACK-2119


 Doc : Adding NICs to guest VMs on VMWare get IPs to the new nics if vm-tools 
 are installed 
 ---

 Key: CLOUDSTACK-2119
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2119
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, VMware
Affects Versions: 4.2.0
 Environment: VMWare
Reporter: Saksham Srivastava
Assignee: Radhika Nair
 Fix For: 4.2.0


 Add NIC API creates new NICs on the guest VM.
 If vm-tools are not present running dhclient does not result in IPs assigned 
 to the NICs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-3545) NPE while listing the storage pools for migrating a volume

2013-07-16 Thread ASF subversion and git services (JIRA)

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

Devdeep Singh resolved CLOUDSTACK-3545.
---

Resolution: Fixed

NPE while listing the storage pools for migrating a volume
--

at
org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72)

at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)

[jira] [Commented] (CLOUDSTACK-3545) NPE while listing the storage pools for migrating a volume

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

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

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

NPE while listing the storage pools for migrating a volume
--

at
org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72)

at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)

[jira] [Updated] (CLOUDSTACK-3193) Remove SecondaryStorageDiscoverer


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

Animesh Chaturvedi updated CLOUDSTACK-3193:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 Remove SecondaryStorageDiscoverer
 -

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


 Earlier the way secondary storage was discovered was through the
 SecondaryStorageDiscoverer calling on the DummySecondaryStorageResource. Right
 now, with the object storage merge discovery process is delegated to the
 corresponding ImageStoreDriver.
 Deprecate the unused discoverer to reduce confusion.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3285) UCS: Need support for HTTP redirects and HTTPS Certificate handling


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

Animesh Chaturvedi updated CLOUDSTACK-3285:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 UCS: Need support for HTTP redirects and HTTPS Certificate handling
 ---

 Key: CLOUDSTACK-3285
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3285
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UCS
Affects Versions: 4.2.0
 Environment: Master; Basic Bare-metal and UCS
Reporter: Parth Jagirdar
Priority: Critical

 By default UCS has HTTP to HTTPs redirect enabled.
 At which point, addUcsManager fails with following error.
 2013-06-28 14:19:57,020 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
 ===START===  10.217.252.127 -- GET  
 command=addUcsManagerzoneid=d92cc843-8c50-4f57-9c07-1041bf859f8dname=ucsmanagerurl=10.223.184.2username=adminresponse=jsonsessionkey=NiAtOI4sZHTkTJ37Y4jz0ntaeYg%3D_=1372454390205
 2013-06-28 14:19:57,256 WARN  [cloudstack.api.AddUcsManagerCmd] 
 (catalina-exec-20:null) Exception:
 com.cloud.utils.exception.CloudRuntimeException: Cannot get cookie
 at 
 com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:174)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.listBlades(UcsManagerImpl.java:179)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.discoverBlades(UcsManagerImpl.java:123)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.addUcsManager(UcsManagerImpl.java:154)
 at 
 org.apache.cloudstack.api.AddUcsManagerCmd.execute(AddUcsManagerCmd.java:68)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 
 org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
 at 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 
 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
 htmlhead
 title302 Found/title
 /headbody
 h1Found/h1
 pThe document has moved a href=https://10.223.184.2/nuova;here/a./p
 /body/html
 at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:50)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:166)
 ... 26 more
 Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 
 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
 htmlhead
 title302 Found/title
 /headbody
 h1Found/h1
 pThe document has moved a href=https://10.223.184.2/nuova;here/a./p
 /body/html
 at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:41)
 ... 27 more
 2013-06-28 14:19:57,257 INFO  [cloud.api.ApiServer] (catalina-exec-20:null) 
 Cannot get cookie
 2013-06-28 14:19:57,258 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
 ===END===  10.217.252.127 -- GET

[jira] [Updated] (CLOUDSTACK-2793) Ubuntu 13.04 - Unable to start Stopped VM


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

Animesh Chaturvedi updated CLOUDSTACK-2793:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 Ubuntu 13.04 - Unable to start Stopped VM
 -

 Key: CLOUDSTACK-2793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2793
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
 Environment: MS ubuntu 13.04 KVM ACS 4.2 PVLAN
 host ubuntu 13.04 KVM ACS 4.2 PVLAN
Reporter: angeline shen
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.log.gz, management-server.log.gz, 
 Screenshot-CloudStack - Mozilla Firefox-5.png


 1. advance zone. Add 2 hosts.
   create PVLAN shared network with VLAN ID, private VLAN ID, IPV4 gateway, 
 netmask, start IP, end IP
  gatewayprimary vlan secondary vlan IP
 network1:  10.223.161.65  1611998
 10.223.161.110- 10.223.161.113
 network2:  10.223.161.1291612997
 10.223.161.150-10.223.161.153
 2. Deploy VMs in both PVLAN shared network
 3. stop VMs in both PVLAN shared networks
 4. Start stopped VMs in network2  failed .  Start stopped VMs in network1 
 succeeded.
 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-57:job-55) Successfully released network resources for the vm 
 VM[User|z1admin1612-153V86]
 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-57:job-55) Successfully cleanued up resources for the vm 
 VM[User|z1admin1612-153V86] in Starting state
 2013-05-31 20:01:36,077 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-57:job-55) VM state transitted from :Starting to Stopped with 
 event: OperationFailedvm's original host id: 4 new host id: null host id 
 before s
 tate transition: 4
 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-57:job-55) Hosts's actual total CPU: 9040 and CPU after 
 applying overprovisioning: 9040
 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-57:job-55) Hosts's actual total RAM: 16816881664 and RAM after 
 applying overprovisioning: 16816881664
 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-57:job-55) release cpu from host: 4, old used: 1200,reserved: 
 0, actual total: 9040, total with overprovisioning: 9040; new used: 
 1100,reserved
 :0; movedfromreserved: false,moveToReserveredfalse
 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-57:job-55) release mem from host: 4, old used: 
 2281701376,reserved: 0, total: 16816881664; new used: 1744830464,reserved:0; 
 movedfromreserved: false,moveToReserveredfalse
 2013-05-31 20:01:36,101 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-57:job-55) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.StartVMCmd
 com.cloud.exception.AgentUnavailableException: Resource [Host:4] is 
 unreachable: Host 4: Unable to start instance due to Unable to get answer 
 that is of class com.cloud.agent.api.StartAnswer
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:937)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3243)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1786)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at

[jira] [Updated] (CLOUDSTACK-2450) SRX:F5:guestvm deployement with userdata failed with exception


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

Animesh Chaturvedi updated CLOUDSTACK-2450:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 SRX:F5:guestvm deployement with userdata failed with exception
 --

 Key: CLOUDSTACK-2450
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2450
 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: sadhu suresh
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 guest vm deployment with user-data failed where as guestvm deployment without 
 user-data successful.
 Steps:
 1.create a network offering with following service capabilities 
   Firewall: JuniperSRX, UserData: VirtualRouter, SourceNat: JuniperSRX, 
 Lb: F5BigIp, Dns: VirtualRouter, Dhcp: VirtualRouter, PortForwarding: 
 JuniperSRX, StaticNat: JuniperSRXr, 
 2.create shared guest network with scope as account
 3. deploy a VM without user data
 4. deploy a vm with user-data
 http://10.147.59.83:8080/client/api?command=deployVirtualMachinezoneId=80b8c228-7244-40d9-b567-e0c60591a57etemplateId=66b3548a-b702-11e2-bb08-068a723bhypervisor=XenServerserviceOfferingId=e2fdf625-532b-43c8-80a2-4d232dbdf5danetworkIds=09607cd1-71ff-4d87-90f2-e5d54528ec3cdisplayname=guestvm3name=guestvm3response=jsonuserdata=Y3VzdG9tZXJWTQ==sessionkey=uyRu4Dei1T3VlQOmDFPmI%2BJDWF0%3D_=1368420957885
 actual result :
 step3:
 uservm deployment was successful
 step4:
 uservm deployment  failed with  below exception:
 2013-05-13 06:27:37,010 DEBUG [agent.transport.Request] 
 (Job-Executor-4:job-135) Seq 1-1546190956: Sending  { Cmd , MgmtId: 
 7191687856187, via: 1, Ver: v1, Flags: 100111, 
 [{routing.SavePasswordCommand:{password:fnirq_cnffjbeq,vmIpAddress:192.168.40.35,vmName:guestvm3,accessDetails:{router.guest.ip:192.168.40.30,zone.network.type:Advanced,router.ip:169.254.2.156,router.name:r-13-VM},wait:0}},{routing.VmDataCommand:{vmIpAddress:192.168.40.35,vmName:guestvm3,accessDetails:{router.guest.ip:192.168.40.30,zone.network.type:Advanced,router.ip:169.254.2.156,router.name:r-13-VM},wait:0}}]
  }
 2013-05-13 06:27:37,011 DEBUG [agent.transport.Request] 
 (Job-Executor-4:job-135) Seq 1-1546190956: Executing:  { Cmd , MgmtId: 
 7191687856187, via: 1, Ver: v1, Flags: 100111, 
 [{routing.SavePasswordCommand:{password:fnirq_cnffjbeq,vmIpAddress:192.168.40.35,vmName:guestvm3,accessDetails:{router.guest.ip:192.168.40.30,zone.network.type:Advanced,router.ip:169.254.2.156,router.name:r-13-VM},wait:0}},{routing.VmDataCommand:{vmIpAddress:192.168.40.35,vmName:guestvm3,accessDetails:{router.guest.ip:192.168.40.30,zone.network.type:Advanced,router.ip:169.254.2.156,router.name:r-13-VM},wait:0}}]
  }
 2013-05-13 06:27:37,012 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-76:null) Seq 1-1546190956: Executing request
 2013-05-13 06:27:47,326 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-76:null) Seq 1-1546190956: Response Received:
 2013-05-13 06:27:47,327 DEBUG [agent.transport.Request] (DirectAgent-76:null) 
 Seq 1-1546190956: Processing:  { Ans: , MgmtId: 7191687856187, via: 1, Ver: 
 v1, Flags: 110, 
 [{Answer:{result:true,wait:0}},{Answer:{result:false,details:vm_data
  failed,wait:0}}] }
 2013-05-13 06:27:47,327 DEBUG [agent.transport.Request] 
 (Job-Executor-4:job-135) Seq 1-1546190956: Received:  { Ans: , MgmtId: 
 7191687856187, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
 2013-05-13 06:27:47,328 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-4:job-135) Unable to contact resource.
 com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is 
 unreachable: Unable to apply userdata and password entry on router
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3458)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2752)
 at 
 com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:860)
 at 
 com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:1616)
 at 
 com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:1721)
 at 
 com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:1662)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:810)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:529)
 at

[jira] [Updated] (CLOUDSTACK-3274) Object_store_refactor: secretkey and accesskey of the backing store is found in plaintext in the logs


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

Animesh Chaturvedi updated CLOUDSTACK-3274:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 Object_store_refactor: secretkey and accesskey of the backing store is found 
 in plaintext in the logs
 -

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


 Should we be printing the s3 store credentials in the logs in plaintext? Can 
 it be sanitized?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2776) UI Implicit dedication planner: createServiceOffering UI should be changed to take in key-value details


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

Animesh Chaturvedi updated CLOUDSTACK-2776:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 UI Implicit dedication planner: createServiceOffering UI should be changed to 
 take in key-value details 
 

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


 The UI changes done to the createServiceOffering page as part of the Implicit 
 dedication planner are not correct and very specific to this feature. Instead 
 we need a generic design.
 We should make following changes:
 1) Create Service Offering Page should show option ‘Add Details’ and then 
 take in 2 text boxes titled ‘key’ and ‘value’  - This is same as the UI for 
 adding Tags to a resource like network
 2) After adding one pair, UI can show the option to add another key-value 
 detail
 3) UI can then send all the key-value pairs in a Map while calling 
 CreateServiceOffering API

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3294) CLONE - System VMs not coming up due to “InsufficientServerCapacityException”.(not consistently reproducible)


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

Animesh Chaturvedi updated CLOUDSTACK-3294:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 CLONE - System VMs not coming up due to 
 “InsufficientServerCapacityException”.(not consistently reproducible)
 -

 Key: CLOUDSTACK-3294
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3294
 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: Nitin Mehta
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.zip


 Seps:t
 1.Have a CS with advanced zone .
 2.Created some user VMs.
 3.Created VPCs and VMs under VPCs.
 4.Shutdown the Host(Xen) and MS.
 5.Start the Host and MS.
 Observation:
 The SSVM and CPVM were not coming up with 
 “InsufficientServerCapacityException” exception.
 The Dashboard was showing exhausted  management IPs .
 Deleted all the VMS ,still the IPs were not released.
 Below is the table which shows that all the management ips are reserved.
 mysql select * from op_dc_ip_address_alloc;
 ++---++++--+-+-+
 | id | ip_address| data_center_id | pod_id | nic_id | reservation_id  
  | taken   | mac_address |
 ++---++++--+-+-+
 |  1 | 10.147.40.181 |  1 |  1 | 34 | 
 48d95839-6fb1-4bc4-b23a-c9f1891bf1fa | 2013-05-31 17:10:06 |   1 |
 |  2 | 10.147.40.182 |  1 |  1 |  3 | 
 a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 |   2 |
 |  3 | 10.147.40.183 |  1 |  1 |  7 | 
 238830cd-8cbe-411e-8016-352129885df6 | 2013-05-31 17:07:30 |   3 |
 |  4 | 10.147.40.184 |  1 |  1 |  7 | 
 70f091d4-acb4-435b-bfde-9bdb35bcfa6b | 2013-05-31 17:09:15 |   4 |
 |  5 | 10.147.40.185 |  1 |  1 | 29 | 
 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 |   5 |
 |  6 | 10.147.40.186 |  1 |  1 | 30 | 
 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 |   6 |
 |  7 | 10.147.40.187 |  1 |  1 |  4 | 
 a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 |   7 |
 |  8 | 10.147.40.188 |  1 |  1 |  7 | 
 ea8644d1-7801-4dbb-aa0c-204f31e922a1 | 2013-05-31 17:08:25 |   8 |
 |  9 | 10.147.40.189 |  1 |  1 |  7 | 
 245e0082-d697-454d-9689-b36cc3b6e113 | 2013-05-31 17:11:16 |   9 |
 | 10 | 10.147.40.190 |  1 |  1 |  7 | 
 094e371a-da69-44e0-80fd-14c2d090e935 | 2013-05-31 17:10:15 |  10 |
 ++---++++--+-+-+
 As all the IPs were in  reserved state ,SSVM and CPVM were not coming up.
 Was not able to reproduce this issue again .
 Attached is the server log.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3250) PVLAN - When host is put in maintenance mode , the rules for the router and the user Vms that get migrated out of this host are not getting cleared from this host.


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

Animesh Chaturvedi updated CLOUDSTACK-3250:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 PVLAN - When host is put in maintenance mode , the rules for the router and 
 the user Vms that get migrated out of this host are not getting cleared from 
 this host. 
 

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

 Attachments: management-server.log


 1. Advance zone  cluster with 2 hosts. 
 2. Create  Shared NW1  scope zone  pVLAN1, sVLAN1. 
 3. Deploy few Vms in this network. 
 4. In my case:
 host1 - had SSVM,CPVM and 1 user vm
 host2 - had 1 router and 2 user Vms.
 Put host2 in maintenance mode.
 All the vms running in host2 got migrated to host1.
 As part of this migration , we see all the rules relating to the router and 
 user Vms that got migrated being reprogrammed in host1. 
 But the rules that existed for these Vms in host2 continue to be present in 
 the host.
 Expected Behavior:
 The rules relating to the Vms that migrated out of this host needs to be 
 cleared from this host.
 root@xenserver-sangee2 ~]# ovs-ofctl dump-flows xenbr0
 NXST_FLOW reply (xid=0x4):
  cookie=0x0, duration=352.296s, table=0, n_packets=2, n_bytes=96, 
 priority=60,dl_vlan=997,dl_src=06:a5:26:00:00:11 actions=output:1
  cookie=0x0, duration=361.825s, table=0, n_packets=76, n_bytes=9304, 
 priority=60,dl_vlan=997,dl_src=06:3d:cc:00:00:10 actions=output:1
  cookie=0x0, duration=6082.819s, table=0, n_packets=2635, n_bytes=199830, 
 priority=60,dl_vlan=997,dl_src=06:64:5e:00:00:0e actions=output:1
  cookie=0x0, duration=352.302s, table=0, n_packets=2, n_bytes=96, 
 priority=50,vlan_tci=0x,dl_src=06:a5:26:00:00:11 
 actions=mod_vlan_vid:997,resubmit:1
  cookie=0x0, duration=6082.824s, table=0, n_packets=2717, n_bytes=207263, 
 priority=50,vlan_tci=0x,dl_src=06:64:5e:00:00:0e 
 actions=mod_vlan_vid:997,resubmit:1
  cookie=0x0, duration=361.829s, table=0, n_packets=83, n_bytes=9838, 
 priority=50,vlan_tci=0x,dl_src=06:3d:cc:00:00:10 
 actions=mod_vlan_vid:997,resubmit:1
  cookie=0x0, duration=343.987s, table=0, n_packets=0, n_bytes=0, 
 priority=100,udp,dl_vlan=997,nw_dst=255.255.255.255,tp_dst=67 
 actions=strip_vlan,output:24
  cookie=0x0, duration=343.995s, table=0, n_packets=4, n_bytes=168, 
 priority=200,arp,dl_vlan=997,nw_dst=10.223.161.141 
 actions=strip_vlan,output:24
  cookie=0x0, duration=8241.736s, table=0, n_packets=19016430, 
 n_bytes=24109319550, priority=0 actions=NORMAL
  cookie=0x0, duration=343.991s, table=0, n_packets=7, n_bytes=646, 
 priority=150,dl_vlan=997,dl_dst=06:ba:9c:00:00:0f actions=strip_vlan,output:24
 [root@xenserver-sangee1 ~]# ovs-ofctl dump-flows xenbr0
 NXST_FLOW reply (xid=0x4):
  cookie=0x0, duration=734.85s, table=0, n_packets=54, n_bytes=6732, 
 priority=60,dl_vlan=997,dl_src=06:3d:cc:00:00:10 actions=output:1
  cookie=0x0, duration=597.648s, table=0, n_packets=158, n_bytes=19572, 
 priority=60,dl_vlan=997,dl_src=06:a5:26:00:00:11 actions=output:1
  cookie=0x0, duration=597.653s, table=0, n_packets=182, n_bytes=22797, 
 priority=50,vlan_tci=0x,dl_src=06:a5:26:00:00:11 
 actions=mod_vlan_vid:997,resubmit:1
  cookie=0x0, duration=734.854s, table=0, n_packets=64, n_bytes=7884, 
 priority=50,vlan_tci=0x,dl_src=06:3d:cc:00:00:10 
 actions=mod_vlan_vid:997,resubmit:1
  cookie=0x0, duration=1032.129s, table=0, n_packets=6, n_bytes=2052, 
 priority=100,udp,dl_vlan=997,nw_dst=255.255.255.255,tp_dst=67 
 actions=strip_vlan,output:4
  cookie=0x0, duration=1032.137s, table=0, n_packets=13, n_bytes=656, 
 priority=200,arp,dl_vlan=997,nw_dst=10.223.161.141 actions=strip_vlan,output:4
  cookie=0x0, duration=8231.759s, table=0, n_packets=2165619, 
 n_bytes=2671820347, priority=0 actions=NORMAL
  cookie=0x0, duration=1032.133s, table=0, n_packets=42, n_bytes=3685, 
 priority=150,dl_vlan=997,dl_dst=06:ba:9c:00:00:0f actions=strip_vlan,output:4
 root@r-4-VM:~# cat /etc/dhcphosts.txt 
 06:64:5e:00:00:0e,set:10_223_161_140,10.223.161.140,test-123,infinite
 06:3d:cc:00:00:10,set:10_223_161_142,10.223.161.142,test345,infinite
 06:a5:26:00:00:11,set:10_223_161_143,10.223.161.143,yuyu,infinite
 root@r-4-VM:~# 

--
This message is automatically generated by JIRA.
If you think it was

[jira] [Updated] (CLOUDSTACK-2005) Condition mapping entries / rules are not working as expected


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

Animesh Chaturvedi updated CLOUDSTACK-2005:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 Condition mapping entries / rules are not working as expected
 -

 Key: CLOUDSTACK-2005
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2005
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VNC Proxy
Affects Versions: 4.2.0
 Environment: Build No.#133 
 (CloudStack-non-OSS-MASTER-133-rhel6.3.tar.gz)
 XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr 
 Server, Win7Entx64SP1 for Client machine. 
Reporter: Minying Bao
Priority: Critical
 Fix For: 4.2.0

 Attachments: v3Extensive Test of the Conditional mapping entry.docx


 Steps
 Setup the CloudStack environments with build 4.2#133.
 Add template and then create as an instance.
 Manually modify the condition mapping entries in the ajaxkeys.js file, 
 synchronize the script to v-2-VM.
 Launch the VM via ConsoleProxy in client machine, to check if the condition 
 mapping entries are working as expected.
 Note
 The requirements link have the following list of rules/conditional mapping 
 entries: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Non-US+Keyboard+Support+for+Console+Proxy
 Conditional mapping entry   { 
  type: event type, code: mapped key code, modifiers: modifiers,
  shift : shift state match condition,-- match on shift 
 state
  guestos : guest os match condition, -- match on guestos type
  browser: browser type match condition,  -- match on browser
  browserVersion: brower version match condition  -- match on 
 browser version
 }
 Expected Result
 All the condition mapping entries / rules should be working as expected.
 Actual Result 
 Condition mapping entries / rules are not working as expected.
 Please refer to attached for details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2909) EN, SC, KO: Key translation fails for the US keyboard and KO keyboard keys ' , ; :, Tab

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

Animesh Chaturvedi updated CLOUDSTACK-2909:
---

This issue has not been picked up, please review and see if you can help fix
the issue

EN, SC, KO: Key translation fails for the US keyboard and KO keyboard keys '
, ; :, Tab

Key: CLOUDSTACK-2909
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2909
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VNC Proxy
Affects Versions: 4.2.0
Environment: Build No.#426
(CloudStack-non-OSS-MASTER-426-rhel6.3.tar.gz)
XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr
Server, Win7-x86 for Client machine.
Reporter: Minying Bao
Priority: Critical
Fix For: 4.2.0

Attachments: US,SC,KO Keyboard_issues.xlsx

Steps
1. Setup the CloudStack environments with build 4.2#426.
2. Bring US,SC,KO Win-7 x86 VMs.
3. Access the VM via Console Proxy from the US,SC,KO client machines, choose
the Stardtand (US) Keyboard for Keyboard Option.
4. Hit all the keys with US/KO keyboard.
Expected Result
All the keys should work fine.
Actual Result
The US/KO keyboard keys ' , ; :, Tab are not working well.
Please refer to the details as attached Excel.

[jira] [Updated] (CLOUDSTACK-3256) UI - AWS Regions - When switching between regions after logging out and logging in as a different user , we are authenticated as the previous user probably due to br

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

Animesh Chaturvedi updated CLOUDSTACK-3256:
---

This issue has not been picked up, please review and see if you can help fix
the issue

UI - AWS Regions - When switching between regions after logging out and
logging in as a different user , we are authenticated as the previous user
probably due to browser cache.
--

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

UI - AWS Regions - When switching between regions after logging out and
logging in as a different user , we are authenticated as the previous user.
Steps to reproduce the problem:
Set up - 2 Regions - Region1 and Region2.
Scenario1:
Log in as user1 to Region1.
Switch to Region2.
User is prompted for password .
Enter username and password for user1.
User is logged in to Region2 successfully.

From Region2 , now switch to Region1.
User is not prompted for password and is directed to Region1 UI.
Expected Bhevaior:
User should be prompted for password.
Scenario2:
Log in as user1 to Region1.
Switch to Region2.
User is prompted for password .
Enter username and password for user1.
User is logged in to Region2 successfully.
Log out.
Log in as user2.
From Region2 (where we are logged in as user2) , now switch to Region1.
User is not prompted for password.
He is redirected to Region1 and is authenticated as user1.
Expected Bhevaior:
User should be prompted for password.

[jira] [Updated] (CLOUDSTACK-3229) Object_Store_Refactor - Snapshot fails due to an internal error

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

Animesh Chaturvedi updated CLOUDSTACK-3229:
---

This issue has not been picked up, please review and see if you can help fix
the issue

Object_Store_Refactor - Snapshot fails due to an internal error
---

Key: CLOUDSTACK-3229
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3229
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0
Environment: chrome on linux
devcloud
Cloudian or Amazon S3 Object store
Reporter: Thomas O'Dowd
Priority: Critical

Assuming initial devcloud state...
I added a cache for the S3 storage like this.
on devcloud machine as root:
# mkdir /opt/storage/cache
# vi /etc/exports (and append this line)
/opt/storage/cache *(rw,no_subtree_check,no_root_squash,fsid=)
# exportfs -a
On Mgmt server GUI:
1. navigate to infrastructure - secondary storage
2. delete the NFS SS.
3. add S3 storage for Cloudian (I used 6 as the timeouts - assuming
millis). I used the /opt/storage/cache thing as the s3 cache.
4. nav to templates
5. register a new template (I uploaded tinyLinux again as mytiny (5.3
64bit)).
6. confirm with s3cmd that 2 objects are now on S3.
- s3 objects ---
template/tmpl/1/1/routing-1/acton-systemvm-02062012.vhd.bz2
2013-06-27T03:01:46.203Z None 140616708 b533e7b65219439ee7fca0146ddd7ffa-27
template/tmpl/2/201/201-2-ae9e9409-4c8e-3ad8-a62f-abec7a35fe26/tinylinux.vhd
2013-06-27T03:04:06.730Z None 50430464 4afac316e865adf74ca1a8039fae7399-10
- s3 objects ---
7. I restarted the management server at this point which actually resulted in
another object on S3.
- the new s3 object ---
template/tmpl/1/5/tiny Linux/ttylinux_pv.vhd 2013-06-27T03:43:26.494Z None
50430464 4afac316e865adf74ca1a8039fae7399-10
- the new s3 object ---
8. Go to instance and create a new choosing the mytiny template which we
registered.
9. launch it after selecting all defaults.
10. wait until it starts.
11. nav to storage. I see ROOT-8. Click on this to open.
12. click the camera to take the snapshot.
after a pause I get a popup
Failed to create snapshot due to an internal error creating snapshot
for volume 8
Also on the mgmt terminal I get the following log entry (only 1):
INFO [user.snapshot.CreateSnapshotCmd] (Job-Executor-8:job-16) VOLSS:
createSnapshotCmd starts:1372321251009
If I check the view snapshots button under storage, I can however see the
snapshot. It says its on primary. I'm expecting it to go to secondary storage
though. Nothing is in the S3 logs and no snapshots.
If I try to delete that snapshot from here I get this error in the logs:
ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-12:job-20) Unexpected
exception while executing
org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to delete
snapshot:com.cloud.exception.InvalidParameterValueException: Can't delete
snapshotshot 4 due to it is not in BackedUp Status
at
com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshot(SnapshotManagerImpl.java:513)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd.execute(DeleteSnapshotCmd.java:96)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
If I navigate to instance, my instance, and try to take a vm snapshot from
here, I get a different pop-up which says:
There is other active volume snapshot tasks on the instance to which the
volume is attached, please try again later
And I get an exception:
ERROR [cloud.api.ApiServer] (352129314@qtp-2110413789-32:) unhandled
exception executing api command: createVMSnapshot
com.cloud.utils.exception.CloudRuntimeException: There is other active volume
snapshot tasks on the instance to which the volume is attached, please try

[jira] [Updated] (CLOUDSTACK-3254) Anti-Affinity - UI - Admin should be able to view the affinity groups that belong to all other users. He should be allowed to delete affinity group that belongs to o


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

Animesh Chaturvedi updated CLOUDSTACK-3254:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 Anti-Affinity - UI - Admin should be able to view the affinity groups that 
 belong to all other users. He should be allowed to delete affinity group that 
 belongs to other users. 
 -

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


 Anti-Affinity - UI - Admin should be able to view the affinity groups that 
 belong to all other users. He should be allowed to delete affinity group that 
 belongs to other users.
 As regular users , create few affinity groups.
 When logged in as Admin , we are not able to list all the affinity group that 
 is owned by other users.
 Expected Behavior:
 UI should allow for admins to list all affinity groups.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2911) KO: Key translation fails for KO keyboard Right Alt, Han/Eng, Hanja keys

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

Animesh Chaturvedi updated CLOUDSTACK-2911:
---

This issue has not been picked up, please review and see if you can help fix
the issue

KO: Key translation fails for KO keyboard Right Alt, Han/Eng, Hanja keys

Key: CLOUDSTACK-2911
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2911
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VNC Proxy
Affects Versions: 4.2.0
Environment: Build No.#426
(CloudStack-non-OSS-MASTER-426-rhel6.3.tar.gz)
XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr
Server, Win7-x86 for Client machine.
Reporter: Minying Bao
Priority: Critical
Fix For: 4.2.0

Attachments: Korean Keyboard_issues.xlsx

Steps
1. Setup the CloudStack environments with build 4.2#426.
2. Bring KO Win-7 x86 VMs.
3. Access the VM via Console Proxy from the KO client machines, choose the
Stardtand (US) Keyboard for Keyboard Option.
4. Hit all the keys with KO keyboard.
Expected Result
All the keys should work fine.
Actual Result
The KO keyboard Right Alt, Han/Eng, Hanja keys are not working well.
Please refer to the details as attached Excel.

[jira] [Updated] (CLOUDSTACK-3037) [UI] [Snapshot] deletion of Allocated snapshot is showing successful in UI, but server is failing to delete it


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

Animesh Chaturvedi updated CLOUDSTACK-3037:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 [UI] [Snapshot] deletion of Allocated snapshot is showing successful in UI, 
 but server is failing to delete it
 --

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


 In UI, 
 Try to delete the Allocated snapshot. 
 UI show snapshot is deleted, But server throws the exception properly. 
 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-3:job-40) Unexpected 
 exception while executing 
 org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to delete 
 snapshot:com.cloud.exception.InvalidParameterValueException: Can't delete 
 snapshotshot 4 due to it is not in BackedUp Status
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshot(SnapshotManagerImpl.java:543)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd.execute(DeleteSnapshotCmd.java:96)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:722)
 After refreshing the page, listsnapshot is getting called and then showing 
 the snapshot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3289) StorageSubsystem: cannot add image store of a different provider in a different zone


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

Animesh Chaturvedi updated CLOUDSTACK-3289:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 StorageSubsystem: cannot add image store of a different provider in a 
 different zone
 

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


 The storage code right now restricts usage of multiple image store providers 
 in the same zone. But it restricts this even when the image store may be in a 
 different zone/region.
 From StorageManagerImpl.java:
 // check if we have already image stores from other different 
 providers,
 // we currently are not supporting image stores from different
 // providers co-existing
 ListImageStoreVO imageStores = _imageStoreDao.listImageStores();
 for (ImageStoreVO store : imageStores) {
 if (!store.getProviderName().equalsIgnoreCase(providerName)) {
 throw new InvalidParameterValueException(You can only add 
 new image stores from the same provider  + store.getProviderName()
 +  already added);
 }
 }
 search criteria lists all add images stores:
 @Override
 public ListImageStoreVO listImageStores() {
 SearchCriteriaImageStoreVO sc = createSearchCriteria();
 sc.addAnd(role, SearchCriteria.Op.EQ, DataStoreRole.Image);
 return listBy(sc);
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2910) SC: Ctrl combinated with . is not working of SC IME

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

Animesh Chaturvedi updated CLOUDSTACK-2910:
---

This issue has not been picked up, please review and see if you can help fix
the issue

SC: Ctrl combinated with . is not working of SC IME

Key: CLOUDSTACK-2910
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2910
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VNC Proxy
Affects Versions: 4.2.0
Environment: Build No.#426
(CloudStack-non-OSS-MASTER-426-rhel6.3.tar.gz)
XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr
Server, Win7-x86 for Client machine.
Reporter: Minying Bao
Priority: Critical
Fix For: 4.2.0

Steps
1. Setup the CloudStack environments with build 4.2#426.
2. Bring SC Win-7 x86 VMs.
3. Access the VM via Console Proxy from the SC client machine, choose the
Standtard (US) Keyboard for Keyboard Option.
4. Test with the Ctrl combinations.
Expected Result
All the Ctrl combinations should work fine.
Ctrl + . should switch the punctuation between full-width and half-width of
SC IME.
Actual Result
Ctrl + . did not work.
Note
The SC IME contained Sougou Input Method, Microsoft Pinyin New Experience
Input

[jira] [Updated] (CLOUDSTACK-3108) Disk related statistics of a VM always show 0 values


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

Animesh Chaturvedi updated CLOUDSTACK-3108:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 Disk related statistics of a VM  always show 0 values
 -

 Key: CLOUDSTACK-3108
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3108
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
 Environment: build:
 CloudPlatform-4.2-117-rhel6.3.tar.gz
Reporter: shweta agarwal
Priority: Critical
 Fix For: 4.2.0


 Repro steps:
 1. Set global configuration value for storage.stas to 600 milliseconds or 
 other small value and restart Management server
 2. Create a VM
 4. Create Some data on a VM (create a data heavy file)
 5. Wait for storage collector thread to run
 Bug:
 Even after storage stats collector thread runs Disk Read, Disk write shows 
 values a zero.
 Expectations:
 Disk read , disk write stats for VM  should show correct value.
 I waited for several Stats collector thread to collect data but still value 
 in VM shows Zero
 For example:
 VM  stats shows
 API : 
 http://10.147.38.141:8080/client/api?command=listVirtualMachinesdetails=statsid=c448201a-9fc5-4cc1-ab28-c8cd2a53594dresponse=jsonsessionkey=4xWeT9Rw4XpRnWMGa1yIqr2vYSA%3D_=1371794494563
 Response:
 { listvirtualmachinesresponse : { count:1 ,virtualmachine : [  
 {id:c448201a-9fc5-4cc1-ab28-c8cd2a53594d,name:c448201a-9fc5-4cc1-ab28-c8cd2a53594d,account:admin,domainid:9df32920-d98f-11e2-95e7-0682fe17,domain:ROOT,created:2013-06-20T18:16:16+0530,state:Running,haenable:false,zoneid:0d3e68a9-4f66-4077-a934-6a07b7bde4d1,zonename:xen,hostid:897004e4-4eab-471a-88c6-0f9ad84386c0,hostname:Rack1Pod1Host27,cpuused:0%,networkkbsread:39873,networkkbswrite:1336,diskkbsread:0,diskkbswrite:0,diskioread:0,diskiowrite:0,guestosid:9ea5e3d0-d98f-11e2-95e7-0682fe17,securitygroup:[],nic:[{id:832205d4-b9ed-4e35-93fe-25dfa51afe43,networkid:4bda1bc0-8c1b-4368-8ee9-e7d32f842ca9,networkname:vv,netmask:255.255.255.0,gateway:10.0.4.1,ipaddress:10.0.4.237,isolationuri:vlan://1041,broadcasturi:vlan://1041,traffictype:Guest,type:Isolated,isdefault:false,macaddress:02:00:7a:18:00:03},{id:6613398e-b652-41e7-8ca3-77f0d913acc0,networkid:867ab04e-fae0-4e0d-aea0-c3e135273b1a,networkname:tier1,netmask:255.255.255.0,gateway:10.0.3.1,ipaddress:10.0.3.121,isolationuri:vlan://1046,broadcasturi:vlan://1046,traffictype:Guest,type:Isolated,isdefault:false,macaddress:02:00:40:00:00:01}],hypervisor:XenServer,instancename:i-2-8-VM,tags:[],affinitygroup:[],displayvm:true}
  ] } }
 Where as VM   shows following file sizes
 ls -ltr
 -rw-r--r-- 1 root root3965 Jun 20 18:30 ter
 -rw-r--r-- 1 root root3965 Jun 20 18:30 ter1
 -rw-r--r-- 1 root root  206180 Jun 20 18:31 ter4
 -rw-r--r-- 1 root root  206180 Jun 20 18:31 ter5
 -rw-r--r-- 1 root root 9071920 Jun 20 18:31 ter3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2979) [Object_Store_Refactor] UI: No provision for the user to add additional NFS Cache Storage if S3 is being used as secondary storage provider


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

Animesh Chaturvedi updated CLOUDSTACK-2979:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 [Object_Store_Refactor] UI: No provision for the user to add additional NFS 
 Cache Storage if S3 is being used as secondary storage provider
 ---

 Key: CLOUDSTACK-2979
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2979
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
 Environment: Latest build from object store branch
Reporter: Sanjeev N
Priority: Critical
 Fix For: 4.2.0


 [Object_Store_Refactor] No provision for the user to add additional NFS Cache 
 Storage if S3 is being used as secondary storage provider
 Steps to Reproduce:
 =
 1.Bring up CS in advanced zone with s3 as the secondary storage provider.
 During zone creation we provide S3 image store and optional NFS cache storage 
 details.
 After zone creation if the admin wants to add another NFS cache storage into 
 the zone, there is no way to do it through UI or dint find any API to do it 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3262) [ZWPS][VMWARE] exception while creating template from snapshot


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

Animesh Chaturvedi updated CLOUDSTACK-3262:
---


This issue has not been picked up, please review and see if you can help fix 
the issue

 [ZWPS][VMWARE] exception while creating template from snapshot
 --

 Key: CLOUDSTACK-3262
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3262
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Template
Affects Versions: 4.2.0
 Environment: VMWARE deployment, ESXI 5.1
Reporter: Srikanteswararao Talluri
Priority: Critical
 Fix For: 4.2.0


 Steps to reproduce:
 ==
 create a VM with its root volume on zone wide primary storage
 create  a snapshot of the root volume
 create a template from snaphot.
 ===START===  10.252.192.7 -- GET  
 command=createTemplateresponse=jsonsessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3Dsnapshotid=8b9f5778-4788-4455-8e8a-db754e6634bbname=tdisplayText=tosTypeId=f9a1c012-de74-11e2-b754-06e1a630isPublic=truepasswordEnabled=false_=1372403272346
 2013-06-28 18:03:13,209 DEBUG [cloud.template.TemplateManagerImpl] 
 (catalina-exec-16:null) This template is getting created from other template, 
 setting source template Id to: 7
 2013-06-28 18:03:13,299 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-16:null) submit async job-91, details: AsyncJobVO {id:91, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: Template, 
 instanceId: 209, cmd: 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd, 
 cmdOriginator: null, cmdInfo: 
 {sessionkey:ywi4cWnDQTL903lMXK6spFaF6U4\u003d,ctxUserId:2,httpmethod:GET,osTypeId:f9a1c012-de74-11e2-b754-06e1a630,isPublic:true,response:json,id:209,displayText:t,snapshotid:8b9f5778-4788-4455-8e8a-db754e6634bb,passwordEnabled:false,name:t,_:1372403272346,ctxAccountId:2,ctxStartEventId:324},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-06-28 18:03:13,306 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) 
 ===END===  10.252.192.7 -- GET  
 command=createTemplateresponse=jsonsessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3Dsnapshotid=8b9f5778-4788-4455-8e8a-db754e6634bbname=tdisplayText=tosTypeId=f9a1c012-de74-11e2-b754-06e1a630isPublic=truepasswordEnabled=false_=1372403272346
 2013-06-28 18:03:13,308 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-41:job-91) Executing 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-91
 2013-06-28 18:03:13,344 DEBUG [storage.image.ImageDataFactoryImpl] 
 (Job-Executor-41:job-91) template 209 is not in store:1, type:Image
 2013-06-28 18:03:13,446 DEBUG [storage.motion.AncientDataMotionStrategy] 
 (Job-Executor-41:job-91) copy failed
 com.cloud.utils.exception.CloudRuntimeException: Unable to find storage pools 
 in zone 1
   at 
 org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.createTemplateFromSnashot(AncientDataMotionStrategy.java:559)
   at 
 org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:486)
   at 
 org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:59)
   at 
 org.apache.cloudstack.storage.image.ImageServiceImpl.createTemplateFromSnapshotAsync(ImageServiceImpl.java:174)
   at 
 com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1755)
   at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
   at 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:256)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
   at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
   at java.util.concurrent.FutureTask.run(FutureTask.java:166)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
   at java.lang.Thread.run(Thread.java:679)
 2013-06-28 18:03:13,460 DEBUG [cloud.template.TemplateManagerImpl] 
 (Job-Executor-41:job-91) Failed to create 
 templatecom.cloud.utils.exception.CloudRuntimeException: Unable to find 
 storage pools in zone 1
 2013-06-28 18:03:13,488

[jira] [Updated] (CLOUDSTACK-1964) Simplified Chinese -- Some combination keys used to switch IME cannot work well

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

Animesh Chaturvedi updated CLOUDSTACK-1964:
---

This issue has not been picked up, please review and see if you can help fix
the issue

Simplified Chinese -- Some combination keys used to switch IME cannot work
well
---

Key: CLOUDSTACK-1964
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1964
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VNC Proxy
Affects Versions: 4.2.0
Environment: Build No.#133
(CloudStack-non-OSS-MASTER-133-rhel6.3.tar.gz)
XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr
Server, Win7Entx64SP1 for Client machine.
Reporter: Minying Bao
Priority: Critical
Fix For: 4.2.0

Steps
Setup the CloudStack environments with build 4.2#133.
Add SC-Win7 template and then create as an instance.
Open Firefox, launch the SC-Win7 via ConsoleProxy in client machine.
Hit all the keys with Simplified Chinese Keyboard (the same as US-101
standard keyboard).
Expected Result
All the keys should remap as same as the Simplified Chinese Keyboard layout
behavior.
Actual Result
Simplified Chinese follows US-101 keyboard style, so most of the keys are
working fine for Simplified Chinese apart from few combination keys used to
switch IME.
1. Ctrl+Shift
Repro frequency is 30%. As the key combinations are accepted correctly, we
may not able to fix using keytranslation.
Ctrl+Shift is used to switch of Microsoft Pinyin New Experience Input
Style, Microsoft Pinyin ABC Input Style and SouGou Pingyin input Style
2. Ctrl+Space
Not working.
Ctrl + Space to switch keyboard layout between SC-US keyboard and SC-IME are
not working at all.
3. Ctrl+Dot
Not working in IE browser, but works fine in Firefox.
Ctrl + Dot to switch Half/Full shape punctuation are not working at all.

[jira] [Commented] (CLOUDSTACK-2725) [Automation] Re-attaching volume on VM failing in KVM

2013-07-16 Thread Marcus Sorensen (JIRA)


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

Marcus Sorensen commented on CLOUDSTACK-2725:
-

Scratch that, centos 6.4 with stock libvirt. I'm not sure it makes a 
difference. I don't imagine we'd launch 4.2 targeting CentOS 6.3, though, so if 
the older libvirt of CentOS 6.3 is the issue then that may conveniently make 
the problem disappear. On the other hand, Ubuntu 12.04's libvirt is older than 
CentOS 6.4's so it may crop up again.

Just more pains with targeting the moving targets of built-in distribution 
libvirt.


 [Automation] Re-attaching volume on VM failing in KVM
 -

 Key: CLOUDSTACK-2725
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.2.0
 Environment: Automation environment KVM 
 Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
Reporter: Rayees Namathponnan
Assignee: Fang Wang
Priority: Blocker
 Fix For: 4.2.0

 Attachments: CLOUDSTACK-2725.rar


 Below two test case failing from BVT 
 integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 
 integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume 
 Steps to reproduce 
 Step 1 : Create an account, service offering, create volume, create VM
 Step 2 : Attach volume to VM , 
 Step 3 : Detach volume
 Step 4 : Attach volume to VM  again 
 Actual result 
 Attachment failed with below error
 2013-05-28 13:45:39,101 DEBUG [agent.transport.Request] 
 (Job-Executor-98:job-1246) Seq 5-258539658: Rec
 eived:  { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, { 
 AttachAnswer } }
 2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-98:job-1246) Unexpected e
 xception while executing 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume: 
 TestDiskServ to VM: ce79edb6-
 a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error 
 unable to execute QEMU comman
 d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
 at 
 com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
 at 
 com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
 t(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
 22)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-05-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-98:job-1246) Complete asy
 nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error 
 text: Failed to attach volume
 : TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e; 
 org.libvirt.LibvirtException: internal erro

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-3108) Disk related statistics of a VM always show 0 values

2013-07-16 Thread Wei Zhou (JIRA)


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

Wei Zhou reassigned CLOUDSTACK-3108:


Assignee: Wei Zhou

 Disk related statistics of a VM  always show 0 values
 -

 Key: CLOUDSTACK-3108
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3108
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
 Environment: build:
 CloudPlatform-4.2-117-rhel6.3.tar.gz
Reporter: shweta agarwal
Assignee: Wei Zhou
Priority: Critical
 Fix For: 4.2.0


 Repro steps:
 1. Set global configuration value for storage.stas to 600 milliseconds or 
 other small value and restart Management server
 2. Create a VM
 4. Create Some data on a VM (create a data heavy file)
 5. Wait for storage collector thread to run
 Bug:
 Even after storage stats collector thread runs Disk Read, Disk write shows 
 values a zero.
 Expectations:
 Disk read , disk write stats for VM  should show correct value.
 I waited for several Stats collector thread to collect data but still value 
 in VM shows Zero
 For example:
 VM  stats shows
 API : 
 http://10.147.38.141:8080/client/api?command=listVirtualMachinesdetails=statsid=c448201a-9fc5-4cc1-ab28-c8cd2a53594dresponse=jsonsessionkey=4xWeT9Rw4XpRnWMGa1yIqr2vYSA%3D_=1371794494563
 Response:
 { listvirtualmachinesresponse : { count:1 ,virtualmachine : [  
 {id:c448201a-9fc5-4cc1-ab28-c8cd2a53594d,name:c448201a-9fc5-4cc1-ab28-c8cd2a53594d,account:admin,domainid:9df32920-d98f-11e2-95e7-0682fe17,domain:ROOT,created:2013-06-20T18:16:16+0530,state:Running,haenable:false,zoneid:0d3e68a9-4f66-4077-a934-6a07b7bde4d1,zonename:xen,hostid:897004e4-4eab-471a-88c6-0f9ad84386c0,hostname:Rack1Pod1Host27,cpuused:0%,networkkbsread:39873,networkkbswrite:1336,diskkbsread:0,diskkbswrite:0,diskioread:0,diskiowrite:0,guestosid:9ea5e3d0-d98f-11e2-95e7-0682fe17,securitygroup:[],nic:[{id:832205d4-b9ed-4e35-93fe-25dfa51afe43,networkid:4bda1bc0-8c1b-4368-8ee9-e7d32f842ca9,networkname:vv,netmask:255.255.255.0,gateway:10.0.4.1,ipaddress:10.0.4.237,isolationuri:vlan://1041,broadcasturi:vlan://1041,traffictype:Guest,type:Isolated,isdefault:false,macaddress:02:00:7a:18:00:03},{id:6613398e-b652-41e7-8ca3-77f0d913acc0,networkid:867ab04e-fae0-4e0d-aea0-c3e135273b1a,networkname:tier1,netmask:255.255.255.0,gateway:10.0.3.1,ipaddress:10.0.3.121,isolationuri:vlan://1046,broadcasturi:vlan://1046,traffictype:Guest,type:Isolated,isdefault:false,macaddress:02:00:40:00:00:01}],hypervisor:XenServer,instancename:i-2-8-VM,tags:[],affinitygroup:[],displayvm:true}
  ] } }
 Where as VM   shows following file sizes
 ls -ltr
 -rw-r--r-- 1 root root3965 Jun 20 18:30 ter
 -rw-r--r-- 1 root root3965 Jun 20 18:30 ter1
 -rw-r--r-- 1 root root  206180 Jun 20 18:31 ter4
 -rw-r--r-- 1 root root  206180 Jun 20 18:31 ter5
 -rw-r--r-- 1 root root 9071920 Jun 20 18:31 ter3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3108) Disk related statistics of a VM always show 0 values

2013-07-16 Thread Wei Zhou (JIRA)


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

Wei Zhou commented on CLOUDSTACK-3108:
--

Animesh,

I picked it up. 

The data collection mechanisms in hypervisors are different. KVM provides 
traffic data aggregation value , and Vmware/Xen provide traffic rate value.
Hence, we can collect aggregation value for KVM only, and disk I/O statistics 
(CLOUDSTACK-1192) supports KVM only.
Stats Collector is ok for KVM (it collects aggregation value). I will change 
the codes to show polling traffic rate value for Vmware/Xen.

-Wei

 Disk related statistics of a VM  always show 0 values
 -

 Key: CLOUDSTACK-3108
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3108
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
 Environment: build:
 CloudPlatform-4.2-117-rhel6.3.tar.gz
Reporter: shweta agarwal
Assignee: Wei Zhou
Priority: Critical
 Fix For: 4.2.0


 Repro steps:
 1. Set global configuration value for storage.stas to 600 milliseconds or 
 other small value and restart Management server
 2. Create a VM
 4. Create Some data on a VM (create a data heavy file)
 5. Wait for storage collector thread to run
 Bug:
 Even after storage stats collector thread runs Disk Read, Disk write shows 
 values a zero.
 Expectations:
 Disk read , disk write stats for VM  should show correct value.
 I waited for several Stats collector thread to collect data but still value 
 in VM shows Zero
 For example:
 VM  stats shows
 API : 
 http://10.147.38.141:8080/client/api?command=listVirtualMachinesdetails=statsid=c448201a-9fc5-4cc1-ab28-c8cd2a53594dresponse=jsonsessionkey=4xWeT9Rw4XpRnWMGa1yIqr2vYSA%3D_=1371794494563
 Response:
 { listvirtualmachinesresponse : { count:1 ,virtualmachine : [  
 {id:c448201a-9fc5-4cc1-ab28-c8cd2a53594d,name:c448201a-9fc5-4cc1-ab28-c8cd2a53594d,account:admin,domainid:9df32920-d98f-11e2-95e7-0682fe17,domain:ROOT,created:2013-06-20T18:16:16+0530,state:Running,haenable:false,zoneid:0d3e68a9-4f66-4077-a934-6a07b7bde4d1,zonename:xen,hostid:897004e4-4eab-471a-88c6-0f9ad84386c0,hostname:Rack1Pod1Host27,cpuused:0%,networkkbsread:39873,networkkbswrite:1336,diskkbsread:0,diskkbswrite:0,diskioread:0,diskiowrite:0,guestosid:9ea5e3d0-d98f-11e2-95e7-0682fe17,securitygroup:[],nic:[{id:832205d4-b9ed-4e35-93fe-25dfa51afe43,networkid:4bda1bc0-8c1b-4368-8ee9-e7d32f842ca9,networkname:vv,netmask:255.255.255.0,gateway:10.0.4.1,ipaddress:10.0.4.237,isolationuri:vlan://1041,broadcasturi:vlan://1041,traffictype:Guest,type:Isolated,isdefault:false,macaddress:02:00:7a:18:00:03},{id:6613398e-b652-41e7-8ca3-77f0d913acc0,networkid:867ab04e-fae0-4e0d-aea0-c3e135273b1a,networkname:tier1,netmask:255.255.255.0,gateway:10.0.3.1,ipaddress:10.0.3.121,isolationuri:vlan://1046,broadcasturi:vlan://1046,traffictype:Guest,type:Isolated,isdefault:false,macaddress:02:00:40:00:00:01}],hypervisor:XenServer,instancename:i-2-8-VM,tags:[],affinitygroup:[],displayvm:true}
  ] } }
 Where as VM   shows following file sizes
 ls -ltr
 -rw-r--r-- 1 root root3965 Jun 20 18:30 ter
 -rw-r--r-- 1 root root3965 Jun 20 18:30 ter1
 -rw-r--r-- 1 root root  206180 Jun 20 18:31 ter4
 -rw-r--r-- 1 root root  206180 Jun 20 18:31 ter5
 -rw-r--r-- 1 root root 9071920 Jun 20 18:31 ter3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2776) UI Implicit dedication planner: createServiceOffering UI should be changed to take in key-value details

2013-07-16 Thread Prachi Damle (JIRA)


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

Prachi Damle commented on CLOUDSTACK-2776:
--

Yes the key-value pair UI can be added after creating the compute offering. 
Will that be edit service offering action? This enhancement can be done for the 
next release.

Atleast for now, for the implicit dedication planner, we should make sure that 
the option to choose the planner mode is shown to the user only when the 
implicit planner is chosen from the planner list.


 UI Implicit dedication planner: createServiceOffering UI should be changed to 
 take in key-value details 
 

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


 The UI changes done to the createServiceOffering page as part of the Implicit 
 dedication planner are not correct and very specific to this feature. Instead 
 we need a generic design.
 We should make following changes:
 1) Create Service Offering Page should show option ‘Add Details’ and then 
 take in 2 text boxes titled ‘key’ and ‘value’  - This is same as the UI for 
 adding Tags to a resource like network
 2) After adding one pair, UI can show the option to add another key-value 
 detail
 3) UI can then send all the key-value pairs in a Map while calling 
 CreateServiceOffering API

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

2013-07-16 Thread Prachi Damle (JIRA)


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

Prachi Damle closed CLOUDSTACK-2777.



This issue has been fixed and EC2 SOAP calls were verified.

 AWSAPI: build and packaging issue causing EC2 SOAP test failures
 

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


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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error

2013-07-16 Thread ASF subversion and git services (JIRA)

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

Sailaja Mada closed CLOUDSTACK-2927.

Regressed with latest 4.2 master . Reported issue is fixed now.

[root@ec2 bin]# ./ec2-describe-instances
RESERVATION 1ea6fdbd-1c26-428e-a2e5-bb7991282542
fd3eb4f3-f117-40fd-8bd6-6cbd728a481d:dcuser1
INSTANCE1ea6fdbd-1c26-428e-a2e5-bb7991282542
109c7564-f730-453f-9667-80e3abb8df43stopped
Small Instance 2013-07-15T20:06:37+0530AdvZone1
monitoring- 10.1.1.70
TAG instance1ea6fdbd-1c26-428e-a2e5-bb7991282542
[root@ec2 bin]#

Hence closing the bug.

[AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
---

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

Attachments: awsapi.log

Set enable.ec2.api to true.
Register user using cloudstack-aws-api-register.
Make any SOAP API call e.g. ec2-describe-images using ec2 tools.
Output - Server.InternalError: An unexpected error occurred
Attached awsapi.log for log details

[jira] [Commented] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref


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

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

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

CLOUDSTACK-3293. DeleteAccount fails with ConstraintViolation on 
snapshot_store_ref.


 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at

[jira] [Closed] (CLOUDSTACK-1355) Exception when DB upgrade from 4.0.0 to 4.2.0-SNAPSHOT

2013-07-16 Thread gavin lee (JIRA)


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

gavin lee closed CLOUDSTACK-1355.
-


Thanks Rohit. Sorry for the late response. It's ok now.

 Exception when DB upgrade  from 4.0.0 to 4.2.0-SNAPSHOT
 ---

 Key: CLOUDSTACK-1355
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1355
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.2.0
 Environment: osx 10.8.2
 apache-maven-3.0.4
Reporter: gavin lee
Assignee: Rohit Yadav
  Labels: db, upgrade
 Fix For: 4.2.0

   Original Estimate: 48h
  Remaining Estimate: 48h

 Build for DevCloud on master, after pull latest code, run jetty will raise 
 below Exception:
 bash$ mvn -pl client jetty:run
 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:) Grabbing lock to check 
 for database upgrade.
 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:) DB version = 4.0.0 Code 
 Version = 4.2.0-SNAPSHOT
 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:) Database upgrade must be 
 performed from 4.0.0 to 4.2.0-SNAPSHOT
 ERROR [utils.db.ScriptRunner] (main:) Error executing: alter table 
 storage_pool modify id bigint unsigned AUTO_INCREMENT UNIQUE NOT NULL 
 ERROR [utils.db.ScriptRunner] (main:) java.sql.SQLException: Cannot change 
 column 'id': used in a foreign key constraint 
 'fk_storage_pool_details__pool_id' of table 'cloud.storage_pool_details'
 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (main:) Unable to execute 
 upgrade script: 
 /Users/gavin_lee/projects/cs-apache/incubator-cloudstack/client/target/utilities/scripts/db/db/schema-40to410.sql
 java.sql.SQLException: Cannot change column 'id': used in a foreign key 
 constraint 'fk_storage_pool_details__pool_id' of table 
 'cloud.storage_pool_details'
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
   at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:172)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:232)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:357)
   at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
   at 
 org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
   at 
 com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
   at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
   at 
 org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
   at 
 org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:72)
 When apply following work around:
 SET foreign_key_checks = 0; 
 on top of setup/db/db/schema-40to410.sql
 and 
 SET foreign_key_checks = 1; 
 at bottom of setup/db/db/schema-40to410.sql
 Another exception will raise:
 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:) Grabbing lock to check 
 for database upgrade.
 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:) DB version = 4.0.0 Code 
 Version = 4.2.0-SNAPSHOT
 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:) Database upgrade must be 
 performed from 4.0.0 to 4.2.0-SNAPSHOT
 ERROR [utils.db.ScriptRunner] (main:) Error executing: alter table 
 vm_template add image_data_store_id bigint unsigned 
 ERROR [utils.db.ScriptRunner] (main:)

[jira] [Commented] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref

2013-07-16 Thread ASF subversion and git services (JIRA)


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

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

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

CLOUDSTACK-3293. DeleteAccount fails with ConstraintViolation on 
snapshot_store_ref.


 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at

[jira] [Assigned] (CLOUDSTACK-3388) No error message shows when a dedicate operation failed during the creation of a pod/cluster

2013-07-16 Thread Isaac Chiang (JIRA)


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

Isaac Chiang reassigned CLOUDSTACK-3388:


Assignee: Isaac Chiang

 No error message shows when a dedicate operation failed during the creation 
 of a pod/cluster
 

 Key: CLOUDSTACK-3388
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3388
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
 Environment: Master
Reporter: Isaac Chiang
Assignee: Isaac Chiang
  Labels: ui
 Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot-3.png


 There should be a error message when trying to make an explicit dedication to 
 a nonexistent account during the creation of a pod/cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref


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

Likitha Shetty resolved CLOUDSTACK-3293.


Resolution: Fixed

 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:455)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at

[jira] [Resolved] (CLOUDSTACK-3533) [IPv6][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm

2013-07-16 Thread ASF subversion and git services (JIRA)


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

Jayapal Reddy resolved CLOUDSTACK-3533.
---

Resolution: Fixed

 [IPv6][dnsmasq] VM not able get ip from dhcp which is previously assigned to 
 vm
 ---

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


 1. Create a guest network with small ip range (ex: max ips 3)
 2. Deploy VMs utill ip address exhaust.
 3. Now delete the one vm ex: V3 . Here one IP got freed.
 4. deploy new vm Ex: name V4. Now the V4 supposed to get ip address which is 
 release by V3.
 Issue 1:
 V4 is not getting ip address.
 Issue 2:
 1.destroy vm ex: v1 with ipv1.
 2. create a vm ex:v2. v2 got ip address of v1.
 3. Now observe the dhcphosts.txt. It contains the two entries for with same 
 IP.
 edithosts.sh failed to delete entry with ip already in dhcphosts.txt 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3388) No error message shows when a dedicate operation failed during the creation of a pod/cluster

2013-07-16 Thread Isaac Chiang (JIRA)


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

Isaac Chiang commented on CLOUDSTACK-3388:
--

Create a branch: original/ui-dedicatedresources-refactoring for solving the 
issue.

 No error message shows when a dedicate operation failed during the creation 
 of a pod/cluster
 

 Key: CLOUDSTACK-3388
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3388
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
 Environment: Master
Reporter: Isaac Chiang
Assignee: Isaac Chiang
  Labels: ui
 Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot-3.png


 There should be a error message when trying to make an explicit dedication to 
 a nonexistent account during the creation of a pod/cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref


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

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

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

Revert CLOUDSTACK-3293. DeleteAccount fails with ConstraintViolation on 
snapshot_store_ref.

This reverts commit d0955663cf0324afda52765801033f92b94bf52f.


 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at

[jira] [Reopened] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref

2013-07-16 Thread ASF subversion and git services (JIRA)


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

Likitha Shetty reopened CLOUDSTACK-3293:



 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:455)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at

[jira] [Commented] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref


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

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

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

Revert CLOUDSTACK-3293. DeleteAccount fails with ConstraintViolation on 
snapshot_store_ref.

This reverts commit 22ddc3fa0644b9dae6bbbc6e87d425d11f574f30.


 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at

[jira] [Created] (CLOUDSTACK-3546) [DOC] Updated 4.2 Developer Guide

Radhika Nair created CLOUDSTACK-3546:


 Summary: [DOC] Updated 4.2 Developer Guide
 Key: CLOUDSTACK-3546
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3546
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Affects Versions: 4.1.0
Reporter: Radhika Nair
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3546) [DOC] Update 4.2 Developer Guide


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

Radhika Nair updated CLOUDSTACK-3546:
-

Summary: [DOC] Update 4.2 Developer Guide  (was: [DOC] Updated 4.2 
Developer Guide)

 [DOC] Update 4.2 Developer Guide
 

 Key: CLOUDSTACK-3546
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3546
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.1.0
Reporter: Radhika Nair
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3548) Update Removed API Commands

Radhika Nair created CLOUDSTACK-3548:


 Summary: Update Removed API Commands
 Key: CLOUDSTACK-3548
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3548
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Radhika Nair
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3547) Update Added API Commands

Radhika Nair created CLOUDSTACK-3547:


 Summary: Update Added API Commands
 Key: CLOUDSTACK-3547
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3547
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Reporter: Radhika Nair
Assignee: Radhika Nair
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3549) Update Remove API Commands

Radhika Nair created CLOUDSTACK-3549:


 Summary: Update Remove API Commands
 Key: CLOUDSTACK-3549
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3549
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Radhika Nair
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3550) Create What' New in 4.2 Section

2013-07-16 Thread ASF subversion and git services (JIRA)

Radhika Nair created CLOUDSTACK-3550:


 Summary: Create What' New in 4.2 Section
 Key: CLOUDSTACK-3550
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3550
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Radhika Nair
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3547) Update Added API Commands


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

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

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

CLOUDSTACK-3547


 Update Added API Commands
 -

 Key: CLOUDSTACK-3547
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3547
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Reporter: Radhika Nair
Assignee: Radhika Nair
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-2862) CS AWSAPI SOAP calls fail with NPE


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

Sailaja Mada closed CLOUDSTACK-2862.



Regressed with 4.2 branch build.  Issue is fixed now .


[root@ec2 bin]# ./ec2-describe-images
IMAGE   109c7564-f730-453f-9667-80e3abb8df43/CentOS5.3  
available   public  machine
BLOCKDEVICEMAPPING  0
TAG image   109c7564-f730-453f-9667-80e3abb8df43
IMAGE   8ffd90c2-45d7-4ecd-8cf2-3d5910364d93/Centos6_2  
available   public  machine
BLOCKDEVICEMAPPING  0
TAG image   8ffd90c2-45d7-4ecd-8cf2-3d5910364d93
[
root@ec2 bin]# ./ec2-describe-tags

[root@ec2 bin]# ./ec2-describe-instances
RESERVATION 1ea6fdbd-1c26-428e-a2e5-bb7991282542
fd3eb4f3-f117-40fd-8bd6-6cbd728a481d:dcuser1
INSTANCE1ea6fdbd-1c26-428e-a2e5-bb7991282542
109c7564-f730-453f-9667-80e3abb8df43stopped 
Small Instance  2013-07-15T20:06:37+0530AdvZone1
 monitoring- 10.1.1.70
TAG instance1ea6fdbd-1c26-428e-a2e5-bb7991282542

[root@ec2 bin]# ./ec2-describe-snapshots
SNAPSHOTee182500-a52c-4668-8616-22ecdd8e5145
6688fd4c-939c-41e6-9ab2-01351d25d583error   2013-07-15T20:45:12+0530
0%  fd3eb4f3-f117-40fd-8bd6-6cbd728a481d:dcuser10   
dcuser1i1_ROOT-9_20130715151512
TAG snapshotee182500-a52c-4668-8616-22ecdd8e5145

[root@ec2 bin]# ./ec2-describe-availability-zones
AVAILABILITYZONEAdvZone1available   Enabled
[root@ec2 bin]#


Hence closing the bug. 


 CS AWSAPI SOAP calls fail with NPE
 --

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


 Enable ec2 api flag. Use EC2 API Soap tool to run 
 ec2-describe-availability-zones. 
 Ouput - Server:unknown
 Contents of awsapi.log -
 2013-05-28 15:53:53,127 WARN  [controller.s3.ServiceProvider] 
 (catalina-exec-int-6:null) Unhandled exception null 
 java.lang.reflect.InvocationTargetException
 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 
 com.cloud.bridge.service.controller.s3.ServiceProvider$2.invoke(ServiceProvider.java:356)
 at $Proxy67.describeAvailabilityZones(Unknown Source)
 at 
 com.cloud.bridge.service.EC2SoapService.describeAvailabilityZones(EC2SoapService.java:230)
 at 
 com.amazon.ec2.AmazonEC2MessageReceiverInOut.invokeBusinessLogic(AmazonEC2MessageReceiverInOut.java:874)
 at 
 org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
 at 
 org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
 at 
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
 at 
 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 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.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
 at 
 org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
 at 
 org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
 at 
 org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
 at 
 com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:114)
 at 
 com.cloud.bridge.service.EC2MainServlet.doPost(EC2MainServlet.java:89)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at

[jira] [Created] (CLOUDSTACK-3551) scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling VM

prashant kumar mishra created CLOUDSTACK-3551:
-

 Summary: scaling up VM from small SO to a SO (with 2 GB RAM) is 
failing ; Unable to scale vm due to Catch exception 
com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-10-VM due to 
MEMORY_CONSTRAINT_VIOLATIONMemory
 Key: CLOUDSTACK-3551
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3551
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.2.0
 Environment: hypervisor :Xen 6.1
Reporter: prashant kumar mishra
Priority: Critical
 Fix For: 4.2.0


Steps to reproduce
-
1-prepare a CS setup with xen server(6.1)
2-Deploy a vm with small service offering (cpu=500,RAM=512)
3-create a SO say mem2 (cpu=500 or 1000 and RAM=2048)
4-scaleup vm from small SO to mem2

Expected
-
Scale up vm should be successful

Actual
---
Scaling up failed 

My observation 
--
- if i try to scale up to a SO (RAM=1.5 GB)  ( successful) 
i see minRam:1610612736,maxRam:1610612736,

-for scale up to a SO (RAM= 2GB)
 i see minRam:2147483648,maxRam:-2147483648,  (overflow)






Logs:
---
h overprovisioning: 9576; new used:2500, reserved:0; requested 
cpu:1000,alloc_from_last:false
2013-07-16 10:06:31,146 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) RAM STATS 
after allocation: for host: 1, old used: 1476395008, old reserved: 0, total: 
16190156800; new used: 3623878656, reserved: 0; requested mem: 
2147483648,alloc_from_last:false
2013-07-16 10:06:31,160 DEBUG [agent.transport.Request] (Job-Executor-9:job-47 
= [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 1-1237451203: Sending  { Cmd , 
MgmtId: 7635042566263, via: 1, Ver: v1, Flags: 100111, 
[{com.cloud.agent.api.ScaleVmCommand:{vm:{id:1,name:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:true},vmName:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,wait:0}}]
 }
2013-07-16 10:06:31,161 DEBUG [agent.transport.Request] (Job-Executor-9:job-47 
= [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 1-1237451203: Executing:  { Cmd 
, MgmtId: 7635042566263, via: 1, Ver: v1, Flags: 100111, 
[{com.cloud.agent.api.ScaleVmCommand:{vm:{id:1,name:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:true},vmName:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,wait:0}}]
 }
2013-07-16 10:06:31,162 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-350:null) Seq 1-1237451203: Executing request
2013-07-16 10:06:31,202 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-1:null) Ping from 3
2013-07-16 10:06:31,364 DEBUG [xen.resource.CitrixResourceBase] 
(DirectAgent-350:null) Catch exception 
com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-10-VM due to 
MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min â¤ 
dynamic_min â¤ dynamic_max â¤ static_max
2013-07-16 10:06:31,364 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-350:null) Seq 1-1237451203: Response Received:
2013-07-16 10:06:31,365 DEBUG [agent.transport.Request] (DirectAgent-350:null) 
Seq 1-1237451203: Processing:  { Ans: , MgmtId: 7635042566263, via: 1, Ver: v1, 
Flags: 110, 
[{com.cloud.agent.api.ScaleVmAnswer:{result:false,details:Catch 
exception com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-10-VM 
due to MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min â¤ 
dynamic_min â¤ dynamic_max â¤ static_max,wait:0}}] }
2013-07-16 10:06:31,366 DEBUG [agent.transport.Request] (Job-Executor-9:job-47 
= [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 1-1237451203: Received:  { Ans: 
, MgmtId: 7635042566263, via: 1, Ver: v1, Flags: 110, { ScaleVmAnswer } }
2013-07-16 10:06:31,366 ERROR [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Unable to 
scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when 
scaling VM:i-2-10-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory limits must 
satisfy: static_min â¤ dynamic_min â¤ dynamic_max â¤ static_max
2013-07-16 10:06:31,371 DEBUG [agent.manager.AgentAttache] 
(DirectAgent-350:null) Seq 1-1237451203: No more commands found
2013-07-16 10:06:31,382 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Hosts's 
actual total CPU: 9576 and CPU after applying overprovisioning: 9576
2013-07-16 10:06:31,383 DEBUG [cloud.capacity.CapacityManagerImpl]

[jira] [Updated] (CLOUDSTACK-3551) scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling VM


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

prashant kumar mishra updated CLOUDSTACK-3551:
--

Attachment: XEN_MS_DB.rar

 scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to 
 scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException 
 when scaling VM:i-2-10-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory
 

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

 Attachments: XEN_MS_DB.rar


 Steps to reproduce
 -
 1-prepare a CS setup with xen server(6.1)
 2-Deploy a vm with small service offering (cpu=500,RAM=512)
 3-create a SO say mem2 (cpu=500 or 1000 and RAM=2048)
 4-scaleup vm from small SO to mem2
 Expected
 -
 Scale up vm should be successful
 Actual
 ---
 Scaling up failed 
 My observation 
 --
 - if i try to scale up to a SO (RAM=1.5 GB)  ( successful) 
 i see minRam:1610612736,maxRam:1610612736,
 -for scale up to a SO (RAM= 2GB)
  i see minRam:2147483648,maxRam:-2147483648,  (overflow)
 Logs:
 ---
 h overprovisioning: 9576; new used:2500, reserved:0; requested 
 cpu:1000,alloc_from_last:false
 2013-07-16 10:06:31,146 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) RAM STATS 
 after allocation: for host: 1, old used: 1476395008, old reserved: 0, total: 
 16190156800; new used: 3623878656, reserved: 0; requested mem: 
 2147483648,alloc_from_last:false
 2013-07-16 10:06:31,160 DEBUG [agent.transport.Request] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 
 1-1237451203: Sending  { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1, Flags: 
 100111, 
 [{com.cloud.agent.api.ScaleVmCommand:{vm:{id:1,name:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:true},vmName:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,wait:0}}]
  }
 2013-07-16 10:06:31,161 DEBUG [agent.transport.Request] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 
 1-1237451203: Executing:  { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1, 
 Flags: 100111, 
 [{com.cloud.agent.api.ScaleVmCommand:{vm:{id:1,name:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:true},vmName:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,wait:0}}]
  }
 2013-07-16 10:06:31,162 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-350:null) Seq 1-1237451203: Executing request
 2013-07-16 10:06:31,202 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-1:null) Ping from 3
 2013-07-16 10:06:31,364 DEBUG [xen.resource.CitrixResourceBase] 
 (DirectAgent-350:null) Catch exception 
 com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-10-VM due to 
 MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min â¤ 
 dynamic_min â¤ dynamic_max â¤ static_max
 2013-07-16 10:06:31,364 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-350:null) Seq 1-1237451203: Response Received:
 2013-07-16 10:06:31,365 DEBUG [agent.transport.Request] 
 (DirectAgent-350:null) Seq 1-1237451203: Processing:  { Ans: , MgmtId: 
 7635042566263, via: 1, Ver: v1, Flags: 110, 
 [{com.cloud.agent.api.ScaleVmAnswer:{result:false,details:Catch 
 exception com.xensource.xenapi.Types$XenAPIException when scaling 
 VM:i-2-10-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: 
 static_min â¤ dynamic_min â¤ dynamic_max â¤ static_max,wait:0}}] }
 2013-07-16 10:06:31,366 DEBUG [agent.transport.Request] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 
 1-1237451203: Received:  { Ans: , MgmtId: 7635042566263, via: 1, Ver: v1, 
 Flags: 110, { ScaleVmAnswer } }
 2013-07-16 10:06:31,366 ERROR [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Unable to 
 scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException 
 when scaling VM:i-2-10-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory limits 
 must

[jira] [Closed] (CLOUDSTACK-2085) VM weight on xen remain same as before vmscaleup ;because Add-To-VCPUs-Params-Live.sh is not getting copied on xs host

2013-07-16 Thread ASF subversion and git services (JIRA)


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

prashant kumar mishra closed CLOUDSTACK-2085.
-


passed

 VM weight on xen remain same as before vmscaleup ;because 
 Add-To-VCPUs-Params-Live.sh is not getting copied  on xs host
 -

 Key: CLOUDSTACK-2085
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2085
 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: prashant kumar mishra
Assignee: Harikrishna Patnala
Priority: Critical
 Fix For: 4.2.0


 Hypervisor Xen 
 Commit 2057221f4f1fd5afde422b367fc416d4e44275cb
 VM weight on xen is not getting changed after scaleup
 Step to reproduce
 
 1-Deployed a vm with service offering small instance (weight on xen 52) ,
 2-Scaled up vm to service offering medium instance 
 Expected
 -
 after scale up  VM should get weight according to new service offering
 Actual
 -
 VM weight remain same as before scale up
 Work around
 ---
  copy script Add-To-VCPUs-Params-Live.sh to /opt/xensource/bin   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref


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

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

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

CLOUDSTACK-3293. DeleteAccount fails with ConstraintViolation on 
snapshot_store_ref.


 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at

[jira] [Commented] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref

2013-07-16 Thread ASF subversion and git services (JIRA)


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

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

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

CLOUDSTACK-3293. DeleteAccount fails with ConstraintViolation on 
snapshot_store_ref.


 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at

[jira] [Resolved] (CLOUDSTACK-3293) [Automation] DeleteAccount fails with ConstraintViolation on snapshot_store_ref

2013-07-16 Thread ASF subversion and git services (JIRA)


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

Likitha Shetty resolved CLOUDSTACK-3293.


Resolution: Fixed

 [Automation] DeleteAccount fails with ConstraintViolation on 
 snapshot_store_ref
 ---

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


 The following issue was encountered when deleting accounts:
 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd 
 for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]
 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] 
 (706873057@qtp-20348362-3:null) ===END===  127.0.0.1 -- GET  
 signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3DapiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNwcommand=queryAsyncJobResultresponse=jsonjobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b
 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed 
 account 28
 2013-06-30 13:38:49,053 WARN  [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to delete all snapshot for volume 47 on secondary storage 
 nfs://10.147.28.6:/export/home/sandbox/secondary
 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) 
 unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand
 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling 
 back the transaction: Time = 1 Name =  
 -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-30 13:38:49,056 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed 
 to cleanup account Acct[28-test-5E4I97] due to 
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE 
 snapshots.id= 3
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:455)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at

[jira] [Commented] (CLOUDSTACK-2875) VM password is not correct after deployment and resetpassword on KVM


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

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

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

CLOUDSTACK-2875: change runlevel of cloud-passwd-srvr to remove error message 
at systemvm startup


 VM password is not correct after deployment and resetpassword on KVM
 

 Key: CLOUDSTACK-2875
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2875
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
 Environment: CentOS 6.4
Reporter: Wei Zhou
Assignee: Wei Zhou
  Labels: integration-test

 After fixed CLOUDSTACK-2823, the systemvms are running finally.
 A new issue is that I can not log in the VM (Ubuntu 12.04 64bit) as the 
 password is not correct, even after reset password. The IP and hostname are 
 correct in VM.
 systemvm from 
 http://jenkins.cloudstack.org/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-2013-06-04-master-kvm.qcow2.bz2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3552) Domain/Account details are not displayed for the implicitly dedicated hosts neither in UI nor in DB.

2013-07-16 Thread Kiran Koneti (JIRA)

Kiran Koneti created CLOUDSTACK-3552:


 Summary: Domain/Account details are not displayed for the 
implicitly dedicated hosts neither in UI nor in DB.
 Key: CLOUDSTACK-3552
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3552
 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: Kiran Koneti
Priority: Critical
 Fix For: 4.2.0


When a host is implicitly dedicated to an domain/account then the dedication 
details for that particular account is not recorded neither in DB nor in UI.

The op_host_planner_reservation; shows the details as of weather a host is 
dedicated or not but it doesn't make a note of to which account it is dedicated 
.

The op_host_planner_reservation; table details are as below:

mysql select * from op_host_planner_reservation;
+++++-++
| id | data_center_id | pod_id | cluster_id | host_id | resource_usage |
+++++-++
|  1 |  1 |  1 |  1 |   1 | Shared |
+++++-++
1 row in set (0.00 sec)

This will be an issue when the number of accounts and hosts in the setup 
increases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-3551) scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling V

2013-07-16 Thread Harikrishna Patnala (JIRA)


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

Harikrishna Patnala reassigned CLOUDSTACK-3551:
---

Assignee: Harikrishna Patnala

 scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to 
 scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException 
 when scaling VM:i-2-10-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory
 

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

 Attachments: XEN_MS_DB.rar


 Steps to reproduce
 -
 1-prepare a CS setup with xen server(6.1)
 2-Deploy a vm with small service offering (cpu=500,RAM=512)
 3-create a SO say mem2 (cpu=500 or 1000 and RAM=2048)
 4-scaleup vm from small SO to mem2
 Expected
 -
 Scale up vm should be successful
 Actual
 ---
 Scaling up failed 
 My observation 
 --
 - if i try to scale up to a SO (RAM=1.5 GB)  ( successful) 
 i see minRam:1610612736,maxRam:1610612736,
 -for scale up to a SO (RAM= 2GB)
  i see minRam:2147483648,maxRam:-2147483648,  (overflow)
 Logs:
 ---
 h overprovisioning: 9576; new used:2500, reserved:0; requested 
 cpu:1000,alloc_from_last:false
 2013-07-16 10:06:31,146 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) RAM STATS 
 after allocation: for host: 1, old used: 1476395008, old reserved: 0, total: 
 16190156800; new used: 3623878656, reserved: 0; requested mem: 
 2147483648,alloc_from_last:false
 2013-07-16 10:06:31,160 DEBUG [agent.transport.Request] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 
 1-1237451203: Sending  { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1, Flags: 
 100111, 
 [{com.cloud.agent.api.ScaleVmCommand:{vm:{id:1,name:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:true},vmName:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,wait:0}}]
  }
 2013-07-16 10:06:31,161 DEBUG [agent.transport.Request] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 
 1-1237451203: Executing:  { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1, 
 Flags: 100111, 
 [{com.cloud.agent.api.ScaleVmCommand:{vm:{id:1,name:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:true},vmName:i-2-10-VM,cpus:1,minSpeed:1000,maxSpeed:1000,minRam:2147483648,maxRam:-2147483648,wait:0}}]
  }
 2013-07-16 10:06:31,162 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-350:null) Seq 1-1237451203: Executing request
 2013-07-16 10:06:31,202 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-1:null) Ping from 3
 2013-07-16 10:06:31,364 DEBUG [xen.resource.CitrixResourceBase] 
 (DirectAgent-350:null) Catch exception 
 com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-10-VM due to 
 MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min â¤ 
 dynamic_min â¤ dynamic_max â¤ static_max
 2013-07-16 10:06:31,364 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-350:null) Seq 1-1237451203: Response Received:
 2013-07-16 10:06:31,365 DEBUG [agent.transport.Request] 
 (DirectAgent-350:null) Seq 1-1237451203: Processing:  { Ans: , MgmtId: 
 7635042566263, via: 1, Ver: v1, Flags: 110, 
 [{com.cloud.agent.api.ScaleVmAnswer:{result:false,details:Catch 
 exception com.xensource.xenapi.Types$XenAPIException when scaling 
 VM:i-2-10-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: 
 static_min â¤ dynamic_min â¤ dynamic_max â¤ static_max,wait:0}}] }
 2013-07-16 10:06:31,366 DEBUG [agent.transport.Request] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Seq 
 1-1237451203: Received:  { Ans: , MgmtId: 7635042566263, via: 1, Ver: v1, 
 Flags: 110, { ScaleVmAnswer } }
 2013-07-16 10:06:31,366 ERROR [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-9:job-47 = [ 1ad7dec8-2fbc-4ef5-a748-928a20d047a7 ]) Unable to 
 scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException 
 when scaling VM:i-2-10-VM due to

[jira] [Closed] (CLOUDSTACK-2297) Delete Account/Domain is not updating the resources usage of the parent domain

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

Sailaja Mada closed CLOUDSTACK-2297.

Reported issue is fixed with 4.2. There are issues with delete account when it
has snapshots. That is tracked as a different ticket. Closing this defect.

Delete Account/Domain is not updating the resources usage of the parent domain
--

Key: CLOUDSTACK-2297
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2297
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: Sailaja Mada
Assignee: Sanjay Tripathi
Priority: Critical
Fix For: 4.2.0

Attachments: apilog.log, parentdomainresourcesbeforedelete.png,
ROOTDomainusagebeforedelete.png, useraccountbeforedelete.png

Setup: Advanced Networking Zone, Xen 6.1 , MS- RHEL 6.3
Steps:
1. Create Child domains under ROOT domain
2. Create user/admin accounts under this child domain
3. Deploy one instance as the child Domain user other instance as one more
account.
4. Delete the User
Verify the resources usage
5. Delete the Domain
Verify the resources usage
Observation:
Delete Account/Domain is not updating the resources usage of the parent domain

[jira] [Assigned] (CLOUDSTACK-3500) [Object_Store_Refactor] Deleting snapshots in CS doesn't delete them physically on the secondary storage.

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

Likitha Shetty reassigned CLOUDSTACK-3500:
--

Assignee: Likitha Shetty

[Object_Store_Refactor] Deleting snapshots in CS doesn't delete them
physically on the secondary storage.
--

Key: CLOUDSTACK-3500
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3500
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Snapshot
Affects Versions: 4.2.0
Environment: Primary Storage : iscsii
Secondary Storage : NFS
Hypervisor : Xen 6.2
Build : CS 4.2
Reporter: Abhinav Roy
Assignee: Likitha Shetty
Priority: Critical
Fix For: 4.2.0

Attachments: CS-3500_apilog, CS-3500_DB.sql,
CS-3500_management-server.zip

Steps :
===
1. Create an Advanced networking setup
2. Deploy a VM.
3. Take a snapshot of the ROOT disk of the VM.
4. Delete the snapshot
Expected behaviour :
==
1. After step 3 , a snapshot should be created on CS and also a physical disk
for that snapshot is created on the secondary storage.
2. After step 4, the physical disk created for the snapshot should be deleted
from the secondary storage
Observed behaviour :
=
1. A snapshot does get created on CS and also a physical disk for that
snapshot is created on the secondary storage.
2. But, after deletion of snapshot from CS the physical disk on the secondary
storage is not deleted.

[jira] [Closed] (CLOUDSTACK-2181) Scale down is allowed when one resource(say cpu) is being scale up and other resource (say ram)is being scale down ;but not allowed when both resources are being sc


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

prashant kumar mishra closed CLOUDSTACK-2181.
-


passed

 Scale down is allowed  when  one resource(say cpu) is being scale up and 
 other resource (say ram)is being scale down ;but not allowed when both 
 resources are being scaledown 
 --

 Key: CLOUDSTACK-2181
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2181
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, XenServer
Affects Versions: 4.2.0
Reporter: prashant kumar mishra
Assignee: Harikrishna Patnala
Priority: Minor
 Fix For: 4.2.0

 Attachments: apilog.log, catalina.out, management-server.log, 
 scaleup.png


 Scale down is not allowed as per FS and condition is valid when you try to 
 scale down both resources (cpu and RAM); but not valid when you try to scale 
 up one resource and scale down other resource
 Steps to repo
 --
 1-Deploy a vm with small instance SO
 2-create three service offering say a1, a2 ,a3 (a1{cpu=1 
 GHz,ram=256};a2{cpu=500MGz,ram=512};a3{cpu=300 MGz,ram=256})
 3-try to scaledown to service offering a3 (it will fail with message Only 
 scaling up the vm is supported, new service offering should have both cpu and 
 memory greater than the old values)
 4-Try to scaleup to SO a1(successful)
 5-Try to scaleup to SO a2 from a1(successful)
 Expected
 --
 AS per FS scale down should not be allowed in any case
 Snippet of Log
 ---
 ---
 1-VM details
 --
 2013-04-25 08:50:27,150 DEBUG [agent.transport.Request] 
 (Job-Executor-7:job-171) Seq 5-1339424813: Sending  { Cmd , MgmtId: 
 7635042566263, via: 5, Ver: v1, Flags: 100111, 
 [{StartCommand:{vm:{id:29,name:i-2-29-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:536870912,maxRam:536870912,arch:x86_64,os:CentOS
  5.3 
 (64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,vncPassword:f406158baa072feb,params:{},uuid:3355e0f2-d9c7-4fc1-adad-d6337adea271,disks:[{id:39,name:ROOT-29,mountPoint:/export/home/prashant/asfprime,path:d1e10716-38ec-4d02-b785-6d3c9e381779,size:21474836480,type:ROOT,storagePoolType:NetworkFilesystem,storagePoolUuid:59f08402-b4ed-3a26-9d59-eb04cc22886b,deviceId:0},{id:29,name:CentOS
  5.6(64-bit) no GUI 
 (XenServer),size:0,type:ISO,storagePoolType:ISO,deviceId:3}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:e86fb52c-4e3e-4963-99c9-197038404f25,ip:10.1.1.61,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:73:4c:00:18,dns1:10.103.128.16,broadcastType:Vlan,type:Guest,broadcastUri:vlan://1101,isolationUri:vlan://1101,isSecurityGroupEnabled:false}]},hostIp:10.147.40.8,wait:0}}]
  }
 2013-04-25 08:50:27,153 DEBUG [agent.transport.Request] 
 (Job-Executor-7:job-171) Seq 5-1339424813: Executing:  { Cmd , MgmtId: 
 7635042566263, via: 5, Ver: v1, Flags: 100111, 
 [{StartCommand:{vm:{id:29,name:i-2-29-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:536870912,maxRam:536870912,arch:x86_64,os:CentOS
  5.3 
 (64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,vncPassword:f406158baa072feb,params:{},uuid:3355e0f2-d9c7-4fc1-adad-d6337adea271,disks:[{id:39,name:ROOT-29,mountPoint:/export/home/prashant/asfprime,path:d1e10716-38ec-4d02-b785-6d3c9e381779,size:21474836480,type:ROOT,storagePoolType:NetworkFilesystem,storagePoolUuid:59f08402-b4ed-3a26-9d59-eb04cc22886b,deviceId:0},{id:29,name:CentOS
  5.6(64-bit) no GUI 
 (XenServer),size:0,type:ISO,storagePoolType:ISO,deviceId:3}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:e86fb52c-4e3e-4963-99c9-197038404f25,ip:10.1.1.61,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:73:4c:00:18,dns1:10.103.128.16,broadcastType:Vlan,type:Guest,broadcastUri:vlan://1101,isolationUri:vlan://1101,isSecurityGroupEnabled:false}]},hostIp:10.147.40.8,wait:0}}]
  }
 2013-04-25 08:50:27,154 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-29:null) Seq 5-1339424813: Executing request
 2013-04-25 08:50:27,236 DEBUG [xen.resource.CitrixResourceBase] 
 (DirectAgent-29:null) 1. The VM i-2-29-VM is in Starting state
 2-Scale down(cpu and ram) to a3
 --
 2013-04-25 08:53:37,706 INFO  [cloud.api.ApiServer] (catalina-exec-3:null) 
 Only scaling up the vm is supported, new service offering should have both 
 cpu and memory gre
 3-Scale up cpu and  scale down ram-SO a1
 -
 2013-04-25 08:55:33,229 DEBUG

[jira] [Comment Edited] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

2013-07-16 Thread Nitin Mehta (JIRA)


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

Nitin Mehta edited comment on CLOUDSTACK-1809 at 7/16/13 10:06 AM:
---

This means we are not showing the total capacity for cluster right. I am 
pasting the text from description for clarification. This will lead to vm 
deployment failures. This is a severe issue. The vmware expert needs to fix it 
and ALSO needs to take care of UPGRADE.


For vmware cluster(with only one host) vcenter shows total capacity of 
cluster is (Memory 13431 MB, CPU 7752MHz) which is available for vm deployment 
and cloud stack shows (Memory 15.99 GB, CPU 9572) . 
-Due to this calculation difference CS allocator shows capacity is available 
on host but vm deployment fails with run time error 

  was (Author: nitinme):
This means we are not showing the total capacity for cluster right. I am 
pasting the text from description for clarification. This will lead to vm 
deployment failures. This is a sever issue. The vmware expert needs to fix it 
and ALSO needs to take care of UPGRADE.


For vmware cluster(with only one host) vcenter shows total capacity of 
cluster is (Memory 13431 MB, CPU 7752MHz) which is available for vm deployment 
and cloud stack shows (Memory 15.99 GB, CPU 9572) . 
-Due to this calculation difference CS allocator shows capacity is available 
on host but vm deployment fails with run time error 
  
 Actual capacity availble for vm deployement in vmware cluster is less than 
 what Dashboard shows (total_capacity in op_host_capacity  table)
 ---

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

 Attachments: DB_Logs.rar, screenshot-1.jpg, screenshot-2.jpg


 -For vmware cluster(with only  one host)  vcenter shows total capacity of 
 cluster is (Memory 13431 MB, CPU 7752MHz) which is available for vm 
 deployment and cloud stack shows (Memory 15.99 GB, CPU  9572)  .
 -Due to this calculation difference CS allocator shows capacity is available 
 on host but   vm deployment fails  with run time error 
 2013-06-13 12:23:01,945 WARN  [vmware.resource.VmwareResource] 
 (DirectAgent-141:10.147.40.7) StartCommand failed due to Exception: 
 java.lang.RuntimeException
 Message: The available CPU resources in the parent resource pool are 
 insufficient for the operation.
 java.lang.RuntimeException: The available CPU resources in the parent 
 resource pool are insufficient for the operation.

 DB
 -
 mysql select *from op_host_capacity where capacity_type in (0,1)\G;
 *** 1. row ***
id: 1
   host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
 used_capacity: 6039797760
 reserved_capacity: 0
total_capacity: 17169539072
 capacity_type: 0
capacity_state: Enabled
   update_time: 2013-06-13 15:29:33
   created: 2013-06-05 16:05:51
 *** 2. row ***
id: 2
   host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
 used_capacity: 7700
 reserved_capacity: 0
total_capacity: 9572
 capacity_type: 1
capacity_state: Enabled
   update_time: 2013-06-13 15:29:33
   created: 2013-06-05 16:05:51
 2 rows in set (0.00 sec)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

2013-07-16 Thread Nitin Mehta (JIRA)


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

Nitin Mehta commented on CLOUDSTACK-1809:
-

This means we are not showing the total capacity for cluster right. I am 
pasting the text from description for clarification. This will lead to vm 
deployment failures. This is a sever issue. The vmware expert needs to fix it 
and ALSO needs to take care of UPGRADE.


For vmware cluster(with only one host) vcenter shows total capacity of 
cluster is (Memory 13431 MB, CPU 7752MHz) which is available for vm deployment 
and cloud stack shows (Memory 15.99 GB, CPU 9572) . 
-Due to this calculation difference CS allocator shows capacity is available 
on host but vm deployment fails with run time error 

 Actual capacity availble for vm deployement in vmware cluster is less than 
 what Dashboard shows (total_capacity in op_host_capacity  table)
 ---

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

 Attachments: DB_Logs.rar, screenshot-1.jpg, screenshot-2.jpg


 -For vmware cluster(with only  one host)  vcenter shows total capacity of 
 cluster is (Memory 13431 MB, CPU 7752MHz) which is available for vm 
 deployment and cloud stack shows (Memory 15.99 GB, CPU  9572)  .
 -Due to this calculation difference CS allocator shows capacity is available 
 on host but   vm deployment fails  with run time error 
 2013-06-13 12:23:01,945 WARN  [vmware.resource.VmwareResource] 
 (DirectAgent-141:10.147.40.7) StartCommand failed due to Exception: 
 java.lang.RuntimeException
 Message: The available CPU resources in the parent resource pool are 
 insufficient for the operation.
 java.lang.RuntimeException: The available CPU resources in the parent 
 resource pool are insufficient for the operation.

 DB
 -
 mysql select *from op_host_capacity where capacity_type in (0,1)\G;
 *** 1. row ***
id: 1
   host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
 used_capacity: 6039797760
 reserved_capacity: 0
total_capacity: 17169539072
 capacity_type: 0
capacity_state: Enabled
   update_time: 2013-06-13 15:29:33
   created: 2013-06-05 16:05:51
 *** 2. row ***
id: 2
   host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
 used_capacity: 7700
 reserved_capacity: 0
total_capacity: 9572
 capacity_type: 1
capacity_state: Enabled
   update_time: 2013-06-13 15:29:33
   created: 2013-06-05 16:05:51
 2 rows in set (0.00 sec)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-2184) Failed to scale up number of vcpus;Only scaling up the vm is supported, new service offering should have both cpu and memory greater than the old values


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

prashant kumar mishra closed CLOUDSTACK-2184.
-


tested on xen 6.1 ;

=
Tried scaling up from SO(CPU=1000,vcpu=1,RAM=1024) to SO 
(CPU=1000,vcp=2,RAM=1024) passed.

 Failed to  scale up  number of vcpus;Only scaling up the vm is supported, new 
 service offering should have both cpu and memory greater than the old values
 --

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

 Attachments: access_log.2013-04-25.txt, apilog.log, 
 management-server.log, scaleup.png


 Step to reproduce
 --
 1-Deploy a vm with service offering small instance(vcpu=1,cpu=500,RAM=512)
 2-create a service offering vcpu(vcpu=2,cpu=500,ram=512)
 3-Try to scaleup vm to new service offering vcpu
 Expected
 -
 -scaleup should be successful
 Actual
 
 Scaleup failed  with message  Only scaling up the vm is supported, new 
 service offering should have both cpu and memory greater than the old values
 Snippet of log
 
 2013-04-25 11:53:50,397 INFO  [cloud.api.ApiServer] (catalina-exec-2:null) 
 Only scaling up the vm is supported, new service offering should have both 
 cpu and memory greater than the old values

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3553) [UI]UI remains in the processing state forever when it failed to delete primary storage

Sailaja Mada created CLOUDSTACK-3553:


 Summary: [UI]UI remains in the processing state forever when it 
failed to delete primary storage
 Key: CLOUDSTACK-3553
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3553
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Minor


Steps:

1. Configure Adv zone with VMWARE 
2. Have Primary storage added at the cluster level.
3. Deploy VM's using a new user account 
4. Pu the host into maintenance . There are no other storage pools to migrate 
its volumes 
5.  Tried to delete primary storage when it has volumes 
6. It failed to remove saying 'Cannot delete pool PS1 as there are associated 
non-destroyed vols for this pool' 

Observation :
But UI remains in the processing state forever when it failed to delete primary 
storage (Attached the snap)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3553) [UI]UI remains in the processing state forever when it failed to delete primary storage


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

Sailaja Mada updated CLOUDSTACK-3553:
-

Attachment: storageUI.png

 [UI]UI remains in the processing state forever when it failed to delete 
 primary storage
 ---

 Key: CLOUDSTACK-3553
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3553
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Minor
 Attachments: storageUI.png


 Steps:
 1. Configure Adv zone with VMWARE 
 2. Have Primary storage added at the cluster level.
 3. Deploy VM's using a new user account 
 4. Pu the host into maintenance . There are no other storage pools to migrate 
 its volumes 
 5.  Tried to delete primary storage when it has volumes 
 6. It failed to remove saying 'Cannot delete pool PS1 as there are associated 
 non-destroyed vols for this pool' 
 Observation :
 But UI remains in the processing state forever when it failed to delete 
 primary storage (Attached the snap)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3369) Autoscaling: Deleting an isolated network of an account deletes also the autoscaling rule for a network associated with another account

2013-07-16 Thread Rajesh Battala (JIRA)


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

Rajesh Battala commented on CLOUDSTACK-3369:


Verified on the lastest 4.2 branch, issue is not reproducible. 
Will verify on 4.1 and update the findings.

 Autoscaling: Deleting an isolated network of an account deletes also the 
 autoscaling rule for a network associated with another account
 ---

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

 Hypothesis:
 - Say you have a Network Offering with NetScaler as external load balancer, 
 and you configure it to be shared.
 - Say you have two accounts (A and B), and both have a network using that LB 
 offering
 If you create an autoscaling rule on network associated with account A, and 
 you delete a network associated with account B, it will also delete the 
 autoscaling rule of the network associated with account A.
 To Reproduce:
 - Add a NetScaler, and make it shared (not dedicated)
 - Create a network offering with LB service on the NetScaler
 - Create a network for Account A using the NS network offering
 - Create a network for Account B using the same offering
 - Create an autoscaling rule on network A, and wait until you see VMs spun up 
 by the NS.
 - Spin a VM on network B, and then destroy that VM
 - Delete the Network B
 You should see instances being created with the name VM-Date-NONE.
 Netscaler Logs:
 Jul  4 19:48:36 local0.notice 172.30.100.5 Device 
 server_vip_NSSVC_HTTP_x:80(Cloud-VirtualServer-74.121.246.141-80) - 
 State DOWN
 Jul  4 19:48:36 local0.info 172.30.100.5 User nsroot - Remote_ip 
 172.30.100.15 - Command rm server 
 autoscale-internal_server_Cloud241781113fa541a8aafb46bb45b8a719 - Status 
 Success
 Jul  4 19:48:36 local0.info 172.30.100.5 User nsroot - Remote_ip 
 172.30.100.15 - Command unbind vlan 3654 -ifnum 1/3 -tagged - Status 
 Success
 Jul  4 19:48:36 local0.info 172.30.100.5 User nsroot - Remote_ip 
 172.30.100.15 - Command unbind vlan 3654 -IPAddress 10.3.96.69 
 255.255.240.0 - Status Success
 Jul  4 19:48:36 local0.info 172.30.100.5 User nsroot - Remote_ip 
 172.30.100.15 - Command show ns ip 10.3.96.69 - Status Success
 Jul  4 19:48:36 local0.info 172.30.100.5 Route 
 route(10.3.96.0_255.255.240.0) - State DOWN
 Jul  4 19:48:36 local0.info 172.30.100.5 User nsroot - Remote_ip 
 172.30.100.15 - Command rm ns ip 10.3.96.69 - Status Success
 Jul  4 19:48:36 local0.info 172.30.100.5 User nsroot - Remote_ip 
 172.30.100.15 - Command show vlan 3654 - Status Success
 Jul  4 19:48:36 local0.info 172.30.100.5 User nsroot - Remote_ip 
 172.30.100.15 - Command rm vlan 3654 - Status Success

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2725) [Automation] Re-attaching volume on VM failing in KVM

2013-07-16 Thread Wei Zhou (JIRA)


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

Wei Zhou commented on CLOUDSTACK-2725:
--

Can someone log into the VM , and check if acpiphp module is already loaded?

root@NEW:~# lsmod |grep acpiphp
acpiphp24231  0

if not, please run modprobe acpiphp, and try again

-Wei

 [Automation] Re-attaching volume on VM failing in KVM
 -

 Key: CLOUDSTACK-2725
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.2.0
 Environment: Automation environment KVM 
 Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
Reporter: Rayees Namathponnan
Assignee: Fang Wang
Priority: Blocker
 Fix For: 4.2.0

 Attachments: CLOUDSTACK-2725.rar


 Below two test case failing from BVT 
 integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 
 integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume 
 Steps to reproduce 
 Step 1 : Create an account, service offering, create volume, create VM
 Step 2 : Attach volume to VM , 
 Step 3 : Detach volume
 Step 4 : Attach volume to VM  again 
 Actual result 
 Attachment failed with below error
 2013-05-28 13:45:39,101 DEBUG [agent.transport.Request] 
 (Job-Executor-98:job-1246) Seq 5-258539658: Rec
 eived:  { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, { 
 AttachAnswer } }
 2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-98:job-1246) Unexpected e
 xception while executing 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume: 
 TestDiskServ to VM: ce79edb6-
 a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error 
 unable to execute QEMU comman
 d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
 at 
 com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
 at 
 com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
 t(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
 22)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-05-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-98:job-1246) Complete asy
 nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error 
 text: Failed to attach volume
 : TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e; 
 org.libvirt.LibvirtException: internal erro

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-3552) Domain/Account details are not displayed for the implicitly dedicated hosts neither in UI nor in DB.


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

Devdeep Singh reassigned CLOUDSTACK-3552:
-

Assignee: Devdeep Singh

 Domain/Account details are not displayed for the implicitly dedicated hosts 
 neither in UI nor in DB.
 

 Key: CLOUDSTACK-3552
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3552
 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: Kiran Koneti
Assignee: Devdeep Singh
Priority: Critical
 Fix For: 4.2.0


 When a host is implicitly dedicated to an domain/account then the dedication 
 details for that particular account is not recorded neither in DB nor in UI.
 The op_host_planner_reservation; shows the details as of weather a host is 
 dedicated or not but it doesn't make a note of to which account it is 
 dedicated .
 The op_host_planner_reservation; table details are as below:
 mysql select * from op_host_planner_reservation;
 +++++-++
 | id | data_center_id | pod_id | cluster_id | host_id | resource_usage |
 +++++-++
 |  1 |  1 |  1 |  1 |   1 | Shared |
 +++++-++
 1 row in set (0.00 sec)
 This will be an issue when the number of accounts and hosts in the setup 
 increases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-3552) Domain/Account details are not displayed for the implicitly dedicated hosts neither in UI nor in DB.


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

Devdeep Singh resolved CLOUDSTACK-3552.
---

Resolution: Won't Fix

op_host_planner_reservation table is meant for internal house keeping and it 
doesn't hold the information on who the resource is dedicated too. It is used 
by the deployment planning manager to make sure that when a vm deployment 
request is placed and a dedicated resource isn't asked for; a resource 
explicitly/implicitly dedicated to an account isn't picked up.

When a host is implicitly dedicated the information isn't persisted in the db. 
This is done to make sure when the last instance/vm is removed from the host, 
the host automatically becomes available to the free pool. Right now there 
isn't any use case that requires for information on an implicitly dedicated 
host to be persisted.

 Domain/Account details are not displayed for the implicitly dedicated hosts 
 neither in UI nor in DB.
 

 Key: CLOUDSTACK-3552
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3552
 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: Kiran Koneti
Assignee: Devdeep Singh
Priority: Critical
 Fix For: 4.2.0


 When a host is implicitly dedicated to an domain/account then the dedication 
 details for that particular account is not recorded neither in DB nor in UI.
 The op_host_planner_reservation; shows the details as of weather a host is 
 dedicated or not but it doesn't make a note of to which account it is 
 dedicated .
 The op_host_planner_reservation; table details are as below:
 mysql select * from op_host_planner_reservation;
 +++++-++
 | id | data_center_id | pod_id | cluster_id | host_id | resource_usage |
 +++++-++
 |  1 |  1 |  1 |  1 |   1 | Shared |
 +++++-++
 1 row in set (0.00 sec)
 This will be an issue when the number of accounts and hosts in the setup 
 increases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-3513) [Automation] Failed to copy iso and template between zones


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

Jayapal Reddy reassigned CLOUDSTACK-3513:
-

Assignee: (was: Jayapal Reddy)

 [Automation] Failed to copy iso and template between zones
 --

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

 Attachments: CLOUDSTACK-3513.rar


 bvt test cases failed 
 1) integration.smoke.test_templates.TestTemplates.test_06_copy_template
 2) integration.smoke.test_iso.TestISO.test_06_copy_iso
 Steps to reproduce 
 1) Register ISO 
 2) copy ISO to another zone
 3) iso not getting copied to second zone, 
 i didnt observe any error in ms log, please see the attached log.
 Job 220
 i didnt see any response (job 220) even after 5 minute
 2013-07-13 02:52:00,982 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]) 
 Executing org.apache.cloudstack.api.command.user.iso.Cop
 yIsoCmd for job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]
 2013-07-13 02:52:00,985 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-9:null) submit async job-220 = [ 
 ccea3738-731d-4745-bdd0-5d81bbf126b6 ], details: AsyncJobVO {id:220, userId: 2
 , accountId: 2, sessionKey: null, instanceType: Template, instanceId: 209, 
 cmd: org.apache.cloudstack.api.command.user.iso.CopyIsoCmd, cmdOriginator: 
 null, cmdInfo: {id:b1106f0c-d183-4c75
 -99ae-02993d3a91c7,response:json,sessionkey:blwF0jxkh/BXBlAaOW4fzjITizc\u003d,destzoneid:cfd13d3f-38dd-4ccf-baea-dc5d859dbdea,cmdEventType:TEMPLATE.COPY,ctxUserId:2,htt
 pmethod:GET,_:1373698373159,ctxAccountId:2,sourcezoneid:b76325a6-71dc-486d-98cd-346ea1c3a511,ctxStartEventId:915},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, s
 tatus: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 
 29066118877352, completeMsid: null, lastUpdated: null, lastPolled: null, 
 created: null}
 2013-07-13 02:52:00,988 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null) 
 ===END===  10.216.51.171 -- GET  
 command=copyIsoid=b1106f0c-d183-4c75-99ae-02993d3a91c7sourcezoneid=b76325a6-71d
 c-486d-98cd-346ea1c3a511destzoneid=cfd13d3f-38dd-4ccf-baea-dc5d859dbdearesponse=jsonsessionkey=blwF0jxkh%2FBXBlAaOW4fzjITizc%3D_=1373698373159
 2013-07-13 02:52:01,010 DEBUG [storage.image.TemplateDataFactoryImpl] 
 (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]) 
 template 209 is not in store:2, type:Image
 2013-07-13 02:52:01,035 DEBUG [agent.transport.Request] 
 (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]) Seq 
 10-544932010: Sending  { Cmd , MgmtId: 29066118877352, via: 10, Ver: v1, 
 Flags: 100011, 
 [{org.apache.cloudstack.storage.command.DownloadCommand:{hvm:true,description:test,checksum:b11099d68763f87ee90eab7af1d4dd1e,maxDownloadSizeInBytes:53687091200,id:209,resourceType:TEMPLATE,installPath:template/tmpl/2/209,_store:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary3,_role:Image}},url:http://people.apache.org/~tsp/dummy.iso,format:ISO,accountId:2,name:209-2-f327a840-fc0b-3784-b292-b04cf483c01e,secUrl:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary3,wait:0}}]
  }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3513) [Automation] Failed to copy iso and template between zones


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

Jayapal Reddy commented on CLOUDSTACK-3513:
---

looked at the logs. The copyIsoCmd got executed and ISO copied successfully. 
Due to some reason the async job not returned result.

2013-07-13 02:52:04,279 DEBUG [agent.transport.Request] 
(AgentManager-Handler-9:null) Seq 10-544932010: Processing:  { Ans: , MgmtId: 
29066118877352, via: 10, Ver: v1, Flags: 10, 
[{com.cloud.agent.api.storage.DownloadAnswer:{jobId:cc1f16b9-abb6-4129-ab6b-0f9b816481b5,downloadPct:100,errorString:Install
 completed successfully at 7/13/13 1:53 
PM,downloadStatus:DOWNLOADED,downloadPath:/mnt/SecStorage/b3d8be18-cb6f-3033-bb2c-88e079d0ff31/template/tmpl/2/209/dnld2066499795727855873tmp_,installPath:template/tmpl/2/209/209-2-f327a840-fc0b-3784-b292-b04cf483c01e.iso,templateSize:360448,templatePhySicalSize:360448,checkSum:b11099d68763f87ee90eab7af1d4dd1e,result:true,details:Install
 completed successfully at 7/13/13 1:53 PM,wait:0}}] }


 [Automation] Failed to copy iso and template between zones
 --

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

 Attachments: CLOUDSTACK-3513.rar


 bvt test cases failed 
 1) integration.smoke.test_templates.TestTemplates.test_06_copy_template
 2) integration.smoke.test_iso.TestISO.test_06_copy_iso
 Steps to reproduce 
 1) Register ISO 
 2) copy ISO to another zone
 3) iso not getting copied to second zone, 
 i didnt observe any error in ms log, please see the attached log.
 Job 220
 i didnt see any response (job 220) even after 5 minute
 2013-07-13 02:52:00,982 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]) 
 Executing org.apache.cloudstack.api.command.user.iso.Cop
 yIsoCmd for job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]
 2013-07-13 02:52:00,985 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-9:null) submit async job-220 = [ 
 ccea3738-731d-4745-bdd0-5d81bbf126b6 ], details: AsyncJobVO {id:220, userId: 2
 , accountId: 2, sessionKey: null, instanceType: Template, instanceId: 209, 
 cmd: org.apache.cloudstack.api.command.user.iso.CopyIsoCmd, cmdOriginator: 
 null, cmdInfo: {id:b1106f0c-d183-4c75
 -99ae-02993d3a91c7,response:json,sessionkey:blwF0jxkh/BXBlAaOW4fzjITizc\u003d,destzoneid:cfd13d3f-38dd-4ccf-baea-dc5d859dbdea,cmdEventType:TEMPLATE.COPY,ctxUserId:2,htt
 pmethod:GET,_:1373698373159,ctxAccountId:2,sourcezoneid:b76325a6-71dc-486d-98cd-346ea1c3a511,ctxStartEventId:915},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, s
 tatus: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 
 29066118877352, completeMsid: null, lastUpdated: null, lastPolled: null, 
 created: null}
 2013-07-13 02:52:00,988 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null) 
 ===END===  10.216.51.171 -- GET  
 command=copyIsoid=b1106f0c-d183-4c75-99ae-02993d3a91c7sourcezoneid=b76325a6-71d
 c-486d-98cd-346ea1c3a511destzoneid=cfd13d3f-38dd-4ccf-baea-dc5d859dbdearesponse=jsonsessionkey=blwF0jxkh%2FBXBlAaOW4fzjITizc%3D_=1373698373159
 2013-07-13 02:52:01,010 DEBUG [storage.image.TemplateDataFactoryImpl] 
 (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]) 
 template 209 is not in store:2, type:Image
 2013-07-13 02:52:01,035 DEBUG [agent.transport.Request] 
 (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]) Seq 
 10-544932010: Sending  { Cmd , MgmtId: 29066118877352, via: 10, Ver: v1, 
 Flags: 100011, 
 [{org.apache.cloudstack.storage.command.DownloadCommand:{hvm:true,description:test,checksum:b11099d68763f87ee90eab7af1d4dd1e,maxDownloadSizeInBytes:53687091200,id:209,resourceType:TEMPLATE,installPath:template/tmpl/2/209,_store:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary3,_role:Image}},url:http://people.apache.org/~tsp/dummy.iso,format:ISO,accountId:2,name:209-2-f327a840-fc0b-3784-b292-b04cf483c01e,secUrl:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary3,wait:0}}]
  }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3554) NPE while attaching VMWARE Tools ISO to the instance

Sailaja Mada created CLOUDSTACK-3554:


 Summary: NPE while attaching VMWARE Tools ISO to the instance 
 Key: CLOUDSTACK-3554
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3554
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Blocker


Steps:

1. Configure Adv Zone with VMWARE
2.  Deploy instance with newly added account 
3.  Tried to attach VMWARE tools iso to this instance 

Observation:

It failed with NPE:

2013-07-16 17:22:43,089 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
===START===  10.144.6.19 -- GET  
command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
2013-07-16 17:22:43,146 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-18:null) submit async job-77 = [ 
24362d6b-4eb7-48d0-893a-2ac61fa84d5e ], details: AsyncJobVO {id:77, userId: 8, 
accountId: 8, sessionKey: null, instanceType: None, instanceId: null, cmd: 
org.apache.cloudstack.api.command.user.iso.AttachIsoCmd, cmdOriginator: null, 
cmdInfo: 
{id:e09209bc-4731-4aac-b65e-00aed3540993,response:json,sessionkey:5vYbKOzqMAqkmN9vVQ/695HcVDs\u003d,virtualmachineid:0f7b7a84-2325-4100-817a-e63e216c2b75,cmdEventType:ISO.ATTACH,ctxUserId:8,httpmethod:GET,_:1373975773858,ctxAccountId:8,ctxStartEventId:299},
 cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903, 
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-07-16 17:22:43,149 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
===END===  10.144.6.19 -- GET  
command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
2013-07-16 17:22:43,152 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Executing 
org.apache.cloudstack.api.command.user.iso.AttachIsoCmd for job-77 = [ 
24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]
2013-07-16 17:22:43,186 DEBUG [cloud.user.AccountManagerImpl] 
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by 
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,188 DEBUG [cloud.user.AccountManagerImpl] 
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
VM[User|dc2user1i1] granted to Acct[8-dc2user1] by 
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,192 DEBUG [cloud.user.AccountManagerImpl] 
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by 
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,194 DEBUG [cloud.user.AccountManagerImpl] 
(Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
VM[User|dc2user1i1] granted to Acct[8-dc2user1] by 
DomainChecker_EnhancerByCloudStack_1028f2c
2013-07-16 17:22:43,209 DEBUG [agent.transport.Request] (Job-Executor-18:job-77 
= [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq 4-1669464340: Sending  { Cmd , 
MgmtId: 187767034175903, via: 4, Ver: v1, Flags: 100011, 
[{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
 Tools Installer 
ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
 }
2013-07-16 17:22:43,210 DEBUG [agent.transport.Request] (Job-Executor-18:job-77 
= [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq 4-1669464340: Executing:  { Cmd 
, MgmtId: 187767034175903, via: 4, Ver: v1, Flags: 100011, 
[{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
 Tools Installer 
ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
 }
2013-07-16 17:22:43,211 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-191:null) Seq 4-1669464340: Executing request
2013-07-16 17:22:43,211 DEBUG [vmware.mo.HostMO] 
(DirectAgent-191:10.102.192.23) find VM i-8-13-VM on host
2013-07-16 17:22:43,211 DEBUG [vmware.mo.HostMO] 
(DirectAgent-191:10.102.192.23) load VM cache on host
2013-07-16 17:22:43,221 ERROR [storage.resource.VmwareStorageProcessor] 
(DirectAgent-191:10.102.192.23) AttachIsoCommand(attach) failed due to 
Exception: java.lang.NullPointerException

[jira] [Updated] (CLOUDSTACK-3554) NPE while attaching VMWARE Tools ISO to the instance


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

Sailaja Mada updated CLOUDSTACK-3554:
-

Fix Version/s: 4.2.0

 NPE while attaching VMWARE Tools ISO to the instance 
 -

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


 Steps:
 1. Configure Adv Zone with VMWARE
 2.  Deploy instance with newly added account 
 3.  Tried to attach VMWARE tools iso to this instance 
 Observation:
 It failed with NPE:
 2013-07-16 17:22:43,089 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
 ===START===  10.144.6.19 -- GET  
 command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
 2013-07-16 17:22:43,146 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-18:null) submit async job-77 = [ 
 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ], details: AsyncJobVO {id:77, userId: 
 8, accountId: 8, sessionKey: null, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.user.iso.AttachIsoCmd, cmdOriginator: null, 
 cmdInfo: 
 {id:e09209bc-4731-4aac-b65e-00aed3540993,response:json,sessionkey:5vYbKOzqMAqkmN9vVQ/695HcVDs\u003d,virtualmachineid:0f7b7a84-2325-4100-817a-e63e216c2b75,cmdEventType:ISO.ATTACH,ctxUserId:8,httpmethod:GET,_:1373975773858,ctxAccountId:8,ctxStartEventId:299},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-07-16 17:22:43,149 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
 ===END===  10.144.6.19 -- GET  
 command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
 2013-07-16 17:22:43,152 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Executing 
 org.apache.cloudstack.api.command.user.iso.AttachIsoCmd for job-77 = [ 
 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]
 2013-07-16 17:22:43,186 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
 Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by 
 DomainChecker_EnhancerByCloudStack_1028f2c
 2013-07-16 17:22:43,188 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
 VM[User|dc2user1i1] granted to Acct[8-dc2user1] by 
 DomainChecker_EnhancerByCloudStack_1028f2c
 2013-07-16 17:22:43,192 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
 Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by 
 DomainChecker_EnhancerByCloudStack_1028f2c
 2013-07-16 17:22:43,194 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
 VM[User|dc2user1i1] granted to Acct[8-dc2user1] by 
 DomainChecker_EnhancerByCloudStack_1028f2c
 2013-07-16 17:22:43,209 DEBUG [agent.transport.Request] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq 
 4-1669464340: Sending  { Cmd , MgmtId: 187767034175903, via: 4, Ver: v1, 
 Flags: 100011, 
 [{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
  Tools Installer 
 ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
  }
 2013-07-16 17:22:43,210 DEBUG [agent.transport.Request] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq 
 4-1669464340: Executing:  { Cmd , MgmtId: 187767034175903, via: 4, Ver: v1, 
 Flags: 100011, 
 [{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
  Tools Installer 
 ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
  }
 2013-07-16 17:22:43,211 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-191:null) Seq 4-1669464340: Executing request
 2013-07-16 17:22:43,211 DEBUG [vmware.mo.HostMO] 
 (DirectAgent-191:10.102.192.23) find VM i-8-13-VM on host

[jira] [Updated] (CLOUDSTACK-3554) NPE while attaching VMWARE Tools ISO to the instance


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

Sailaja Mada updated CLOUDSTACK-3554:
-

Attachment: management-server.log
apilog.log

 NPE while attaching VMWARE Tools ISO to the instance 
 -

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

 Attachments: apilog.log, management-server.log


 Steps:
 1. Configure Adv Zone with VMWARE
 2.  Deploy instance with newly added account 
 3.  Tried to attach VMWARE tools iso to this instance 
 Observation:
 It failed with NPE:
 2013-07-16 17:22:43,089 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
 ===START===  10.144.6.19 -- GET  
 command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
 2013-07-16 17:22:43,146 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-18:null) submit async job-77 = [ 
 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ], details: AsyncJobVO {id:77, userId: 
 8, accountId: 8, sessionKey: null, instanceType: None, instanceId: null, cmd: 
 org.apache.cloudstack.api.command.user.iso.AttachIsoCmd, cmdOriginator: null, 
 cmdInfo: 
 {id:e09209bc-4731-4aac-b65e-00aed3540993,response:json,sessionkey:5vYbKOzqMAqkmN9vVQ/695HcVDs\u003d,virtualmachineid:0f7b7a84-2325-4100-817a-e63e216c2b75,cmdEventType:ISO.ATTACH,ctxUserId:8,httpmethod:GET,_:1373975773858,ctxAccountId:8,ctxStartEventId:299},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-07-16 17:22:43,149 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
 ===END===  10.144.6.19 -- GET  
 command=attachIsovirtualmachineid=0f7b7a84-2325-4100-817a-e63e216c2b75id=e09209bc-4731-4aac-b65e-00aed3540993response=jsonsessionkey=5vYbKOzqMAqkmN9vVQ%2F695HcVDs%3D_=1373975773858
 2013-07-16 17:22:43,152 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Executing 
 org.apache.cloudstack.api.command.user.iso.AttachIsoCmd for job-77 = [ 
 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]
 2013-07-16 17:22:43,186 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
 Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by 
 DomainChecker_EnhancerByCloudStack_1028f2c
 2013-07-16 17:22:43,188 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
 VM[User|dc2user1i1] granted to Acct[8-dc2user1] by 
 DomainChecker_EnhancerByCloudStack_1028f2c
 2013-07-16 17:22:43,192 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
 Tmpl[200-ISO-vmware-tools.iso granted to Acct[8-dc2user1] by 
 DomainChecker_EnhancerByCloudStack_1028f2c
 2013-07-16 17:22:43,194 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Access to 
 VM[User|dc2user1i1] granted to Acct[8-dc2user1] by 
 DomainChecker_EnhancerByCloudStack_1028f2c
 2013-07-16 17:22:43,209 DEBUG [agent.transport.Request] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq 
 4-1669464340: Sending  { Cmd , MgmtId: 187767034175903, via: 4, Ver: v1, 
 Flags: 100011, 
 [{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
  Tools Installer 
 ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
  }
 2013-07-16 17:22:43,210 DEBUG [agent.transport.Request] 
 (Job-Executor-18:job-77 = [ 24362d6b-4eb7-48d0-893a-2ac61fa84d5e ]) Seq 
 4-1669464340: Executing:  { Cmd , MgmtId: 187767034175903, via: 4, Ver: v1, 
 Flags: 100011, 
 [{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:e09209bc-4731-4aac-b65e-00aed3540993,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
  Tools Installer 
 ISO,name:vmware-tools.iso}},type:ISO},vmName:i-8-13-VM,_storagePort:0,_managed:false,wait:0}}]
  }
 2013-07-16 17:22:43,211 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-191:null) Seq 4-1669464340: Executing request
 2013-07-16

[jira] [Commented] (CLOUDSTACK-2433) Enable rps and rfs support on virtual router.


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

Jayapal Reddy commented on CLOUDSTACK-2433:
---

Please find the below test results for the RPS/RFS.
Created the VR with 4 cores and 1 MB RAM.
netperf command:
 netperf -H 10.146.0.134 -l 60  -n 4

netserver is running two hosts 10.146.0.134 and 10.147.59.206.
From the VR run netperf command to send traffic to two netservers parallel.
With the basic tests I could not see big difference in the results. 
Run the netperf command by changing the various options but in my test setup I 
did not much difference.

With RPS/RFS enable 
==
echo f  /sys/class/net/eth0/queues/rx-0/rps_cpus
echo 256  /proc/sys/net/core/rps_sock_flow_entries
echo 256  /sys/class/net/eth0/queues/rx-0/rps_flow_cnt

TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.147.59.206 
(10.147.59.206) port 0 AF_INET : demo
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.146.0.134 
(10.146.0.134) port 0 AF_INET : demo
Recv   SendSend
Socket Socket  Message  Elapsed
Size   SizeSize Time Throughput
bytes  bytes   bytessecs.10^6bits/sec

 87380  16384  1638460.02 423.40
Recv   SendSend
Socket Socket  Message  Elapsed
Size   SizeSize Time Throughput
bytes  bytes   bytessecs.10^6bits/sec

 87380  16384  1638460.81   8.20


With RPS/RFS DISABLE:
===

TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.146.0.134 
(10.146.0.134) port 0 AF_INET : demo
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.147.59.206 
(10.147.59.206) port 0 AF_INET : demo

root@systemvm:~# Recv   SendSend
Socket Socket  Message  Elapsed
Size   SizeSize Time Throughput
#!/bin/sh
bytes  bytes   bytessecs.10^6bits/sec

 87380  16384  1638460.03 394.06
Recv   SendSend
Socket Socket  Message  Elapsed
Size   SizeSize Time Throughput
bytes  bytes   bytessecs.10^6bits/sec

 87380  16384  1638460.96   8.19


 Enable rps and rfs support on virtual router.
 -

 Key: CLOUDSTACK-2433
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2433
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Devices
Affects Versions: 4.2.0
Reporter: Bharat Kumar
Assignee: Jayapal Reddy
Priority: Blocker
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-3489) Failed to start VR due to error in finalizeStart with KVM hypervisor

2013-07-16 Thread Sanjeev N (JIRA)


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

Sanjeev N resolved CLOUDSTACK-3489.
---

Resolution: Cannot Reproduce

Not able to reproduce the issue. Could be setup issue or might have fixed part 
of the bug fix CLOUDSTACK-3425

 Failed to start VR due to error in finalizeStart with KVM hypervisor
 

 Key: CLOUDSTACK-3489
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3489
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
 Environment: Latest build from ACS 4.2 branch.
 Zone: Advanced with KVM cluster
 Stoarage: S3 and Local storage
Reporter: Sanjeev N
Assignee: Kishan Kavala
 Fix For: 4.2.0

 Attachments: management-server.rar


 Failed to start VR due to error in finalizeStart with KVM hypervisor:
 KVM routing template being used: 
 systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2
 Steps to Reproduce:
 
 1.Bring up CS in advanced zone with KVM cluster 
 2.Use s3 as the secondary storage and Local storage as the primary storage
 3.Use default cent os template to deploy guest vm
 Observations:
 ===
 VR was started as part of vm deployment process and it remained in starting 
 state for a while. However later it was stopped with following exceptions:
 com.cloud.exception.AgentUnavailableException: Resource [Host:4] is 
 unreachable: Host 4: Unable to start instance due to Unable to start 
 VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:944)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3124)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3074)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.cloud.utils.exception.ExecutionException: Unable to start 
 VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911)
 ... 19 more
 2013-07-12 02:38:24,430 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-8:job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ]) Complete 
 async job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ], jobStatus: 2, 
 resultCode: 530, result: Error Code: 530 Error text: Resource [Host:4] is 
 unreachable: Host 4: Unable to start instance due to Unable to start 
 VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
 Few more log snippets from mgmt server log file:
 2013-07-12 02:36:21,128 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-4:null) Seq 4-691668978: Processing:  { Ans: , MgmtId: 
 6615759585382, via: 4, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.StartAnswer:{vm:{id:13,name:r-13-VM,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,arch:x86_64,os:Debian
  GNU/Linux 5.0 (32-bit),bootArgs: template=domP name=r-13-VM 
 eth2ip=10.147.48.5 eth2mask=255.255.255.0 gateway=10.147.48.1 eth0ip=10.1.1.1 
 eth0mask=255.255.255.0 domain=cs2cloud.internal dhcprange=10.1.1.1 
 eth1ip=169.254.1.161 eth1mask=255.255.0.0 type=router disable_rp_filter=true

[jira] [Closed] (CLOUDSTACK-3489) Failed to start VR due to error in finalizeStart with KVM hypervisor

2013-07-16 Thread Sanjeev N (JIRA)


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

Sanjeev N closed CLOUDSTACK-3489.
-


 Failed to start VR due to error in finalizeStart with KVM hypervisor
 

 Key: CLOUDSTACK-3489
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3489
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
 Environment: Latest build from ACS 4.2 branch.
 Zone: Advanced with KVM cluster
 Stoarage: S3 and Local storage
Reporter: Sanjeev N
Assignee: Kishan Kavala
 Fix For: 4.2.0

 Attachments: management-server.rar


 Failed to start VR due to error in finalizeStart with KVM hypervisor:
 KVM routing template being used: 
 systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2
 Steps to Reproduce:
 
 1.Bring up CS in advanced zone with KVM cluster 
 2.Use s3 as the secondary storage and Local storage as the primary storage
 3.Use default cent os template to deploy guest vm
 Observations:
 ===
 VR was started as part of vm deployment process and it remained in starting 
 state for a while. However later it was stopped with following exceptions:
 com.cloud.exception.AgentUnavailableException: Resource [Host:4] is 
 unreachable: Host 4: Unable to start instance due to Unable to start 
 VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:944)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3124)
 at 
 com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3074)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.cloud.utils.exception.ExecutionException: Unable to start 
 VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
 at 
 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911)
 ... 19 more
 2013-07-12 02:38:24,430 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-8:job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ]) Complete 
 async job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ], jobStatus: 2, 
 resultCode: 530, result: Error Code: 530 Error text: Resource [Host:4] is 
 unreachable: Host 4: Unable to start instance due to Unable to start 
 VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
 Few more log snippets from mgmt server log file:
 2013-07-12 02:36:21,128 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-4:null) Seq 4-691668978: Processing:  { Ans: , MgmtId: 
 6615759585382, via: 4, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.StartAnswer:{vm:{id:13,name:r-13-VM,type:DomainRouter,cpus:1,minSpeed:500,maxSpeed:500,minRam:134217728,maxRam:134217728,arch:x86_64,os:Debian
  GNU/Linux 5.0 (32-bit),bootArgs: template=domP name=r-13-VM 
 eth2ip=10.147.48.5 eth2mask=255.255.255.0 gateway=10.147.48.1 eth0ip=10.1.1.1 
 eth0mask=255.255.255.0 domain=cs2cloud.internal dhcprange=10.1.1.1 
 eth1ip=169.254.1.161 eth1mask=255.255.0.0 type=router disable_rp_filter=true

[jira] [Created] (CLOUDSTACK-3555) [VMWARE]Newly registered Templates size is set to zero after download is complete

Sailaja Mada created CLOUDSTACK-3555:


 Summary: [VMWARE]Newly registered Templates size is set to zero  
after download is complete 
 Key: CLOUDSTACK-3555
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3555
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Critical


Steps:

1. Configure Adv Zone with VMWARE 
2.  Register new Cent OS template 
3. Deployed VM using this instance
4. Check the size of the template from template_store_ref table 
5. Check the size of the ROOT disk of the instance which is created using this 
template 

Observations :

1.  Template size is set to 0 for template
2. ROOT disk size is set  to 0 which is created using this template.

Note:
This is not observed with Xenserver 

mysql select * from template_store_ref\G;
*** 1. row ***
id: 3
  store_id: 1
   template_id: 8
   created: 2013-07-15 10:24:22
  last_updated: 2013-07-16 09:31:11
job_id: NULL
  download_pct: 100
  size: 2097152000
store_role: Image
 physical_size: 283761664
download_state: DOWNLOADED
 error_str: NULL
local_path: NULL
  install_path: template/tmpl/1/8/8f42153d-a165-43c2-ad24-7e7328a37e6b.ova
   url: 
http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova
 state: Ready
 destroyed: 0
   is_copy: 0
  update_count: 0
   ref_cnt: 0
   updated: NULL
*** 2. row ***
id: 17
  store_id: 1
   template_id: 204
   created: 2013-07-16 09:31:11
  last_updated: 2013-07-16 09:33:35
job_id: b8b85c0c-12fa-46fb-bd43-2e772b7c86fb
  download_pct: 100
  size: 0
store_role: Image
 physical_size: 0
download_state: DOWNLOADED
 error_str: Install completed successfully at 7/16/13 9:03 AM
local_path: 
/mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/204/dnld6479285553744159047tmp_
  install_path: template/tmpl/2/204/2b8a6845-d031-3d17-927c-ce1dbcb96426.ova
   url: NULL
 state: Ready
 destroyed: 0
   is_copy: 0
  update_count: 3
   ref_cnt: 0
   updated: 2013-07-16 09:33:35
*** 4. row ***
id: 19
  store_id: 1
   template_id: 203
   created: 2013-07-16 09:31:12
  last_updated: 2013-07-16 09:34:16
job_id: 7e1178cf-e9a8-4c8f-b4ad-381b2561250d
  download_pct: 100
  size: 0
store_role: Image
 physical_size: 0
download_state: DOWNLOADED
 error_str: Install completed successfully at 7/16/13 9:04 AM
local_path: 
/mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/203/dnld3848286103866238688tmp_
  install_path: template/tmpl/2/203/9894babd-8cbc-332a-8fc7-609c66834716.ova
   url: NULL
 state: Ready
 destroyed: 0
   is_copy: 0
  update_count: 3
   ref_cnt: 0
   updated: 2013-07-16 09:34:16
*** 5. row ***
id: 20
  store_id: 1
   template_id: 205
   created: 2013-07-16 11:48:23
  last_updated: 2013-07-16 11:55:29
job_id: d49bdb7a-3ea1-4db2-b07b-e35842a23229
  download_pct: 100
  size: 0
store_role: Image
 physical_size: 0
download_state: DOWNLOADED
 error_str: Install completed successfully at 7/16/13 11:25 AM
local_path: 
/mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/205/dnld599624653636661815tmp_
  install_path: template/tmpl/2/205/5573cdd7-94f5-3693-9ec7-7f0f5c341753.ova
   url: NULL
 state: Ready
 destroyed: 0
   is_copy: 0
  update_count: 3
   ref_cnt: 0
   updated: 2013-07-16 11:55:29
5 rows in set (0.00 sec)


ROOT volume:

*** 21. row ***
id: 21
account_id: 8
 domain_id: 6
   pool_id: 7
  last_pool_id: NULL
   instance_id: 13
 device_id: 0
  name: ROOT-13
  uuid: 953256f2-ace0-41d3-a7a5-2c7db77cbeb7
  size: 0
folder: NULL
  path: ROOT-13-21
pod_id: NULL
data_center_id: 1
iscsi_name: NULL
   host_ip: NULL
   volume_type: ROOT
 pool_type: NULL
  disk_offering_id: 1
   template_id: 204
first_snapshot_backup_uuid: NULL
   recreatable: 0
   created: 2013-07-16 11:08:42
  attached: NULL
   updated: 2013-07-16 11:10:45

[jira] [Updated] (CLOUDSTACK-3555) [VMWARE]Newly registered Templates size is set to zero after download is complete


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

Sailaja Mada updated CLOUDSTACK-3555:
-

Attachment: ROOTvolUI.png

 [VMWARE]Newly registered Templates size is set to zero  after download is 
 complete 
 ---

 Key: CLOUDSTACK-3555
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3555
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Critical
 Attachments: ROOTvolUI.png


 Steps:
 1. Configure Adv Zone with VMWARE 
 2.  Register new Cent OS template 
 3. Deployed VM using this instance
 4. Check the size of the template from template_store_ref table 
 5. Check the size of the ROOT disk of the instance which is created using 
 this template 
 Observations :
 1.  Template size is set to 0 for template
 2. ROOT disk size is set  to 0 which is created using this template.
 Note:
 This is not observed with Xenserver 
 mysql select * from template_store_ref\G;
 *** 1. row ***
 id: 3
   store_id: 1
template_id: 8
created: 2013-07-15 10:24:22
   last_updated: 2013-07-16 09:31:11
 job_id: NULL
   download_pct: 100
   size: 2097152000
 store_role: Image
  physical_size: 283761664
 download_state: DOWNLOADED
  error_str: NULL
 local_path: NULL
   install_path: template/tmpl/1/8/8f42153d-a165-43c2-ad24-7e7328a37e6b.ova
url: 
 http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova
  state: Ready
  destroyed: 0
is_copy: 0
   update_count: 0
ref_cnt: 0
updated: NULL
 *** 2. row ***
 id: 17
   store_id: 1
template_id: 204
created: 2013-07-16 09:31:11
   last_updated: 2013-07-16 09:33:35
 job_id: b8b85c0c-12fa-46fb-bd43-2e772b7c86fb
   download_pct: 100
   size: 0
 store_role: Image
  physical_size: 0
 download_state: DOWNLOADED
  error_str: Install completed successfully at 7/16/13 9:03 AM
 local_path: 
 /mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/204/dnld6479285553744159047tmp_
   install_path: template/tmpl/2/204/2b8a6845-d031-3d17-927c-ce1dbcb96426.ova
url: NULL
  state: Ready
  destroyed: 0
is_copy: 0
   update_count: 3
ref_cnt: 0
updated: 2013-07-16 09:33:35
 *** 4. row ***
 id: 19
   store_id: 1
template_id: 203
created: 2013-07-16 09:31:12
   last_updated: 2013-07-16 09:34:16
 job_id: 7e1178cf-e9a8-4c8f-b4ad-381b2561250d
   download_pct: 100
   size: 0
 store_role: Image
  physical_size: 0
 download_state: DOWNLOADED
  error_str: Install completed successfully at 7/16/13 9:04 AM
 local_path: 
 /mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/203/dnld3848286103866238688tmp_
   install_path: template/tmpl/2/203/9894babd-8cbc-332a-8fc7-609c66834716.ova
url: NULL
  state: Ready
  destroyed: 0
is_copy: 0
   update_count: 3
ref_cnt: 0
updated: 2013-07-16 09:34:16
 *** 5. row ***
 id: 20
   store_id: 1
template_id: 205
created: 2013-07-16 11:48:23
   last_updated: 2013-07-16 11:55:29
 job_id: d49bdb7a-3ea1-4db2-b07b-e35842a23229
   download_pct: 100
   size: 0
 store_role: Image
  physical_size: 0
 download_state: DOWNLOADED
  error_str: Install completed successfully at 7/16/13 11:25 AM
 local_path: 
 /mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/205/dnld599624653636661815tmp_
   install_path: template/tmpl/2/205/5573cdd7-94f5-3693-9ec7-7f0f5c341753.ova
url: NULL
  state: Ready
  destroyed: 0
is_copy: 0
   update_count: 3
ref_cnt: 0
updated: 2013-07-16 11:55:29
 5 rows in set (0.00 sec)
 ROOT volume:
 *** 21. row ***
 id: 21
 account_id: 8
  domain_id: 6
pool_id: 7
   last_pool_id: NULL
instance_id: 13
  device_id: 0
   name: ROOT-13
   uuid: 953256f2-ace0-41d3-a7a5-2c7db77cbeb7
   size: 0
 folder: NULL
   path: ROOT-13-21
 pod_id: NULL
 data_center_id: 1

[jira] [Updated] (CLOUDSTACK-3543) the cpvm and ssvm' state is still running when the node was crashed


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

terryye updated CLOUDSTACK-3543:


Summary: the cpvm and ssvm' state is still running when the node was 
crashed  (was: the cpvm and ssvm can not start ,the state is still starting )

 the cpvm and ssvm' state is still running when the node was crashed
 ---

 Key: CLOUDSTACK-3543
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3543
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Management Server
Affects Versions: 4.1.0
 Environment: Ubuntu12.04
Reporter: terryye
   Original Estimate: 96h
  Remaining Estimate: 96h

 When the host node crash the vm'state can not be get right state. the vm 
 state is still running.
 2013-07-16 11:18:41,187 DEBUG [cloud.server.StatsCollector] 
 (StatsCollector-2:null) HostStatsCollector is running...
 2013-07-16 11:18:41,791 DEBUG [agent.transport.Request] 
 (StatsCollector-2:null) Seq 5-1056112658: Received:  { Ans: , MgmtId: 
 52242977168, via: 5, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
 2013-07-16 11:18:55,483 DEBUG [cloud.server.StatsCollector] 
 (StatsCollector-1:null) VmStatsCollector is running...
 2013-07-16 11:19:01,137 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-8:null) Ping from 5

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3556) Add NIC icon is not appearing in UI

2013-07-16 Thread Raafat Mhamed (JIRA)


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

Raafat Mhamed updated CLOUDSTACK-3556:
--

Description: 
After upgrading from version 4.0.2 to version 4.1 ,I can't see the ADD NIC icon 
from interface tab.
check image |http://postimg.org/image/ekb5olse9/


  was:
After upgrading from version 4.0.2 to version 4.1 ,I can't see the ADD NIC icon 
from interface tab.
check image [Here |http://postimg.org/image/ekb5olse9/]



 Add NIC icon is not appearing in UI
 ---

 Key: CLOUDSTACK-3556
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3556
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, UI
Affects Versions: 4.1.0
 Environment: Ubuntu (KVM)
Reporter: Raafat Mhamed
Priority: Minor

 After upgrading from version 4.0.2 to version 4.1 ,I can't see the ADD NIC 
 icon from interface tab.
 check image |http://postimg.org/image/ekb5olse9/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-3556) Add NIC icon is not appearing in UI

2013-07-16 Thread Raafat Mhamed (JIRA)

Raafat Mhamed created CLOUDSTACK-3556:
-

 Summary: Add NIC icon is not appearing in UI
 Key: CLOUDSTACK-3556
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3556
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: KVM, UI
Affects Versions: 4.1.0
 Environment: Ubuntu (KVM)
Reporter: Raafat Mhamed
Priority: Minor


After upgrading from version 4.0.2 to version 4.1 ,I can't see the ADD NIC icon 
from interface tab.
check image [Here |http://postimg.org/image/ekb5olse9/]


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3555) [VMWARE]Newly registered Templates size is set to zero after download is complete


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

Sailaja Mada updated CLOUDSTACK-3555:
-

Attachment: management-server.log
cloud-backup.dmp
apilog.log
templateUI.png

 [VMWARE]Newly registered Templates size is set to zero  after download is 
 complete 
 ---

 Key: CLOUDSTACK-3555
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3555
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Critical
 Attachments: apilog.log, cloud-backup.dmp, management-server.log, 
 ROOTvolUI.png, templateUI.png


 Steps:
 1. Configure Adv Zone with VMWARE 
 2.  Register new Cent OS template 
 3. Deployed VM using this instance
 4. Check the size of the template from template_store_ref table 
 5. Check the size of the ROOT disk of the instance which is created using 
 this template 
 Observations :
 1.  Template size is set to 0 for template
 2. ROOT disk size is set  to 0 which is created using this template.
 Note:
 This is not observed with Xenserver 
 mysql select * from template_store_ref\G;
 *** 1. row ***
 id: 3
   store_id: 1
template_id: 8
created: 2013-07-15 10:24:22
   last_updated: 2013-07-16 09:31:11
 job_id: NULL
   download_pct: 100
   size: 2097152000
 store_role: Image
  physical_size: 283761664
 download_state: DOWNLOADED
  error_str: NULL
 local_path: NULL
   install_path: template/tmpl/1/8/8f42153d-a165-43c2-ad24-7e7328a37e6b.ova
url: 
 http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova
  state: Ready
  destroyed: 0
is_copy: 0
   update_count: 0
ref_cnt: 0
updated: NULL
 *** 2. row ***
 id: 17
   store_id: 1
template_id: 204
created: 2013-07-16 09:31:11
   last_updated: 2013-07-16 09:33:35
 job_id: b8b85c0c-12fa-46fb-bd43-2e772b7c86fb
   download_pct: 100
   size: 0
 store_role: Image
  physical_size: 0
 download_state: DOWNLOADED
  error_str: Install completed successfully at 7/16/13 9:03 AM
 local_path: 
 /mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/204/dnld6479285553744159047tmp_
   install_path: template/tmpl/2/204/2b8a6845-d031-3d17-927c-ce1dbcb96426.ova
url: NULL
  state: Ready
  destroyed: 0
is_copy: 0
   update_count: 3
ref_cnt: 0
updated: 2013-07-16 09:33:35
 *** 4. row ***
 id: 19
   store_id: 1
template_id: 203
created: 2013-07-16 09:31:12
   last_updated: 2013-07-16 09:34:16
 job_id: 7e1178cf-e9a8-4c8f-b4ad-381b2561250d
   download_pct: 100
   size: 0
 store_role: Image
  physical_size: 0
 download_state: DOWNLOADED
  error_str: Install completed successfully at 7/16/13 9:04 AM
 local_path: 
 /mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/203/dnld3848286103866238688tmp_
   install_path: template/tmpl/2/203/9894babd-8cbc-332a-8fc7-609c66834716.ova
url: NULL
  state: Ready
  destroyed: 0
is_copy: 0
   update_count: 3
ref_cnt: 0
updated: 2013-07-16 09:34:16
 *** 5. row ***
 id: 20
   store_id: 1
template_id: 205
created: 2013-07-16 11:48:23
   last_updated: 2013-07-16 11:55:29
 job_id: d49bdb7a-3ea1-4db2-b07b-e35842a23229
   download_pct: 100
   size: 0
 store_role: Image
  physical_size: 0
 download_state: DOWNLOADED
  error_str: Install completed successfully at 7/16/13 11:25 AM
 local_path: 
 /mnt/SecStorage/756c37ec-129a-3615-a376-c8f1f77fa7aa/template/tmpl/2/205/dnld599624653636661815tmp_
   install_path: template/tmpl/2/205/5573cdd7-94f5-3693-9ec7-7f0f5c341753.ova
url: NULL
  state: Ready
  destroyed: 0
is_copy: 0
   update_count: 3
ref_cnt: 0
updated: 2013-07-16 11:55:29
 5 rows in set (0.00 sec)
 ROOT volume:
 *** 21. row ***
 id: 21
 account_id: 8
  domain_id: 6
pool_id: 7
   last_pool_id: NULL
instance_id: 13
  device_id: 0
   name: ROOT-13
   uuid: 953256f2-ace0-41d3-a7a5-2c7db77cbeb7

[jira] [Updated] (CLOUDSTACK-3543) the cpvm and ssvm' state is still running when the node was crashed


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

terryye updated CLOUDSTACK-3543:


Description: 
When the host node crash the vm'state can not be get right state. the vm state 
is still running.
in fact,the vm is down,but the state is type running ,and not worked.
so i am edit the database vm state to Stopped. then the ssvm and cpvm can be 
start.


2013-07-16 11:18:41,187 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-2:null) HostStatsCollector is running...
2013-07-16 11:18:41,791 DEBUG [agent.transport.Request] (StatsCollector-2:null) 
Seq 5-1056112658: Received:  { Ans: , MgmtId: 52242977168, via: 5, Ver: v1, 
Flags: 10, { GetHostStatsAnswer } }
2013-07-16 11:18:55,483 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) VmStatsCollector is running...
2013-07-16 11:19:01,137 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-8:null) Ping from 5

  was:
When the host node crash the vm'state can not be get right state. the vm state 
is still running.
in fact,the vm is down,but the state is type running ,and not worked.
so i am edit the database vm state to Stipped. then the ssvm and cpvm can be 
start.


2013-07-16 11:18:41,187 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-2:null) HostStatsCollector is running...
2013-07-16 11:18:41,791 DEBUG [agent.transport.Request] (StatsCollector-2:null) 
Seq 5-1056112658: Received:  { Ans: , MgmtId: 52242977168, via: 5, Ver: v1, 
Flags: 10, { GetHostStatsAnswer } }
2013-07-16 11:18:55,483 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) VmStatsCollector is running...
2013-07-16 11:19:01,137 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-8:null) Ping from 5


 the cpvm and ssvm' state is still running when the node was crashed
 ---

 Key: CLOUDSTACK-3543
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3543
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Management Server
Affects Versions: 4.1.0
 Environment: Ubuntu12.04
Reporter: terryye
   Original Estimate: 96h
  Remaining Estimate: 96h

 When the host node crash the vm'state can not be get right state. the vm 
 state is still running.
 in fact,the vm is down,but the state is type running ,and not worked.
 so i am edit the database vm state to Stopped. then the ssvm and cpvm can be 
 start.
 2013-07-16 11:18:41,187 DEBUG [cloud.server.StatsCollector] 
 (StatsCollector-2:null) HostStatsCollector is running...
 2013-07-16 11:18:41,791 DEBUG [agent.transport.Request] 
 (StatsCollector-2:null) Seq 5-1056112658: Received:  { Ans: , MgmtId: 
 52242977168, via: 5, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
 2013-07-16 11:18:55,483 DEBUG [cloud.server.StatsCollector] 
 (StatsCollector-1:null) VmStatsCollector is running...
 2013-07-16 11:19:01,137 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-8:null) Ping from 5

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3543) the cpvm and ssvm' state is still running when the node was crashed


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

terryye updated CLOUDSTACK-3543:


Description: 
When the host node crash the vm'state can not be get right state. the vm state 
is still running.
in fact,the vm is down,but the state is type running ,and not worked.
so i am edit the database vm state to Stipped. then the ssvm and cpvm can be 
start.


2013-07-16 11:18:41,187 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-2:null) HostStatsCollector is running...
2013-07-16 11:18:41,791 DEBUG [agent.transport.Request] (StatsCollector-2:null) 
Seq 5-1056112658: Received:  { Ans: , MgmtId: 52242977168, via: 5, Ver: v1, 
Flags: 10, { GetHostStatsAnswer } }
2013-07-16 11:18:55,483 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) VmStatsCollector is running...
2013-07-16 11:19:01,137 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-8:null) Ping from 5

  was:
When the host node crash the vm'state can not be get right state. the vm state 
is still running.


2013-07-16 11:18:41,187 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-2:null) HostStatsCollector is running...
2013-07-16 11:18:41,791 DEBUG [agent.transport.Request] (StatsCollector-2:null) 
Seq 5-1056112658: Received:  { Ans: , MgmtId: 52242977168, via: 5, Ver: v1, 
Flags: 10, { GetHostStatsAnswer } }
2013-07-16 11:18:55,483 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-1:null) VmStatsCollector is running...
2013-07-16 11:19:01,137 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-8:null) Ping from 5


 the cpvm and ssvm' state is still running when the node was crashed
 ---

 Key: CLOUDSTACK-3543
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3543
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Management Server
Affects Versions: 4.1.0
 Environment: Ubuntu12.04
Reporter: terryye
   Original Estimate: 96h
  Remaining Estimate: 96h

 When the host node crash the vm'state can not be get right state. the vm 
 state is still running.
 in fact,the vm is down,but the state is type running ,and not worked.
 so i am edit the database vm state to Stipped. then the ssvm and cpvm can be 
 start.
 2013-07-16 11:18:41,187 DEBUG [cloud.server.StatsCollector] 
 (StatsCollector-2:null) HostStatsCollector is running...
 2013-07-16 11:18:41,791 DEBUG [agent.transport.Request] 
 (StatsCollector-2:null) Seq 5-1056112658: Received:  { Ans: , MgmtId: 
 52242977168, via: 5, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
 2013-07-16 11:18:55,483 DEBUG [cloud.server.StatsCollector] 
 (StatsCollector-1:null) VmStatsCollector is running...
 2013-07-16 11:19:01,137 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-8:null) Ping from 5

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3556) Add NIC icon is not appearing in UI

2013-07-16 Thread Raafat Mhamed (JIRA)


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

Raafat Mhamed updated CLOUDSTACK-3556:
--

Description: 
After upgrading from version 4.0.2 to version 4.1 ,I can't see the ADD NIC icon 
from interface tab.
check image http://postimg.org/image/ekb5olse9/


  was:
After upgrading from version 4.0.2 to version 4.1 ,I can't see the ADD NIC icon 
from interface tab.
check image |http://postimg.org/image/ekb5olse9/



 Add NIC icon is not appearing in UI
 ---

 Key: CLOUDSTACK-3556
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3556
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, UI
Affects Versions: 4.1.0
 Environment: Ubuntu (KVM)
Reporter: Raafat Mhamed
Priority: Minor

 After upgrading from version 4.0.2 to version 4.1 ,I can't see the ADD NIC 
 icon from interface tab.
 check image http://postimg.org/image/ekb5olse9/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-3543) the cpvm and ssvm' state is still running when the computer node was crashed