[jira] [Commented] (CLOUDSTACK-4537) [Automation] Test case test_vpc_vm_life_cycle.py: TestVMLifeCycleSharedNwVPC failed with Insufficient address capacity error

[Girish Shilamkar (JIRA)]

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

Girish Shilamkar commented on CLOUDSTACK-4537:
--

https://reviews.apache.org/r/14248/

> [Automation] Test case test_vpc_vm_life_cycle.py: TestVMLifeCycleSharedNwVPC  
> failed with Insufficient address capacity error 
> --
>
> Key: CLOUDSTACK-4537
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4537
> Project: CloudStack
>  Issue Type: Test
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Affects Versions: 4.2.0
> Environment: Automaiton
>Reporter: Rayees Namathponnan
>Assignee: Girish Shilamkar
>Priority: Critical
> Fix For: 4.2.1
>
>
> Test case test_vpc_vm_life_cycle.py:failed in latest runs, failed with 
> insuffcient address capacity, before  running this test, i checked the env; 
> there are enough free IP, but still it failed
> Observed below error in test log
> Error Message
> Execute cmd: deployvirtualmachine failed, due to: errorCode: 533, 
> errorText:Insufficient address capacity
> Stacktrace
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 208, in 
> run
> self.setUp()
>   File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 291, in 
> setUp
> self.setupContext(ancestor)
>   File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 314, in 
> setupContext
> try_run(context, names)
>   File "/usr/local/lib/python2.7/site-packages/nose/util.py", line 469, in 
> try_run
> return func()
>   File 
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_vpc_vm_life_cycle.py",
>  line 1005, in setUpClass
> str(cls.network_2.id)]
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py", line 
> 407, in create
> virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
>  line 618, in deployVirtualMachine
> response = self.connection.marvin_request(command, 
> response_type=response, method=method)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 
> 222, in marvin_request
> response = jsonHelper.getResultObj(response.json(), response_type)
>   File "/usr/local/lib/python2.7/site-packages/marvin/jsonHelper.py", line 
> 148, in getResultObj
> raise cloudstackException.cloudstackAPIException(respname, errMsg)
> cloudstackAPIException: Execute cmd: deployvirtualmachine failed, due to: 
> errorCode: 533, errorText:Insufficient address capacity
> Below error from MS log
> 2013-08-28 07:51:27,808 WARN  [cloud.network.NetworkManagerImpl] 
> (catalina-exec-5:null) Unable to get ip adress in  zone id=1, vlanId 
> id=[Ljava.lang.Object;@5b50eae5, network
> id=500
> 2013-08-28 07:51:27,819 DEBUG [db.Transaction.Transaction] 
> (catalina-exec-5:null) Rolling back the transaction: Time = 65 Name =  
> createVirtualMachine; called by -Transaction.
> rollback:898-Transaction.removeUpTo:841-Transaction.close:665-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.interce
> pt:133-NetworkManagerImpl.assignPublicIpAddress:376-NetworkManagerImpl.allocateDirectIp:4482-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-DirectNetw
> orkGuru.allocateDirectIp:233-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-DirectNetworkGuru.allocate:204-NetworkManagerImpl.allocateNic:1746
> 2013-08-28 07:51:27,876 INFO  [user.vm.DeployVMCmd] (catalina-exec-5:null) 
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient 
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> 2013-08-28 07:51:27,877 TRACE [user.vm.DeployVMCmd] (catalina-exec-5:null) 
> Insufficient address capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient 
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at 
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> com.cloud.network.NetworkManagerImpl.assignPublicIpAddress(NetworkManagerImpl.java:376)
> at 
> com.cloud.network.NetworkManagerImpl.allocateDirectIp(NetworkManagerImpl.java:4482)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiat

[jira] [Commented] (CLOUDSTACK-4648) [Automation] Test cases TestCreateVMSnapshotTemplate.test_01_createVM_snapshotTemplate failed with assert error

[Gaurav Aradhye (JIRA)]

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

Gaurav Aradhye commented on CLOUDSTACK-4648:


Added patch for this
https://reviews.apache.org/r/14346/

[This patch contains common solution for 4647 and 4648]

> [Automation] Test cases 
> TestCreateVMSnapshotTemplate.test_01_createVM_snapshotTemplate failed with 
> assert error 
> 
>
> Key: CLOUDSTACK-4648
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4648
> Project: CloudStack
>  Issue Type: Test
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation, Test
>Affects Versions: 4.2.1
> Environment: KVM
> 4.2-forward 
>Reporter: Rayees Namathponnan
>Assignee: Gaurav Aradhye
>Priority: Critical
> Fix For: 4.2.1
>
>
> Test case 
> integration.component.test_snapshots.TestCreateVMSnapshotTemplate.test_01_createVM_snapshotTemplate
>  failed with asset errorr 
> Error Message
> False is not True
>  >> begin captured logging << 
> test_01_createVM_snapshotTemplate 
> (integration.component.test_snapshots.TestCreateVMSnapshotTemplate): DEBUG: 
> Created VM with ID: c7bc243f-54ed-49e1-abfb-41e59ab4e559
> test_01_createVM_snapshotTemplate 
> (integration.component.test_snapshots.TestCreateVMSnapshotTemplate): DEBUG: 
> Snapshot created: ID - 7c76e8d0-0351-4be0-95f3-04f0b6075551
> test_01_createVM_snapshotTemplate 
> (integration.component.test_snapshots.TestCreateVMSnapshotTemplate): DEBUG: 
> select backup_snap_id, account_id, volume_id from snapshots where uuid = 
> '7c76e8d0-0351-4be0-95f3-04f0b6075551';
> test_01_createVM_snapshotTemplate 
> (integration.component.test_snapshots.TestCreateVMSnapshotTemplate): DEBUG: 
> Created template from snapshot: 26c7a850-7295-4cd2-bf5e-87214f9ae666
> test_01_createVM_snapshotTemplate 
> (integration.component.test_snapshots.TestCreateVMSnapshotTemplate): DEBUG: 
> Created VM with ID: ddb07a66-e123-4577-8b7e-16be730829ed from template: 
> 26c7a850-7295-4cd2-bf5e-87214f9ae666
> paramiko.transport: DEBUG: starting thread (client mode): 0x4654c10L
> paramiko.transport: INFO: Connected (version 2.0, client OpenSSH_5.3)
> paramiko.transport: DEBUG: kex algos:['diffie-hellman-group-exchange-sha256', 
> 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 
> 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client 
> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 
> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 
> 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] server 
> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 
> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 
> 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] client 
> mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 
> 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server 
> mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 
> 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client 
> compress:['none', 'z...@openssh.com'] server compress:['none', 
> 'z...@openssh.com'] client lang:[''] server lang:[''] kex follows?False
> paramiko.transport: DEBUG: Ciphers agreed: local=aes128-ctr, remote=aes128-ctr
> paramiko.transport: DEBUG: using kex diffie-hellman-group1-sha1; server key 
> type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local 
> hmac-sha1, remote hmac-sha1; compression: local none, remote none
> paramiko.transport: DEBUG: Switch to new keys ...
> paramiko.transport: DEBUG: Adding ssh-rsa host key for 10.223.49.195: 
> 46bde2f19851ddbdf5b062510a1d4200
> paramiko.transport: DEBUG: Trying discovered key 
> 76be480fa6b8ad3b78082d6d19e4ee44 in /root/.ssh/id_rsa
> paramiko.transport: DEBUG: userauth is OK
> paramiko.transport: INFO: Authentication (publickey) successful!
> sshClient: DEBUG: SSH connect: root@10.223.49.195 with passwd password
> paramiko.transport: DEBUG: [chan 1] Max packet in: 34816 bytes
> paramiko.transport: DEBUG: [chan 1] Max packet out: 32768 bytes
> paramiko.transport: INFO: Secsh channel 1 opened.
> paramiko.transport: DEBUG: [chan 1] Sesch channel 1 request ok
> paramiko.transport: DEBUG: [chan 1] EOF received (1)
> sshClient: DEBUG: {Cmd: mkdir -p %s /mnt/tmp via Host: 10.223.49.195} 
> {returns: []}
> paramiko.transport: DEBUG: [chan 2] Max packet in: 34816 bytes
> paramiko.transport: DEBUG: [chan 1] EOF sent (1)
> paramiko.transport: DEBUG: [chan 2] Max packet out: 32768 bytes
> paramiko.transport: INFO:

[jira] [Commented] (CLOUDSTACK-4647) [Automation] Test case TestAccountSnapshotClean.test_02_accountSnapshotClean failed to mount nfs1 server

[Gaurav Aradhye (JIRA)]

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

Gaurav Aradhye commented on CLOUDSTACK-4647:


Added patch for this
https://reviews.apache.org/r/14346/

