[jira] [Updated] (CLOUDSTACK-6290) [Windows] Generate SSL Keys at the time of installation

2014-03-28 Thread Damodar Reddy T (JIRA)

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

Damodar Reddy T updated CLOUDSTACK-6290:


Fix Version/s: Future

 [Windows] Generate SSL Keys at the time of installation
 ---

 Key: CLOUDSTACK-6290
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6290
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: Future, 4.4.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
 Fix For: Future, 4.4.0


 Currently the SSL keys will be generated during server start up and on 
 windows it is not happening due to Sudo command. 
 If we can generate SSL keys at the time of installation in hand before 
 starting the server then server will skip this step. Later we can do similar 
 changes for linux based OSes as well.



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


[jira] [Resolved] (CLOUDSTACK-6290) [Windows] Generate SSL Keys at the time of installation

2014-03-28 Thread Damodar Reddy T (JIRA)

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

Damodar Reddy T resolved CLOUDSTACK-6290.
-

Resolution: Fixed

 [Windows] Generate SSL Keys at the time of installation
 ---

 Key: CLOUDSTACK-6290
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6290
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: Future, 4.4.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
 Fix For: Future, 4.4.0


 Currently the SSL keys will be generated during server start up and on 
 windows it is not happening due to Sudo command. 
 If we can generate SSL keys at the time of installation in hand before 
 starting the server then server will skip this step. Later we can do similar 
 changes for linux based OSes as well.



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


[jira] [Updated] (CLOUDSTACK-6290) [Windows] Generate SSL Keys at the time of installation

2014-03-28 Thread Damodar Reddy T (JIRA)

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

Damodar Reddy T updated CLOUDSTACK-6290:


Affects Version/s: Future

 [Windows] Generate SSL Keys at the time of installation
 ---

 Key: CLOUDSTACK-6290
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6290
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: Future, 4.4.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
 Fix For: Future, 4.4.0


 Currently the SSL keys will be generated during server start up and on 
 windows it is not happening due to Sudo command. 
 If we can generate SSL keys at the time of installation in hand before 
 starting the server then server will skip this step. Later we can do similar 
 changes for linux based OSes as well.



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


[jira] [Resolved] (CLOUDSTACK-6029) [Doc] Comments to be put in the Techinical documentation as well as in the FS

2014-03-28 Thread Damodar Reddy T (JIRA)

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

Damodar Reddy T resolved CLOUDSTACK-6029.
-

Resolution: Fixed

 [Doc] Comments to be put in the Techinical documentation as well as in the FS
 -

 Key: CLOUDSTACK-6029
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6029
 Project: CloudStack
  Issue Type: Task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.3.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Priority: Critical
  Labels: documentation
 Fix For: 4.3.0


 The following comments need to be put in the FS as well as int he technical 
 documentation
 1. Explain the additional configuration required to handle split-brain in 
 ticket and FS
 2.  Find the standard terminology(For Active/Active Master/Master) used and 
 document to Make sure the correct terminology is being used in all 
 documentation.
 3. Find the ping timout and document
 4. Find out about the DB version certified with CS, also what version of 
 RHEL/CentOS are supported and what DBs they run
 5. Can you put some pointers to documentation on best practices in FS (For 
 Async and Semi-Sync
 6. Network topology(Same Zone, Multiple Zones) and latency requirements for 
 setting up DB-HA needs to be documented.
 7. Backup and restore mechanism best practices.
 8. Latency in updating slave in case of Async.



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


[jira] [Commented] (CLOUDSTACK-6291) Check registry to verify JAVA is installed or not instead of JAVA_HOME environment variable

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit d8586462e0814fbc91d6f05a6bc17cab84412f1e in cloudstack's branch 
refs/heads/master from [~damoder.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d858646 ]

CLOUDSTACK-6291: [Windows] Checking whether Java and other dependencies are 
installed or not through registry search instead of relying on environment 
variables. Also setting them into Path environment varibale.

Signed-off-by: Abhinandan Prateek aprat...@apache.org


 Check registry to verify JAVA is installed or not instead of JAVA_HOME 
 environment variable
 ---

 Key: CLOUDSTACK-6291
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6291
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.4.0
 Environment: Windows OS
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
 Fix For: Future






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


[jira] [Resolved] (CLOUDSTACK-6291) Check registry to verify JAVA is installed or not instead of JAVA_HOME environment variable

2014-03-28 Thread Damodar Reddy T (JIRA)

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

Damodar Reddy T resolved CLOUDSTACK-6291.
-

Resolution: Fixed

 Check registry to verify JAVA is installed or not instead of JAVA_HOME 
 environment variable
 ---

 Key: CLOUDSTACK-6291
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6291
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.4.0
 Environment: Windows OS
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
 Fix For: Future






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


[jira] [Commented] (CLOUDSTACK-6125) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 91a5e3bb6634f9f0b98e7021fc55e680c6eba45f in cloudstack's branch 
refs/heads/master from SrikanteswaraRao Talluri
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=91a5e3b ]

CLOUDSTACK-6125: adding 'selfservice','provisioning' tags to segregate the tests
that can be run on simulator only and that needs hardware.


 [Automation]: Segregate total TC's in to Self Service and Provisioning Test 
 Cases
 -

 Key: CLOUDSTACK-6125
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6125
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Reporter: Santhosh Kumar Edukulla
Assignee: Srikanteswararao Talluri
   Original Estimate: 120h
  Remaining Estimate: 120h

 This bug is logged to track the categorization of all test cases.
 We have to go through all of the test cases and divide them into two groups:
 1. Provisioning Tests: Tests that require actual hardware.  (e.g. Start/Stop 
 VM on ESX, XS, and KVM;  Create/Remove rules on VR or network equipment; 
 Create Snapshot on storage).
 2. Self-Service Tests: Tests that tests our self-service business logic. 
 Self-Service tests are tests for CloudStack’s business logic.  It’s not a 
 test of whether actual provisioning succeeded.
 VM placement
 Snapshot policies
 Resource limits
 Usage
 Resource cleanups
 Note: I have added an initial estimate to this case. As well, we need to do 
 incremental segregation and have them reviewed parallelly with alex\abhi. 



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


[jira] [Commented] (CLOUDSTACK-6125) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 5f5416a51c0fc5c0bdd9220746e151494b081b87 in cloudstack's branch 
refs/heads/4.4 from SrikanteswaraRao Talluri
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5f5416a ]

CLOUDSTACK-6125: adding 'selfservice','provisioning' tags to segregate the tests
that can be run on simulator only and that needs hardware.

Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org


 [Automation]: Segregate total TC's in to Self Service and Provisioning Test 
 Cases
 -

 Key: CLOUDSTACK-6125
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6125
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Reporter: Santhosh Kumar Edukulla
Assignee: Srikanteswararao Talluri
   Original Estimate: 120h
  Remaining Estimate: 120h

 This bug is logged to track the categorization of all test cases.
 We have to go through all of the test cases and divide them into two groups:
 1. Provisioning Tests: Tests that require actual hardware.  (e.g. Start/Stop 
 VM on ESX, XS, and KVM;  Create/Remove rules on VR or network equipment; 
 Create Snapshot on storage).
 2. Self-Service Tests: Tests that tests our self-service business logic. 
 Self-Service tests are tests for CloudStack’s business logic.  It’s not a 
 test of whether actual provisioning succeeded.
 VM placement
 Snapshot policies
 Resource limits
 Usage
 Resource cleanups
 Note: I have added an initial estimate to this case. As well, we need to do 
 incremental segregation and have them reviewed parallelly with alex\abhi. 



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


[jira] [Commented] (CLOUDSTACK-6125) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 14796783fd3f838218c85d35ca7aed26d4a586b1 in cloudstack's branch 
refs/heads/4.4 from SrikanteswaraRao Talluri
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1479678 ]

