[jira] [Assigned] (CLOUDSTACK-7767) [Events] All events are not generated for snapshot creation

2014-10-28 Thread Anshul Gangwar (JIRA)

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

Anshul Gangwar reassigned CLOUDSTACK-7767:
--

Assignee: Anshul Gangwar

 [Events] All events are not generated for snapshot creation
 ---

 Key: CLOUDSTACK-7767
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7767
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Snapshot
Affects Versions: 4.5.0
 Environment: Latest build from 4.5 with commit [root@BPKxDmS ~]# 
 cloudstack-sccs
 562c89544e80dcd61ae5fd179eb8546de2598b33
Reporter: Sanjeev N
Assignee: Anshul Gangwar
Priority: Critical
 Fix For: 4.5.0

 Attachments: cloud.dmp, management-server.rar


 [Events] All events are not generated for snapshot creation
 Steps to Reproduce:
 ===
 1.Bring up CS with latest build from 4.5
 2.Deploy a vm using cent os template
 3.Take a snapshot on the root disk of the vm
 4.Verify the cloud.events table for the snapshot events
 We could see events with states created,sheduled,started and completed for 
 vm,volume and template whereas there is only one event with state scheduled 
 for snapshot creation.
 So by looking at the events user will not be able to find out whether the 
 snaphot creation is completed of not.
 Following is the DB snippet:
 mysql select id,uuid,type,state,description  from event where type in 
 (SNAPSHOT.CREATE,VM.CREATE,VOLUME.CREATE,TEMPLATE.CREATE);
 +-+--+-+---++
 | id  | uuid | type| state | 
 description   
  |
 +-+--+-+---++
 | 189 | 1f48cbef-648e-4728-9eb1-5178bea3b4fd | SNAPSHOT.CREATE | Scheduled | 
 creating snapshot for volume: 10  
  |
 | 207 | 9162ed93-bd6c-4e78-8f4a-1836859f5009 | SNAPSHOT.CREATE | Scheduled | 
 creating snapshot for volume: 15  
  |
 | 208 | 261b95a7-0a4d-45cd-9922-3cde8640ab02 | SNAPSHOT.CREATE | Scheduled | 
 creating snapshot for volume: 15  
  |
 | 212 | e80e1383-944b-4ac9-bc86-70511de86c94 | SNAPSHOT.CREATE | Scheduled | 
 creating snapshot for volume: 15  
  |
 | 168 | 518e4ae7-e506-4b93-a8b5-696777b91706 | TEMPLATE.CREATE | Completed | 
 Successfully completed creating template. Id: 202 name: cent53
  |
 | 193 | 3d20409e-a9e5-438a-9a00-2deb23ee87fe | TEMPLATE.CREATE | Created   | 
 Successfully created entity for creating template 
  |
 | 194 | 528f823e-b817-4b9a-8935-2f57ac5a4c9b | TEMPLATE.CREATE | Scheduled | 
 creating template: fromSnapRoot10 
  |
 | 195 | 9ab1d914-9f30-4a3d-8070-1fdce6827f6d | TEMPLATE.CREATE | Started   | 
 creating template. Template Id: 203 from snapshot Id: 1   
  |
 | 196 | d2676d55-84c8-4486-9aca-0f3eda74a4a7 | TEMPLATE.CREATE | Completed | 
 Successfully completed creating template. Template Id: 203 from snapshot Id: 
 1 |
 | 154 | 3b9207d6-d120-4762-b9e3-423f849870d6 | VM.CREATE   | Created   | 
 Successfully created entity for deploying Vm. Vm Id: 8
  |
 | 155 | 7c47beb2-e105-478f-9575-e3ab1b2709ec | VM.CREATE   | Scheduled | 
 starting Vm. Vm Id: 8 
  |
 | 156 | 27718b57-b679-412b-b983-0f9cf7757930 | VM.CREATE   | Started   | 
 starting Vm. Vm Id: 8 
  |
 | 159 | 6b5bece5-bfab-41c0-906e-8fbec2ddd2bf | VM.CREATE   | Completed | 
 Successfully completed starting Vm. Vm Id: 8  
  |
 | 170 | 66412dc3-fc03-4a2d-b796-807bd6ec096f | VM.CREATE   | Created   | 
 Successfully created entity for deploying Vm. Vm Id: 10   
  |
 | 171 | a6c91812-9218-451c-a801-60652089ba7b | VM.CREATE   | Scheduled | 
 starting Vm. Vm Id: 10
  |
 | 172 | 3f0cd706-ac3d-48a5-b4f9-a51d96e95dca | VM.CREATE   | Started   | 
 starting Vm. Vm Id: 10
  |
 | 175 | dde1bff2-5f68-43a9-a090-10718c3a14f3 | VM.CREATE   | Completed | 
 Successfully completed starting Vm. Vm Id: 10 
  |
 

[jira] [Created] (CLOUDSTACK-7801) test_volumes.py has import errors

2014-10-28 Thread Gaurav Aradhye (JIRA)
Gaurav Aradhye created CLOUDSTACK-7801:
--

 Summary: test_volumes.py has import errors
 Key: CLOUDSTACK-7801
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7801
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
 Fix For: 4.5.0


test_volumes.py has been introduced with import errors during commit 
5c2094eec1408494586e48d38d9076b31ca3e5f5



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


[jira] [Updated] (CLOUDSTACK-7801) test_volumes.py has import errors

2014-10-28 Thread Gaurav Aradhye (JIRA)

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

Gaurav Aradhye updated CLOUDSTACK-7801:
---
Status: Reviewable  (was: In Progress)

 test_volumes.py has import errors
 -

 Key: CLOUDSTACK-7801
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7801
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 test_volumes.py has been introduced with import errors during commit 
 5c2094eec1408494586e48d38d9076b31ca3e5f5



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