> [Automation] Test case TestAccountSnapshotClean.test_02_accountSnapshotClean  
> failed to mount nfs1 server
> -
>
> Key: CLOUDSTACK-4647
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4647
> Project: CloudStack
>  Issue Type: Test
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Affects Versions: 4.2.1
> Environment: Automation 
> 4.2.1-forward
> KVM
>Reporter: Rayees Namathponnan
>Assignee: Gaurav Aradhye
> Fix For: 4.2.1
>
>
> Test case failed to mount NFS server 
> integration.component.test_snapshot_gc.TestAccountSnapshotClean.test_02_accountSnapshotClea
> Observed below error in log 
> Error Message
> Snapshot was not found on NFS
>  >> begin captured logging << 
> test_02_accountSnapshotClean 
> (integration.component.test_snapshot_gc.TestAccountSnapshotClean): DEBUG: VM 
> ID: 0e161a5c-58f5-4a4f-927e-19ac199ba15f, VM state: Running
> paramiko.transport: DEBUG: starting thread (client mode): 0x426f0d0L
> paramiko.transport: INFO: Connected (version 2.0, client OpenSSH_5.3)
> paramiko.transport: DEBUG: kex algos:['diffie-hellman-group-exchange-sha256', 
> 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 
> 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client 
> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 
> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 
> 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] server 
> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 
> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 
> 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] client 
> mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 
> 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server 
> mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 
> 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client 
> compress:['none', 'z...@openssh.com'] server compress:['none', 
> 'z...@openssh.com'] client lang:[''] server lang:[''] kex follows?False
> paramiko.transport: DEBUG: Ciphers agreed: local=aes128-ctr, remote=aes128-ctr
> paramiko.transport: DEBUG: using kex diffie-hellman-group1-sha1; server key 
> type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local 
> hmac-sha1, remote hmac-sha1; compression: local none, remote none
> paramiko.transport: DEBUG: Switch to new keys ...
> paramiko.transport: DEBUG: Adding ssh-rsa host key for 10.223.49.195: 
> 46bde2f19851ddbdf5b062510a1d4200
> paramiko.transport: DEBUG: Trying discovered key 
> 76be480fa6b8ad3b78082d6d19e4ee44 in /root/.ssh/id_rsa
> paramiko.transport: DEBUG: userauth is OK
> paramiko.transport: INFO: Authentication (publickey) successful!
> sshClient: DEBUG: SSH connect: root@10.223.49.195 with passwd password
> paramiko.transport: DEBUG: [chan 1] Max packet in: 34816 bytes
> paramiko.transport: DEBUG: [chan 1] Max packet out: 32768 bytes
> paramiko.transport: INFO: Secsh channel 1 opened.
> paramiko.transport: DEBUG: [chan 1] Sesch channel 1 request ok
> paramiko.transport: DEBUG: [chan 1] EOF received (1)
> sshClient: DEBUG: {Cmd: mkdir -p %s /mnt/tmp via Host: 10.223.49.195} 
> {returns: []}
> paramiko.transport: DEBUG: [chan 2] Max packet in: 34816 bytes
> paramiko.transport: DEBUG: [chan 1] EOF sent (1)
> paramiko.transport: DEBUG: [chan 2] Max packet out: 32768 bytes
> paramiko.transport: INFO: Secsh channel 2 opened.
> paramiko.transport: DEBUG: [chan 2] Sesch channel 2 request ok
> paramiko.transport: DEBUG: [chan 2] EOF received (2)
> sshClient: DEBUG: {Cmd: mount -t nfs 
> 10.223.49.195:/export/home/rayees/SC_QA_AUTO4/secondary /mnt/tmp via Host: 
> 10.223.49.195} {returns: ['mount.nfs: Connection timed out']}
> paramiko.transport: DEBUG: [chan 3] Max packet in: 34816 bytes
> paramiko.transport: DEBUG: [chan 2] EOF sent (2)
> paramiko.transport: DEBUG: [chan 3] Max packet out: 32768 bytes
> paramiko.transport: INFO: Secsh channel 3 opened.
> paramiko.transport: DEBUG: [chan 3] Sesch channel 3 request ok
> paramiko.transport: DEBUG: [chan 3] EOF received (3)
> paramiko.transport: DEBUG: [chan 3] EOF sent (3)
> sshClient: DEBUG: {Cmd: test -f 
> /mnt/tmp/snapshots/407/700/c5e9ecf6-1cbe-48f2-b836-98460bd81b98 && echo 
> 'snapshot exists' via Host: 10.223.49.195} {return

[jira] [Commented] (CLOUDSTACK-4777) NullPointerException instead of working KVM HA

[Valery Ciareszka (JIRA)]

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

Valery Ciareszka commented on CLOUDSTACK-4777:
--

I was able to resolve this issue by modifying 
a/server/src/com/cloud/storage/VolumeManagerImpl.java

--- a/server/src/com/cloud/storage/VolumeManagerImpl.java
+++ b/server/src/com/cloud/storage/VolumeManagerImpl.java
@@ -2657,7 +2657,8 @@ public class VolumeManagerImpl extends ManagerBase 
implements VolumeManager {
 public boolean canVmRestartOnAnotherServer(long vmId) {
 List vols = _volsDao.findCreatedByInstance(vmId);
 for (VolumeVO vol : vols) {
-if (!vol.isRecreatable() && !vol.getPoolType().isShared()) {
+StoragePoolVO storagePoolVO = 
_storagePoolDao.findById(vol.getPoolId());
+if (!vol.isRecreatable() && storagePoolVO != null && 
storagePoolVO.getPoolType() != null && 
!(storagePoolVO.getPoolType().isShared())) {
 return false;
 }
 }

this is commit from https://issues.apache.org/jira/browse/CLOUDSTACK-4627
But this bug is still present in latest cloudstack 4.2.0 source code (as well 
as in packages from http://cloudstack.apt-get.eu/rhel/4.2/)

> NullPointerException instead of working KVM HA
> --
>
> Key: CLOUDSTACK-4777
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4777
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Hypervisor Controller, KVM, Management Server
>Affects Versions: 4.2.0
> Environment: KVM (CentOS 6.4) with CloudStack 4.2
>Reporter: Valery Ciareszka
>Priority: Critical
>
> If  KVM host goes down, CloudStack management does not start HA-enabled VM on 
> the other hosts. There is NullPointerException in management.log:
> 2013-09-24 11:21:25,500 ERROR [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-4:work-4) Terminating HAWork[4-HA-6-Running-Scheduled]
> java.lang.NullPointerException
> at 
> com.cloud.storage.VolumeManagerImpl.canVmRestartOnAnotherServer(VolumeManagerImpl.java:2641)
> at 
> com.cloud.ha.HighAvailabilityManagerImpl.restart(HighAvailabilityManagerImpl.java:516)
> at 
> com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:831)
> see full log at http://pastebin.com/upnEA601



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

[jira] [Assigned] (CLOUDSTACK-2243) Automation: VMs base image update facility

[Ashutosk Kelkar (JIRA)]

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

Ashutosk Kelkar reassigned CLOUDSTACK-2243:
---

Assignee: Ashutosk Kelkar  (was: Harikrishna Patnala)

> Automation: VMs base image update facility
> --
>
> Key: CLOUDSTACK-2243
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2243
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Reporter: Sudha Ponnaganti
>Assignee: Ashutosk Kelkar
>Priority: Critical
> Fix For: 4.2.0, 4.2.1
>
>




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

[jira] [Commented] (CLOUDSTACK-2243) Automation: VMs base image update facility

[Ashutosk Kelkar (JIRA)]

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

Ashutosk Kelkar commented on CLOUDSTACK-2243:
-

https://reviews.apache.org/r/14459/

> Automation: VMs base image update facility
> --
>
> Key: CLOUDSTACK-2243
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2243
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Reporter: Sudha Ponnaganti
>Assignee: Ashutosk Kelkar
>Priority: Critical
> Fix For: 4.2.0, 4.2.1
>
>




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

[jira] [Created] (CLOUDSTACK-4793) Impore VR Upgrade

[Kishan Kavala (JIRA)]

Kishan Kavala created CLOUDSTACK-4793:
-

 Summary: Impore VR Upgrade
 Key: CLOUDSTACK-4793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4793
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Kishan Kavala
Assignee: Kishan Kavala
 Fix For: Future


Give admin control to sequence the upgrade of the cloud by:
  Infrastructure hierarchy: by Cluster, Pod, and Zone etc.
  Administrative hierarchy: by Tenant or Domain 
Minimize service interruption to users
Improve the speed of the upgrade time by making as many upgrade operations in 
parallel as possible



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

[jira] [Created] (CLOUDSTACK-4794) Searching docs on http://cloudstack.apache.org/docs fails

[Syed Ahmed (JIRA)]

Syed Ahmed created CLOUDSTACK-4794:
--

 Summary: Searching docs on http://cloudstack.apache.org/docs fails
 Key: CLOUDSTACK-4794
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4794
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Reporter: Syed Ahmed


Searching on the docs page http://cloudstack.apache.org/docs sends me to google 
which shows the following 

 test site:http://localhost/ - did not match any documents.


looks like the site parameter needs to be changed.



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

[jira] [Created] (CLOUDSTACK-4795) Deploy multiple copies of a template at once

[Chris Sciarrino (JIRA)]

Chris Sciarrino created CLOUDSTACK-4795:
---

 Summary: Deploy multiple copies of a template at once
 Key: CLOUDSTACK-4795
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4795
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.2.0
 Environment: vsphere 5.1, xenserver 6.2
Reporter: Chris Sciarrino
Priority: Minor


It may be useful in some environments to automate the deployment of several 
copies of a template. For example if a user needed to deploy 10 instances from 
the same template at once there should be an option in the instance deployment 
to specify quantity to be deployed.  



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

[jira] [Commented] (CLOUDSTACK-899) QA Scaling up CPU and RAM for running VMs

[Gaurav Aradhye (JIRA)]

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

Gaurav Aradhye commented on CLOUDSTACK-899:
---

Hi Prashant,

In test scenarios such as CS behaviour while scaling up CPU and RAM, also in 
"Snapshot creation while scaling up CPU and RAM", do we take snapshot while 
scaling operation is in progress or after scaling is completed? In that case 
snapshot shouldn't fail. Do we have to carry out scaling and the other 
operation (snapshot creation/ switching on,off the host) asynchronously or 
synchronously? The steps in test scenarios say synchronous operations but the 
overall meaning suggests asynchronous operations.

> QA Scaling up CPU and RAM for running VMs
> -
>
> Key: CLOUDSTACK-899
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-899
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Test
>Reporter: Chip Childers
>Assignee: prashant kumar mishra
> Fix For: 4.2.0
>
>




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

[jira] [Commented] (CLOUDSTACK-4637) [Automation] test_egress_fw_rules.py fails with Script result is ['send: spawn id exp3 not open' ....'] is not matching with ['100'] in KVM

[Girish Shilamkar (JIRA)]

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

Girish Shilamkar commented on CLOUDSTACK-4637:
--

https://reviews.apache.org/r/14469/

> [Automation] test_egress_fw_rules.py fails with Script result is ['send: 
> spawn id exp3 not open' '] is not matching with ['100'] in KVM
> ---
>
> Key: CLOUDSTACK-4637
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4637
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Reporter: Girish Shilamkar
>Assignee: Girish Shilamkar
>Priority: Critical
>
> Still fails
> Script result is ['send: spawn id exp3 not open', ' while executing', '"send 
> "ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
> LogLevel=quiet root@10.1.1.183 ping -c 1 www.google.com; exit $?', '""', ' 
> (file "/tmp/expect_script.exp" line 4)'] is not matching with ['100']
>  >> begin captured logging << 
> testclient.testcase.TestEgressFWRules: DEBUG: Creating network with network 
> offering: 05d985b1-ee1c-4b04-9cee-d6c97e43032d
> testclient.testcase.TestEgressFWRules: DEBUG: Created network with ID: 
> 02187a7a-9afe-45ff-b9c3-069b00c731fc
> testclient.testcase.TestEgressFWRules: DEBUG: Deploying instance in the 
> account: test-B0F0Z8
> testclient.testcase.TestEgressFWRules: DEBUG: Deployed instance in account: 
> test-B0F0Z8
> testclient.testcase.TestEgressFWRules: DEBUG: Creating Egress FW rule for 
> networkid=02187a7a-9afe-45ff-b9c3-069b00c731fc networkname=Test Network
> testclient.testcase.TestEgressFWRules: DEBUG: Created 
> rule=fe84b110-8042-47d3-8b72-917607ab8811
> testclient.testcase.TestEgressFWRules: DEBUG: expect_script>>
> #!/usr/bin/expect
> spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
> LogLevel=quiet -i /root/.ssh/id_rsa.cloud -p 3922 root@169.254.2.102
> expect "root@r-588-QA:~#"
> send "ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o 
> LogLevel=quiet root@10.1.1.183 ping -c 1 www.google.com; exit $?
> "
> expect "root@10.1.1.183's password: "
> send "password
> "
> interact
> < paramiko.transport: DEBUG: starting thread (client mode): 0x204143d0L
> paramiko.transport: INFO: Connected (version 2.0, client OpenSSH_5.3)
> paramiko.transport: DEBUG: kex algos:['diffie-hellman-group-exchange-sha256', 
> 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 
> 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client 
> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 
> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 
> 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] server 
> encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 
> 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 
> 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] client 
> mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 
> 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server 
> mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 
> 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client 
> compress:['none', 'z...@openssh.com'] server compress:['none', 
> 'z...@openssh.com'] client lang:[''] server lang:[''] kex follows?False
> paramiko.transport: DEBUG: Ciphers agreed: local=aes128-ctr, remote=aes128-ctr
> paramiko.transport: DEBUG: using kex diffie-hellman-group1-sha1; server key 
> type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local 
> hmac-sha1, remote hmac-sha1; compression: local none, remote none
> paramiko.transport: DEBUG: Switch to new keys ...
> paramiko.transport: DEBUG: Adding ssh-rsa host key for 10.223.50.66: 
> 41aef5f507e1ddd99077b11f4bf26553
> paramiko.transport: DEBUG: Trying discovered key 
> 76be480fa6b8ad3b78082d6d19e4ee44 in /root/.ssh/id_rsa
> paramiko.transport: DEBUG: userauth is OK
> paramiko.transport: INFO: Authentication (publickey) failed.
> paramiko.transport: DEBUG: userauth is OK
> paramiko.transport: INFO: Authentication (password) successful!
> sshClient: DEBUG: SSH connect: root@10.223.50.66 with passwd password
> testclient.testcase.TestEgressFWRules: DEBUG: SSH client to : 10.223.50.66 
> obtained
> paramiko.transport: DEBUG: starting thread (client mode): 0x204b6b90L
> paramiko.transport: INFO: Connected (version 2.0, client OpenSSH_5.3)
> paramiko.transport: DEBUG: kex algos:['diffie-hellman-group-exchange-sha256', 
> 'diffie-hellman-gr

[jira] [Assigned] (CLOUDSTACK-4747) [Automation] Test cases creating account with more 100 character; account creation failing due to this

[Girish Shilamkar (JIRA)]

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

Girish Shilamkar reassigned CLOUDSTACK-4747:


Assignee: Girish Shilamkar

> [Automation] Test cases creating account with more 100 character;  account 
> creation failing due to this 
> 
>
> Key: CLOUDSTACK-4747
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4747
> Project: CloudStack
>  Issue Type: Test
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation, marvin, Test
>Affects Versions: 4.2.1
> Environment: Automation 
>Reporter: Rayees Namathponnan
>Assignee: Girish Shilamkar
>Priority: Blocker
> Fix For: 4.2.1
>
>
> You cannot create account more than 100 characters; 
> We added test case's name in account;  but should trim the account name 
> maximum to 99 characters to avoid these kind of failures 
> integration.component.test_netscaler_nw_off.TestNOWithNetscaler.test_02_network_off_with_conserve_mode_netscaler
> Execute cmd: createaccount failed, due to: errorCode: 530, errorText:DB 
> Exception on: com.mysql.jdbc.PreparedStatement@4d345362: INSERT INTO account 
> (account.account_name, account.type, account.domain_id, account.state, 
> account.cleanup_needed, account.network_domain, account.uuid, 
> account.default_zone_id, account.default) VALUES 
> (_binary'test-test_netscaler_nw_off-TestNwOffSToDUpgrade-test_02_network_off_with_conserve_mode_netscaler-AZBFBO',
>  2, 1, 'enabled', 0, null, _binary'0c361f17-c605-456f-ad0b-b1952bce575a', 
> null, 0)
> Stacktrace
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 311, in run
> self.setUp()
>   File 
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_netscaler_nw_off.py",
>  line 2428, in setUp
> domainid=self.domain.id
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py", line 
> 116, in create
> account = apiclient.createAccount(cmd)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
>  line 495, in createAccount
> response = self.connection.marvin_request(command, 
> response_type=response, method=method)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 
> 222, in marvin_request
> response = jsonHelper.getResultObj(response.json(), response_type)
>   File "/usr/local/lib/python2.7/site-packages/marvin/jsonHelper.py", line 
> 148, in getResultObj
> raise cloudstackException.cloudstackAPIException(respname, errMsg)
> cloudstackAPIException: Execute cmd: createaccount failed, due to: errorCode: 
> 530, errorText:DB Exception on: com.mysql.jdbc.PreparedStatement@4d345362: 
> INSERT INTO account (account.account_name, account.type, account.domain_id, 
> account.state, account.cleanup_needed, account.network_domain, account.uuid, 
> account.default_zone_id, account.default) VALUES 
> (_binary'test-test_netscaler_nw_off-TestNwOffSToDUpgrade-test_02_network_off_with_conserve_mode_netscaler-AZBFBO',
>  2, 1, 'enabled', 0, null, _binary'0c361f17-c605-456f-ad0b-b1952bce575a', 
> null, 0)



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

[jira] [Assigned] (CLOUDSTACK-4766) [Automation] test_reset_ssh_keypair executing in infinite loop and regression suite hang

[Girish Shilamkar (JIRA)]

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

Girish Shilamkar reassigned CLOUDSTACK-4766:


Assignee: Girish Shilamkar

> [Automation] test_reset_ssh_keypair executing in infinite loop and regression 
> suite hang
> 
>
> Key: CLOUDSTACK-4766
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4766
> Project: CloudStack
>  Issue Type: Test
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Affects Versions: 4.2.1
> Environment: Automation advanced zone 
>Reporter: Rayees Namathponnan
>Assignee: Girish Shilamkar
>Priority: Blocker
> Fix For: 4.2.1
>
>
> Few test cases from test_reset_ssh_keypair.py suite executing infinite loop 
> hang automation 
> See the below code from test_reset_ssh_keypair.py,   here test case checking 
> VM's state in every 60 sec, due to some reason if this vm never comes to 
> running; this code will execute in a loop 
>  578 while True:
>  579 vms = VirtualMachine.list(
>  580   self.apiclient,
>  581   account=self.account.name,
>  582   domainid=self.account.domainid,
>  583   listall=True
>  584   )
>  585 if vms[0].state == "Running":
>  586 break
>  587 self.debug("Vm not in Running state sleep 60s")
>  588 time.sleep(60)



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

[jira] [Created] (CLOUDSTACK-4796) Allow instances to be assigned to another user through the UI

[Chris Sciarrino (JIRA)]

Chris Sciarrino created CLOUDSTACK-4796:
---

 Summary: Allow instances to be assigned to another user through 
the UI
 Key: CLOUDSTACK-4796
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4796
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Chris Sciarrino


There should be an option in the UI, to allow the root admin or domain admin 
accounts to assign an instance to a particular user. If the admin gets a 
request from a user he should be able to deploy the VM and network and then 
migrate them to the control of the end user.



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

[jira] [Commented] (CLOUDSTACK-4790) [VMware] Reserved SCSI device number prevents CloudStack to attach more than 6 data volumes to a VM

[ASF subversion and git services (JIRA)]

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

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

Commit a3babdd61ca8cae668a1b13c2724a0a6dd13fa05 in branch refs/heads/ui-restyle 
from [~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a3babdd ]

CLOUDSTACK-4790: Skip reserved VMware scsi device number for SCSI disks


> [VMware] Reserved SCSI device number prevents CloudStack to attach more than 
> 6 data volumes to a VM
> ---
>
> Key: CLOUDSTACK-4790
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4790
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Kelven Yang
>
> Reserved SCSI device number prevents CloudStack to attach more than 6 data 
> volumes to a VM



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

[jira] [Commented] (CLOUDSTACK-1857) DEB package repository instructions in installation guide borked?

[Douglas Almquist (JIRA)]

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

Douglas Almquist commented on CLOUDSTACK-1857:
--

The correction described here works fine and it's trivial nature and high 
priority leaves me wondering why this isn't fixed.
This will block thousands of users and restrict uptake of CloudStack.  Every 
second/minute/hour/day/week counts here.
Please expedite this fix.

> DEB package repository instructions in installation guide borked?
> -
>
> Key: CLOUDSTACK-1857
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1857
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: David A. Buser
>Priority: Critical
>
> There seems to be a problem with the DEB package repository instructions in 
> section 4.4.1 of the 4.0.1-incubating installation guide: 
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/configure-package-repository.html#configure-package-repository-deb
> I think you want to say:
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list
> rather than:
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack
> See related gist: https://gist.github.com/elithrar/5180751



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

[jira] [Comment Edited] (CLOUDSTACK-1857) DEB package repository instructions in installation guide borked?

[Douglas Almquist (JIRA)]

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

Douglas Almquist edited comment on CLOUDSTACK-1857 at 10/3/13 8:14 PM:
---

The correction described here works fine and it's trivial nature and high 
priority leaves me wondering why this isn't fixed.  This was reported in March 
of 2013.  It's now October.
This will block thousands of users and restrict uptake of CloudStack.  Every 
second/minute/hour/day/week counts here.
Please expedite this fix.

As for myself I just concluded this was the best choice. 
Suddenly I'm wondering if I should reconsider OpenStack.  
There appears to be a problem with the team.


was (Author: dougga):
The correction described here works fine and it's trivial nature and high 
priority leaves me wondering why this isn't fixed.  This was reported in March 
of 2013.  It's now October.
This will block thousands of users and restrict uptake of CloudStack.  Every 
second/minute/hour/day/week counts here.
Please expedite this fix.

> DEB package repository instructions in installation guide borked?
> -
>
> Key: CLOUDSTACK-1857
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1857
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: David A. Buser
>Priority: Critical
>
> There seems to be a problem with the DEB package repository instructions in 
> section 4.4.1 of the 4.0.1-incubating installation guide: 
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/configure-package-repository.html#configure-package-repository-deb
> I think you want to say:
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list
> rather than:
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack
> See related gist: https://gist.github.com/elithrar/5180751



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

[jira] [Comment Edited] (CLOUDSTACK-1857) DEB package repository instructions in installation guide borked?

[Douglas Almquist (JIRA)]

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

Douglas Almquist edited comment on CLOUDSTACK-1857 at 10/3/13 8:13 PM:
---

The correction described here works fine and it's trivial nature and high 
priority leaves me wondering why this isn't fixed.  This was reported in March 
of 2013.  It's now October.
This will block thousands of users and restrict uptake of CloudStack.  Every 
second/minute/hour/day/week counts here.
Please expedite this fix.


was (Author: dougga):
The correction described here works fine and it's trivial nature and high 
priority leaves me wondering why this isn't fixed.
This will block thousands of users and restrict uptake of CloudStack.  Every 
second/minute/hour/day/week counts here.
Please expedite this fix.

> DEB package repository instructions in installation guide borked?
> -
>
> Key: CLOUDSTACK-1857
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1857
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: David A. Buser
>Priority: Critical
>
> There seems to be a problem with the DEB package repository instructions in 
> section 4.4.1 of the 4.0.1-incubating installation guide: 
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/configure-package-repository.html#configure-package-repository-deb
> I think you want to say:
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list
> rather than:
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack
> See related gist: https://gist.github.com/elithrar/5180751



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

[jira] [Commented] (CLOUDSTACK-1857) DEB package repository instructions in installation guide borked?

[Douglas Almquist (JIRA)]

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

Douglas Almquist commented on CLOUDSTACK-1857:
--

The fix here is for 4.0.  4.1 has since released, the 4.2 repository exists as 
well so it's not clear which one is ready for prime time.

> DEB package repository instructions in installation guide borked?
> -
>
> Key: CLOUDSTACK-1857
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1857
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: David A. Buser
>Priority: Critical
>
> There seems to be a problem with the DEB package repository instructions in 
> section 4.4.1 of the 4.0.1-incubating installation guide: 
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/configure-package-repository.html#configure-package-repository-deb
> I think you want to say:
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list
> rather than:
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack
> See related gist: https://gist.github.com/elithrar/5180751



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

[jira] [Created] (CLOUDSTACK-4797) Installation guide for 4.2 instructs users to install 4.1

[Douglas Almquist (JIRA)]

Douglas Almquist created CLOUDSTACK-4797:


 Summary: Installation guide for 4.2 instructs users to install 4.1
 Key: CLOUDSTACK-4797
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4797
 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
 Environment: Debian/Ubuntu
Reporter: Douglas Almquist
Priority: Critical
 Fix For: 4.2.0


In the 4.2.0 Installation guide (

It states the following: [cut/paste from web page]
4.4.1. DEB package repository
You can add a DEB package repository to your apt sources with the following 
commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
being built at this time.
Use your preferred editor and open (or create) 
/etc/apt/sources.list.d/cloudstack.list. Add the community provided repository 
to the file:

deb http://cloudstack.apt-get.eu/ubuntu precise 4.1



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

[jira] [Updated] (CLOUDSTACK-4797) Installation guide for 4.2 instructs users to install 4.1

[Douglas Almquist (JIRA)]

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

Douglas Almquist updated CLOUDSTACK-4797:
-

Affects Version/s: 4.2.0
Fix Version/s: (was: 4.2.0)
   Future

> Installation guide for 4.2 instructs users to install 4.1
> -
>
> Key: CLOUDSTACK-4797
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4797
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0, 4.2.0
> Environment: Debian/Ubuntu
>Reporter: Douglas Almquist
>Priority: Critical
>  Labels: 4.2, guide, installation
> Fix For: Future
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the 4.2.0 Installation guide (
> It states the following: [cut/paste from web page]
> 4.4.1. DEB package repository
> You can add a DEB package repository to your apt sources with the following 
> commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
> being built at this time.
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list. Add the community provided 
> repository to the file:
> deb http://cloudstack.apt-get.eu/ubuntu precise 4.1



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

[jira] [Created] (CLOUDSTACK-4798) [Automation]Include the ability to get templates using keyword.

[Sangeetha Hariharan (JIRA)]

Sangeetha Hariharan created CLOUDSTACK-4798:
---

 Summary: [Automation]Include the ability to get templates using 
keyword.
 Key: CLOUDSTACK-4798
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4798
 Project: CloudStack
  Issue Type: Task
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: marvin
Affects Versions: 4.2.1
Reporter: Sangeetha Hariharan
Assignee: Sangeetha Hariharan
 Fix For: 4.2.1


Currently get_template() call i common.py allows for getting template by ostype 
and template_id.

It would be good to include the ability to get templates using keyword 
search.This will enable us to get a template by passing the name/partial name 
of the template.



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

[jira] [Updated] (CLOUDSTACK-4797) Installation guide for 4.2 instructs users to install 4.1

[Douglas Almquist (JIRA)]

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

Douglas Almquist updated CLOUDSTACK-4797:
-

Component/s: Doc

> Installation guide for 4.2 instructs users to install 4.1
> -
>
> Key: CLOUDSTACK-4797
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4797
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Management Server
>Affects Versions: 4.1.0, 4.2.0
> Environment: Debian/Ubuntu
>Reporter: Douglas Almquist
>  Labels: 4.2, guide, installation
> Fix For: Future
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the 4.2.0 Installation guide (
> It states the following: [cut/paste from web page]
> 4.4.1. DEB package repository
> You can add a DEB package repository to your apt sources with the following 
> commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
> being built at this time.
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list. Add the community provided 
> repository to the file:
> deb http://cloudstack.apt-get.eu/ubuntu precise 4.1



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

[jira] [Updated] (CLOUDSTACK-4797) Installation guide for 4.2 instructs users to install 4.1

[Douglas Almquist (JIRA)]

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

Douglas Almquist updated CLOUDSTACK-4797:
-

Priority: Major  (was: Critical)

> Installation guide for 4.2 instructs users to install 4.1
> -
>
> Key: CLOUDSTACK-4797
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4797
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Management Server
>Affects Versions: 4.1.0, 4.2.0
> Environment: Debian/Ubuntu
>Reporter: Douglas Almquist
>  Labels: 4.2, guide, installation
> Fix For: Future
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the 4.2.0 Installation guide (
> It states the following: [cut/paste from web page]
> 4.4.1. DEB package repository
> You can add a DEB package repository to your apt sources with the following 
> commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
> being built at this time.
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list. Add the community provided 
> repository to the file:
> deb http://cloudstack.apt-get.eu/ubuntu precise 4.1



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

[jira] [Created] (CLOUDSTACK-4799) Update Deployment Architecture Overview section

[Travis Graham (JIRA)]

Travis Graham created CLOUDSTACK-4799:
-

 Summary: Update Deployment Architecture Overview section
 Key: CLOUDSTACK-4799
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4799
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Affects Versions: 4.2.0
Reporter: Travis Graham
Priority: Critical
 Fix For: 4.2.0


Adds in links to other docs it only loosely references by name and adds the 
Primary Storage info about being zone wide for 4.2.



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

[jira] [Updated] (CLOUDSTACK-4799) Update Deployment Architecture Overview section

[Travis Graham (JIRA)]

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

Travis Graham updated CLOUDSTACK-4799:
--

Attachment: deployment-architecture-overview.patch

> Update Deployment Architecture Overview section
> ---
>
> Key: CLOUDSTACK-4799
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4799
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: Travis Graham
>Priority: Critical
>  Labels: documentaion
> Fix For: 4.2.0
>
> Attachments: deployment-architecture-overview.patch
>
>
> Adds in links to other docs it only loosely references by name and adds the 
> Primary Storage info about being zone wide for 4.2.



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

[jira] [Created] (CLOUDSTACK-4800) Updating sections of the Cloud Infrastructure Concepts chapter of the Admin Guide

[Travis Graham (JIRA)]

Travis Graham created CLOUDSTACK-4800:
-

 Summary: Updating sections of the Cloud Infrastructure Concepts 
chapter of the Admin Guide
 Key: CLOUDSTACK-4800
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4800
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Affects Versions: 4.2.0
Reporter: Travis Graham
 Fix For: 4.2.0
 Attachments: cloud-infrastructure-concepts.patch

Adding missing links to referenced sections of the Admin Guide and fixes a few 
typos.



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

[jira] [Updated] (CLOUDSTACK-4800) Updating sections of the Cloud Infrastructure Concepts chapter of the Admin Guide

[Travis Graham (JIRA)]

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

Travis Graham updated CLOUDSTACK-4800:
--

Attachment: cloud-infrastructure-concepts.patch

> Updating sections of the Cloud Infrastructure Concepts chapter of the Admin 
> Guide
> -
>
> Key: CLOUDSTACK-4800
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4800
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: Travis Graham
>  Labels: documentation
> Fix For: 4.2.0
>
> Attachments: cloud-infrastructure-concepts.patch
>
>
> Adding missing links to referenced sections of the Admin Guide and fixes a 
> few typos.



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

[jira] [Created] (CLOUDSTACK-4801) System Offerings are mixed with Disk Offerings

[Mike Tutkowski (JIRA)]

Mike Tutkowski created CLOUDSTACK-4801:
--

 Summary: System Offerings are mixed with Disk Offerings
 Key: CLOUDSTACK-4801
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4801
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: Future
 Environment: On master branch
Reporter: Mike Tutkowski
 Fix For: Future


Looking at the Disk Offerings in the GUI, System Offerings are mixed in with 
Disk Offerings.

This is also true on the Add Volume dialog.



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

[jira] [Assigned] (CLOUDSTACK-4790) [VMware] Reserved SCSI device number prevents CloudStack to attach more than 6 data volumes to a VM

[Kelven Yang (JIRA)]

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

Kelven Yang reassigned CLOUDSTACK-4790:
---

Assignee: Kelven Yang

> [VMware] Reserved SCSI device number prevents CloudStack to attach more than 
> 6 data volumes to a VM
> ---
>
> Key: CLOUDSTACK-4790
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4790
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Kelven Yang
>Assignee: Kelven Yang
>
> Reserved SCSI device number prevents CloudStack to attach more than 6 data 
> volumes to a VM



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

[jira] [Resolved] (CLOUDSTACK-4790) [VMware] Reserved SCSI device number prevents CloudStack to attach more than 6 data volumes to a VM

[Kelven Yang (JIRA)]

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

Kelven Yang resolved CLOUDSTACK-4790.
-

Resolution: Fixed

> [VMware] Reserved SCSI device number prevents CloudStack to attach more than 
> 6 data volumes to a VM
> ---
>
> Key: CLOUDSTACK-4790
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4790
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Kelven Yang
>Assignee: Kelven Yang
>
> Reserved SCSI device number prevents CloudStack to attach more than 6 data 
> volumes to a VM



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

[jira] [Created] (CLOUDSTACK-4802) [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2

[Kelven Yang (JIRA)]

Kelven Yang created CLOUDSTACK-4802:
---

 Summary: [VMware] Unable to start VM if VM has VM snapshot been 
taken in vSphere version 5.0 Update 2
 Key: CLOUDSTACK-4802
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4802
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Kelven Yang
Assignee: Kelven Yang
Priority: Critical


CloudStack VM-start flow is broken by the behave of vSphere 5.0 Update 2. VM 
can not be started after VM has VM snapshot been taken. This issue is currently 
known to only happen in vSphere 5.0 Update 2



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

[jira] [Created] (CLOUDSTACK-4803) fix listVirtualMachines to not display vms to the normal users with forDisplay=false

[Nitin Mehta (JIRA)]

Nitin Mehta created CLOUDSTACK-4803:
---

 Summary: fix listVirtualMachines to not display vms to the normal 
users with forDisplay=false
 Key: CLOUDSTACK-4803
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4803
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Fix For: Future






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

[jira] [Commented] (CLOUDSTACK-4803) fix listVirtualMachines to not display vms to the normal users with forDisplay=false

[ASF subversion and git services (JIRA)]

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

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

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

CLOUDSTACK-4803:
fix listVirtualMachines to not display vms to the normal users with 
forDisplay=false. But displayvms to ROOT Admin irrespective of the flag.
Signed off by : nitin mehta


> fix listVirtualMachines to not display vms to the normal users with 
> forDisplay=false
> 
>
> Key: CLOUDSTACK-4803
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4803
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
>Reporter: Nitin Mehta
>Assignee: Nitin Mehta
> Fix For: Future
>
>




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

[jira] [Updated] (CLOUDSTACK-4799) Update Deployment Architecture Overview section

[Travis Graham (JIRA)]

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

Travis Graham updated CLOUDSTACK-4799:
--

Priority: Major  (was: Critical)

> Update Deployment Architecture Overview section
> ---
>
> Key: CLOUDSTACK-4799
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4799
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: Travis Graham
>  Labels: documentaion
> Fix For: 4.2.0
>
> Attachments: deployment-architecture-overview.patch
>
>
> Adds in links to other docs it only loosely references by name and adds the 
> Primary Storage info about being zone wide for 4.2.



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

[jira] [Updated] (CLOUDSTACK-4797) Installation guide for 4.2 instructs users to install 4.1

[Travis Graham (JIRA)]

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

Travis Graham updated CLOUDSTACK-4797:
--

Attachment: configure-package-respository.patch

Fixes repo version information for both DEB and RPM repositories

> Installation guide for 4.2 instructs users to install 4.1
> -
>
> Key: CLOUDSTACK-4797
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4797
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Management Server
>Affects Versions: 4.1.0, 4.2.0
> Environment: Debian/Ubuntu
>Reporter: Douglas Almquist
>  Labels: 4.2, guide, installation
> Fix For: Future
>
> Attachments: configure-package-respository.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the 4.2.0 Installation guide (
> It states the following: [cut/paste from web page]
> 4.4.1. DEB package repository
> You can add a DEB package repository to your apt sources with the following 
> commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
> being built at this time.
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list. Add the community provided 
> repository to the file:
> deb http://cloudstack.apt-get.eu/ubuntu precise 4.1



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

[jira] [Comment Edited] (CLOUDSTACK-4797) Installation guide for 4.2 instructs users to install 4.1

[Travis Graham (JIRA)]

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

Travis Graham edited comment on CLOUDSTACK-4797 at 10/3/13 10:27 PM:
-

Attachment fixes repo version information for both DEB and RPM repositories


was (Author: tgraham):
Fixes repo version information for both DEB and RPM repositories

> Installation guide for 4.2 instructs users to install 4.1
> -
>
> Key: CLOUDSTACK-4797
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4797
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Management Server
>Affects Versions: 4.1.0, 4.2.0
> Environment: Debian/Ubuntu
>Reporter: Douglas Almquist
>  Labels: 4.2, guide, installation
> Fix For: Future
>
> Attachments: configure-package-respository.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the 4.2.0 Installation guide (
> It states the following: [cut/paste from web page]
> 4.4.1. DEB package repository
> You can add a DEB package repository to your apt sources with the following 
> commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
> being built at this time.
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list. Add the community provided 
> repository to the file:
> deb http://cloudstack.apt-get.eu/ubuntu precise 4.1



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

[jira] [Resolved] (CLOUDSTACK-4803) fix listVirtualMachines to not display vms to the normal users with forDisplay=false

[Nitin Mehta (JIRA)]

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

Nitin Mehta resolved CLOUDSTACK-4803.
-

Resolution: Fixed

> fix listVirtualMachines to not display vms to the normal users with 
> forDisplay=false
> 
>
> Key: CLOUDSTACK-4803
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4803
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
>Reporter: Nitin Mehta
>Assignee: Nitin Mehta
> Fix For: Future
>
>




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

[jira] [Resolved] (CLOUDSTACK-4785) Add support for adding details to UserVm

[Nitin Mehta (JIRA)]

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

Nitin Mehta resolved CLOUDSTACK-4785.
-

Resolution: Fixed

> Add support for adding details to UserVm
> 
>
> Key: CLOUDSTACK-4785
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4785
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
>Reporter: Nitin Mehta
>Assignee: Nitin Mehta
> Fix For: 4.2.1
>
>




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

[jira] [Commented] (CLOUDSTACK-4782) Product name is not correct in Installation Guide section

[Travis Graham (JIRA)]

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

Travis Graham commented on CLOUDSTACK-4782:
---

This has been fixed in the 4.2.0 docs.

> Product name is not correct in Installation Guide section
> -
>
> Key: CLOUDSTACK-4782
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4782
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.1.1
>Reporter: Demetrius Tsitrelis
>Priority: Minor
>
> In several places in the admin and install guides the $PRODUCT variable is 
> used.  For instance, in section "3.6. Building RPMs from Source", there is a 
> phrase "Building RPMs for $PRODUCT". The "$PRODUCT" is presumably Apache 
> CloudStack?



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

[jira] [Created] (CLOUDSTACK-4804) Can't install to Debian with build infrastructure (Apt)

[Douglas Almquist (JIRA)]

Douglas Almquist created CLOUDSTACK-4804:


 Summary: Can't install to Debian with build infrastructure (Apt)
 Key: CLOUDSTACK-4804
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4804
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Install and Setup, Management Server
Affects Versions: 4.2.0
 Environment: Though 4.2 has released, the Debian build sources do not 
support this release.
Reporter: Douglas Almquist
 Fix For: Future


Changing 4.1 -> 4.2 in sources generates errors.
It appears only 4.1 is supported.

Test system:  Ubuntu 12.04.3 LTR




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

[jira] [Updated] (CLOUDSTACK-4797) Installation guide for 4.2 instructs users to install 4.1

[Douglas Almquist (JIRA)]

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

Douglas Almquist updated CLOUDSTACK-4797:
-

Description: 
In the 4.2.0 Installation guide (

It states the following: [cut/paste from web page]
4.4.1. DEB package repository
You can add a DEB package repository to your apt sources with the following 
commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
being built at this time.
Use your preferred editor and open (or create) 
/etc/apt/sources.list.d/cloudstack.list. Add the community provided repository 
to the file:

deb http://cloudstack.apt-get.eu/ubuntu precise 4.1

Note:  attempting to change source files to point to the 4.2 branch creates 
errors.  It appears only 4.1 is supported despite the release of 4.2.
Reference bug CLOUDSTACK-4804 

  was:
In the 4.2.0 Installation guide (

It states the following: [cut/paste from web page]
4.4.1. DEB package repository
You can add a DEB package repository to your apt sources with the following 
commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
being built at this time.
Use your preferred editor and open (or create) 
/etc/apt/sources.list.d/cloudstack.list. Add the community provided repository 
to the file:

deb http://cloudstack.apt-get.eu/ubuntu precise 4.1


> Installation guide for 4.2 instructs users to install 4.1
> -
>
> Key: CLOUDSTACK-4797
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4797
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Management Server
>Affects Versions: 4.1.0, 4.2.0
> Environment: Debian/Ubuntu
>Reporter: Douglas Almquist
>  Labels: 4.2, guide, installation
> Fix For: Future
>
> Attachments: configure-package-respository.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the 4.2.0 Installation guide (
> It states the following: [cut/paste from web page]
> 4.4.1. DEB package repository
> You can add a DEB package repository to your apt sources with the following 
> commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are 
> being built at this time.
> Use your preferred editor and open (or create) 
> /etc/apt/sources.list.d/cloudstack.list. Add the community provided 
> repository to the file:
> deb http://cloudstack.apt-get.eu/ubuntu precise 4.1
> Note:  attempting to change source files to point to the 4.2 branch creates 
> errors.  It appears only 4.1 is supported despite the release of 4.2.
> Reference bug CLOUDSTACK-4804 



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

[jira] [Created] (CLOUDSTACK-4805) Installation instructions drops support for Ubuntu

[Douglas Almquist (JIRA)]

Douglas Almquist created CLOUDSTACK-4805:


 Summary: Installation instructions drops support for Ubuntu 
 Key: CLOUDSTACK-4805
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4805
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc, Install and Setup
Affects Versions: 4.1.0
 Environment: Ubuntu 12.04 LTR
Reporter: Douglas Almquist
 Fix For: Future


In section 4.5.7.2. Using the Management Server as the NFS Server, 
the instructions fail to include steps relevant to Ubuntu.

Files and directories referenced do not exist in this environment.



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

[jira] [Created] (CLOUDSTACK-4806) Return "path" parameter as a result of all Volume calls.

[Nitin Mehta (JIRA)]

Nitin Mehta created CLOUDSTACK-4806:
---

 Summary: Return "path" parameter as a result of all Volume calls.
 Key: CLOUDSTACK-4806
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4806
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Reporter: Nitin Mehta






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

[jira] [Assigned] (CLOUDSTACK-1579) List view widget: Support actions on multiple rows

[Chris Suich (JIRA)]

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

Chris Suich reassigned CLOUDSTACK-1579:
---

Assignee: Brian Federle  (was: Chris Suich)

I have passed on the torch for this issue. My changes for actually creating the 
checkboxes and handling the multi-select actions is now in master. There is 
some styling work left to be done and hardening that will come along with 
actually using this feature throughout the UI.

> List view widget: Support actions on multiple rows
> --
>
> Key: CLOUDSTACK-1579
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1579
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Reporter: Brian Federle
>Assignee: Brian Federle
> Fix For: Future
>
> Attachments: Screen Shot 2013-08-30 at 8.46.11 AM.png, Screen Shot 
> 2013-08-30 at 8.46.29 AM.png, Screen Shot 2013-08-30 at 8.46.36 AM.png
>
>   Original Estimate: 144h
>  Remaining Estimate: 144h
>
> Currently, actions can only be executed manually, 1 row at a time. Need to 
> implement ability to select multiple list view items, and perform actions on 
> them at once:
> -Adds checkboxes to the left side of the list view
> -If 1 or more rows are checked, adds toolbar menu under table header with 
> supported actions to apply to all selected rows
> Technical requirements:
> -Need design for new layout and UX for executing multi-row actions
> -Refactor list view widget code to support selection of multiple list items, 
> and passing multiple items of data to API call code.
> -Change API calls to support multiple row objects passed though the context 
> object, in all sections where it is useful:
> -- Instances page
> -- Events/alerts (for deleting multiple events/alerts)
> -- Storage page
> -- etc.



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

[jira] [Commented] (CLOUDSTACK-4806) Return "path" parameter as a result of all Volume calls.

[Nitin Mehta (JIRA)]

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

Nitin Mehta commented on CLOUDSTACK-4806:
-

commit 73f68438400699da9e1821a7012cc9516f8d7572
Author: Nitin Mehta 
Date:   Thu Oct 3 18:00:42 2013 -0700

CLOUDSTACK-4803:
Return "path" parameter as a result of all Volume calls. But to the admin 
only
Signed off by : nitin mehta


> Return "path" parameter as a result of all Volume calls.
> 
>
> Key: CLOUDSTACK-4806
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4806
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
>Reporter: Nitin Mehta
>




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

[jira] [Commented] (CLOUDSTACK-4803) fix listVirtualMachines to not display vms to the normal users with forDisplay=false

[ASF subversion and git services (JIRA)]

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

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

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

CLOUDSTACK-4803:
Return "path" parameter as a result of all Volume calls. But to the admin only
Signed off by : nitin mehta


> fix listVirtualMachines to not display vms to the normal users with 
> forDisplay=false
> 
>
> Key: CLOUDSTACK-4803
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4803
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
>Reporter: Nitin Mehta
>Assignee: Nitin Mehta
> Fix For: Future
>
>




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

[jira] [Resolved] (CLOUDSTACK-4806) Return "path" parameter as a result of all Volume calls.

[Nitin Mehta (JIRA)]

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

Nitin Mehta resolved CLOUDSTACK-4806.
-

Resolution: Fixed

> Return "path" parameter as a result of all Volume calls.
> 
>
> Key: CLOUDSTACK-4806
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4806
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
>Reporter: Nitin Mehta
>




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

[jira] [Commented] (CLOUDSTACK-4804) Can't install to Debian with build infrastructure (Apt)

[Travis Graham (JIRA)]

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

Travis Graham commented on CLOUDSTACK-4804:
---

Here's the error from an apt-get update:

---

W: Failed to fetch http://cloudstack.apt-get.eu/ubuntu/dists/precise/Release  
Unable to find expected entry '4.2/binary-amd64/Packages' in Release file 
(Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones 
used instead.



This is caused by what looks like an incomplete binary-amd64 build in the 
Release info.

To work around this for now: 

* comment out the repo in /etc/apt/source.list.d/cloudstack.list
* rerun apt-get update
* download the packages you need 
(http://cloudstack.apt-get.eu/ubuntu/dists/precise/4.2/pool/)
* manually try to install with dpkg -i  for each package (you'll see a 
bunch of dependency error messages)
* run apt-get install -f to install the missing dependencies
* rerun dpkg -i  for each package that's needed



> Can't install to Debian with build infrastructure (Apt)
> ---
>
> Key: CLOUDSTACK-4804
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4804
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup, Management Server
>Affects Versions: 4.2.0
> Environment: Though 4.2 has released, the Debian build sources do not 
> support this release.
>Reporter: Douglas Almquist
> Fix For: Future
>
>
> Changing 4.1 -> 4.2 in sources generates errors.
> It appears only 4.1 is supported.
> Test system:  Ubuntu 12.04.3 LTR



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

[jira] [Commented] (CLOUDSTACK-1579) List view widget: Support actions on multiple rows

[David La Motta (JIRA)]

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

David La Motta commented on CLOUDSTACK-1579:


Sweet!

// David

Sent from my iPad



> List view widget: Support actions on multiple rows
> --
>
> Key: CLOUDSTACK-1579
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1579
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Reporter: Brian Federle
>Assignee: Brian Federle
> Fix For: Future
>
> Attachments: Screen Shot 2013-08-30 at 8.46.11 AM.png, Screen Shot 
> 2013-08-30 at 8.46.29 AM.png, Screen Shot 2013-08-30 at 8.46.36 AM.png
>
>   Original Estimate: 144h
>  Remaining Estimate: 144h
>
> Currently, actions can only be executed manually, 1 row at a time. Need to 
> implement ability to select multiple list view items, and perform actions on 
> them at once:
> -Adds checkboxes to the left side of the list view
> -If 1 or more rows are checked, adds toolbar menu under table header with 
> supported actions to apply to all selected rows
> Technical requirements:
> -Need design for new layout and UX for executing multi-row actions
> -Refactor list view widget code to support selection of multiple list items, 
> and passing multiple items of data to API call code.
> -Change API calls to support multiple row objects passed though the context 
> object, in all sections where it is useful:
> -- Instances page
> -- Events/alerts (for deleting multiple events/alerts)
> -- Storage page
> -- etc.



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

[jira] [Created] (CLOUDSTACK-4807) Add unittests for methods in NetUtils

[Saksham Srivastava (JIRA)]

Saksham Srivastava created CLOUDSTACK-4807:
--

 Summary: Add unittests for methods in NetUtils
 Key: CLOUDSTACK-4807
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4807
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Saksham Srivastava
 Fix For: Future


Adding missing unit tests for methods in NetUtils namely mac2Long, byte2Mac, 
long2Mac, ip2Long and long2Ip.



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

[jira] [Created] (CLOUDSTACK-4808) 4.2.1 RPM build failing due to release related changes made in 4.2 branch

[Rayees Namathponnan (JIRA)]

Rayees Namathponnan created CLOUDSTACK-4808:
---

 Summary: 4.2.1 RPM build failing due to release related changes 
made in 4.2 branch 
 Key: CLOUDSTACK-4808
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4808
 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.1
 Environment: 4.2.1 build
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.2.1


4.2.1 RPM build failing, we need to remove below two check-ins from 4.2.1 
branch; these changes are made during 4.2 release build

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8689f7f504acee7ccbf6870d409cbb47b177d598
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=db9f5243c31cf00dbf3ed4a81585671c27bab469

I have a patch for this already , i will submit this patch .



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

[jira] [Created] (CLOUDSTACK-4809) Can't execute Disk Offering to create a Volume

[Mike Tutkowski (JIRA)]

Mike Tutkowski created CLOUDSTACK-4809:
--

 Summary: Can't execute Disk Offering to create a Volume
 Key: CLOUDSTACK-4809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: Future
 Environment: Ubuntu 12.04
Reporter: Mike Tutkowski
 Fix For: Future


I'm trying to create a volume from a Disk Offering that specifies a 10 GB disk.

When attempting to create a volume from this Disk Offering, I'm told the 
maximum size I can create for a volume is 0 GB.

In VolumeApiServiceImpl, I see a private instance variable called 
_maxVolumeSizeInGb, which appears to be the problem.

It is read from, but never written to (its default value is 0 since it is a 
'long' member variable).



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

[jira] [Created] (CLOUDSTACK-4810) Enable hypervisor snapshots for CloudStack-managed storage (for XenServer and VMware)

[Mike Tutkowski (JIRA)]

Mike Tutkowski created CLOUDSTACK-4810:
--

 Summary: Enable hypervisor snapshots for CloudStack-managed 
storage (for XenServer and VMware)
 Key: CLOUDSTACK-4810
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4810
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
 Environment: Ubuntu 12.04
Reporter: Mike Tutkowski
Assignee: Mike Tutkowski
 Fix For: Future


CloudStack-managed storage was introduced into CloudStack with the new storage 
framework in 4.2.

This allows CloudStack to create and delete storage repositories and datastores 
as needed.

For 4.2 the VDI inside of an SR takes up almost as much space as is available 
in the SR (so there is a one-to-one mapping between an SR and a VDI). This is 
the same idea for datastores and VMDKs.

The SR or datastore should be sized larger than its VDI or VMDK so there is 
space available for hypervisor snapshots that get stored on the same SR or 
datastore.

How much larger can be determined by a cluster-level setting.

For example, if you want a 10 GB CloudStack volume, the storage plug-in in 
question can create, say, a 20 GB volume on its SAN. 10 GB to be used for the 
CloudStack volume and an additional 10 GB for hypervisor snapshots.



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

[jira] [Created] (CLOUDSTACK-4811) Adding Incorrect CIDR in public ip range of zone create wizard is allowing

[Jayapal Reddy (JIRA)]

Jayapal Reddy created CLOUDSTACK-4811:
-

 Summary: Adding Incorrect CIDR in public ip range of zone create 
wizard is allowing
 Key: CLOUDSTACK-4811
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4811
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Controller, UI
Reporter: Jayapal Reddy
 Fix For: 4.2.1


1. Add a new zone from UI add zone wizard.
2. Add incorrect cidr in in 3rd tab Setup network  PUBLIC TRAFFIC
gateway   netmask   VLANStart IP End IP 
10.147.52.1 255.255.25.0   52  10.147.52.100  10.147.52.120

3. UI is allowing the above config
4. The zone will also get deployed.
5. The problem is coming in creating the public interface in system vms. If the 
interface got created problem in reaching the public network.
6. This issue is pain to user because after deploying zone user need to 
recreate zone again. Also some times user don't realise about the 
misconfiguration.



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

[jira] [Created] (CLOUDSTACK-4812) Can't run KVM agent on Ubuntu 12.04

[Mike Tutkowski (JIRA)]

Mike Tutkowski created CLOUDSTACK-4812:
--

 Summary: Can't run KVM agent on Ubuntu 12.04
 Key: CLOUDSTACK-4812
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4812
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: KVM
Affects Versions: Future
 Environment: Ubuntu 12.04
Reporter: Mike Tutkowski
 Fix For: Future


>From an e-mail thread:

Wei ZHOU
Sep 30 (3 days ago)

to me 
Mike,
 
Does CloudStack master bracnh sill not work on your machines for jna related 
issues?
 
If so, could you try backup and remove jna.jar in /usr/share/java directory? 
There could be more than one jna.jar on your managament server, the correct 
jna-4.0.0.jar is in /usr/share/cloudstack-agent/lib/ directory, and Java is 
supposed to search the jar in /usr/share/java at first.
 
I will fix it today.


Wei ZHOU
Sep 30 (3 days ago)

to me 
In cloudstack 4.1, the jna-3.2.4.jar was deployed to /usr/share/java.
It is not removed in cloudstack 4.2 installation.


Wei ZHOU
Sep 30 (3 days ago)

to me 
sorry, jna-3.2.4.jar was deployed by jna-3.2.4-2.el6.x86_64
 
# rpm -qf /usr/share/java/
jna-3.2.4-2.el6.x86_64

Wei ZHOU
Sep 30 (3 days ago)

to me 
[root@da-upgr-01-mgmt ~]# rpm -qf /usr/share/java/
jpackage-utils-1.7.5-3.12.el6.noarch
libgcj-4.4.7-3.el6.x86_64


Wei ZHOU
Sep 30 (3 days ago)

to me 
on Ubuntu
 
root@cs-kvm004:~# apt-file search /usr/share/java/jna-3.2.7.jar
libjna-java: /usr/share/java/jna-3.2.7.jar
 
It could be OK after removing jna.jar from /usr/share/java/:
 
[root@weizhou-centos master(master)]# ls -l /usr/share/java/jna*.jar
-rw-r--r--. 1 root root 133615 Sep 30 10:32 /usr/share/java/jna-3.2.7.jar
[root@weizhou-centos master(master)]# ls -l 
/usr/share/cloudstack-agent/lib/jna*.jar
-rw-r--r--. 1 root root 914639 Sep 25 10:59 
/usr/share/cloudstack-agent/lib/jna-4.0.0.jar

Wei ZHOU
Sep 30 (3 days ago)

to me 
Mike,
 
Sorry to distrub you.
 
I just noticed Wido fixed the issue in commit 
e6fd794ca0b10a00f3fc93e5f3e81ab342f5b860
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=e6fd794ca0b10a00f3fc93e5f3e81ab342f5b860
 
so, please try latest source codes. 


Mike Tutkowski 
Sep 30 (3 days ago)

to Wei 
Hi Wei,

Thanks for the messages.

Yeah, I actually updated after Wido's changes, cleaned, rebuilt, redeployed the 
DEBs, then saw a different JNA error:

log4j:WARN No appenders could be found for logger 
(org.apache.commons.httpclient.params.DefaultHttpParams).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
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:606)
at 
org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
Caused by: java.lang.UnsatisfiedLinkError: Can't obtain updateLastError method 
for class com.sun.jna.Native
at com.sun.jna.Native.initIDs(Native Method)
at com.sun.jna.Native.(Native.java:139)
at org.libvirt.jna.Libvirt.(Unknown Source)
at org.libvirt.Library.(Unknown Source)
at org.libvirt.Connect.(Unknown Source)
at 
com.cloud.hypervisor.kvm.resource.LibvirtConnection.getConnection(LibvirtConnection.java:44)
at 
com.cloud.hypervisor.kvm.resource.LibvirtConnection.getConnection(LibvirtConnection.java:37)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:733)
at com.cloud.agent.Agent.(Agent.java:161)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:421)
at 
com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:376)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:357)
at com.cloud.agent.AgentShell.start(AgentShell.java:454)
... 5 more
Cannot start daemon
Service exit with a return value of 5


Wei ZHOU
Sep 30 (3 days ago)

to me 
Mike,
Could you check the jna*.jar  in /usr/share/java and 
/usr/share/cloudstack-agent/lib?
 
I installed on Ubuntu 13.04, and cloudstack-agent started successfully. It is 
strange.


Mike Tutkowski 
Sep 30 (3 days ago)

to Wei 
Hi Wei,

jna*.jar in /usr/share/java:

-rw-r--r-- 1 root root   133615 Jun  6  2011 jna-3.2.7.jar
lrwxrwxrwx 1 root root   13 Jun  6  2011 jna.jar -> jna-3.2.7.jar
-rw-r--r-- 1 root root   319903 Jun  6  2011 jna-platform-3.2.7.jar
lrwxrwxrwx 1 root root   22 Jun  6  2011 jna-platform.jar -> 
jna-platform-3.2.7.jar

jna*.jar in /usr/share/cloudstack-agent/lib:

-rwxr-xr-x 1 root 

[jira] [Updated] (CLOUDSTACK-4724) [Vmware] Deploy VM in designated cluster fail if there is only zone wide primary storage and no cluster PS

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4724:
---

Fix Version/s: (was: 4.2.0)
   4.2.1

> [Vmware] Deploy VM in designated cluster fail if there is only zone wide 
> primary storage and no cluster PS 
> ---
>
> Key: CLOUDSTACK-4724
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4724
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: MS   10.223.195.99   vmware  upgrade  2.2.16 ->  
> 4.2
> host  ESXi   5.0 
> 1.  advance zone ,  zone 1 cluster 1  host 1
>  zone 2 cluster 2  host 2
> 2. upgrade  2.2.16 -> 4.2
> 3. after upgrade add cluster 3 host 3 to zone 1:
>  zone 1 cluster 1  host 1
>   cluster primary storage PS1
> cluster 3  host 3
>   ZONE wide primary storage 
> zonewidePS8
>  zone 2 cluster 2  host 2
>   cluster primary storage PS2
> 4. Deploy VM on host 3 using host tags FAIL  even  when there is ZONE wide PS 
> and no cluster wide PS
> 
>Reporter: angeline shen
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - 
> Mozilla Firefox-1.png, Screenshot-CloudPlatform™ - Mozilla Firefox-2.png, 
> Screenshot-CloudPlatform™ - Mozilla Firefox-2.png
>
>
> MS   10.223.195.99   vmware  upgrade  2.2.16 ->  4.2
> host  ESXi   5.0 
> 1.  advance zone ,  zone 1 cluster 1  host 1
>  zone 2 cluster 2  host 2
> 2. upgrade  2.2.16 -> 4.2
> 3. after upgrade add cluster 3 host 3 to zone 1:
>  zone 1 cluster 1  host 1
>   cluster primary storage PS1
> cluster 3  host 3
>   ZONE wide primary storage 
> zonewidePS8
>  zone 2 cluster 2  host 2
>   cluster primary storage PS2
> 4. Deploy VM on host 3 using host tags FAIL  even  when there is ZONE wide PS 
> and no cluster wide PS



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

[jira] [Updated] (CLOUDSTACK-4750) bond.VLAN mapping in iptables FORWARD chain not created consistently

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4750:
---

Fix Version/s: (was: 4.2.1)
   (was: 4.2.0)

> bond.VLAN mapping in iptables FORWARD chain not created consistently
> 
>
> Key: CLOUDSTACK-4750
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4750
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
> Environment: CloudStack 4.2, Advanced Zone with Security Groups, 
> XenServer 6.2
>Reporter: Gerard Lynch
>Priority: Critical
> Fix For: Future
>
>
> Create an Advanced Zone with Security Groups.
> Setup multiple subnets using multiple VLANs (e.g. 
> 1230,1231,1232,1233,1234,1235) on a physical network labelled GUEST.
> Run up VM's in each network
> Note I'm not able to consistently reproduce this.
> *Issue:*
> bond.VLAN interface does not consistently get added to the FORWARD chain in 
> iptables preventing connectivity to/from a VM
> e.g. if I run up a machine on VLAN 1233
> Looking through the management-server.log files I see it setting it up:
> [root@csm1 management]# zcat management-server.log.2013-09-26.gz | grep 1233 
> -A 5 -B 5
> ...
> 2013-09-26 18:52:27,850 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-20:null) Creating VIF for i-2-22-VM on nic 
> [Nic:Guest-192.168.3.69-vlan://1233]
> 2013-09-26 18:52:27,852 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-20:null) Looking for network named GUEST
> 2013-09-26 18:52:27,882 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-20:null) Found a network called GUEST on host=10.1.2.3;  
> Network=ceb6ea91-de34-cf95-5326-f865be6851a2; 
> pif=5884f784-f9ce-58a6-517f-30caa04e67be
> 2013-09-26 18:52:27,883 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-20:null) Creating VLAN 1233 on host 10.1.2.3 on device bond2
> 2013-09-26 18:52:28,482 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-8:null) Seq 9-390463667: Response Received: 
> 2013-09-26 18:52:28,482 DEBUG [agent.transport.Request] 
> (StatsCollector-1:null) Seq 9-390463667: Received:  { Ans: , MgmtId: 
> 345052351047, via: 9, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-09-26 18:52:28,488 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-427:null) Seq 10-1220149422: Executing request
> 2013-09-26 18:52:28,637 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-20:null) VLAN is created for 1233.  The uuid is 
> 85d5ad86-40e6-8e6c-e1a6-254ea64df8cd
> 2013-09-26 18:52:28,646 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-20:null) Created a vif b57fdf9e-7d90-7689-0eee-9ad550951189 on 0
> 2013-09-26 18:52:29,262 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-427:null) Seq 10-1220149422: Response Received: 
> 2013-09-26 18:52:29,263 DEBUG [agent.transport.Request] 
> (StatsCollector-1:null) Seq 10-1220149422: Received:  { Ans: , MgmtId: 
> 345052351047, via: 10, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> …
> I inspect the host machine however and see
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>  pkts bytes target prot opt in out source   
> destination 
>94  7460 BRIDGE-FIREWALL  all  --  *  *   0.0.0.0/0
> 0.0.0.0/0   PHYSDEV match --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out bond2.1234 --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out bond2.1230 --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out eth2 --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out bond0 --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out eth3 --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out eth6 --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out eth4 --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out eth7 --physdev-is-bridged 
> 0 0 ACCEPT all  --  *  *   0.0.0.0/00.0.0.0/0 
>   PHYSDEV match --physdev-out eth10 --physdev-is-bridged 
> 0 0 A

[jira] [Updated] (CLOUDSTACK-4777) NullPointerException instead of working KVM HA

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4777:
---

Fix Version/s: Future

> NullPointerException instead of working KVM HA
> --
>
> Key: CLOUDSTACK-4777
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4777
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Hypervisor Controller, KVM, Management Server
>Affects Versions: 4.2.0
> Environment: KVM (CentOS 6.4) with CloudStack 4.2
>Reporter: Valery Ciareszka
>Priority: Critical
> Fix For: Future
>
>
> If  KVM host goes down, CloudStack management does not start HA-enabled VM on 
> the other hosts. There is NullPointerException in management.log:
> 2013-09-24 11:21:25,500 ERROR [cloud.ha.HighAvailabilityManagerImpl] 
> (HA-Worker-4:work-4) Terminating HAWork[4-HA-6-Running-Scheduled]
> java.lang.NullPointerException
> at 
> com.cloud.storage.VolumeManagerImpl.canVmRestartOnAnotherServer(VolumeManagerImpl.java:2641)
> at 
> com.cloud.ha.HighAvailabilityManagerImpl.restart(HighAvailabilityManagerImpl.java:516)
> at 
> com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:831)
> see full log at http://pastebin.com/upnEA601



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

[jira] [Updated] (CLOUDSTACK-4711) UCS:API: Premature API response prevernt CS from syncing association status

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4711:
---

Fix Version/s: 4.2.1

> UCS:API: Premature API response prevernt CS from syncing association status
> ---
>
> Key: CLOUDSTACK-4711
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4711
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS
>Affects Versions: 4.2.0
> Environment: UCS
>Reporter: Parth Jagirdar
>Priority: Critical
> Fix For: 4.2.1
>
>
> We rely on association tag from UCS manager to determine the association 
> success.
> association="none" 
> However UCS sometimes send this response prematurely in which case CS fails 
> the API and association is unsuccessful.
> Eventually UCS finishes association and CS and UCS are now out of sync.
> Now if admin attempts to re-associate this blade then it will error out 
> saying the "Object already exists" 
> We need to device another strategy for this to work flawlessly.
> 2013-09-19 14:35:08,554 WARN  
> [commons.httpclient.SimpleHttpConnectionManager] (Job-Executor-19:job-19 = [ 
> 561e963d-be42-418b-be73-dcb7abf98e08 ]) SimpleHttpConnectionManager being 
> used incorrectly.  Be sure that HttpMethod.releaseConnection() is always 
> called and that only one thread and/or method is using this connection 
> manager at a time.
> 2013-09-19 14:35:08,563 DEBUG [ucs.manager.UcsManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) 
> association response is   cookie="1379626356/ce72a30f-c52f-4772-a546-b2620243" response="yes"> 
>   assignedToDn="" association="none" availability="available" 
> availableMemory="65536" chassisId="1" checkPoint="discovered"  connPath="A" 
> connStatus="A" descr="" discovery="complete" dn="sys/chassis-1/blade-1" 
> fltAggr="0" fsmDescr="" fsmFlags="" fsmPrev="DisassociateSuccess" 
> fsmProgr="100" fsmRmtInvErrCode="none" fsmRmtInvErrDescr="" fsmRmtInvRslt="" 
> fsmStageDescr="" fsmStamp="2013-09-19T14:35:06.906" fsmStatus="nop" 
> fsmTry="0" intId="36071" lc="discovered" lcTs="1969-12-31T16:00:00.000" 
> lowVoltageMemory="low-voltage" managingInst="A" memorySpeed="1333" 
> mfgTime="2012-10-14T01:00:00.000" model="UCSB-B200-M3" name="" 
> numOfAdaptors="1" numOfCores="12" numOfCoresEnabled="12" numOfCpus="2" 
> numOfEthHostIfs="0" numOfFcHostIfs="0" numOfThreads="24" operPower="off" 
> operQualifier="" operState="unassociated" operability="operable" 
> originalUuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" partNumber="73-13217-08" 
> presence="equipped" revision="0"  serial="FCH16407N8A" serverId="1/1" 
> slotId="1"  totalMemory="65536" usrLbl="" 
> uuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" vendor="Cisco Systems Inc" 
> vid="V03"/>  
> 2013-09-19 14:35:08,563 WARN  [cloudstack.api.AssociateUcsProfileToBladeCmd] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Exception:
> com.cloud.utils.exception.CloudRuntimeException: cannot associated a profile 
> to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger for 
> detailed error information
> at 
> com.cloud.ucs.manager.UcsManagerImpl.isBladeAssociated(UcsManagerImpl.java:351)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.associateProfileToBlade(UcsManagerImpl.java:380)
> at 
> org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd.execute(AssociateUcsProfileToBladeCmd.java:58)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-09-19 14:35:08,565 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Complete 
> async job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ], jobStatus: 2, 
> resultCode: 530, result: Error Code: 530 Error text: cannot associated a 
> profile to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger 
> for detailed error information
> 2013-09-19 14:35:09,006 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
> ===START===  10.252.113.141 -- GET  
> command=queryAsyncJobResult&jobId=561e963d-be42-418b-be73-dcb7abf98e08&r

[jira] [Updated] (CLOUDSTACK-4740) Some vSphere VMs are shutdown when ACS is restarted

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4740:
---

Fix Version/s: (was: 4.1.1)
   (was: 4.2.0)
   (was: Future)
   (was: 4.1.0)
   4.2.1

> Some vSphere VMs are shutdown when ACS is restarted
> ---
>
> Key: CLOUDSTACK-4740
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4740
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0, 4.1.1, 4.2.0, Future
> Environment: I'm running ACS 4.1.1 with vSphere 5.1
>Reporter: ilya musayev
>Priority: Critical
>  Labels: management, poweroff
> Fix For: 4.2.1
>
>
> If management server is restarted, when management server starts - it checks 
> whether the agentState for vSphere VMs and if it does not get a proper 
> response, it marks them as stopped.
> As the result, some of my virtual instances would shutdown.
> Attempting to analyze this issue further, here are my findings and errors 
> seen in the log.
> 2013-09-25 14:35:49,928 DEBUG [vmware.resource.VmwareResource] 
> (AgentTaskPool-1:null) Detecting a new state but couldn't find a old state so 
> adding it to the changes: i-2-262-acs-docs-fc17
> 2013-09-25 14:35:51,213 DEBUG [agent.transport.Request] 
> (AgentTaskPool-1:null) Seq -1--1: Startup request from directly connected 
> host:  { Cmd , MgmtId: -1, via: -1, Ver: v1, Flags: 11, 
> [{"cpus":16,"speed":2199,"memory":68683468800,"dom0MinMemory":0,"poolSync":false,"vms":{"i-8-270-CLOUD411":{"state":"Running"},"r-15-CLOUD41-OLD":{"state":"Stopped"},"v-260-CLOUD411":{"state":"Running"},"i-2-283-vmbld01l-ops-08":{"state":"Running"},"i-2-104-ACS41VM":{"state":"Running"},"--s-1-CLOUD41-OLD":{"state":"Running"},"i-27-280-CLOUD411":{"state":"Running"},"i-2-285-ossec01l-ops-08":{"state":"Running"},"i-2-262-acs-docs-fc17":{"state":"Stopped"},"i-24-265-test3":{"state":"Running"},"cloud01l-ops-08.portal.webmd.com":{"state":"Running"},"i-2-278-demo01t-ops-08":{"state":"Running"},"s-63-CLOUD411":{"state":"Running"},"r-66-CLOUD411":{"state":"Running"},"i-2-281-acs-appliance":{"state":"Running"}},"caps":"hvm","hypervisorType":"VMware","hostDetails":{"com.cloud.network.Networks.RouterPrivateIpStrategy":"DcGlobal","NativeHA":"true"},"hypervisorVersion":"5.0","type":"Routing","dataCenter":"2","pod":"2","cluster":"3","guid":"HostSystem:host-19...@vc00q-ops-08.portal.webmd.com","name":"vmha62d-ops-08.portal.webmd.com","version":"4.1.1-SNAPSHOT","privateIpAddress":"172.25.243.31","privateMacAddress":"68:b5:99:73:0b:c2","privateNetmask":"255.255.255.0","storageIpAddress":"172.25.243.31","storageNetmask":"255.255.255.0","storageMacAddress":"68:b5:99:73:0b:c2","wait":0},{"totalSize":0,"poolInfo":{"uuid":"72c8aedb-58c4-4569-ac51-adc5af770bf6","host":"vmha62d-ops-08.portal.webmd.com","localPath":"","hostPath":"datastore-19718","poolType":"LVM","capacityBytes":141465485312,"availableBytes":140383354880},"resourceType":"STORAGE_POOL","hostDetails":{},"type":"Storage","dataCenter":"2","pod":"2","cluster":"3","guid":"72c8aedb-58c4-4569-ac51-adc5af770bf6","name":"72c8aedb-58c4-4569-ac51-adc5af770bf6","wait":0}]
>  }
> 2013-09-25 14:35:53,614 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (AgentTaskPool-1:null) VM i-2-262-acs-docs-fc17: cs state = Running and 
> realState = Stopped
> 2013-09-25 14:35:53,614 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (AgentTaskPool-1:null) VM i-2-262-acs-docs-fc17: cs state = Running and 
> realState = Stopped
> 2013-09-25 14:35:53,614 INFO  [cloud.ha.HighAvailabilityManagerImpl] 
> (AgentTaskPool-1:null) Skip HA for VMware VM i-2-262-acs-docs-fc17
> 2013-09-25 14:35:53,694 DEBUG [agent.transport.Request] 
> (AgentTaskPool-1:null) Seq 11-1418264581: Sending  { Cmd , MgmtId: 
> 345049078181, via: 11, Ver: v1, Flags: 100101, 
> [{"StopCommand":{"isProxy":false,"vmName":"i-2-262-acs-docs-fc17","wait":0}},{"StopCommand":{"isProxy":false,"vmName":"i-2-278-demo01t-ops-08","wait":0}},{"StopCommand":{"isProxy":false,"vmName":"i-2-281-acs-appliance","wait":0}},{"StopCommand":{"isProxy":false,"vmName":"i-2-283-vmbld01l-ops-08","wait":0}},{"StopCommand":{"isProxy":false,"vmName":"i-2-285-ossec01l-ops-08","wait":0}}]
>  }
> 2013-09-25 14:35:53,695 DEBUG [agent.transport.Request] 
> (AgentTaskPool-1:null) Seq 11-1418264581: Executing:  { Cmd , MgmtId: 
> 345049078181, via: 11, Ver: v1, Flags: 100101, 
> [{"StopCommand":{"isProxy":false,"vmName":"i-2-262-acs-docs-fc17","wait":0}},{"StopCommand":{"isProxy":false,"vmName":"i-2-278-demo01t-ops-08","wait":0}},{"StopCommand":{"isProxy":false,"vmName":"i-2-281-acs-appliance","wait

[jira] [Updated] (CLOUDSTACK-4549) ceph:deployvm from template created from snapshot is failing

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4549:
---

Fix Version/s: 4.2.1

> ceph:deployvm from template created from snapshot is failing
> 
>
> Key: CLOUDSTACK-4549
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4549
> 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.1
>
> Attachments: management-server.rar
>
>
> VM deployment form template which is created form snapshot is failing where 
> as VM deployment with uploaded template successful.
> created template form snapshot is storing in raw 
> format(https://10-147-49-100.realhostip.com/userdata/0c826645-ec82-40f1-a1b0-38fc9ba1c76f.raw)..
>  not sure are we converting again to QCwo2
> when we try to deploy a VM
> steps:
> 1.create a ceph instance(configure compute offering with RBD and deploy a vm)
> 2.Once it successful,select the root partition and perform snapshot
> 3.once snapshot successful,create a template from snapshot
> 4 try to create vm uning above VM
> actual result:
> deploy vm failing with exception
> -29 15:21:43,756 DEBUG [cloud.network.NetworkModelImpl] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Service 
> SecurityGroup is not supported in the network id=204
> 2013-08-29 15:21:43,762 DEBUG 
> [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-14:job-42 = 
> [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Applying userdata and password 
> entry in network Ntwk[204|Guest|8]
> 2013-08-29 15:21:43,800 DEBUG [agent.transport.Request] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Seq 
> 1-2089159931: Sending  { Cmd , MgmtId: 7175246184473, via: 1, Ver: v1, Flags: 
> 100111, 
> [{"com.cloud.agent.api.routing.SavePasswordCommand":{"password":"fnirq_cnffjbeq","vmIpAddress":"10.1.1.140","vmName":"6e798618-8e4d-4305-94a1-642e5f3aad08","executeInSequence":true,"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.ip":"169.254.2.248","router.name":"r-15-VM"},"wait":0}},{"com.cloud.agent.api.routing.VmDataCommand":{"vmIpAddress":"10.1.1.140","vmName":"6e798618-8e4d-4305-94a1-642e5f3aad08","executeInSequence":true,"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.ip":"169.254.2.248","router.name":"r-15-VM"},"wait":0}}]
>  }
> 2013-08-29 15:21:44,168 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-14:null) Seq 1-2089159931: Processing:  { Ans: , 
> MgmtId: 7175246184473, via: 1, Ver: v1, Flags: 110, 
> [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":true,"wait":0}}]
>  }
> 2013-08-29 15:21:44,169 DEBUG [agent.manager.AgentAttache] 
> (AgentManager-Handler-14:null) Seq 1-2089159931: No more commands found
> 2013-08-29 15:21:44,169 DEBUG [agent.transport.Request] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Seq 
> 1-2089159931: Received:  { Ans: , MgmtId: 7175246184473, via: 1, Ver: v1, 
> Flags: 110, { Answer, Answer } }
> 2013-08-29 15:21:44,179 DEBUG [cloud.network.NetworkModelImpl] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Service 
> SecurityGroup is not supported in the network id=204
> 2013-08-29 15:21:44,182 DEBUG [cloud.storage.VolumeManagerImpl] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Checking 
> if we need to prepare 1 volumes for 
> VM[User|6e798618-8e4d-4305-94a1-642e5f3aad08]
> 2013-08-29 15:21:44,207 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) template 
> 202 is already in store:1, type:Image
> 2013-08-29 15:21:44,219 DEBUG [storage.datastore.PrimaryDataStoreImpl] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Not found 
> (templateId:202poolId:5) in template_spool_ref, persisting it
> 2013-08-29 15:21:44,234 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) template 
> 202 is already in store:5, type:Primary
> 2013-08-29 15:21:44,237 DEBUG [storage.volume.VolumeServiceImpl] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Found 
> template 246c1e4ac-9fc0-3122-bcfb-77deff789f61 in storage pool 5 with 
> VMTemplateStoragePool id: 5
> 2013-08-29 15:21:44,433 DEBUG [storage.volume.VolumeServiceImpl] 
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Acquire 
> lock on VMTemplateStoragePool 5 with timeout 3600 seconds
> 2013-08-29 15:21:44,438 I

[jira] [Updated] (CLOUDSTACK-4351) 4.3.2. Host/Hypervisor System Requirements has misleading or premature note

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4351:
---

Priority: Critical  (was: Blocker)

> 4.3.2. Host/Hypervisor System Requirements has misleading  or premature note
> 
>
> Key: CLOUDSTACK-4351
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4351
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
> Environment: All
>Reporter: Ron Wheeler
>Priority: Critical
> Fix For: 4.2.1
>
>
> Note
> If DHCP is used for hosts, ensure that no conflict occurs between DHCP server
> used for these hosts and the DHCP router created by CloudStack.
> How can you do this at this point?
> Cloudstack does not have a DHCP server at this point.
> There is nothing for the user to do at this point.
> It should be moved to closer to the point where the DHCP server addresses are 
> specified.



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

[jira] [Updated] (CLOUDSTACK-4348) EN: Regression Truncation issues occurred when moving the cursor to the "plus" buttons.

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4348:
---

Fix Version/s: 4.2.1

> EN: Regression Truncation issues occurred when moving the cursor to the 
> "plus" buttons.
> ---
>
> Key: CLOUDSTACK-4348
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4348
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, UI
>Affects Versions: 4.2.0
> Environment: Environment
> Build#CloudPlatform-4.2-426(CloudPlatform-4.2-426-rhel6.3.tar.gz) 
> XenServer6.1 for Host Server
> CentOS6.3 for NFS, CS-Mgr Servers.
> Client & Browser: Win7-Chrome, Win7-Firefox22.0, Mac-Safari, Win7-IE10
>Reporter: Minying Bao
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: 1.Instance_Truncation.jpg, Truncation Issues.zip
>
>
> Prerequisite
> Upload a Template/ISO. then created vm in instances tab.
> Repro Steps
> 1. Open the browser and login to Web Portal.
> 2. Navigate the “instances” tab.
> 3. Click to the newly created vm.
> 4. Move the mouse cursor to “plus” button.
> 5. Observe the UI.
> Expected Result
> It should display as normal.
> Actual Result
> Truncation issue occurred.
> Some other 'plus' buttons are all repro the truncations. Please refer to 
> attached screenshots for details.
> Brower Info.
> Mac-Safari -> Fail
> Win7-Firefox22.0 -> Fail
> Win7-Chrome -> Fail
> Win7-IE10 -> Fail
> Regression Info.
> Build#CloudPlatform-4.2-373->Pass
> Build#CloudPlatform-4.2-389->Fail
> Build#CloudPlatform-4.2-426->Fail



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

[jira] [Updated] (CLOUDSTACK-4351) 4.3.2. Host/Hypervisor System Requirements has misleading or premature note

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4351:
---

Fix Version/s: 4.2.1

> 4.3.2. Host/Hypervisor System Requirements has misleading  or premature note
> 
>
> Key: CLOUDSTACK-4351
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4351
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
> Environment: All
>Reporter: Ron Wheeler
>Priority: Blocker
> Fix For: 4.2.1
>
>
> Note
> If DHCP is used for hosts, ensure that no conflict occurs between DHCP server
> used for these hosts and the DHCP router created by CloudStack.
> How can you do this at this point?
> Cloudstack does not have a DHCP server at this point.
> There is nothing for the user to do at this point.
> It should be moved to closer to the point where the DHCP server addresses are 
> specified.



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

[jira] [Updated] (CLOUDSTACK-4366) G11n: JA: Ubuntu VM: Key translation fails for the Japanese keyboard Menu key & Caps Lock

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4366:
---

Fix Version/s: 4.2.1

> G11n: JA: Ubuntu VM: Key translation fails for the Japanese keyboard Menu key 
> & Caps Lock
> -
>
> Key: CLOUDSTACK-4366
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4366
> 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: Environment:
> Build# CloudPlatform-4.2-426 (CloudPlatform-4.2-426-rhel6.3.tar.gz) 
> XenServer6.1 for Host Server
> CentOS6.3 for NFS & CS-Mgr Servers
> Launch a Ubuntu VM
> Ubuntu/Win7 for Client machine 
>Reporter: Minying Bao
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: Build#4.2-389_JA Ubuntu Keyboard_issues.xlsx
>
>
> Steps
> 1. Setup the CloudStack environments with build#4.2-426.
> 2. Bring Japanese Ubuntu12.04 TSL VM.
> 3. Access the VM via Console Proxy from the Japanese client machine connected 
> to Japanese Keyboard.
> 4. Hit all the keys with Japanese localized keyboard.
> Expected Result
> All the keys should work fine.
> Actual Result
> The Menu key & Caps Lock key are not working well.(Refer to attached Excel.)



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

[jira] [Updated] (CLOUDSTACK-4099) update the systemvm templates in DevCloud2

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4099:
---

Fix Version/s: Future

> update the systemvm templates in DevCloud2
> --
>
> Key: CLOUDSTACK-4099
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4099
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: DevCloud
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Priority: Critical
> Fix For: Future
>
>
> DevCloud2 is still using the old templates for systemVMs. These need to be
> updated to the latest stable templates available from jenkins. Fixes exist for
> 1. vm time sync with hypervisor
> 2. vhd-util within systemvm
> 3. latest haproxy
> 4. irqbalance fix
> etc



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

[jira] [Assigned] (CLOUDSTACK-4148) usage:usage stats are not triggered for shared network

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek reassigned CLOUDSTACK-4148:
--

Assignee: Kishan Kavala

> usage:usage stats are not triggered for shared network
> --
>
> Key: CLOUDSTACK-4148
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4148
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Usage
>Affects Versions: 4.2.0
>Reporter: sadhu suresh
>Assignee: Kishan Kavala
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.rar
>
>
> steps:
> 1.create network offering with SRX and F5 
> 2.create a shared guestnetwork using above NO
> 3.deploy a VM using abobve network
> 4.generate the traffic and check the usage stats after 10 min
> actual:
> NetworkUsageCommand: is running only for isolated network and its not issuing 
> for  for sharednetwok.
> router-12 isbelongs to sharednetwork.
> r-4-0vm belongs to isloated network
> No query specified
> mysql> select * from user_statistics;
> ++++---+---+--++++++++
> | id | data_center_id | account_id | public_ip_address | device_id | 
> device_type  | network_id | net_bytes_received | net_bytes_sent | 
> current_bytes_received | current_bytes_sent | agg_bytes_received | 
> agg_bytes_sent |
> ++++---+---+--++++++++
> |  1 |  1 |  2 | NULL  | 4 | 
> DomainRouter |204 |  0 |  0 | 
>  0 | 401016 |  0 | 401016 |
> |  2 |  1 |  1 | NULL  |12 | 
> DomainRouter |206 |  0 |  0 | 
>  0 |  0 |  0 |  0 |
> |  3 |  1 |  1 | NULL  |18 | 
> DomainRouter |209 |  0 |  0 | 
>  0 |  0 |  0 |  0 |
> |  4 |  1 |  2 | 10.147.49.106 |21 | 
> DomainRouter |200 |  0 |  0 | 
>4195797 | 148136 |4195797 | 148136 |
> |  5 |  1 |  2 | NULL  |21 | 
> DomainRouter |210 |  0 |  0 | 
>  0 |  0 |  0 |  0 |
> ++++---+---+--++++++++
> 5 rows in set (0.00 sec)



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

[jira] [Updated] (CLOUDSTACK-4148) usage:usage stats are not triggered for shared network

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4148:
---

Fix Version/s: (was: Future)
   4.2.1

> usage:usage stats are not triggered for shared network
> --
>
> Key: CLOUDSTACK-4148
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4148
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Usage
>Affects Versions: 4.2.0
>Reporter: sadhu suresh
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.rar
>
>
> steps:
> 1.create network offering with SRX and F5 
> 2.create a shared guestnetwork using above NO
> 3.deploy a VM using abobve network
> 4.generate the traffic and check the usage stats after 10 min
> actual:
> NetworkUsageCommand: is running only for isolated network and its not issuing 
> for  for sharednetwok.
> router-12 isbelongs to sharednetwork.
> r-4-0vm belongs to isloated network
> No query specified
> mysql> select * from user_statistics;
> ++++---+---+--++++++++
> | id | data_center_id | account_id | public_ip_address | device_id | 
> device_type  | network_id | net_bytes_received | net_bytes_sent | 
> current_bytes_received | current_bytes_sent | agg_bytes_received | 
> agg_bytes_sent |
> ++++---+---+--++++++++
> |  1 |  1 |  2 | NULL  | 4 | 
> DomainRouter |204 |  0 |  0 | 
>  0 | 401016 |  0 | 401016 |
> |  2 |  1 |  1 | NULL  |12 | 
> DomainRouter |206 |  0 |  0 | 
>  0 |  0 |  0 |  0 |
> |  3 |  1 |  1 | NULL  |18 | 
> DomainRouter |209 |  0 |  0 | 
>  0 |  0 |  0 |  0 |
> |  4 |  1 |  2 | 10.147.49.106 |21 | 
> DomainRouter |200 |  0 |  0 | 
>4195797 | 148136 |4195797 | 148136 |
> |  5 |  1 |  2 | NULL  |21 | 
> DomainRouter |210 |  0 |  0 | 
>  0 |  0 |  0 |  0 |
> ++++---+---+--++++++++
> 5 rows in set (0.00 sec)



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

[jira] [Updated] (CLOUDSTACK-4072) [DOC][upgrade][2.2.14 to 4.2][CentOS5 RPM builds] mysql-connector-java rpm dependency while upgrading from 2.2.14 to 4.2

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4072:
---

Fix Version/s: (was: 4.2.0)
   4.2.1

> [DOC][upgrade][2.2.14 to 4.2][CentOS5 RPM builds] mysql-connector-java rpm 
> dependency while upgrading from 2.2.14 to 4.2
> 
>
> Key: CLOUDSTACK-4072
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4072
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Packaging
>Affects Versions: 4.2.0
> Environment: MS : CentOS 5.6
> Host : ESX 4.1
> Rhel 5 builds are used to install and upgrade
>Reporter: Abhinav Roy
>Priority: Critical
> Fix For: 4.2.1
>
>
> Steps :
> ===
> 1. Install CS advanced zone setup on CentOS 5.6 management server with Rhel 5 
> build for 2.2.14 
> 2. Do some operations before upgrade.
> 3. Upgrade to 4.2 , rhel 5 build .
> Upgrade fails with this dependency :
> [root@MS-CentOS56 CloudPlatform-4.2-4.2-55-rhel5]# ./install.sh
> Setting up the temporary repository...
> Cleaning Yum cache...
> Loaded plugins: fastestmirror
> 7 metadata files removed
> Welcome to the CloudPlatform Installer.  What would you like to do?
> NOTE:   For installing KVM agent, please setup 
> EPEL yum repo first;
> For installing CloudPlatform on RHEL6.x, please setup 
> distribution yum repo either from ISO or from your registeration account.
> 3.We detect you already have MySql server installed, you can 
> bypass mysql install chapter in CloudPlatform installation guide.
> Or you can use E) to remove current mysql then re-run install.sh 
> selecting D) to reinstall if you think existing MySql server has some trouble.
> For MySql downloaded from community, the script may not be able to 
> detect it.
> M) Install the Management Server
> A) Install the Agent
> B) Install BareMetal Agent
> S) Install the Usage Monitor
> U) Upgrade the CloudPlatform packages installed on this computer
> R) Stop any running CloudPlatform services and remove the CloudPlatform 
> packages from this computer
> E) Remove the MySQL server (will not remove the MySQL databases)
> Q) Quit
>  > u
> Updating the CloudPlatform and its dependencies...
> Loaded plugins: fastestmirror
> Loading mirror speeds from cached hostfile
>  * base: centos.mirror.net.in
>  * extras: centos.mirror.net.in
>  * updates: centos.mirror.net.in
> base
> cloud-temp
> cloud-temp/primary
> cloud-temp
> extras
> updates
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated
> ---> Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el5 set to be 
> updated
> --> Processing Dependency: cloudstack-awsapi = 4.2.0 for package: 
> cloudstack-management
> --> Processing Dependency: mysql-connector-java for package: 
> cloudstack-management
> --> Running transaction check
> ---> Package cloudstack-awsapi.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated
> ---> Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el5 set to be 
> updated
> --> Processing Dependency: mysql-connector-java for package: 
> cloudstack-management
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.
> workaround : Download that package from 
> http://dl.fedoraproject.org/pub/epel/5/x86_64/  follow the 
> instructions at 
> http://pkgs.org/centos-5-rhel-5/epel-i386/mysql-connector-java-5.1.12-2.el5.i386.rpm.html
>   .



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