CLOUDSTACK-6125: added smoke tests with following tags 1. selfservice - tests 
which can be run on simulator. 2. provisioning - tests that need actual 
hypervisor resource.

Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org


 [Automation]: Segregate total TC's in to Self Service and Provisioning Test 
 Cases
 -

 Key: CLOUDSTACK-6125
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6125
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Reporter: Santhosh Kumar Edukulla
Assignee: Srikanteswararao Talluri
   Original Estimate: 120h
  Remaining Estimate: 120h

 This bug is logged to track the categorization of all test cases.
 We have to go through all of the test cases and divide them into two groups:
 1. Provisioning Tests: Tests that require actual hardware.  (e.g. Start/Stop 
 VM on ESX, XS, and KVM;  Create/Remove rules on VR or network equipment; 
 Create Snapshot on storage).
 2. Self-Service Tests: Tests that tests our self-service business logic. 
 Self-Service tests are tests for CloudStack’s business logic.  It’s not a 
 test of whether actual provisioning succeeded.
 VM placement
 Snapshot policies
 Resource limits
 Usage
 Resource cleanups
 Note: I have added an initial estimate to this case. As well, we need to do 
 incremental segregation and have them reviewed parallelly with alex\abhi. 



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


[jira] [Commented] (CLOUDSTACK-6015) Write Sellenium tests for the UI

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 9b07979442c251438004bfb0781dee85a5c29100 in cloudstack's branch 
refs/heads/master from [~yichi.lu]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9b07979 ]

CLOUDSTACK-6015: add user account, add user, login as new user, delete user, 
delete user account.

Signed-off-by: Sebastien Goasguen run...@gmail.com


 Write Sellenium tests for the UI
 

 Key: CLOUDSTACK-6015
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.4.0
Reporter: sebastien goasguen
Assignee: Yichi Lu
  Labels: gsoc2014

 To increase tests coverage for CloudStack we need to write a test suite for 
 the UI. Using Sellenium we can write these tests for multiple browsers and 
 export everything in Python.
 http://docs.seleniumhq.org
 These will be used with the unittest and the integration tests to make 
 CloudStack higher quality.



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


[jira] [Assigned] (CLOUDSTACK-6233) Add new tab GPU in Host detailView for gpu enabled hosts

2014-03-28 Thread Mihaela Stoica (JIRA)

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

Mihaela Stoica reassigned CLOUDSTACK-6233:
--

Assignee: Mihaela Stoica

 Add new tab GPU in Host detailView for gpu enabled hosts
 --

 Key: CLOUDSTACK-6233
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6233
 Project: CloudStack
  Issue Type: Task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Sanjay Tripathi
Assignee: Mihaela Stoica
 Fix For: 4.4.0

 Attachments: screenshot-1.jpg


 For GPU/vGPU enabled Hosts, UI should display the supported vGPU types and 
 remaining capacity of GPU card.
 The tab should only be visible for GPU enabled hosts.
 For GPU/vGPU enabled Hosts, listHosts API gives the following response:
 memorytotal15972703488/memorytotal
 memoryallocated1610612736/memoryallocated
 memoryused2600064/memoryused
 gpugroup
 gpugroupnameGroup of NVIDIA Corporation GK104GL [GRID K2] 
 GPUs/gpugroupname
 vgpu
 vgputypeGRID K200/vgputype
 remainingcapacity16/remainingcapacity
 /vgpu
 vgpu
 vgputypepassthrough/vgputype
 remainingcapacity2/remainingcapacity
 /vgpu
 vgpu
 vgputypeGRID K260Q/vgputype
 remainingcapacity4/remainingcapacity
 /vgpu
 vgpu
 vgputypeGRID K240Q/vgputype
 remainingcapacity8/remainingcapacity
 /vgpu
 /gpugroup
 capabilities
 xen-3.0-x86_64 , xen-3.0-x86_32p , hvm-3.0-x86_32 , hvm-3.0-x86_32p , 
 hvm-3.0-x86_64
 /capabilities
 This response tells about the no. of GPU cards and remaining capacity per 
 vGPU types in the GPU cards.



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


[jira] [Created] (CLOUDSTACK-6299) GetVMPassword decypher instructions are wrong

2014-03-28 Thread Antoine Coetsier (JIRA)
Antoine Coetsier created CLOUDSTACK-6299:


 Summary: GetVMPassword decypher instructions are wrong
 Key: CLOUDSTACK-6299
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6299
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.3.0
Reporter: Antoine Coetsier
Priority: Trivial


The procedure described in the Wiki at 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34014652 is 
incorrect.

The first openssl conversion step will give you an empty file.

The correct procedure is:

openssl enc -base64 -in encryptedpassword -out binarytext -d -A
openssl rsautl -decrypt -in binarytext -out plaintext -inkey private.pem

Please correct the wiki page and add detail in the API doc to the base64 format 
of the API getVMpassword result.



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


[jira] [Commented] (CLOUDSTACK-6294) mysql-ha pom has incorrect relative path

2014-03-28 Thread Alex Hitchins (JIRA)

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

Alex Hitchins commented on CLOUDSTACK-6294:
---

Fixed by Hugo:

From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: 28 March 2014 09:42
To: d...@cloudstack.apache.org
Subject: Re: [4.4] mysql-ha POM error

Fixed.

Cheers,

Hugo


 mysql-ha pom has incorrect relative path
 

 Key: CLOUDSTACK-6294
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6294
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Packaging
Affects Versions: 4.4.0
 Environment: Centos6.5
Reporter: Paul Angus
Assignee: Alex Hitchins
Priority: Blocker

 Cannot build 4.4 noredist because relative parent path is incorrect
 ../pom.xml
 should be 
 ../../pom.xml



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


[jira] [Resolved] (CLOUDSTACK-6294) mysql-ha pom has incorrect relative path

2014-03-28 Thread Alex Hitchins (JIRA)

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

Alex Hitchins resolved CLOUDSTACK-6294.
---

   Resolution: Fixed
Fix Version/s: 4.4.0

Resolved by Hugo T

 mysql-ha pom has incorrect relative path
 

 Key: CLOUDSTACK-6294
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6294
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Packaging
Affects Versions: 4.4.0
 Environment: Centos6.5
Reporter: Paul Angus
Assignee: Alex Hitchins
Priority: Blocker
 Fix For: 4.4.0


 Cannot build 4.4 noredist because relative parent path is incorrect
 ../pom.xml
 should be 
 ../../pom.xml



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


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

2014-03-28 Thread Kishan Kavala (JIRA)

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

Kishan Kavala reassigned CLOUDSTACK-6239:
-

Assignee: Kishan Kavala  (was: Amogh Vasekar)

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

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

 Attachments: log.zip


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

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

2014-03-28 Thread Kishan Kavala (JIRA)

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

Kishan Kavala edited comment on CLOUDSTACK-6239 at 3/28/14 12:45 PM:
-

Regression due to 68b8891c620e78009ec4dbcbd326e4bbfa79da4e.
While inserting values in configuration table, params with category 'Hidden' or 
'Secure' have to be encrypted before inserting in DB


was (Author: kishan):
Regression due to 68b8891c620e78009ec4dbcbd326e4bbfa79da4e.
While inserting valuse in configuration table, params with category 'Hidden' or 
'Secure' have to be encrypted before inserting in DB

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

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

 Attachments: log.zip


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

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

2014-03-28 Thread Kishan Kavala (JIRA)

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

Kishan Kavala commented on CLOUDSTACK-6239:
---

Regression due to 68b8891c620e78009ec4dbcbd326e4bbfa79da4e.
While inserting valuse in configuration table, params with category 'Hidden' or 
'Secure' have to be encrypted before inserting in DB

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

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

 Attachments: log.zip


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