[jira] [Created] (CLOUDSTACK-7802) test_vpc_network.TestVPCNetworkUpgrade.test_01_network_services_upgrade fails while checking the network state

2014-10-28 Thread Gaurav Aradhye (JIRA)
Gaurav Aradhye created CLOUDSTACK-7802:
--

 Summary: 
test_vpc_network.TestVPCNetworkUpgrade.test_01_network_services_upgrade fails 
while checking the network state
 Key: CLOUDSTACK-7802
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7802
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
 Fix For: 4.5.0


Test case fails with Network state should change to Allocated, it is 
Implemented after all the VMs in the network are stopped and network state is 
checked.

We are already waiting for 600 seconds, but still it is taking much longer for 
network state to change.



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


[jira] [Created] (CLOUDSTACK-7803) Storage live migration of instance may not happen if instance has ISO attached.

2014-10-28 Thread Sateesh Chodapuneedi (JIRA)
Sateesh Chodapuneedi created CLOUDSTACK-7803:


 Summary: Storage live migration of instance may not happen if 
instance has ISO attached.
 Key: CLOUDSTACK-7803
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7803
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: VMware
 Environment: vSphere 5.1
CloudStack 4.3
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
 Fix For: 4.5.0


If user instance has ISO (other than vmware tools ISO) attached, then storage 
live migration may not happen.
Steps:-
1) Create user instance
2) Register ISO, wait till it is installed successfully
3) Attach registered ISO in step(2)
4) Migrate VM to another host which needs storage migration.





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


[jira] [Created] (CLOUDSTACK-7804) [CEPH] Adding RBD primary storage is failing

2014-10-28 Thread shweta agarwal (JIRA)
shweta agarwal created CLOUDSTACK-7804:
--

 Summary: [CEPH] Adding  RBD primary storage is failing 
 Key: CLOUDSTACK-7804
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7804
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Storage Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0


Repro steps :
1. Create a LXC zone with NFS primary storage
2. Once System VMs are up add Ceph storage as another primary storage

Bug:
Storage addition is failing. It goes to initialized state but after some time 
gets message storage addition failed .



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


[jira] [Updated] (CLOUDSTACK-7804) [CEPH] Adding RBD primary storage is failing

2014-10-28 Thread shweta agarwal (JIRA)

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

shweta agarwal updated CLOUDSTACK-7804:
---
Attachment: agent.tar.gz

 [CEPH] Adding  RBD primary storage is failing 
 --

 Key: CLOUDSTACK-7804
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7804
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.tar.gz


 Repro steps :
 1. Create a LXC zone with NFS primary storage
 2. Once System VMs are up add Ceph storage as another primary storage
 Bug:
 Storage addition is failing. It goes to initialized state but after some time 
 gets message storage addition failed .



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


[jira] [Updated] (CLOUDSTACK-7804) [CEPH] Adding RBD primary storage is failing

2014-10-28 Thread shweta agarwal (JIRA)

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

shweta agarwal updated CLOUDSTACK-7804:
---
Attachment: MS.tar.gz

 [CEPH] Adding  RBD primary storage is failing 
 --

 Key: CLOUDSTACK-7804
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7804
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: MS.tar.gz, agent.tar.gz


 Repro steps :
 1. Create a LXC zone with NFS primary storage
 2. Once System VMs are up add Ceph storage as another primary storage
 Bug:
 Storage addition is failing. It goes to initialized state but after some time 
 gets message storage addition failed .



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


[jira] [Updated] (CLOUDSTACK-7804) [CEPH] Adding RBD primary storage is failing

2014-10-28 Thread shweta agarwal (JIRA)

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

shweta agarwal updated CLOUDSTACK-7804:
---
Description: 
Repro steps :
1. Create a LXC zone with NFS primary storage
2. Once System VMs are up add Ceph storage as another primary storage

Bug:
Storage addition is failing. It goes to initialized state but after some time 
gets message storage addition failed .


attached MS log and Agents log for the same

  was:
Repro steps :
1. Create a LXC zone with NFS primary storage
2. Once System VMs are up add Ceph storage as another primary storage

Bug:
Storage addition is failing. It goes to initialized state but after some time 
gets message storage addition failed .


 [CEPH] Adding  RBD primary storage is failing 
 --

 Key: CLOUDSTACK-7804
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7804
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: MS.tar.gz, agent.tar.gz


 Repro steps :
 1. Create a LXC zone with NFS primary storage
 2. Once System VMs are up add Ceph storage as another primary storage
 Bug:
 Storage addition is failing. It goes to initialized state but after some time 
 gets message storage addition failed .
 attached MS log and Agents log for the same



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


[jira] [Updated] (CLOUDSTACK-7802) test_vpc_network.TestVPCNetworkUpgrade.test_01_network_services_upgrade fails while checking the network state

2014-10-28 Thread Gaurav Aradhye (JIRA)

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

Gaurav Aradhye updated CLOUDSTACK-7802:
---
Status: Reviewable  (was: In Progress)

 test_vpc_network.TestVPCNetworkUpgrade.test_01_network_services_upgrade fails 
 while checking the network state
 --

 Key: CLOUDSTACK-7802
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7802
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 Test case fails with Network state should change to Allocated, it is 
 Implemented after all the VMs in the network are stopped and network state 
 is checked.
 We are already waiting for 600 seconds, but still it is taking much longer 
 for network state to change.



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


[jira] [Created] (CLOUDSTACK-7805) test_vpc_vms_deployment.TestVMDeployVPC.test_07_delete_network_with_rules fails while matching acquired IP address wth listed IP