[jira] [Updated] (CLOUDSTACK-3243) [DOC]Wrong NFS mount point in documentation

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-3243:
---

Fix Version/s: 4.2.1

> [DOC]Wrong NFS mount point in documentation
> ---
>
> Key: CLOUDSTACK-3243
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3243
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Install and Setup
>Affects Versions: 4.1.0, 4.2.0
> Environment: KVM
>Reporter: Ron Wheeler
>Priority: Blocker
> Fix For: 4.2.1
>
>
> At "4.5.8. Prepare the System VM Template" the instructions give the 
> following command.
>  
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>  -m /mnt/secondary -u 
> http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 
> -h kvm -s  -F
> In "4.5.6.2. Using the Management Server as the NFS Server" the following 
> commands were give
> # mkdir /primarymount
> # mount -t nfs :/export/primary /primarymount
> # umount /primarymount
> # mkdir /secondarymount
> # mount -t nfs :/export/secondary /secondarymount
> # umount /secondarymount
> This results in a mismatch betweenthe location of the NSF storage which 
> causes the error:
> mount point /mnt/secondary doesn't exist\n
> Installation failed
> "4.5.6.1. Using a Separate NFS Server"  has the storage mounted at  
> /mnt/secondary
> The documentation needs to be made consistent. 
> Probably  "4.5.6.2. Using the Management Server as the NFS Server" needs 
> fixing.



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