[jira] [Assigned] (CLOUDSTACK-6223) removeNicFromVirtualMachine fails if another instance in another domain has a nic with the same ip and a forwarding rule configured on it

2014-03-28 Thread upendra moturi (JIRA)

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

upendra moturi reassigned CLOUDSTACK-6223:
--

Assignee: upendra moturi

 removeNicFromVirtualMachine fails if another instance in another domain has a 
 nic with the same ip and a forwarding rule configured on it
 -

 Key: CLOUDSTACK-6223
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6223
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.1
Reporter: Joris van Lieshout
Assignee: upendra moturi
Priority: Blocker

 When removeNicFromVirtualMachine is called for a nic on an instance the code 
 below is evaluated. This piece of code searches for portforwarding rules 
 across all domains. If another instance exists that has a nic with the same 
 ip and a forwarding rule the search returns 1 and the 
 removeNicFromVirtualMachine call failed. 
 server/src/com/cloud/network/rules/RulesManagerImpl.java
 @Override
 public ListFirewallRuleVO listAssociatedRulesForGuestNic(Nic nic){
 ListFirewallRuleVO result = new ArrayListFirewallRuleVO();
 // add PF rules
 
 result.addAll(_portForwardingDao.listByDestIpAddr(nic.getIp4Address()));
 // add static NAT rules
 Stack trace:
 2014-03-11 15:24:04,944 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-102:job-193607 = [ 30e81de3-2a00-49f2-8d80-545a765e4c1e ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.RemoveNicFromVMCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to remove nic from 
 VM[User|zzz1] in Ntwk[994|Guest|14], nic has associated Port forwarding or 
 Load balancer or Static NAT rules.
 at 
 com.cloud.vm.VirtualMachineManagerImpl.removeNicFromVm(VirtualMachineManagerImpl.java:3058)
 at 
 com.cloud.vm.UserVmManagerImpl.removeNicFromVirtualMachine(UserVmManagerImpl.java:1031)
 at 
 org.apache.cloudstack.api.command.user.vm.RemoveNicFromVMCmd.execute(RemoveNicFromVMCmd.java:103)
 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)



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


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

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 45ab288e26865f377723452c119d4f0835e2 in cloudstack's branch 
refs/heads/4.4 from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=45ab288 ]

CLOUDSTACK-6239: Encrypt security related config values before inserting into DB


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

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

 Attachments: log.zip


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

[jira] [Resolved] (CLOUDSTACK-6299) GetVMPassword decypher instructions are wrong

2014-03-28 Thread sebastien goasguen (JIRA)

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

sebastien goasguen resolved CLOUDSTACK-6299.


   Resolution: Fixed
Fix Version/s: 4.3.1
   4.4.0

All fixed, thanks for the bug

 GetVMPassword decypher instructions are wrong
 -

 Key: CLOUDSTACK-6299
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6299
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.3.0
Reporter: Antoine Coetsier
Assignee: sebastien goasguen
Priority: Trivial
  Labels: documentation
 Fix For: 4.4.0, 4.3.1


 The procedure described in the Wiki at 
 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34014652 is 
 incorrect.
 The first openssl conversion step will give you an empty file.
 The correct procedure is:
 openssl enc -base64 -in encryptedpassword -out binarytext -d -A
 openssl rsautl -decrypt -in binarytext -out plaintext -inkey private.pem
 Please correct the wiki page and add detail in the API doc to the base64 
 format of the API getVMpassword result.



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


[jira] [Commented] (CLOUDSTACK-6299) GetVMPassword decypher instructions are wrong

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit af66d0e4f65cd524370b9b919cba11e11edd46c4 in cloudstack's branch 
refs/heads/master from [~sebgoa]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=af66d0e ]

CLOUDSTACK-6299: Fixed apidoc info with base64 encoded


 GetVMPassword decypher instructions are wrong
 -

 Key: CLOUDSTACK-6299
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6299
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.3.0
Reporter: Antoine Coetsier
Priority: Trivial
  Labels: documentation

 The procedure described in the Wiki at 
 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34014652 is 
 incorrect.
 The first openssl conversion step will give you an empty file.
 The correct procedure is:
 openssl enc -base64 -in encryptedpassword -out binarytext -d -A
 openssl rsautl -decrypt -in binarytext -out plaintext -inkey private.pem
 Please correct the wiki page and add detail in the API doc to the base64 
 format of the API getVMpassword result.



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


[jira] [Commented] (CLOUDSTACK-6302) Missing dependency on libmysql-java for management debian package.

2014-03-28 Thread JIRA

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

翁翊成 commented on CLOUDSTACK-6302:
-

It seems like it was resolved in master branch.

@@ -15,14 +15,14 @@ Description: A common package which contains files which 
are shared by several C

 Package: cloudstack-management
 Architecture: all
-Depends: cloudstack-common (= ${source:Version}), tomcat6, sysvinit-utils, 
sudo, jsvc, python-mysqldb, libmysql-java, python-paramiko, augea
+Depends: cloudstack-common (= ${source:Version}), tomcat6, sysvinit-utils, 
sudo, jsvc, python-mysqldb, python-paramiko, augeas-tools
 Conflicts: cloud-server, cloud-client, cloud-client-ui
 Description: CloudStack server library
  The CloudStack management server

 Missing dependency on libmysql-java for management debian package.
 --

 Key: CLOUDSTACK-6302
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6302
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Ubuntu 12.04
Reporter: 翁翊成
  Labels: deb

 The debian package of Cloud Stack 4.3.0 management does not has dependency on 
 libmysql-java, so that it will cause the tomcat application start failed.
 $ dpkg --info cloudstack-management_4.3.0_all.deb
  new debian package, version 2.0.
  size 155760322 bytes: control archive= 21171 bytes.
  800 bytes,19 lines  conffiles
  470 bytes,13 lines  control
78077 bytes,   642 lines  md5sums
 2062 bytes,55 lines   *  postinst #!/bin/sh
  279 bytes,14 lines   *  prerm#!/bin/sh
  Package: cloudstack-management
  Source: cloudstack
  Version: 4.3.0
  Architecture: all
  Maintainer: Wido den Hollander w...@widodh.nl
  Installed-Size: 167408
  Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
 python-mysqldb, python-paramiko, augeas-tools
  Conflicts: cloud-client, cloud-client-ui, cloud-server
  Section: libs
  Priority: extra
  Homepage: http://www.cloudstack.org/
  Description: CloudStack server library
   The CloudStack management server



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


[jira] [Commented] (CLOUDSTACK-6301) kvm : vnc password is disabled when rebooted

2014-03-28 Thread John Kinsella (JIRA)

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

John Kinsella commented on CLOUDSTACK-6301:
---

I'm unable to reproduce this. If you are using dumpxml, make sure you pass 
--security-info or password will not be displayed.

On a rebooted KVM VM on an ACS 4.2 agent:

# virsh dumpxml 23 |grep pass
# virsh dumpxml 23 --security-info|grep pass
graphics type='vnc' port='5909' autoport='yes' listen='0.0.0.0' 
passwd='bb28f84e09a1'



 kvm : vnc password is disabled when rebooted
 

 Key: CLOUDSTACK-6301
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6301
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.2.0
Reporter: Francois Scala
Assignee: John Kinsella
  Labels: security

 When a VM is rebooted from the cloudstack GUI, the xml recreated without the 
 vnc password.
 Here is the libvirt vnc configuration from a running vm :
 graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' 
 passwd='a671096d9ecda37e'
   listen type='address' address='0.0.0.0'/
 /graphics
 The same configuration afger a reboot :
 graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'
   listen type='address' address='0.0.0.0'/
 /graphics



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