2014-10-28 Thread Gaurav Aradhye (JIRA)
Gaurav Aradhye created CLOUDSTACK-7805:
--

 Summary: 
test_vpc_vms_deployment.TestVMDeployVPC.test_07_delete_network_with_rules fails 
while matching acquired IP address wth listed IP
 Key: CLOUDSTACK-7805
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7805
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
 Fix For: 4.5.0


The test case fails because there are two ip addresses acquired in a network. 
The step in the test case matches the first element in the list with the 2nd ip 
addresses. It can't be guaranteed to succeed because the elements can be listed 
in any order.



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


[jira] [Commented] (CLOUDSTACK-7102) Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' expection

2014-10-28 Thread Likitha Shetty (JIRA)

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

Likitha Shetty commented on CLOUDSTACK-7102:


And if an attempt is made to migrate a volume (attached to a VM and present in 
the same datastore) to another storage, then it will fail with the below error -
{noformat}
INFO  [c.c.h.v.m.DatastoreMO] (DirectAgent-102:ctx-ec935ae6 10.102.192.12) 
Search file 2e715c4920ca47089585bf882f814bdd.vmdk on 
[651747c0f6a6315193ae68e3ca3d271c] i-2-3-VM
ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-102:ctx-ec935ae6 10.102.192.12) 
Catch Exception java.lang.RuntimeException due to java.lang.RuntimeException: 
File [651747c0f6a6315193ae68e3ca3d271c] i-2-3-VM was not found
java.lang.RuntimeException: File [651747c0f6a6315193ae68e3ca3d271c] i-2-3-VM 
was not found
at 
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:336)
at 
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:57)
at 
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:78)
at 
com.cloud.hypervisor.vmware.mo.DatastoreMO.fileExists(DatastoreMO.java:308)
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4793)
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:531)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:215)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:50)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:47)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}

 Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' 
 expection
 ---

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


 Steps to reproduce
 
 1. Set global config 'vm.instancename.flag' to true.
 2. Bring up CS in advanced zone with at-least one vmware cluster.
 3. Add two primary storages to the cluster.
 4. Deploy one guest VM.
 5. Create a volume and attach the volume to the guest VM. (Ensure the volume 
 is in primary storage that doesn't contain the root disk).
 6. Migrate the volume to the primary storage that contains the root disk.
 Volume Migration will fail with the below error -
 {noformat}
 2014-07-14 12:21:33,112 ERROR [c.c.h.v.r.VmwareResource] 
 (DirectAgent-398:ctx-4797dd6a 10.102.192.7, job-878/job-879, cmd: 
 MigrateVolumeCommand) Catch Exception java.lang.Exception due to 
 java.lang.Exception: VM i-2-32-VM does not exist in VMware datacenter 
 datacenter-30215
 java.lang.Exception: VM i-2-32-VM does not exist in VMware datacenter 
 datacenter-30215
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3139)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:416)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293)
 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-7806) Agent state remians connecting for secondary storage VM

2014-10-28 Thread shweta agarwal (JIRA)

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

shweta agarwal updated CLOUDSTACK-7806:
---
Attachment: cloud.log

 Agent state remians connecting for secondary storage VM
 ---

 Key: CLOUDSTACK-7806
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7806
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: SystemVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Blocker
 Fix For: 4.5.0

 Attachments: cloud.log


 Repro steps :
 Create a LXC Zone setup.
 Notice Agent status of Secondary storage VM will be connecting once Sceondary 
 Storage VM is in running state .
 SSVM cloud log shows :
 2014-10-28 09:38:10,340 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:nulll
 ) Executing: /usr/local/cloud/systemvm/config_ssl.sh -i 10.147.30.190 -h 
 s-1-VM
 2014-10-28 09:38:10,377 DEBUG [cloud.agent.Agent] (Agent-Handler-4:null) 
 Receivee
 d response: Seq 0-159:  { Ans: , MgmtId: 233845178472723, via: 1, Ver: v1, 
 Flagss
 : 100010, 
 [{com.cloud.agent.api.PingAnswer:{_command:{hostType:Storage,
 hostId:0,wait:0},result:true,wait:0}}] }
 2014-10-28 09:38:11,487 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:nulll
 ) Execution is successful.
 2014-10-28 09:38:11,487 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:nulll
 ) Stopping web server: apache2apache2: Could not reliably determine the 
 server'ss
  fully qualified domain name, using 10.147.30.190 for ServerName
  ... waiting .
 Starting web server: apache2apache2: Could not reliably determine the 
 server's ff
 ully qualified domain name, using 10.147.30.190 for ServerName
 .
 2014-10-28 09:38:11,487 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-1:null)
 Seq 1-7097954487712612353:  { Ans: , MgmtId: 233845178472723, via: 1, Ver: 
 v1, FF
 lags: 110, 
 [{com.cloud.agent.api.SecStorageSetupAnswer:{_dir:4a409f9f-33f8--
 3898-b4b8-39a2e3d01cb1,result:true,details:success,wait:0}}] }
 attaching entire cloud.log



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


[jira] [Created] (CLOUDSTACK-7806) Agent state remians connecting for secondary storage VM

2014-10-28 Thread shweta agarwal (JIRA)
shweta agarwal created CLOUDSTACK-7806:
--

 Summary: Agent state remians connecting for secondary storage VM
 Key: CLOUDSTACK-7806
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7806
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: SystemVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Blocker
 Fix For: 4.5.0
 Attachments: cloud.log

Repro steps :

Create a LXC Zone setup.

Notice Agent status of Secondary storage VM will be connecting once Sceondary 
Storage VM is in running state .