[jira] [Updated] (CLOUDSTACK-3715) Live Migration of Virtual instances operation is getting timedout

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-3715:
---

Fix Version/s: (was: 4.2.0)
   4.2.1

> Live Migration of Virtual instances operation is getting timedout 
> --
>
> Key: CLOUDSTACK-3715
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3715
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: 195113management-server.log.gz, 
> 195117management-server.log.gz, apilog.log, cloud-backup.dmp.gz, 
> cloud-backup.sql.gz, management-server.log, migrationlogs.rar
>
>
> Setup: Multinode Management setup. 
> Steps:
> 1. Configure Adv Zone with 2 VMWARE clusters each with one hosts with Zone 
> wide primary storage ( Standard vSwitch cluster) 
> 2. Deploy VM using User account 
> 3. Tried to Live migrate VM from cluster1 (host 1)  to  Cluster 2 (host2 ) 
> Observation:
> 1. Migration took very log time and finally failed saying operation timed out 
> :
> 2013-07-22 17:46:06,288 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) VM state 
> transitted from :Migrating to Running with event: OperationFailedvm's 
> original host id: 4 new host id: 4 host id before state transition: 1
> 2013-07-22 17:46:06,292 INFO  [vmware.resource.VmwareResource] 
> (DirectAgent-421:10.102.192.18) VM i-4-9-VM is no longer in vSphere
> 2013-07-22 17:46:06,293 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-421:null) Seq 1-1311245319: Response Received:
> 2013-07-22 17:46:06,294 DEBUG [agent.transport.Request] 
> (DirectAgent-421:null) Seq 1-1311245319: Processing:  { Ans: , MgmtId: 
> 94838926819810, via: 1, Ver: v1, Flags: 10, 
> [{"com.cloud.agent.api.StopAnswer":{"vncPort":0,"result":true,"details":"VM 
> i-4-9-VM is no longer in vSphere","wait":0}}] }
> 2013-07-22 17:46:06,294 DEBUG [agent.manager.AgentAttache] 
> (DirectAgent-421:null) Seq 1-1311245319: Unable to find listener.
> 2013-07-22 17:46:06,307 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) Hosts's 
> actual total CPU: 9572 and CPU after applying overprovisioning: 9572
> 2013-07-22 17:46:06,307 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) Hosts's 
> actual total RAM: 17166258176 and RAM after applying overprovisioning: 
> 17166258176
> 2013-07-22 17:46:06,307 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) release 
> cpu from host: 1, old used: 2000,reserved: 0, actual total: 9572, total with 
> overprovisioning: 9572; new used: 200,reserved:0; movedfromreserved: 
> false,moveToReserveredfalse
> 2013-07-22 17:46:06,307 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) release 
> mem from host: 1, old used: 2013265920,reserved: 0, total: 17166258176; new 
> used: 2013265920,reserved:0; movedfromreserved: false,moveToReserveredfalse
> 2013-07-22 17:46:06,345 ERROR [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) 
> Unexpected exception while executing 
> org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm 
> VM[User|newuser1i1] along with its volumes. 
> com.cloud.exception.AgentUnavailableException: Resource [Host:1] is 
> unreachable: Host 1: Operation timed out on storage motion for 
> VM[User|newuser1i1]
> at 
> com.cloud.storage.VolumeManagerImpl.migrateVolumes(VolumeManagerImpl.java:2263)
> at 
> com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1780)
> at 
> com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4046)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:137)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Syn