[jira] [Commented] (CLOUDSTACK-6227) Add copy-paste support for detail view fields

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 6d7978ea457404bd41149bd9d9666a4960fe8c61 in cloudstack's branch 
refs/heads/4.4 from [~gabora]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6d7978e ]

CLOUDSTACK-6227 (Add copy-paste support for detail view fields):

DetailView widget now supports bool isCopyPaste property that can be set
for fields. If this is set to true, the text of this field is displayed
using ellipsis formatting* and a copy-paste icon is available right next
to it. On clicking this icon, the full text is displayed

*: tooltip is also enabled showing the original non-ellipsed value


 Add copy-paste support for detail view fields
 -

 Key: CLOUDSTACK-6227
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6227
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.3.0
Reporter: Brian Federle
Assignee: Gabor Apati-Nagy
 Fix For: 4.4.0

 Attachments: copy-paste-concept.png


 Right now long value fields are displayed in a scrollbox to prevent overflow, 
 examples being the API and secret key fields. Visually, this is not an 
 optimal solution and can also make copy-pasting the values hard.
 There should be a new option in the detailView to provide a 'copy' button 
 next to long fields, which would copy the entire field's contents to the 
 clipboard. The displayed value field can then be truncated via ellipses '...'



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


[jira] [Updated] (CLOUDSTACK-6302) Missing dependency on libmysql-java for management debian package.

2014-03-28 Thread JIRA

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

翁翊成 updated CLOUDSTACK-6302:


Description: 
The debian package of Cloud Stack 4.3.0 management does not has dependency on 
libmysql-java, so that it will cause the tomcat application start failed.

{code}
$ dpkg --info cloudstack-management_4.3.0_all.deb
 new debian package, version 2.0.
 size 155760322 bytes: control archive= 21171 bytes.
 800 bytes,19 lines  conffiles
 470 bytes,13 lines  control
   78077 bytes,   642 lines  md5sums
2062 bytes,55 lines   *  postinst #!/bin/sh
 279 bytes,14 lines   *  prerm#!/bin/sh
 Package: cloudstack-management
 Source: cloudstack
 Version: 4.3.0
 Architecture: all
 Maintainer: Wido den Hollander w...@widodh.nl
 Installed-Size: 167408
 Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
python-mysqldb, python-paramiko, augeas-tools
 Conflicts: cloud-client, cloud-client-ui, cloud-server
 Section: libs
 Priority: extra
 Homepage: http://www.cloudstack.org/
 Description: CloudStack server library
  The CloudStack management server
{code}

  was:
The debian package of Cloud Stack 4.3.0 management does not has dependency on 
libmysql-java, so that it will cause the tomcat application start failed.

$ dpkg --info cloudstack-management_4.3.0_all.deb
 new debian package, version 2.0.
 size 155760322 bytes: control archive= 21171 bytes.
 800 bytes,19 lines  conffiles
 470 bytes,13 lines  control
   78077 bytes,   642 lines  md5sums
2062 bytes,55 lines   *  postinst #!/bin/sh
 279 bytes,14 lines   *  prerm#!/bin/sh
 Package: cloudstack-management
 Source: cloudstack
 Version: 4.3.0
 Architecture: all
 Maintainer: Wido den Hollander w...@widodh.nl
 Installed-Size: 167408
 Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
python-mysqldb, python-paramiko, augeas-tools
 Conflicts: cloud-client, cloud-client-ui, cloud-server
 Section: libs
 Priority: extra
 Homepage: http://www.cloudstack.org/
 Description: CloudStack server library
  The CloudStack management server


 Missing dependency on libmysql-java for management debian package.
 --

 Key: CLOUDSTACK-6302
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6302
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Ubuntu 12.04
Reporter: 翁翊成
  Labels: deb

 The debian package of Cloud Stack 4.3.0 management does not has dependency on 
 libmysql-java, so that it will cause the tomcat application start failed.
 {code}
 $ dpkg --info cloudstack-management_4.3.0_all.deb
  new debian package, version 2.0.
  size 155760322 bytes: control archive= 21171 bytes.
  800 bytes,19 lines  conffiles
  470 bytes,13 lines  control
78077 bytes,   642 lines  md5sums
 2062 bytes,55 lines   *  postinst #!/bin/sh
  279 bytes,14 lines   *  prerm#!/bin/sh
  Package: cloudstack-management
  Source: cloudstack
  Version: 4.3.0
  Architecture: all
  Maintainer: Wido den Hollander w...@widodh.nl
  Installed-Size: 167408
  Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
 python-mysqldb, python-paramiko, augeas-tools
  Conflicts: cloud-client, cloud-client-ui, cloud-server
  Section: libs
  Priority: extra
  Homepage: http://www.cloudstack.org/
  Description: CloudStack server library
   The CloudStack management server
 {code}



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


[jira] [Updated] (CLOUDSTACK-6302) Missing dependency on libmysql-java for management debian package.

2014-03-28 Thread JIRA

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

翁翊成 updated CLOUDSTACK-6302:


Description: 
The debian package of Cloud Stack 4.3.0 management does not has dependency on 
libmysql-java, so that it will cause the tomcat application start failed.

$ dpkg --info cloudstack-management_4.3.0_all.deb
 new debian package, version 2.0.
 size 155760322 bytes: control archive= 21171 bytes.
 800 bytes,19 lines  conffiles
 470 bytes,13 lines  control
   78077 bytes,   642 lines  md5sums
2062 bytes,55 lines   *  postinst #!/bin/sh
 279 bytes,14 lines   *  prerm#!/bin/sh
 Package: cloudstack-management
 Source: cloudstack
 Version: 4.3.0
 Architecture: all
 Maintainer: Wido den Hollander w...@widodh.nl
 Installed-Size: 167408
 Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
python-mysqldb, python-paramiko, augeas-tools
 Conflicts: cloud-client, cloud-client-ui, cloud-server
 Section: libs
 Priority: extra
 Homepage: http://www.cloudstack.org/
 Description: CloudStack server library
  The CloudStack management server


  was:
The debian package of Cloud Stack 4.3.0 management does not has dependency on 
libmysql-java, so that it will cause the tomcat application start failed.

{code}
$ dpkg --info cloudstack-management_4.3.0_all.deb
 new debian package, version 2.0.
 size 155760322 bytes: control archive= 21171 bytes.
 800 bytes,19 lines  conffiles
 470 bytes,13 lines  control
   78077 bytes,   642 lines  md5sums
2062 bytes,55 lines   *  postinst #!/bin/sh
 279 bytes,14 lines   *  prerm#!/bin/sh
 Package: cloudstack-management
 Source: cloudstack
 Version: 4.3.0
 Architecture: all
 Maintainer: Wido den Hollander w...@widodh.nl
 Installed-Size: 167408
 Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
python-mysqldb, python-paramiko, augeas-tools
 Conflicts: cloud-client, cloud-client-ui, cloud-server
 Section: libs
 Priority: extra
 Homepage: http://www.cloudstack.org/
 Description: CloudStack server library
  The CloudStack management server
{code}


 Missing dependency on libmysql-java for management debian package.
 --

 Key: CLOUDSTACK-6302
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6302
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Ubuntu 12.04
Reporter: 翁翊成
  Labels: deb

 The debian package of Cloud Stack 4.3.0 management does not has dependency on 
 libmysql-java, so that it will cause the tomcat application start failed.
 $ dpkg --info cloudstack-management_4.3.0_all.deb
  new debian package, version 2.0.
  size 155760322 bytes: control archive= 21171 bytes.
  800 bytes,19 lines  conffiles
  470 bytes,13 lines  control