SSVM cloud log shows :
2014-10-28 09:38:10,340 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:nulll
) Executing: /usr/local/cloud/systemvm/config_ssl.sh -i 10.147.30.190 -h s-1-VM
2014-10-28 09:38:10,377 DEBUG [cloud.agent.Agent] (Agent-Handler-4:null) 
Receivee
d response: Seq 0-159:  { Ans: , MgmtId: 233845178472723, via: 1, Ver: v1, 
Flagss
: 100010, 
[{com.cloud.agent.api.PingAnswer:{_command:{hostType:Storage,
hostId:0,wait:0},result:true,wait:0}}] }
2014-10-28 09:38:11,487 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:nulll
) Execution is successful.
2014-10-28 09:38:11,487 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:nulll
) Stopping web server: apache2apache2: Could not reliably determine the 
server'ss
 fully qualified domain name, using 10.147.30.190 for ServerName
 ... waiting .
Starting web server: apache2apache2: Could not reliably determine the server's 
ff
ully qualified domain name, using 10.147.30.190 for ServerName
.

2014-10-28 09:38:11,487 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null)
Seq 1-7097954487712612353:  { Ans: , MgmtId: 233845178472723, via: 1, Ver: v1, 
FF
lags: 110, 
[{com.cloud.agent.api.SecStorageSetupAnswer:{_dir:4a409f9f-33f8--
3898-b4b8-39a2e3d01cb1,result:true,details:success,wait:0}}] }

attaching entire cloud.log



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


[jira] [Created] (CLOUDSTACK-7807) Allow rate limiting on VPC public interface only

2014-10-28 Thread Pierre-Luc Dion (JIRA)
Pierre-Luc Dion created CLOUDSTACK-7807:
---

 Summary: Allow rate limiting on VPC public interface only
 Key: CLOUDSTACK-7807
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7807
 Project: CloudStack
  Issue Type: Wish
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Virtual Router
Affects Versions: 4.2.1, 4.3.1, 4.4.1
Reporter: Pierre-Luc Dion


It would be interesting to have Network throttling Rate only on the Public 
Interface of a VPC. Currently enabling Global setting: 
``network.throttling.rate``
on a VPC will enable rate limiting on all VPC interface which impact traffic 
between Tiers.

We should be able to configure rate limiting only on the Public Interface as 
well as all interfaces.



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


[jira] [Updated] (CLOUDSTACK-7807) Allow rate limiting on VPC public interface only

2014-10-28 Thread Pierre-Luc Dion (JIRA)

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

Pierre-Luc Dion updated CLOUDSTACK-7807:

Priority: Minor  (was: Major)

 Allow rate limiting on VPC public interface only
 

 Key: CLOUDSTACK-7807
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7807
 Project: CloudStack
  Issue Type: Wish
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.2.1, 4.3.1, 4.4.1
Reporter: Pierre-Luc Dion
Priority: Minor

 It would be interesting to have Network throttling Rate only on the Public 
 Interface of a VPC. Currently enabling Global setting: 
 ``network.throttling.rate``
 on a VPC will enable rate limiting on all VPC interface which impact traffic 
 between Tiers.
 We should be able to configure rate limiting only on the Public Interface as 
 well as all interfaces.



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


[jira] [Created] (CLOUDSTACK-7808) Typo in Zone Creation Wizard

2014-10-28 Thread Gabor Apati-Nagy (JIRA)
Gabor Apati-Nagy created CLOUDSTACK-7808:


 Summary: Typo in Zone Creation Wizard
 Key: CLOUDSTACK-7808
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7808
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.1
Reporter: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy
Priority: Minor
 Fix For: 4.5.0


Steps to reproduce:
1. Go to the New Zone creation wizard
2. In Step 3 (Setup Network, Pod) look at the reference text on the upper part 
of the box. 

There is a typo in the text: CloudStack\'s is shown instead of CloudStack's.



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


[jira] [Resolved] (CLOUDSTACK-7795) Fix multiple baremetal rct configuraitons

2014-10-28 Thread frank zhang (JIRA)

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

frank zhang resolved CLOUDSTACK-7795.
-
Resolution: Fixed

 Fix multiple baremetal rct configuraitons
 -

 Key: CLOUDSTACK-7795
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7795
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Baremetal
Affects Versions: 4.5.0
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.5.0






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


[jira] [Commented] (CLOUDSTACK-7796) UI remove unnecessary module check.

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

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

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

Commit 26cf97e2ded7d512a7b7c69fadb82e0cd42b4711 in cloudstack's branch 
refs/heads/4.5 from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=26cf97e ]

CLOUDSTACK-7796: UI  network  detail view  data provider  remove 
unnecessary module check.


 UI  remove unnecessary module check.
 -

 Key: CLOUDSTACK-7796
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7796
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical





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


[jira] [Commented] (CLOUDSTACK-7796) UI remove unnecessary module check.

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

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

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

Commit 11c53f04470fb436b529f1370cb70ab556004dfc in cloudstack's branch 
refs/heads/4.5 from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=11c53f0 ]

CLOUDSTACK-7796: UI  Infrastructure  zone  physical network  guest  
details tab  network tab  detail view  dataProvider  remove unnecessary 
module check.


 UI  remove unnecessary module check.
 -

 Key: CLOUDSTACK-7796
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7796
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical





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


[jira] [Commented] (CLOUDSTACK-7796) UI remove unnecessary module check.

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

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

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

Commit 429ea8bc957ed6ed238ccf6f77be718d7ba0ff81 in cloudstack's branch 
refs/heads/4.5 from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=429ea8b ]

CLOUDSTACK-7796: UI  Infrastructure  zones  zone  details tab  
dataProvider  remove unnecessary module check.


 UI  remove unnecessary module check.
 -

 Key: CLOUDSTACK-7796
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7796
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical





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


[jira] [Commented] (CLOUDSTACK-7796) UI remove unnecessary module check.

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

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

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

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