[jira] [Commented] (CLOUDSTACK-4808) 4.2.1 RPM build failing due to release related changes made in 4.2 branch

[Hugo Trippaers (JIRA)]

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

Hugo Trippaers commented on CLOUDSTACK-4808:


Rayees,

Do you have some more details on the error you are encountering? My jenkins 
jobs for packaging report no problem, so i would like to know which error you 
are getting. 

Are you packaging the noredist build or the regular build?

Cheers,

Hugo

> 4.2.1 RPM build failing due to release related changes made in 4.2 branch 
> --
>
> Key: CLOUDSTACK-4808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4808
> 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.1
> Environment: 4.2.1 build
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.1
>
>
> 4.2.1 RPM build failing, we need to remove below two check-ins from 4.2.1 
> branch; these changes are made during 4.2 release build
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8689f7f504acee7ccbf6870d409cbb47b177d598
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=db9f5243c31cf00dbf3ed4a81585671c27bab469
> I have a patch for this already , i will submit this patch .



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

[jira] [Assigned] (CLOUDSTACK-4808) 4.2.1 RPM build failing due to release related changes made in 4.2 branch

[Hugo Trippaers (JIRA)]

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

Hugo Trippaers reassigned CLOUDSTACK-4808:
--

Assignee: Hugo Trippaers