78077 bytes,   642 lines  md5sums
 2062 bytes,55 lines   *  postinst #!/bin/sh
  279 bytes,14 lines   *  prerm#!/bin/sh
  Package: cloudstack-management
  Source: cloudstack
  Version: 4.3.0
  Architecture: all
  Maintainer: Wido den Hollander w...@widodh.nl
  Installed-Size: 167408
  Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
 python-mysqldb, python-paramiko, augeas-tools
  Conflicts: cloud-client, cloud-client-ui, cloud-server
  Section: libs
  Priority: extra
  Homepage: http://www.cloudstack.org/
  Description: CloudStack server library
   The CloudStack management server



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


[jira] [Updated] (CLOUDSTACK-6301) kvm : vnc password is disabled when rebooted

2014-03-28 Thread John Kinsella (JIRA)

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

John Kinsella updated CLOUDSTACK-6301:
--

Security: Public  (was: Non-Public)

 kvm : vnc password is disabled when rebooted
 

 Key: CLOUDSTACK-6301
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6301
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.2.0
Reporter: Francois Scala
  Labels: security

 When a VM is rebooted from the cloudstack GUI, the xml recreated without the 
 vnc password.
 Here is the libvirt vnc configuration from a running vm :
 graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' 
 passwd='a671096d9ecda37e'
   listen type='address' address='0.0.0.0'/
 /graphics
 The same configuration afger a reboot :
 graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'
   listen type='address' address='0.0.0.0'/
 /graphics



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


[jira] [Assigned] (CLOUDSTACK-6301) kvm : vnc password is disabled when rebooted

2014-03-28 Thread John Kinsella (JIRA)

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

John Kinsella reassigned CLOUDSTACK-6301:
-

Assignee: John Kinsella

 kvm : vnc password is disabled when rebooted
 

 Key: CLOUDSTACK-6301
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6301
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.2.0
Reporter: Francois Scala
Assignee: John Kinsella
  Labels: security

 When a VM is rebooted from the cloudstack GUI, the xml recreated without the 
 vnc password.
 Here is the libvirt vnc configuration from a running vm :
 graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' 
 passwd='a671096d9ecda37e'
   listen type='address' address='0.0.0.0'/
 /graphics
 The same configuration afger a reboot :
 graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'
   listen type='address' address='0.0.0.0'/
 /graphics



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


[jira] [Comment Edited] (CLOUDSTACK-6302) Missing dependency on libmysql-java for management debian package.

2014-03-28 Thread JIRA

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

翁翊成 edited comment on CLOUDSTACK-6302 at 3/28/14 3:47 PM:
--

It seems like it was resolved in master branch.

{code}
@@ -15,14 +15,14 @@ Description: A common package which contains files which 
are shared by several C

 Package: cloudstack-management
 Architecture: all
-Depends: cloudstack-common (= ${source:Version}), tomcat6, sysvinit-utils, 
sudo, jsvc, python-mysqldb, libmysql-java, python-paramiko, augea
+Depends: cloudstack-common (= ${source:Version}), tomcat6, sysvinit-utils, 
sudo, jsvc, python-mysqldb, python-paramiko, augeas-tools
 Conflicts: cloud-server, cloud-client, cloud-client-ui
 Description: CloudStack server library
  The CloudStack management server
{code}


was (Author: wengych):
It seems like it was resolved in master branch.

@@ -15,14 +15,14 @@ Description: A common package which contains files which 
are shared by several C

 Package: cloudstack-management
 Architecture: all
-Depends: cloudstack-common (= ${source:Version}), tomcat6, sysvinit-utils, 
sudo, jsvc, python-mysqldb, libmysql-java, python-paramiko, augea
+Depends: cloudstack-common (= ${source:Version}), tomcat6, sysvinit-utils, 
sudo, jsvc, python-mysqldb, python-paramiko, augeas-tools
 Conflicts: cloud-server, cloud-client, cloud-client-ui
 Description: CloudStack server library
  The CloudStack management server

 Missing dependency on libmysql-java for management debian package.
 --

 Key: CLOUDSTACK-6302
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6302
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Ubuntu 12.04
Reporter: 翁翊成
  Labels: deb

 The debian package of Cloud Stack 4.3.0 management does not has dependency on 
 libmysql-java, so that it will cause the tomcat application start failed.
 $ dpkg --info cloudstack-management_4.3.0_all.deb
  new debian package, version 2.0.
  size 155760322 bytes: control archive= 21171 bytes.
  800 bytes,19 lines  conffiles
  470 bytes,13 lines  control
78077 bytes,   642 lines  md5sums
 2062 bytes,55 lines   *  postinst #!/bin/sh
  279 bytes,14 lines   *  prerm#!/bin/sh
  Package: cloudstack-management
  Source: cloudstack
  Version: 4.3.0
  Architecture: all
  Maintainer: Wido den Hollander w...@widodh.nl
  Installed-Size: 167408
  Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
 python-mysqldb, python-paramiko, augeas-tools
  Conflicts: cloud-client, cloud-client-ui, cloud-server
  Section: libs
  Priority: extra
  Homepage: http://www.cloudstack.org/
  Description: CloudStack server library
   The CloudStack management server



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


[jira] [Commented] (CLOUDSTACK-6227) Add copy-paste support for detail view fields

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 61a0c128a741d39b118116482abbe5e56243dfce in cloudstack's branch 
refs/heads/4.4 from [~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=61a0c12 ]

CLOUDSTACK-6227: Don't show API/secret key fields in quickview


 Add copy-paste support for detail view fields
 -

 Key: CLOUDSTACK-6227
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6227
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.3.0
Reporter: Brian Federle
Assignee: Gabor Apati-Nagy
 Fix For: 4.4.0

 Attachments: copy-paste-concept.png


 Right now long value fields are displayed in a scrollbox to prevent overflow, 
 examples being the API and secret key fields. Visually, this is not an 
 optimal solution and can also make copy-pasting the values hard.
 There should be a new option in the detailView to provide a 'copy' button 
 next to long fields, which would copy the entire field's contents to the 
 clipboard. The displayed value field can then be truncated via ellipses '...'



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


[jira] [Commented] (CLOUDSTACK-6299) GetVMPassword decypher instructions are wrong

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 6d15f6c27e9b5019106c7d3f07eb64ed42e3b6ce in cloudstack's branch 
refs/heads/4.4 from [~sebgoa]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6d15f6c ]

CLOUDSTACK-6299: Fixed apidoc info with base64 encoded


 GetVMPassword decypher instructions are wrong
 -

 Key: CLOUDSTACK-6299
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6299
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.3.0
Reporter: Antoine Coetsier
Priority: Trivial
  Labels: documentation

 The procedure described in the Wiki at 
 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34014652 is 
 incorrect.
 The first openssl conversion step will give you an empty file.
 The correct procedure is:
 openssl enc -base64 -in encryptedpassword -out binarytext -d -A
 openssl rsautl -decrypt -in binarytext -out plaintext -inkey private.pem
 Please correct the wiki page and add detail in the API doc to the base64 
 format of the API getVMpassword result.



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


[jira] [Assigned] (CLOUDSTACK-6299) GetVMPassword decypher instructions are wrong

2014-03-28 Thread sebastien goasguen (JIRA)

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

sebastien goasguen reassigned CLOUDSTACK-6299:
--

Assignee: sebastien goasguen

 GetVMPassword decypher instructions are wrong
 -

 Key: CLOUDSTACK-6299
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6299
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.3.0
Reporter: Antoine Coetsier
Assignee: sebastien goasguen
Priority: Trivial
  Labels: documentation

 The procedure described in the Wiki at 
 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34014652 is 
 incorrect.
 The first openssl conversion step will give you an empty file.
 The correct procedure is:
 openssl enc -base64 -in encryptedpassword -out binarytext -d -A
 openssl rsautl -decrypt -in binarytext -out plaintext -inkey private.pem
 Please correct the wiki page and add detail in the API doc to the base64 
 format of the API getVMpassword result.



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