CLOUDSTACK-7796: UI  network  detail view  data provider  remove 
unnecessary module check.


 UI  remove unnecessary module check.
 -

 Key: CLOUDSTACK-7796
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7796
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical





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


[jira] [Commented] (CLOUDSTACK-7796) UI remove unnecessary module check.

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

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

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

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

CLOUDSTACK-7796: UI  Infrastructure  zone  physical network  guest  
details tab  network tab  detail view  dataProvider  remove unnecessary 
module check.


 UI  remove unnecessary module check.
 -

 Key: CLOUDSTACK-7796
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7796
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical





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


[jira] [Commented] (CLOUDSTACK-7796) UI remove unnecessary module check.

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

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

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

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

CLOUDSTACK-7796: UI  Infrastructure  zones  zone  details tab  
dataProvider  remove unnecessary module check.


 UI  remove unnecessary module check.
 -

 Key: CLOUDSTACK-7796
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7796
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical





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


[jira] [Created] (CLOUDSTACK-7809) UI – get user data from API calls instead of cookies when a new tab is open

2014-10-28 Thread Jessica Wang (JIRA)
Jessica Wang created CLOUDSTACK-7809:


 Summary: UI – get user data from API calls instead of cookies when 
a new tab is open
 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Reporter: Jessica Wang
Priority: Critical
 Fix For: 4.5.0


including all user data(first name, last name, role, account, domainID, 
capabilities, ~) except sessionKey.



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


[jira] [Assigned] (CLOUDSTACK-7809) UI – get user data from API calls instead of cookies when a new tab is open

2014-10-28 Thread Jessica Wang (JIRA)

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

Jessica Wang reassigned CLOUDSTACK-7809:


Assignee: Jessica Wang

 UI – get user data from API calls instead of cookies when a new tab is open
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0


 including all user data(first name, last name, role, account, domainID, 
 capabilities, ~) except sessionKey.



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


[jira] [Updated] (CLOUDSTACK-7765) Field Validations Missing for VPC IP Address Fields

2014-10-28 Thread Gabor Apati-Nagy (JIRA)

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

Gabor Apati-Nagy updated CLOUDSTACK-7765:
-
Status: Reviewable  (was: In Progress)

 Field Validations Missing for VPC IP Address Fields
 ---

 Key: CLOUDSTACK-7765
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7765
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy
Priority: Minor
 Fix For: 4.5.0


 Steps -
 1. Go to the Networks section
 2. Click on Network-VPC and click Add VPC
 There are no IP address validations in the VPC creation form. 



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


[jira] [Updated] (CLOUDSTACK-7766) Field Validations Missing for Ingress and Egress Rules

2014-10-28 Thread Gabor Apati-Nagy (JIRA)

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

Gabor Apati-Nagy updated CLOUDSTACK-7766:
-
Status: Reviewable  (was: In Progress)

 Field Validations Missing for Ingress and Egress Rules
 --

 Key: CLOUDSTACK-7766
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7766
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy
Priority: Minor
 Fix For: 4.5.0


 Steps-
 1. For a Network-Security groups, go to the Ingress Rule (or Egress Rule) tab.
 There are no Field Validations for the Start Port, End Port and CIDR fields. 
 This issue exists for both: CIDR and Account. 
 Additionally, the same applies for both: Ingress and Egress rules.



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


[jira] [Updated] (CLOUDSTACK-7764) No IP Address Validations when Adding Networks

2014-10-28 Thread Gabor Apati-Nagy (JIRA)

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

Gabor Apati-Nagy updated CLOUDSTACK-7764:
-
Status: Reviewable  (was: In Progress)

 No IP Address Validations when Adding Networks
 --

 Key: CLOUDSTACK-7764
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7764
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy
Priority: Minor
 Fix For: 4.5.0


 Steps -
 1. Go to the Network tab under Zones. 
 2. Click Add guest network to add a new network.
 There are no field validations for 
 -IPv4 Gateway
 -IPv4 Netmask
 -IPv4 Start IP
 -IPv4 End IP
 -IPv6 Gateway
 -IPv6 CIDR
 -IPv6 Start IP
 -IPv6 End IP
 on the form.



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


[jira] [Updated] (CLOUDSTACK-7808) Typo in Zone Creation Wizard

2014-10-28 Thread Gabor Apati-Nagy (JIRA)

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

Gabor Apati-Nagy updated CLOUDSTACK-7808:
-
Status: Reviewable  (was: In Progress)

 Typo in Zone Creation Wizard
 

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


 Steps to reproduce:
 1. Go to the New Zone creation wizard
 2. In Step 3 (Setup Network, Pod) look at the reference text on the upper 
 part of the box. 
 There is a typo in the text: CloudStack\'s is shown instead of 
 CloudStack's.



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


[jira] [Resolved] (CLOUDSTACK-7798) listing 2 guest networks is taking close to 4 seconds (Slow compare to previous releases)

2014-10-28 Thread Min Chen (JIRA)

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

Min Chen resolved CLOUDSTACK-7798.
--
Resolution: Fixed

Added requestHasSensitiveInfo and responseHasSensitiveInfo annotation to some 
missing Admin API command classes.

 listing 2 guest networks is taking close to 4 seconds (Slow compare to 
 previous releases)
 -

 Key: CLOUDSTACK-7798
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7798
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
Reporter: Min Chen
Assignee: Min Chen
Priority: Critical
 Fix For: 4.5.0


 Steps:
 1. Install and configure Adv zone with XS 6.5
 2. Created two guest networks
 3. Tried to deploy VM.
 Observation:
 While deploying the VM it has to select the network so listnetworks is called 
 from UI. It took close to 4 seconds to list two guest networks. UI dash board 
 is blank for 4 mins 



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