> 4.2.1 RPM build failing due to release related changes made in 4.2 branch 
> --
>
> Key: CLOUDSTACK-4808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4808
> 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.1
> Environment: 4.2.1 build
>Reporter: Rayees Namathponnan
>Assignee: Hugo Trippaers
>Priority: Blocker
> Fix For: 4.2.1
>
>
> 4.2.1 RPM build failing, we need to remove below two check-ins from 4.2.1 
> branch; these changes are made during 4.2 release build
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8689f7f504acee7ccbf6870d409cbb47b177d598
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=db9f5243c31cf00dbf3ed4a81585671c27bab469
> I have a patch for this already , i will submit this patch .



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

[jira] [Commented] (CLOUDSTACK-4808) 4.2.1 RPM build failing due to release related changes made in 4.2 branch

[Rayees Namathponnan (JIRA)]

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

Rayees Namathponnan commented on CLOUDSTACK-4808:
-

yes issue us only with non oss builds from 4.2.1

> 4.2.1 RPM build failing due to release related changes made in 4.2 branch 
> --
>
> Key: CLOUDSTACK-4808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4808
> 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.1
> Environment: 4.2.1 build
>Reporter: Rayees Namathponnan
>Assignee: Hugo Trippaers
>Priority: Blocker
> Fix For: 4.2.1
>
>
> 4.2.1 RPM build failing, we need to remove below two check-ins from 4.2.1 
> branch; these changes are made during 4.2 release build
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8689f7f504acee7ccbf6870d409cbb47b177d598
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=db9f5243c31cf00dbf3ed4a81585671c27bab469
> I have a patch for this already , i will submit this patch .



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