[jira] [Commented] (CLOUDSTACK-6299) GetVMPassword decypher instructions are wrong

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 7830a0f0f494353685fb6ebdbb44c6d2423353db in cloudstack's branch 
refs/heads/4.3 from [~sebgoa]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7830a0f ]

CLOUDSTACK-6299: Fixed apidoc info with base64 encoded

Conflicts:
api/src/org/apache/cloudstack/api/response/GetVMPasswordResponse.java


 GetVMPassword decypher instructions are wrong
 -

 Key: CLOUDSTACK-6299
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6299
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.3.0
Reporter: Antoine Coetsier
Priority: Trivial
  Labels: documentation

 The procedure described in the Wiki at 
 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34014652 is 
 incorrect.
 The first openssl conversion step will give you an empty file.
 The correct procedure is:
 openssl enc -base64 -in encryptedpassword -out binarytext -d -A
 openssl rsautl -decrypt -in binarytext -out plaintext -inkey private.pem
 Please correct the wiki page and add detail in the API doc to the base64 
 format of the API getVMpassword result.



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


[jira] [Created] (CLOUDSTACK-6300) Dedicated Resources: routers of other domains are provisioned on dedicated clusters

2014-03-28 Thread Anton Opgenoort (JIRA)
Anton Opgenoort created CLOUDSTACK-6300:
---

 Summary: Dedicated Resources: routers of other domains are 
provisioned on dedicated clusters
 Key: CLOUDSTACK-6300
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6300
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Virtual Router
Affects Versions: 4.2.1
Reporter: Anton Opgenoort


To reproduce:
create a new dedicated cluster for domain A, and add primary storage and a host.
Then create a new network within domain B. RouterVM can then end up on the 
dedicated cluster for domain B. 



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


[jira] [Commented] (CLOUDSTACK-6227) Add copy-paste support for detail view fields

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 9b16a6dfdc827fbeafde75ee4a1d027cacd2f4be in cloudstack's branch 
refs/heads/master from [~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9b16a6d ]

CLOUDSTACK-6227: Don't show API/secret key fields in quickview


 Add copy-paste support for detail view fields
 -

 Key: CLOUDSTACK-6227
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6227
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.3.0
Reporter: Brian Federle
Assignee: Gabor Apati-Nagy
 Fix For: 4.4.0

 Attachments: copy-paste-concept.png


 Right now long value fields are displayed in a scrollbox to prevent overflow, 
 examples being the API and secret key fields. Visually, this is not an 
 optimal solution and can also make copy-pasting the values hard.
 There should be a new option in the detailView to provide a 'copy' button 
 next to long fields, which would copy the entire field's contents to the 
 clipboard. The displayed value field can then be truncated via ellipses '...'



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


[jira] [Created] (CLOUDSTACK-6302) Missing dependency on libmysql-java for management debian package.

2014-03-28 Thread JIRA
翁翊成 created CLOUDSTACK-6302:
---

 Summary: Missing dependency on libmysql-java for management debian 
package.
 Key: CLOUDSTACK-6302
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6302
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.3.0
 Environment: Ubuntu 12.04
Reporter: 翁翊成


The debian package of Cloud Stack 4.3.0 management does not has dependency on 
libmysql-java, so that it will cause the tomcat application start failed.

$ dpkg --info cloudstack-management_4.3.0_all.deb
 new debian package, version 2.0.
 size 155760322 bytes: control archive= 21171 bytes.
 800 bytes,19 lines  conffiles
 470 bytes,13 lines  control
   78077 bytes,   642 lines  md5sums
2062 bytes,55 lines   *  postinst #!/bin/sh
 279 bytes,14 lines   *  prerm#!/bin/sh
 Package: cloudstack-management
 Source: cloudstack
 Version: 4.3.0
 Architecture: all
 Maintainer: Wido den Hollander w...@widodh.nl
 Installed-Size: 167408
 Depends: cloudstack-common (= 4.3.0), tomcat6, sysvinit-utils, sudo, jsvc, 
python-mysqldb, python-paramiko, augeas-tools
 Conflicts: cloud-client, cloud-client-ui, cloud-server
 Section: libs
 Priority: extra
 Homepage: http://www.cloudstack.org/
 Description: CloudStack server library
  The CloudStack management server



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


[jira] [Resolved] (CLOUDSTACK-5954) update-ssl.png missing from docs

2014-03-28 Thread sebastien goasguen (JIRA)

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

sebastien goasguen resolved CLOUDSTACK-5954.


   Resolution: Fixed
Fix Version/s: 4.3.0

 update-ssl.png missing from docs
 

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

 Attachments: update-ssl.png


 there does not seem to be a update-ssl.png in en-US/images



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


[jira] [Commented] (CLOUDSTACK-6301) kvm : vnc password is disabled when rebooted

2014-03-28 Thread Francois Scala (JIRA)

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

Francois Scala commented on CLOUDSTACK-6301:


Hi,

I've tested with virsh edit and virsh dumpxml --security-info show the same 
result, no password.
But virsh edit show a port as -1

virsh dumpxml --security-info  i-1-23-VM | grep  vnc
graphics type='vnc' port='5901' autoport='yes' listen='0.0.0.0'

By the way, the exact version is 4.2.1

Regards.



 kvm : vnc password is disabled when rebooted
 

 Key: CLOUDSTACK-6301
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6301
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.2.0
Reporter: Francois Scala
Assignee: John Kinsella
  Labels: security

 When a VM is rebooted from the cloudstack GUI, the xml recreated without the 
 vnc password.
 Here is the libvirt vnc configuration from a running vm :
 graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' 
 passwd='a671096d9ecda37e'
   listen type='address' address='0.0.0.0'/
 /graphics
 The same configuration afger a reboot :
 graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'
   listen type='address' address='0.0.0.0'/
 /graphics



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


[jira] [Updated] (CLOUDSTACK-6015) Write Sellenium tests for the UI

2014-03-28 Thread Yichi Lu (JIRA)

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

Yichi Lu updated CLOUDSTACK-6015:
-

Affects Version/s: (was: 4.4.0)
   4.5.0

 Write Sellenium tests for the UI
 

 Key: CLOUDSTACK-6015
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.5.0
Reporter: sebastien goasguen
Assignee: Yichi Lu
  Labels: gsoc2014

 To increase tests coverage for CloudStack we need to write a test suite for 
 the UI. Using Sellenium we can write these tests for multiple browsers and 
 export everything in Python.
 http://docs.seleniumhq.org
 These will be used with the unittest and the integration tests to make 
 CloudStack higher quality.



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


[jira] [Created] (CLOUDSTACK-6303) [UI] Account creation hang in UI,

2014-03-28 Thread Rayees Namathponnan (JIRA)
Rayees Namathponnan created CLOUDSTACK-6303:
---

 Summary: [UI] Account creation hang in UI,  
 Key: CLOUDSTACK-6303
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6303
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.4.0
 Environment: 4.4 build

Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.4.0


Steps to reproduce 

Step 1 : Create advanced zone
Step 2 Create account 

Result 
Account create failing, observed below api not returning anything 

http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955


I tried to call below API

10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0

observed below error in MS log