[jira] [Resolved] (CLOUDSTACK-7797) listSupportedNetworkServices API takes more than 1 second to complete, slow compared to previous 4.3 release

2014-10-28 Thread Min Chen (JIRA)

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

Min Chen resolved CLOUDSTACK-7797.
--
Resolution: Fixed

Fixed by removing filtering sensitive information from audit log if command 
response does not have sensitive information.

 listSupportedNetworkServices API takes more than 1 second to complete, slow 
 compared to previous 4.3 release
 

 Key: CLOUDSTACK-7797
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7797
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
Reporter: Min Chen
Assignee: Min Chen
Priority: Critical
 Fix For: 4.5.0


 add network offering UI displays Add network offering dialog with only
 Cancel OK button without wizard content.
 select OK UI displays error Status dialog with error:
 Unable to execute API command createnetworkoffering due to missing parameter 
 name
 select close add network offering frame is then correctly displayed



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


[jira] [Created] (CLOUDSTACK-7810) [Automation][Simulator] Fix the script test_vpc_vm_life_cycle.py - Test Cases failing on Simulator due to hardware resources requirement for test execution

2014-10-28 Thread Chandan Purushothama (JIRA)
Chandan Purushothama created CLOUDSTACK-7810:


 Summary: [Automation][Simulator] Fix the script 
test_vpc_vm_life_cycle.py - Test Cases failing on Simulator due to hardware 
resources requirement for test execution
 Key: CLOUDSTACK-7810
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7810
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Chandan Purushothama
 Fix For: 4.5.0


Test Cases are trying to validate SSH access and failing. These Test Cases are 
not meant to be run on SImulator due to their validation requirements. Hence 
they cannot be run with Simulator



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


[jira] [Created] (CLOUDSTACK-7811) [Automation][Simulator] Fix the script test_persistent_networks.py - Test Cases failing on Simulator due to hardware resources requirement for test execution

2014-10-28 Thread Chandan Purushothama (JIRA)
Chandan Purushothama created CLOUDSTACK-7811:


 Summary: [Automation][Simulator] Fix the script 
test_persistent_networks.py - Test Cases failing on Simulator due to hardware 
resources requirement for test execution
 Key: CLOUDSTACK-7811
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7811
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Chandan Purushothama
 Fix For: 4.5.0


Test Cases are trying to validate SSH access and failing. These Test Cases are 
not meant to be run on SImulator due to their validation requirements. Hence 
they cannot be run with Simulator



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


[jira] [Created] (CLOUDSTACK-7812) [Automation][Simulator] Fix the script maint/test_redundant_router_network_rules.py - Test Cases failing on Simulator due to hardware resources requirement for tes

2014-10-28 Thread Chandan Purushothama (JIRA)
Chandan Purushothama created CLOUDSTACK-7812:


 Summary: [Automation][Simulator] Fix the script 
maint/test_redundant_router_network_rules.py - Test Cases failing on 
Simulator due to hardware resources requirement for test execution
 Key: CLOUDSTACK-7812
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7812
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Chandan Purushothama
 Fix For: 4.5.0


Test Cases are trying to validate SSH access and failing. These Test Cases are 
not meant to be run on SImulator due to their validation requirements. Hence 
they cannot be run with Simulator



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


[jira] [Commented] (CLOUDSTACK-7659) UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included.

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

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

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

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

CLOUDSTACK-7659: UI: Upgrade jquery-validate lib to the latest 1.13.0 version 
with the additional-methods included.


 UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the 
 additional-methods included.
 --

 Key: CLOUDSTACK-7659
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7659
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy

 Upgrade jquery-validate lib to the latest 1.13.0 version with the 
 additional-methods included.
 Update the LICESE file.



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


[jira] [Commented] (CLOUDSTACK-7718) No Field Validations on Zone Form

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

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

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

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

CLOUDSTACK-7718: No Field Validations on Zone Form


 No Field Validations on Zone Form
 -

 Key: CLOUDSTACK-7718
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7718
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy
Priority: Minor
 Fix For: 4.5.0


 1. Go to the form for creating a new Zone
 2. Specify the Zone type and then go to the Setup Zone options.
 In the Setup zone tab, there are no field validations for the IP address 
 fields: IPv4 DNS1, IPv4DNS2, etc.



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


[jira] [Commented] (CLOUDSTACK-7764) No IP Address Validations when Adding Networks

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

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

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

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

CLOUDSTACK-7764: No IP Address Validations when Adding Networks Added 
validations for Add Network form on IPv4 Gateway, IPv4 Netmask, IPv4 Start IP, 
IPv4 End IP, IPv6 Gateway, IPv6 CIDR, IPv6 Start IP, IPv6 End IP fields.


 No IP Address Validations when Adding Networks
 --

 Key: CLOUDSTACK-7764
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7764
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy
Priority: Minor
 Fix For: 4.5.0


 Steps -
 1. Go to the Network tab under Zones. 
 2. Click Add guest network to add a new network.
 There are no field validations for 
 -IPv4 Gateway
 -IPv4 Netmask
 -IPv4 Start IP
 -IPv4 End IP
 -IPv6 Gateway
 -IPv6 CIDR
 -IPv6 Start IP
 -IPv6 End IP
 on the form.



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


[jira] [Commented] (CLOUDSTACK-7720) No IP Address Validation for Acquire new secondary IP

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

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

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

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

CLOUDSTACK-7720: No IP Address Validation for Acquire new secondary IP


 No IP Address Validation for Acquire new secondary IP
 -

 Key: CLOUDSTACK-7720
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7720
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy
Priority: Minor
 Fix For: 4.5.0


 Steps:
 1. Go to Instances -- NICs tab.
 2. Click on the View Secondary IPs
 3. Click on Acquire new secondary IP
 There is No IP address validation for Acquire new secondary IP. 
 Additionally, this field should be a required field. Clicking Ok generates 
 an IP, but it can be confusing to the end user.



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