[jira] [Commented] (CLOUDSTACK-4808) 4.2.1 RPM build failing due to release related changes made in 4.2 branch

[Rayees Namathponnan (JIRA)]

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

Rayees Namathponnan commented on CLOUDSTACK-4808:
-

https://reviews.apache.org/r/14482/

> 4.2.1 RPM build failing due to release related changes made in 4.2 branch 
> --
>
> Key: CLOUDSTACK-4808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4808
> 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.1
> Environment: 4.2.1 build
>Reporter: Rayees Namathponnan
>Assignee: Hugo Trippaers
>Priority: Blocker
> Fix For: 4.2.1
>
>
> 4.2.1 RPM build failing, we need to remove below two check-ins from 4.2.1 
> branch; these changes are made during 4.2 release build
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8689f7f504acee7ccbf6870d409cbb47b177d598
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=db9f5243c31cf00dbf3ed4a81585671c27bab469
> I have a patch for this already , i will submit this patch .



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

[jira] [Comment Edited] (CLOUDSTACK-4808) 4.2.1 RPM build failing due to release related changes made in 4.2 branch

[Rayees Namathponnan (JIRA)]

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

Rayees Namathponnan edited comment on CLOUDSTACK-4808 at 10/4/13 6:34 AM:
--

yes issue is only with non-oss builds from 4.2.1


was (Author: rayeesn):
yes issue us only with non oss builds from 4.2.1

> 4.2.1 RPM build failing due to release related changes made in 4.2 branch 
> --
>
> Key: CLOUDSTACK-4808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4808
> 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.1
> Environment: 4.2.1 build
>Reporter: Rayees Namathponnan
>Assignee: Hugo Trippaers
>Priority: Blocker
> Fix For: 4.2.1
>
>
> 4.2.1 RPM build failing, we need to remove below two check-ins from 4.2.1 
> branch; these changes are made during 4.2 release build
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8689f7f504acee7ccbf6870d409cbb47b177d598
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=db9f5243c31cf00dbf3ed4a81585671c27bab469
> I have a patch for this already , i will submit this patch .



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

[jira] [Commented] (CLOUDSTACK-4808) 4.2.1 RPM build failing due to release related changes made in 4.2 branch

[Rayees Namathponnan (JIRA)]

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

Rayees Namathponnan commented on CLOUDSTACK-4808:
-

I am getting below error without my patch

[root@build-rhel63 cloudstack]# cd packaging/centos63/
[root@build-rhel63 centos63]# ./package.sh --pack nonoss
Doing CloudStack Packaging .
4.2.1-SNAPSHOT
error: failed to stat 
/root/jenkins/build/workspace/XX-4.2-rhel63/XXX/cloudstack/dist/rpmbuild/"-D_prerelease:
 No such file or directory
[root@build-rhel63 centos63]#