2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
(ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
timezon
e:null




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


[jira] [Updated] (CLOUDSTACK-6303) [UI] Account creation hang in UI,

2014-03-28 Thread Brian Federle (JIRA)

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

Brian Federle updated CLOUDSTACK-6303:
--

Component/s: (was: UI)
 API

This looks like an API issue, if the API response is not returning correctly.

 [UI] Account creation hang in UI,  
 ---

 Key: CLOUDSTACK-6303
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6303
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: 4.4 build
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.4.0


 Steps to reproduce 
 Step 1 : Create advanced zone
 Step 2 Create account 
 Result 
 Account create failing, observed below api not returning anything 
 http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955
 I tried to call below API
 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0
 observed below error in MS log
 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
 (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
 timezon
 e:null



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


[jira] [Commented] (CLOUDSTACK-6170) Support managed storage for root disks

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 553630b1b91dc991ee27bae654fb06afa2f581ea in cloudstack's branch 
refs/heads/4.4 from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=553630b ]

CLOUDSTACK-6170 (VMware root-disk support for managed storage)


 Support managed storage for root disks
 --

 Key: CLOUDSTACK-6170
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6170
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
 Environment: I expect to support managed storage for root disks on 
 XenServer (ESX and KVM are targeted for 4.5).
Reporter: Mike Tutkowski
Assignee: Mike Tutkowski
 Fix For: 4.4.0


 Cloud environments have a need for guaranteed storage performance. By this I 
 mean having the ability to specify a minimum and maximum number of IOPS on a 
 volume-by-volume basis.
 I added support for this for XenServer and ESX in 4.2 for data disks.
 I added support for this for KVM in 4.3 for data disks.
 It is my intent to add support for this for XenServer and ESX in 4.4 for root 
 disks (with subsequent support for root disks on KVM expected in 4.5).
 The main changes are expected to occur in CloudStack logic that controls 
 hypervisors and additions to the way root-volume orchestration happens.



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


[jira] [Updated] (CLOUDSTACK-6303) [Automation] [UI] Account creation hang in UI,

2014-03-28 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti updated CLOUDSTACK-6303:
-

Summary: [Automation] [UI] Account creation hang in UI,(was: [UI] 
Account creation hang in UI,  )

 [Automation] [UI] Account creation hang in UI,  
 

 Key: CLOUDSTACK-6303
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6303
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: 4.4 build
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.4.0


 Steps to reproduce 
 Step 1 : Create advanced zone
 Step 2 Create account 
 Result 
 Account create failing, observed below api not returning anything 
 http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955
 I tried to call below API
 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0
 observed below error in MS log
 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
 (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
 timezon
 e:null



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


[jira] [Created] (CLOUDSTACK-6304) MySQLSyntaxErrorExceptions and SQLExceptions are seen on catalina.out log during Management Server Deployment

2014-03-28 Thread Chandan Purushothama (JIRA)
Chandan Purushothama created CLOUDSTACK-6304:


 Summary: MySQLSyntaxErrorExceptions and SQLExceptions are seen 
on catalina.out log during Management Server Deployment
 Key: CLOUDSTACK-6304
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6304
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.4.0
 Attachments: catalina.zip

Attached the catalina.out log to the bug report. The log has the details 
pertaining to the MySQLSyntaxErrorExceptions and SQLExceptions seen during 
Management Server Installation.



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


[jira] [Updated] (CLOUDSTACK-6304) MySQLSyntaxErrorExceptions and SQLExceptions are seen on catalina.out log during Management Server Deployment

2014-03-28 Thread Chandan Purushothama (JIRA)

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

Chandan Purushothama updated CLOUDSTACK-6304:
-

Attachment: catalina.zip

 MySQLSyntaxErrorExceptions and SQLExceptions are seen on catalina.out log 
 during Management Server Deployment
 -

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

 Attachments: catalina.zip


 Attached the catalina.out log to the bug report. The log has the details 
 pertaining to the MySQLSyntaxErrorExceptions and SQLExceptions seen 
 during Management Server Installation.



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


[jira] [Commented] (CLOUDSTACK-6170) Support managed storage for root disks

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 0879ab812e8b533bee836ce774c843b0a15baa4a in cloudstack's branch 
refs/heads/master from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0879ab8 ]

CLOUDSTACK-6170 (VMware root-disk support for managed storage)


 Support managed storage for root disks
 --

 Key: CLOUDSTACK-6170
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6170
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
 Environment: I expect to support managed storage for root disks on 
 XenServer (ESX and KVM are targeted for 4.5).
Reporter: Mike Tutkowski
Assignee: Mike Tutkowski
 Fix For: 4.4.0


 Cloud environments have a need for guaranteed storage performance. By this I 
 mean having the ability to specify a minimum and maximum number of IOPS on a 
 volume-by-volume basis.
 I added support for this for XenServer and ESX in 4.2 for data disks.
 I added support for this for KVM in 4.3 for data disks.
 It is my intent to add support for this for XenServer and ESX in 4.4 for root 
 disks (with subsequent support for root disks on KVM expected in 4.5).
 The main changes are expected to occur in CloudStack logic that controls 
 hypervisors and additions to the way root-volume orchestration happens.



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


[jira] [Updated] (CLOUDSTACK-6303) [Automation] [UI] Account creation hang in UI,

2014-03-28 Thread Rayees Namathponnan (JIRA)

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

Rayees Namathponnan updated CLOUDSTACK-6303:


Attachment: CLOUDSTACK-6303.rar

Log and dbdump attached 

 [Automation] [UI] Account creation hang in UI,  
 

 Key: CLOUDSTACK-6303
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6303
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: 4.4 build
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.4.0

 Attachments: CLOUDSTACK-6303.rar


 Steps to reproduce 
 Step 1 : Create advanced zone
 Step 2 Create account 
 Result 
 Account create failing, observed below api not returning anything 
 http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955
 I tried to call below API
 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0
 observed below error in MS log
 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
 (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
 timezon
 e:null



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


[jira] [Assigned] (CLOUDSTACK-6303) [Automation] [UI] Account creation hang in UI,

2014-03-28 Thread Prachi Damle (JIRA)

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

Prachi Damle reassigned CLOUDSTACK-6303:


Assignee: Prachi Damle

 [Automation] [UI] Account creation hang in UI,  
 

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

 Attachments: CLOUDSTACK-6303.rar


 Steps to reproduce 
 Step 1 : Create advanced zone
 Step 2 Create account 
 Result 
 Account create failing, observed below api not returning anything 
 http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955
 I tried to call below API
 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0
 observed below error in MS log
 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
 (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
 timezon
 e:null



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


[jira] [Commented] (CLOUDSTACK-6303) [Automation] [UI] Account creation hang in UI,

2014-03-28 Thread Prachi Damle (JIRA)

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

Prachi Damle commented on CLOUDSTACK-6303:
--

I looked at the issue and found the root cause. There are two issues that needs 
to be fixed:

- A MySql error is encountered during 'Project' account cleanup in the IAM 
service. 
- But this MySql error is not handled by the MessageBus and that does not 
release the lock/decrement the counters in the MessageBus.
- Eventually all callers on the MessageBus are deadlocked and end up waiting to 
enter 

- This commit fixes the account cleanup MySql error in IAM service. This should 
prevent hitting the MessageBus error. 

Following ticket is logged to take a look at the MessagBus: 
https://issues.apache.org/jira/browse/CLOUDSTACK-6305



 [Automation] [UI] Account creation hang in UI,  
 

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

 Attachments: CLOUDSTACK-6303.rar


 Steps to reproduce 
 Step 1 : Create advanced zone
 Step 2 Create account 
 Result 
 Account create failing, observed below api not returning anything 
 http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955
 I tried to call below API
 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0
 observed below error in MS log
 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
 (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
 timezon
 e:null



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


[jira] [Commented] (CLOUDSTACK-6303) [Automation] [UI] Account creation hang in UI,

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 024efbfbd4da262a81a738be4a3f9452546d5a9c in cloudstack's branch 
refs/heads/4.4 from [~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=024efbf ]

CLOUDSTACK-6303 [Automation] [UI] Account creation hang in UI

Changes:
- Caused due to a MySql error during 'Project' account cleanup. The MySql error 
hits a deadlock bug in the MessageBus code that does not release the 
lock/decrement the counter Eventually all callers on the MessageBus end up 
waiting to enter
- This fixes the account cleanup MySql error.


 [Automation] [UI] Account creation hang in UI,  
 

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

 Attachments: CLOUDSTACK-6303.rar


 Steps to reproduce 
 Step 1 : Create advanced zone
 Step 2 Create account 
 Result 
 Account create failing, observed below api not returning anything 
 http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955
 I tried to call below API
 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0
 observed below error in MS log
 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
 (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
 timezon
 e:null



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


[jira] [Commented] (CLOUDSTACK-6303) [Automation] [UI] Account creation hang in UI,

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 4e61e49143ceceb04efbba62e048c648be97cfc4 in cloudstack's branch 
refs/heads/master from [~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4e61e49 ]

CLOUDSTACK-6303 [Automation] [UI] Account creation hang in UI

Changes:
- Caused due to a MySql error during 'Project' account cleanup. The MySql error 
hits a deadlock bug in the MessageBus code that does not release the 
lock/decrement the counter Eventually all callers on the MessageBus end up 
waiting to enter
- This fixes the account cleanup MySql error.


 [Automation] [UI] Account creation hang in UI,  
 

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

 Attachments: CLOUDSTACK-6303.rar


 Steps to reproduce 
 Step 1 : Create advanced zone
 Step 2 Create account 
 Result 
 Account create failing, observed below api not returning anything 
 http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955
 I tried to call below API
 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0
 observed below error in MS log
 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
 (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
 timezon
 e:null



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


[jira] [Commented] (CLOUDSTACK-6305) MessageBus: Needs to handle exceptions from the subscribers and decrement the counter

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 6e093514e463fde23fe7d9dcf15996cbbbce5a21 in cloudstack's branch 
refs/heads/4.4 from [~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6e09351 ]

CLOUDSTACK-6305: protect lock leaking from unhandled exception


 MessageBus: Needs to handle exceptions from the subscribers and decrement the 
 counter
 -

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


 MessageBus needs to handle the runtime exceptions thrown from the subscribers 
 while processing the published messages.
 Currently, the MessageBus easily causes a deadlocked situation if one of the 
 subscriber hits runtime error, because of not releasing the counter.



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


[jira] [Commented] (CLOUDSTACK-6305) MessageBus: Needs to handle exceptions from the subscribers and decrement the counter

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit b6cc6dd8e314a0ff7bac0f1849b69021194c93d5 in cloudstack's branch 
refs/heads/master from [~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b6cc6dd ]

CLOUDSTACK-6305: protect lock leaking from unhandled exception


 MessageBus: Needs to handle exceptions from the subscribers and decrement the 
 counter
 -

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


 MessageBus needs to handle the runtime exceptions thrown from the subscribers 
 while processing the published messages.
 Currently, the MessageBus easily causes a deadlocked situation if one of the 
 subscriber hits runtime error, because of not releasing the counter.



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


[jira] [Resolved] (CLOUDSTACK-6305) MessageBus: Needs to handle exceptions from the subscribers and decrement the counter

2014-03-28 Thread Kelven Yang (JIRA)

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

Kelven Yang resolved CLOUDSTACK-6305.
-

Resolution: Fixed

 MessageBus: Needs to handle exceptions from the subscribers and decrement the 
 counter
 -

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


 MessageBus needs to handle the runtime exceptions thrown from the subscribers 
 while processing the published messages.
 Currently, the MessageBus easily causes a deadlocked situation if one of the 
 subscriber hits runtime error, because of not releasing the counter.



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


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

2014-03-28 Thread ASF subversion and git services (JIRA)

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

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

Commit 7590988dd74aa5c459e9443113385e1b98aa8657 in cloudstack's branch 
refs/heads/master from Edison Su
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7590988 ]

CLOUDSTACK-5329: stupid java box/unbox

Conflicts:

engine/schema/src/com/cloud/vm/VMInstanceVO.java


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

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

 Attachments: management-server.log, management-server.rar, 
 management-server.rar


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

[jira] [Updated] (CLOUDSTACK-6305) MessageBus: Needs to handle exceptions from the subscribers and decrement the counter

2014-03-28 Thread Prachi Damle (JIRA)

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

Prachi Damle updated CLOUDSTACK-6305:
-

Assignee: Kelven Yang

 MessageBus: Needs to handle exceptions from the subscribers and decrement the 
 counter
 -

 Key: CLOUDSTACK-6305
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6305
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Reporter: Prachi Damle
Assignee: Kelven Yang
Priority: Critical
 Fix For: 4.4.0


 MessageBus needs to handle the runtime exceptions thrown from the subscribers 
 while processing the published messages.
 Currently, the MessageBus easily causes a deadlocked situation if one of the 
 subscriber hits runtime error, because of not releasing the counter.



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


[jira] [Commented] (CLOUDSTACK-6297) Cloudstack Fails to Launch on Ubuntu missing MySQL Driver

2014-03-28 Thread Joshua Rogers (JIRA)

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

Joshua Rogers commented on CLOUDSTACK-6297:
---

I was able to resolve this issue by downloading the latest mysql connector to 
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib.

 Cloudstack Fails to Launch on Ubuntu missing MySQL Driver
 -

 Key: CLOUDSTACK-6297
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6297
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.3.0
 Environment: Ubuntu Server 13.10
Reporter: Joshua Rogers
Priority: Critical

 On Ubuntu Server 13.10, installing Cloudstack 4.3 as specified in the 
 documentation does not produce a runnable system. Cloudstack-management dies 
 shortly after it starts with a stack trace indicating that it can't find the 
 MySQL driver (trace listed below.)
 This continues to occur after running
apt-get install libmysql-java
cp /usr/share/java/mysql-connector-java-5.1.25.jar 
 /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/
reboot
 --- Stack Trace ---
 2014-03-27 20:53:11,112 INFO  [c.c.u.d.T.Transaction] (main:null) Is Data 
 Base High Availiability enabled? Ans : false
 2014-03-27 20:53:11,186 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to 
 get a new db connection
 java.sql.SQLException: No suitable driver found for 
 jdbc:mysql://localhost:3306/cloud?autoReconnect=trueprepStmtCacheSize=517cachePrepStmts=true
 at java.sql.DriverManager.getConnection(DriverManager.java:635)
 at java.sql.DriverManager.getConnection(DriverManager.java:195)
 at 
 org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
 at 
 org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
 at 
 org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
 at 
 org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
 at 
 com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:204)
 at com.cloud.utils.db.Merovingian2.init(Merovingian2.java:68)
 at 
 com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:80)
 at 
 com.cloud.server.LockMasterListener.init(LockMasterListener.java:33)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)
 at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:534)
 at 
 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
 at 
 org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)
 at 
 org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280)
 at 
 org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1045)
 at 
 org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:949)
 at 
 org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)
 at 
 org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
 at 
 org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295)
 at 
 org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
 at 
 org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292)
 at 
 org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
 at 
 org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628)
 at 
 org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932)
 at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6303) [Automation] [UI] Account creation hang in UI,

2014-03-28 Thread Prachi Damle (JIRA)

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

Prachi Damle resolved CLOUDSTACK-6303.
--

Resolution: Fixed

 [Automation] [UI] Account creation hang in UI,  
 

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

 Attachments: CLOUDSTACK-6303.rar


 Steps to reproduce 
 Step 1 : Create advanced zone
 Step 2 Create account 
 Result 
 Account create failing, observed below api not returning anything 
 http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955
 I tried to call below API
 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0
 observed below error in MS log
 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] 
 (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 
 timezon
 e:null



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