[jira] [Commented] (CLOUDSTACK-7808) Typo in Zone Creation Wizard

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

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

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

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

CLOUDSTACK-7808: Typo in Zone Creation Wizard


 Typo in Zone Creation Wizard
 

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


 Steps to reproduce:
 1. Go to the New Zone creation wizard
 2. In Step 3 (Setup Network, Pod) look at the reference text on the upper 
 part of the box. 
 There is a typo in the text: CloudStack\'s is shown instead of 
 CloudStack's.



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


[jira] [Updated] (CLOUDSTACK-7809) UI remove unnecessary cookies

2014-10-28 Thread Jessica Wang (JIRA)

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

Jessica Wang updated CLOUDSTACK-7809:
-
Description: (was: including all user data(first name, last name, role, 
account, domainID, capabilities, ~) except sessionKey.)

 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Updated] (CLOUDSTACK-7809) UI remove unnecessary cookies

2014-10-28 Thread Jessica Wang (JIRA)

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

Jessica Wang updated CLOUDSTACK-7809:
-
Summary: UI  remove unnecessary cookies  (was: UI – get user data from API 
calls instead of cookies when a new tab is open)

 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0


 including all user data(first name, last name, role, account, domainID, 
 capabilities, ~) except sessionKey.



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


[jira] [Created] (CLOUDSTACK-7813) Management server is stuck after upgrade from 4.4.0 to 4.4.1

2014-10-28 Thread Thomas Schneider (JIRA)
Thomas Schneider created CLOUDSTACK-7813:


 Summary: Management server is stuck after upgrade from 4.4.0 to 
4.4.1
 Key: CLOUDSTACK-7813
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7813
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Upgrade
Affects Versions: 4.4.0, 4.4.1
 Environment: Ubuntu 12.04.5 + Cloudstack 4.4.1-snapshot (Branch 
4.4-RC20141014)
Reporter: Thomas Schneider
Priority: Critical


The column display from the snapshot _policy table is missing after update.

Just do: ALTER TABLE  `snapshot_policy` ADD  `display` TINYINT( 1 ) NOT NULL 
DEFAULT  '1' 



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


[jira] [Commented] (CLOUDSTACK-7809) UI remove unnecessary cookies

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

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

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

Commit 1ea6f7dd584b8817d025088431845949f8ed1825 in cloudstack's branch 
refs/heads/4.5 from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1ea6f7d ]

CLOUDSTACK-7809: UI  remove unnecessary cookie 'capabilities', 'supportELB', 
'kvmsnapshotenabled', 'regionsecondaryenabled', 'userpublictemplateenabled', 
'userProjectsEnabled'.


 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Commented] (CLOUDSTACK-7809) UI remove unnecessary cookies

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

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

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

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

CLOUDSTACK-7809: UI  remove unnecessary cookie 'capabilities', 'supportELB', 
'kvmsnapshotenabled', 'regionsecondaryenabled', 'userpublictemplateenabled', 
'userProjectsEnabled'.


 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Resolved] (CLOUDSTACK-7809) UI remove unnecessary cookies

2014-10-28 Thread Jessica Wang (JIRA)

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

Jessica Wang resolved CLOUDSTACK-7809.
--
Resolution: Fixed

 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Closed] (CLOUDSTACK-7809) UI remove unnecessary cookies

2014-10-28 Thread Jessica Wang (JIRA)

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

Jessica Wang closed CLOUDSTACK-7809.


 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Commented] (CLOUDSTACK-7809) UI remove unnecessary cookies

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

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

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

Commit 492962520ec0fdf018b18e195efe7478133a3dab in cloudstack's branch 
refs/heads/4.5 from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4929625 ]

CLOUDSTACK-7809: UI  remove unnecessary cookie 'networktype'.


 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Commented] (CLOUDSTACK-7809) UI remove unnecessary cookies

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

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

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

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

CLOUDSTACK-7809: UI  remove unnecessary cookie 'networktype'.


 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Created] (CLOUDSTACK-7814) No default SSL keystore result in upgrade failure

2014-10-28 Thread Sheng Yang (JIRA)
Sheng Yang created CLOUDSTACK-7814:
--

 Summary: No default SSL keystore result in upgrade failure
 Key: CLOUDSTACK-7814
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7814
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.5.0
Reporter: Sheng Yang
Assignee: Sheng Yang
Priority: Blocker
 Fix For: 4.5.0


Currently, after upgrade to 4.5, no agent can connect to mgmt server.

It's due to:

commit 918c320438980f070150f872e3a3ba907572af83
Author: Upendra Moturi upendra.mot...@sungard.com
Date: Fri Jun 20 11:41:58 2014 +0530
CLOUDSTACK-6847.Link.java and console proxy files have hardcoded value

This commit meant to use more flex password for keystore, but they didn't set 
default value for it. So when upgrade, db.properities which suppose have the 
password is empty, the decryption of SSL keystore would fail.



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


[jira] [Commented] (CLOUDSTACK-7814) No default SSL keystore result in upgrade failure

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

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

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

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

CLOUDSTACK-7814: Fix default passphrase for keystores

In upgrade case, the db.properties file is not changed, but the following commit
would require passphrase for keystore in it, thus result in error(NPE in fact
due to there is no such properity).

commit 918c320438980f070150f872e3a3ba907572af83
Author: Upendra Moturi upendra.mot...@sungard.com
Date: Fri Jun 20 11:41:58 2014 +0530
CLOUDSTACK-6847.Link.java and console proxy files have hardcoded value