> 4.2.1 RPM build failing due to release related changes made in 4.2 branch 
> --
>
> Key: CLOUDSTACK-4808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4808
> 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.1
> Environment: 4.2.1 build
>Reporter: Rayees Namathponnan
>Assignee: Hugo Trippaers
>Priority: Blocker
> Fix For: 4.2.1
>
>
> 4.2.1 RPM build failing, we need to remove below two check-ins from 4.2.1 
> branch; these changes are made during 4.2 release build
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8689f7f504acee7ccbf6870d409cbb47b177d598
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=db9f5243c31cf00dbf3ed4a81585671c27bab469
> I have a patch for this already , i will submit this patch .



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

[jira] [Commented] (CLOUDSTACK-4808) 4.2.1 RPM build failing due to release related changes made in 4.2 branch

[Hugo Trippaers (JIRA)]

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

Hugo Trippaers commented on CLOUDSTACK-4808:


Ok, thanks that explains it. I'll backport the fixes i made in master. 
Reverting the commits will introduce errors again when we try to package the 
release.

Thanks for finding this :-)

> 4.2.1 RPM build failing due to release related changes made in 4.2 branch 
> --
>
> Key: CLOUDSTACK-4808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4808
> 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.1
> Environment: 4.2.1 build
>Reporter: Rayees Namathponnan
>Assignee: Hugo Trippaers
>Priority: Blocker
> Fix For: 4.2.1
>
>
> 4.2.1 RPM build failing, we need to remove below two check-ins from 4.2.1 
> branch; these changes are made during 4.2 release build
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8689f7f504acee7ccbf6870d409cbb47b177d598
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=db9f5243c31cf00dbf3ed4a81585671c27bab469
> I have a patch for this already , i will submit this patch .



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

[jira] [Updated] (CLOUDSTACK-4800) Updating sections of the Cloud Infrastructure Concepts chapter of the Admin Guide

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4800:
---

Fix Version/s: (was: Future)
   4.2.1

> Updating sections of the Cloud Infrastructure Concepts chapter of the Admin 
> Guide
> -
>
> Key: CLOUDSTACK-4800
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4800
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: Travis Graham
>  Labels: documentation
> Fix For: 4.2.1
>
> Attachments: cloud-infrastructure-concepts.patch
>
>
> Adding missing links to referenced sections of the Admin Guide and fixes a 
> few typos.



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

[jira] [Updated] (CLOUDSTACK-4799) Update Deployment Architecture Overview section

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4799:
---

Fix Version/s: (was: 4.2.0)
   4.2.1

> Update Deployment Architecture Overview section
> ---
>
> Key: CLOUDSTACK-4799
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4799
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: Travis Graham
>  Labels: documentaion
> Fix For: 4.2.1
>
> Attachments: deployment-architecture-overview.patch
>
>
> Adds in links to other docs it only loosely references by name and adds the 
> Primary Storage info about being zone wide for 4.2.



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

[jira] [Updated] (CLOUDSTACK-4800) Updating sections of the Cloud Infrastructure Concepts chapter of the Admin Guide

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4800:
---

Fix Version/s: (was: 4.2.0)
   Future

> Updating sections of the Cloud Infrastructure Concepts chapter of the Admin 
> Guide
> -
>
> Key: CLOUDSTACK-4800
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4800
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: Travis Graham
>  Labels: documentation
> Fix For: 4.2.1
>
> Attachments: cloud-infrastructure-concepts.patch
>
>
> Adding missing links to referenced sections of the Admin Guide and fixes a 
> few typos.



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

[jira] [Updated] (CLOUDSTACK-4742) Generate a useful error when using an invalid Compute Offering

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4742:
---

Fix Version/s: (was: 4.2.0)
   (was: Future)

> Generate a useful error when using an invalid Compute Offering 
> ---
>
> Key: CLOUDSTACK-4742
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4742
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
> Environment: Cloudstack 4.2,  Advanced Zone with Security Groups, 
> XenServer 6.2. 
>Reporter: Gerard Lynch
> Fix For: 4.2.1
>
>
> Set up an Advanced Zone with Security Groups on XenServer 6.2.
> Identify your hosts's phsyical CPU max speed - e.g. 2GHz.
> Create a service offering that specifies higher e.g. :
>   - name: cpu_to_high
> display_text: the cpu speed is too high
> cpu_number: 1
> cpu_speed: 3750
> limit_cpu_use: 'false'
> memory: 4096
> offer_ha: 'false'
> storage_type: shared
> Try and create an instance using it. 
> *Expected Result:*
> A useful error message - e.g. not able to match the service offering.
> *Actual Result:*
> In the Gui:
> Unable to create a deployment for VM[User|test]
> In the Logs:
> WARN  [apache.cloudstack.alerts] (Job-Executor-1:job-26 = [ 
> 30199e84-95d1-4c9f-a779-c1eec9603879 ])  alertType:: 8 // dataCenterId:: 1 // 
> podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 
> 18, on Host with Id: null
> INFO  [user.vm.DeployVMCmd] (Job-Executor-1:job-26 = [ 
> 30199e84-95d1-4c9f-a779-c1eec9603879 ]) 
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a 
> deployment for VM[User|web1]Scope=interface com.cloud.dc.DataCenter; id=1
> INFO  [user.vm.DeployVMCmd] (Job-Executor-1:job-26 = [ 
> 30199e84-95d1-4c9f-a779-c1eec9603879 ]) Unable to create a deployment for 
> VM[User|web1]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a 
> deployment for VM[User|web1]Scope=interface com.cloud.dc.DataCenter; id=1
> at 
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at 
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at 
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at 
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at 
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)



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

[jira] [Resolved] (CLOUDSTACK-4731) [Doc] [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek resolved CLOUDSTACK-4731.


Resolution: Fixed

> [Doc] [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
> --
>
> Key: CLOUDSTACK-4731
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4731
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, KVM, SystemVM, Upgrade
>Affects Versions: 4.2.0
>Reporter: Radhika Nair
> Fix For: 4.2.0
>
>




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

[jira] [Updated] (CLOUDSTACK-4764) PGP-repository key expired

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4764:
---

Fix Version/s: (was: 4.2.0)
   Future

> PGP-repository key expired
> --
>
> Key: CLOUDSTACK-4764
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4764
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Cloudmonkey
>Affects Versions: 4.1.0
> Environment: Ubuntu 12.04LTS
>Reporter: Nomar Znip
>  Labels: debian, repository, ubuntu, ubuntu_precise
> Fix For: Future
>
>
> If I add the DEB package repository to my sources and download the key my 
> local apt-cache could not be updated. Because of a expired key:
> Do the point 4.4.1:
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/html/Installation_Guide/configure-package-repository.html
> apt-key list
> pub   2048R/86C278E3 2012-09-07 [expired: 2013-09-07]
> uid  Apache CloudStack 
> Regards nomar



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

[jira] [Resolved] (CLOUDSTACK-4727) Update Upgrade Instructions

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek resolved CLOUDSTACK-4727.


Resolution: Fixed

> Update Upgrade Instructions
> ---
>
> Key: CLOUDSTACK-4727
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4727
> 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
>Priority: Blocker
> Fix For: 4.2.0
>
>
> 1. Before upgrading from any version to 4.2 we need to register the new 4.2 
> systemvm templates .
> This step is there in section 3.3 i.e for upgrade from 2.2.14 to 4.2, but 
> it is missing in section 3.1 and 3.2 .
> 2. Section 3.1 
> Step 3&4 : it should be cloudstack-management and cloudstack-usage as the 
> naming conventions have been changed from 4.1 onwards.
> Step 6 : The cloudstack 4.2 repo has not been published yet, currently at 
> http://cloudstack.apt-get.eu/ the repo is available only for 4.0.x and 4.1.x
>  What Indira pointed to, needs to be removed, step 6.g) 
> and 6.h) and step 8 also need to be removed
> In step 6.f) It should be service cloudstack-agent  stop
>
> Step 9.b) : It should be sudo yum upgrade cloudstack-client
>Step 9.c) : it should be sudo yum upgrade cloudstack-agent   and the 
> following line is not required [[" During the installation of 
> cloudstack-agent, the RPM will copy your agent.properties,log4j-cloud.xml, 
> and environment.properties from /etc/cloud/agent to /etc/cloudstack/agent" ]]
>Step 9.d.ii) : it should be sudo yum upgrade cloudstack-usage
>   
> 3. Section 3.2
> Step 1.e) :  The URL of the vmware systemvm template is wrong. It should 
> be http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova . 
>The OSType should be [[Debian GNU/Linux 7.0 
> (32-bit) (or the highestDebian release number available in the dropdown)]]
> Similarly, add templates for xenserver and kvm 
> also.
> 
> Step 7 : Delete this step, it's not needed. 
>Step 16 : It should be cloudstack-sysvmadm
> 4. Section 3.3
>  Step 4.d) : For all the newly registered templates, make the OStype as 
> [[Debian GNU/Linux 7.0 (32-bit) (or the highest Debian release number 
> available in the dropdown)]]
> 
>  Step 13.c) :  It should be /etc/cloudstack/management/components.xml
>  Step 15.c) : It should be /etc/cloudstack/management/db.properties
>  Step 20 :  Remove this step, it's not needed
>
>  Step 21.e) : It should be /etc/cloudstack/agent/agent.properties
> Step 23.a) :  It should be cloudstack-sysvmadm
> 5. In addition to all this,  If we are using KVM hosts as rhel6.0/6.1 then 
> these extra steps need to be documented for each section, 3.2 and 3.3
> (KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes 
> one or more
> clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, you must first upgrade 
> the operating
> system version on those hosts before upgrading CloudStack itself.
> The first order of business will be to change the yum repository for each 
> system with
> CloudStack packages. This means all management servers, and any hosts that 
> have the KVM
> agent. (No changes should be necessary for hosts that are running VMware or 
> Xen.)
> Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have
> CloudStack packages installed.
> [upgrade]
> name=rhel63
> baseurl=url-of-your-rhel6.3-repo
> enabled=1
> gpgcheck=0
> [apache CloudStack]
> name= Apache CloudStack
> baseurl= http://cloudstack.apt-get.eu/rhel/4.0/
> enabled=1
> gpgcheck=0
> If you are using the community provided package repository, change the 
> baseurl to http://
> cloudstack.apt-get.eu/rhel/4.2/
> If you're using your own package repository, change this line to read as 
> appropriate for your
> 4.2.0 repository.
> b. Now that you have the repository configured 
> c. Upgrade the host operating system from RHEL 6.0 to 6.3:
> yum upgrade
>   
> 6.  Also, in all the sections 3.2 and 3.3 , add this step for agent upgrades 
> After running this ,
> Edit /etc/cloudstack/agent/agent.properties to change the resource parameter 
> from com.cloud.agent.resource.computing.LibvirtComputingResource to 
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
> We need to run the following too,
> Upgrade all the existing bridge names to new bridge names by running this 
> script:
> # cloudstack-agent-upgrade
> . Install a libvirt hook with the following commands:
> # mkdir /etc/libvirt/hooks
> # cp /usr/share/cloudstack-agent/lib/libvirtqemuhook /etc/libvirt/hooks/qemu
> # chmod 

[jira] [Updated] (CLOUDSTACK-4670) [Baremetal] Cloudplatform BareMetal installation guide for CP 4.2

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4670:
---

Fix Version/s: (was: 4.2.0)
   4.2.1

> [Baremetal] Cloudplatform BareMetal installation guide for CP 4.2
> -
>
> Key: CLOUDSTACK-4670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4670
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: angeline shen
>Assignee: Jessica Tomechak
>Priority: Minor
> Fix For: 4.2.1
>
>
> Jessica:
> Cloudplatform BareMetal installation guide for CP 4.2:
> Section  titled 'Create a Bare Metal Template ' (page 19 - 20 )  should 
> be moved to after
> Section  titled 'Add the PXE Server and DHCP Server to Your Deployment'



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

[jira] [Updated] (CLOUDSTACK-4623) systemvm 2.6.32-5-xen kernel has oom-killer issues

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4623:
---

Assignee: Jayapal Reddy

> systemvm 2.6.32-5-xen kernel has oom-killer issues
> --
>
> Key: CLOUDSTACK-4623
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4623
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.0.2
>Reporter: Sten Spans
>Assignee: Jayapal Reddy
> Fix For: 4.2.1
>
>
> During regular operation with haproxy active on of the router-vm's we 
> encountered an oom situation which resulted in the kernel killing off 
> haproxy. The end-result was unavailability of services hosted behind this 
> routervm. 
> We believe this was caused by a defect in the kernel supplied with the 4.0.2 
> system vm image.
> The issues we encountered were identical to the ones described here:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700755



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

[jira] [Updated] (CLOUDSTACK-4623) systemvm 2.6.32-5-xen kernel has oom-killer issues

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4623:
---

Fix Version/s: (was: 4.2.0)
   4.2.1

> systemvm 2.6.32-5-xen kernel has oom-killer issues
> --
>
> Key: CLOUDSTACK-4623
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4623
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.0.2
>Reporter: Sten Spans
> Fix For: 4.2.1
>
>
> During regular operation with haproxy active on of the router-vm's we 
> encountered an oom situation which resulted in the kernel killing off 
> haproxy. The end-result was unavailability of services hosted behind this 
> routervm. 
> We believe this was caused by a defect in the kernel supplied with the 4.0.2 
> system vm image.
> The issues we encountered were identical to the ones described here:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700755



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

[jira] [Resolved] (CLOUDSTACK-4429) Generate API Reference doc for next release

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek resolved CLOUDSTACK-4429.


Resolution: Fixed

> Generate API Reference doc for next release
> ---
>
> Key: CLOUDSTACK-4429
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4429
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: Jessica Tomechak
>Priority: Minor
> Fix For: 4.2.0
>
>
> Someone needs to take care of running the API Reference doc build, 
> sanity-checking the result, and posting it on the web. API Reference is 
> posted at http://cloudstack.apache.org/docs/api/index.html. This is 
> auto-generated from the code using a procedure documented in the project wiki 
> at 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+To+Generate+CloudStack+API+Documentation.
>  



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

[jira] [Updated] (CLOUDSTACK-4653) Update What's New Section

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4653:
---

Fix Version/s: (was: 4.2.0)
   4.2.1

> Update What's New Section
> -
>
> Key: CLOUDSTACK-4653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4653
> 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.1
>
>




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

[jira] [Updated] (CLOUDSTACK-4682) VMs are getting deployed with shared service offering and local compute offering

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek updated CLOUDSTACK-4682:
---

Fix Version/s: (was: 4.2.0)

> VMs are getting deployed  with shared service offering and local compute 
> offering 
> --
>
> Key: CLOUDSTACK-4682
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4682
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0, 4.2.1
> Environment: hyp:KVM
>Reporter: prashant kumar mishra
> Fix For: 4.2.1
>
> Attachments: Logs_DB.rar
>
>
> Steps to reproduce
> ---
> 1-prepare a CS setup with kvm host+zone wide primary storage
> 2-mark Local storage enabled to true at zone level and restart MS
> 3-create a local disk offering
> 4-deploy a vm with shared service offering and local compute offering
> expected
> ---
> vm deployment should fail because CS can't move volume between scope: HOST 
> and ZONE
> Actual
> --
> vm deployment went successful  with root disk on shared and data disk on 
> local storage storage
> My observation
> --
> once i detach the data disk(created in step 4) ,was not able to  attach data 
> disk  to vm(deployed in step 4)
> with error
> ---
> 2013-09-16 13:01:53,697 ERROR [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-9:job-35 = [ ad075b33-d308-4056-bc8a-f3a7d71ad60f ]) Unexpected 
> exception while executing 
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Can't move volume between 
> scope: HOST and ZONE
> at 
> com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1605)
> at 
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1880)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-09-16 13:01:53,702 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-9:job-35 = [ ad075b33-d308-4056-bc8a-f3a7d71ad60f ]) Complete 
> async job-35 = [ ad075b33-d308-4056-bc8a-f3a7d71ad60f ], jobStatus: 2, 
> resultCode: 530, result: Error Code: 530 Error text: Can't move volume 
> between scope: HOST and ZONE



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