This commit fix it by put default value for passphrases, also set correct
passphrase if fail-safe keystore is used.


 No default SSL keystore result in upgrade failure
 -

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


 Currently, after upgrade to 4.5, no agent can connect to mgmt server.
 It's due to:
 commit 918c320438980f070150f872e3a3ba907572af83
 Author: Upendra Moturi upendra.mot...@sungard.com
 Date: Fri Jun 20 11:41:58 2014 +0530
 CLOUDSTACK-6847.Link.java and console proxy files have hardcoded value
 This commit meant to use more flex password for keystore, but they didn't set 
 default value for it. So when upgrade, db.properities which suppose have the 
 password is empty, the decryption of SSL keystore would fail.



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


[jira] [Resolved] (CLOUDSTACK-7814) No default SSL keystore result in upgrade failure

2014-10-28 Thread Sheng Yang (JIRA)

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

Sheng Yang resolved CLOUDSTACK-7814.

Resolution: Fixed

 No default SSL keystore result in upgrade failure
 -

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


 Currently, after upgrade to 4.5, no agent can connect to mgmt server.
 It's due to:
 commit 918c320438980f070150f872e3a3ba907572af83
 Author: Upendra Moturi upendra.mot...@sungard.com
 Date: Fri Jun 20 11:41:58 2014 +0530
 CLOUDSTACK-6847.Link.java and console proxy files have hardcoded value
 This commit meant to use more flex password for keystore, but they didn't set 
 default value for it. So when upgrade, db.properities which suppose have the 
 password is empty, the decryption of SSL keystore would fail.



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


[jira] [Commented] (CLOUDSTACK-7814) No default SSL keystore result in upgrade failure

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

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

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

Commit 865b2e6791a37371fff4c43c974c90f44d24c418 in cloudstack's branch 
refs/heads/4.5 from [~yasker]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=865b2e6 ]

CLOUDSTACK-7814: Fix default passphrase for keystores

In upgrade case, the db.properties file is not changed, but the following commit
would require passphrase for keystore in it, thus result in error(NPE in fact
due to there is no such properity).

commit 918c320438980f070150f872e3a3ba907572af83
Author: Upendra Moturi upendra.mot...@sungard.com
Date: Fri Jun 20 11:41:58 2014 +0530
CLOUDSTACK-6847.Link.java and console proxy files have hardcoded value

This commit fix it by put default value for passphrases, also set correct
passphrase if fail-safe keystore is used.


 No default SSL keystore result in upgrade failure
 -

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


 Currently, after upgrade to 4.5, no agent can connect to mgmt server.
 It's due to:
 commit 918c320438980f070150f872e3a3ba907572af83
 Author: Upendra Moturi upendra.mot...@sungard.com
 Date: Fri Jun 20 11:41:58 2014 +0530
 CLOUDSTACK-6847.Link.java and console proxy files have hardcoded value
 This commit meant to use more flex password for keystore, but they didn't set 
 default value for it. So when upgrade, db.properities which suppose have the 
 password is empty, the decryption of SSL keystore would fail.



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


[jira] [Commented] (CLOUDSTACK-7809) UI remove unnecessary cookies

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

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

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

Commit 0d6a277a0051c191cc34645a0a70bf8e3515865e in cloudstack's branch 
refs/heads/4.5 from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0d6a277 ]

CLOUDSTACK-7809: UI  remove unnecessary cookie 'timezoneoffset'.


 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Commented] (CLOUDSTACK-7809) UI remove unnecessary cookies

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

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

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

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

CLOUDSTACK-7809: UI  remove unnecessary cookie 'timezoneoffset'.


 UI  remove unnecessary cookies
 ---

 Key: CLOUDSTACK-7809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
 Fix For: 4.5.0






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


[jira] [Updated] (CLOUDSTACK-7659) UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the additional-methods included.

2014-10-28 Thread Gabor Apati-Nagy (JIRA)

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

Gabor Apati-Nagy updated CLOUDSTACK-7659:
-
Description: 
Upgrade jquery-validate lib to the latest 1.13.0 version with the 
additional-methods included.
Update the LICENSE file.

  was:
Upgrade jquery-validate lib to the latest 1.13.0 version with the 
additional-methods included.
Update the LICESE file.


 UI: Upgrade jquery-validate lib to the latest 1.13.0 version with the 
 additional-methods included.
 --

 Key: CLOUDSTACK-7659
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7659
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy

 Upgrade jquery-validate lib to the latest 1.13.0 version with the 
 additional-methods included.
 Update the LICENSE file.



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


[jira] [Commented] (CLOUDSTACK-7720) No IP Address Validation for Acquire new secondary IP

2014-10-28 Thread Jayapal Reddy (JIRA)

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

Jayapal Reddy commented on CLOUDSTACK-7720:
---

Hi,

The ip address filed is optional field. 
If user doesn't enter the ip it picks the ip from the guest network free pool.
If ip is entered then cloudstack validates for wether the ip is in  guest 
network or not and takes it.

It seems you made it required filed but it is optional field.
It is ip entered then only validate for ipv4.

Thanks,
Jayapal

 No IP Address Validation for Acquire new secondary IP
 -

 Key: CLOUDSTACK-7720
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7720
 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: Gabor Apati-Nagy
Assignee: Gabor Apati-Nagy
Priority: Minor
 Fix For: 4.5.0


 Steps:
 1. Go to Instances -- NICs tab.
 2. Click on the View Secondary IPs
 3. Click on Acquire new secondary IP
 There is No IP address validation for Acquire new secondary IP. 
 Additionally, this field should be a required field. Clicking Ok generates 
 an IP, but it can be confusing to the end user.



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