[jira] [Updated] (CLOUDSTACK-6637) IAM : Integration test cases

2014-05-12 Thread Meghna Kale (JIRA)

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

Meghna Kale updated CLOUDSTACK-6637:


Issue Type: Task  (was: Test)

> IAM : Integration test cases
> 
>
> Key: CLOUDSTACK-6637
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6637
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: IAM
>Reporter: Meghna Kale
>Priority: Minor
>
> Integration test cases for IAM module.



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


[jira] [Created] (CLOUDSTACK-6651) Include resource UUId in usage events

2014-05-12 Thread Kishan Kavala (JIRA)
Kishan Kavala created CLOUDSTACK-6651:
-

 Summary: Include resource UUId in usage events
 Key: CLOUDSTACK-6651
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6651
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Kishan Kavala


While listing usage records, uuid is fetched from cloud db using resource_ids 
in cloud_usage DBs. Related code is in APIResponseHelper createusage response.
This takes takes time and sometimes results in NPEs.
Relevant uuids should be included in usage events to avoid this.



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


[jira] [Resolved] (CLOUDSTACK-6648) [Automation]: vm ha cases were failing in 4.4-forward

2014-05-12 Thread Santhosh Kumar Edukulla (JIRA)

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

Santhosh Kumar Edukulla resolved CLOUDSTACK-6648.
-

Resolution: Fixed

Issue is now fixed and pushed to 4.4-forward

> [Automation]: vm ha cases were failing in 4.4-forward
> -
>
> Key: CLOUDSTACK-6648
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6648
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Affects Versions: 4.4.0
>Reporter: Santhosh Kumar Edukulla
>Assignee: Santhosh Kumar Edukulla
>
> vm_ha.py cases were failing because of proper zone was not getting picked up. 
> Fixed them now, moved the test data out of test cases to get proper test data.



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


[jira] [Updated] (CLOUDSTACK-6550) [Automation] list**** API return empty list if you are not passing listall=true, many testcases failed due to this

2014-05-12 Thread Abhinandan Prateek (JIRA)

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

Abhinandan Prateek updated CLOUDSTACK-6550:
---

Assignee: Santhosh Kumar Edukulla  (was: Girish Shilamkar)

> [Automation] list API return empty list if you are not passing 
> listall=true, many testcases failed due to this
> --
>
> Key: CLOUDSTACK-6550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6550
> Project: CloudStack
>  Issue Type: Test
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, Virtual Router
>Affects Versions: 4.4.0
> Environment: Xen 6.2
> build : 4.4-forward 
>Reporter: Rayees Namathponnan
>Assignee: Santhosh Kumar Edukulla
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Currently test cases are using below command to listrouter (without 
> listall=true),  
> passing accountID and domain ID
>  
> http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0&domainid=22feae40-d076-11e3-8dca-0608081f&command=listRouters
>  
> this API call return empty list in 4.4,  



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


[jira] [Updated] (CLOUDSTACK-6562) [Automation] [XenServer] Secondary Storage count for account shows double the value of the desired count

2014-05-12 Thread Abhinandan Prateek (JIRA)

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

Abhinandan Prateek updated CLOUDSTACK-6562:
---

Assignee: Santhosh Kumar Edukulla  (was: Harikrishna Patnala)

> [Automation] [XenServer] Secondary Storage count for account shows double the 
> value of the desired count
> 
>
> Key: CLOUDSTACK-6562
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6562
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation, Storage Controller, Template
>Affects Versions: 4.4.0
> Environment: XenServer
> No problem on KVM and VMware
>Reporter: Ashutosk Kelkar
>Assignee: Santhosh Kumar Edukulla
>  Labels: automation
> Fix For: 4.4.0
>
>
> Create an account.
> Register a template and download it.
> if the template size is "X", then the secondarystoragetotal for the account 
> shows it as "2X". Desired value is X.



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


[jira] [Commented] (CLOUDSTACK-6519) [Hyper-V] while adding VM to Network it should throw error when it is in running state

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit 260e06d64c07c6e5f3c133d8bdc2779fad62c672 in cloudstack's branch 
refs/heads/4.4-forward from [~rajesh_battala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=260e06d ]

CLOUDSTACK-6519 [Hyper-V] while adding VM to Network it should throw error when 
it is in running state


> [Hyper-V] while adding VM to Network it should throw error when it is in 
> running state
> --
>
> Key: CLOUDSTACK-6519
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6519
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Rajesh Battala
>Assignee: Rajesh Battala
>Priority: Critical
> Fix For: 4.4.0
>
>




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


[jira] [Updated] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error "Can only support create Private VLAN network with IPv4!"

2014-05-12 Thread Abhinandan Prateek (JIRA)

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

Abhinandan Prateek updated CLOUDSTACK-6627:
---

Assignee: Santhosh Kumar Edukulla

> [Automation] createNetwork API failing with error "Can only support create 
> Private VLAN network with IPv4!"
> ---
>
> Key: CLOUDSTACK-6627
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6627
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.4.0
> Environment: KVM and vmware
> build 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Santhosh Kumar Edukulla
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> integration.smoke.test_pvlan.TestPVLAN.test_create_pvlan_network  failing 
> latest run 
> 2014-05-09 14:37:36,948 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-11:ctx-80f69f30) ===START===  10.223.240.194 -- GET  
> apiKey=PqBwvR5XGUP5UMkcchdzGW9QtWAexG7mh
> 0JjGFlcpg7Vf6Xazb9RhhL4j7RAY-bGWpqt_IjM2W3Oy0ukiFF_3Q&startipv6=fc00%3A1234%3A%3A10&zoneid=8ec43c1f-ee32-4b1e-90d2-fce40313aafc&isolatedpvlan=567&displaytext
> =pvlan+network&ip6gateway=fc00%3A1234%3A%3A1&gateway=10.10.10.20&endipv6=fc00%3A1234%3A%3A20&networkofferingid=7&vlan=1234&netmask=255.255.255.0&response=jso
> n&name=pvlan+network&startip=10.10.10.10&ip6cidr=fc00%3A1234%3A%3A%2F64&command=createNetwork&signature=mHKCVFL1AM4NkVrEr%2FiW%2FdIj2NE%3D
> API failing with error "Can only support create Private VLAN network with 
> IPv4!"
> 2014-05-09 14:37:36,971 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) IAM access check 
> for 2-null-nu
> ll-SystemCapability from cache: false
> 2014-05-09 14:37:36,971 DEBUG [c.c.u.AccountManagerImpl] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Root Access granted 
> to Acct[e853580a-d7ae-
> 11e3-a7c8-1a6f7bb0d0a8-admin] by AffinityGroupAccessChecker
> 2014-05-09 14:37:37,011 INFO  [c.c.a.ApiServer] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Can only support 
> create Private VLAN network with IPv4!
> 2014



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


[jira] [Commented] (CLOUDSTACK-5501) Unable to create more than one vpnConnection per vpn customer gateway

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-5501: Allow one vpn customer gateway with multiple connections

This restriction was purposely avoid confusion of VPN setup, but later found too
strictly and cause troubles for deployment. Removed after testing one customer
gateway with multiple connections.


> Unable to create more than one vpnConnection per vpn customer gateway
> -
>
> Key: CLOUDSTACK-5501
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5501
> 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
>Reporter: Alena Prokharchyk
>Assignee: Sheng Yang
>Priority: Critical
> Fix For: 4.4.0
>
>
> There is currently a limitation in the CS code when you can't create more 
> than one vpn connection per customer gateway. There are no technical reasons 
> for this kind of limitation, so we should remove it as the customers might 
> want to use his customer gateway cross zones if he owns VPCs in diff zones.



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


[jira] [Commented] (CLOUDSTACK-5943) [doc] Palo Alto Firewall

2014-05-12 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-5943:


GitHub user swill opened a pull request:

https://github.com/apache/cloudstack-docs-admin/pull/9

CLOUDSTACK-5943: added doc for the Palo Alto Networks firewall integration

I have added documentation for the Palo Alto Networks firewall integration. 
 This change should also be cherry picked back into the 4.3 branch.

I have created it in its own file and included it in the networking2.rst 
file.  

I have tested the build and the menu system and doc is building as expected.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudops/cloudstack-docs-admin master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack-docs-admin/pull/9.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #9


commit 4b49450452939d72ca0e628e4f6dbc468d5608e0
Author: Will Stevens 
Date:   2014-05-12T16:56:36Z

CLOUDSTACK-5943: added doc for the Palo Alto Networks firewall integration




> [doc] Palo Alto Firewall
> 
>
> Key: CLOUDSTACK-5943
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5943
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.3.0
>Reporter: Radhika Nair
> Fix For: 4.3.0
>
>




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


[jira] [Commented] (CLOUDSTACK-6607) Create VPC is failing.

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6607: Correct the result of VpcNetworkUsage

Blank or not shouldn't be used to indicate command is failure or not.


> Create VPC is failing.
> --
>
> Key: CLOUDSTACK-6607
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6607
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.4.0
>Reporter: manasaveloori
>Assignee: Sheng Yang
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> Deploy CS using Xenserver 6.2.
> Create a VPC.
> Observed that VPC creation is failing  with below exception:
> 2014-05-08 04:29:48,225 WARN  [c.c.h.x.r.XenServer56Resource] 
> (DirectAgent-95:ctx-70fed5e6) Failed to get network usage stats due to
> java.lang.Exception:  vpc network usage plugin call failed
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.VPCNetworkUsage(XenServer56Resource.java:183)
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.execute(XenServer56Resource.java:194)
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:58)
> at 
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93)
> at 
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.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)
> 2014-05-08 04:29:48,229 DEBUG [c.c.a.m.DirectAgentAttache] 
> (DirectAgent-95:ctx-70fed5e6) Seq 1-126100789566377982: Response Received:
> 2014-05-08 04:29:48,231 DEBUG [c.c.a.t.Request] (DirectAgent-95:ctx-70fed5e6) 
> Seq 1-126100789566377982: Processing:  { Ans: , MgmtId: 7672522866886, via: 
> 1, Ver: v1, Flags: 110, 
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":10,"name":"r-10-VM","bootloader":"PyGrub","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian
>  GNU/Linux 7(32-bit)","bootArgs":" vpccidr=10.0.0.0/16 
> domain=cs2cloud.internal dns1=10.140.50.6 template=domP name=r-10-VM 
> eth0ip=169.254.1.131 eth0mask=255.255.0.0 type=vpcrouter 
> disable_rp_filter=true","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"91408a0b18abbc99","params":{},"uuid":"6e38c35d-7c5d-4982-bddf-f21b7063e1db","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"c8cf4a4d-e552-4b82-943e-af3df990a445","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"c040ab5c-6f99-3d0b-9377-dcf76c5798de","id":1,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/manasa/primaryxen","port":2049,"url":"NetworkFilesystem://10.147.28.7/export/home/manasa/primaryxen/?ROLE=Primary&STOREUUID=c040ab5c-6f99-3d0b-9377-dcf76c5798de"}},"name":"ROOT-10","size":262144,"path":"e6ed1394-ee6b-44d5-8599-688e5efe30a7","volumeId":11,"vmName":"r-10-VM","accountId":2,"format":"VHD","id":11,"deviceId":0,"hypervisorType":"XenServer"}},"diskSeq":0,"path":"e6ed1394-ee6b-44d5-8599-688e5efe30

[jira] [Resolved] (CLOUDSTACK-6607) Create VPC is failing.

2014-05-12 Thread Sheng Yang (JIRA)

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

Sheng Yang resolved CLOUDSTACK-6607.


Resolution: Fixed

> Create VPC is failing.
> --
>
> Key: CLOUDSTACK-6607
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6607
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.4.0
>Reporter: manasaveloori
>Assignee: Sheng Yang
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> Deploy CS using Xenserver 6.2.
> Create a VPC.
> Observed that VPC creation is failing  with below exception:
> 2014-05-08 04:29:48,225 WARN  [c.c.h.x.r.XenServer56Resource] 
> (DirectAgent-95:ctx-70fed5e6) Failed to get network usage stats due to
> java.lang.Exception:  vpc network usage plugin call failed
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.VPCNetworkUsage(XenServer56Resource.java:183)
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.execute(XenServer56Resource.java:194)
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:58)
> at 
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93)
> at 
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.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)
> 2014-05-08 04:29:48,229 DEBUG [c.c.a.m.DirectAgentAttache] 
> (DirectAgent-95:ctx-70fed5e6) Seq 1-126100789566377982: Response Received:
> 2014-05-08 04:29:48,231 DEBUG [c.c.a.t.Request] (DirectAgent-95:ctx-70fed5e6) 
> Seq 1-126100789566377982: Processing:  { Ans: , MgmtId: 7672522866886, via: 
> 1, Ver: v1, Flags: 110, 
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":10,"name":"r-10-VM","bootloader":"PyGrub","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian
>  GNU/Linux 7(32-bit)","bootArgs":" vpccidr=10.0.0.0/16 
> domain=cs2cloud.internal dns1=10.140.50.6 template=domP name=r-10-VM 
> eth0ip=169.254.1.131 eth0mask=255.255.0.0 type=vpcrouter 
> disable_rp_filter=true","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"91408a0b18abbc99","params":{},"uuid":"6e38c35d-7c5d-4982-bddf-f21b7063e1db","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"c8cf4a4d-e552-4b82-943e-af3df990a445","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"c040ab5c-6f99-3d0b-9377-dcf76c5798de","id":1,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/manasa/primaryxen","port":2049,"url":"NetworkFilesystem://10.147.28.7/export/home/manasa/primaryxen/?ROLE=Primary&STOREUUID=c040ab5c-6f99-3d0b-9377-dcf76c5798de"}},"name":"ROOT-10","size":262144,"path":"e6ed1394-ee6b-44d5-8599-688e5efe30a7","volumeId":11,"vmName":"r-10-VM","accountId":2,"format":"VHD","id":11,"deviceId":0,"hypervisorType":"XenServer"}},"diskSeq":0,"path":"e6ed1394-ee6b-44d5-8599-688e5efe30a7","type":"ROOT","_details":{"managed":"false","storagePort":"2049","storageHost":"10.147.28.7","volumeSize":"262144"}}],"nics":[{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"55d14c0b-b7ff-4698-9387-ec3e16034d36","ip":"169.254.1.131","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:01:83","broadcastType":"LinkLocal","type":"Control","isSe

[jira] [Commented] (CLOUDSTACK-6647) Appending instance name with custom supplied info that contains - character can break vmsync

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6647: appending instance name with custom supplied info that 
contains - character can break vmsync.


> Appending instance name with custom supplied info that contains - character 
> can break vmsync
> 
>
> Key: CLOUDSTACK-6647
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6647
> 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: Kelven Yang
>Assignee: Kelven Yang
>Priority: Critical
>




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


[jira] [Commented] (CLOUDSTACK-6647) Appending instance name with custom supplied info that contains - character can break vmsync

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6647: appending instance name with custom supplied info that 
contains - character can break vmsync.


> Appending instance name with custom supplied info that contains - character 
> can break vmsync
> 
>
> Key: CLOUDSTACK-6647
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6647
> 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: Kelven Yang
>Assignee: Kelven Yang
>Priority: Critical
>




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


[jira] [Assigned] (CLOUDSTACK-6607) Create VPC is failing.

2014-05-12 Thread Sheng Yang (JIRA)

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

Sheng Yang reassigned CLOUDSTACK-6607:
--

Assignee: Sheng Yang  (was: Anthony Xu)

> Create VPC is failing.
> --
>
> Key: CLOUDSTACK-6607
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6607
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.4.0
>Reporter: manasaveloori
>Assignee: Sheng Yang
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> Deploy CS using Xenserver 6.2.
> Create a VPC.
> Observed that VPC creation is failing  with below exception:
> 2014-05-08 04:29:48,225 WARN  [c.c.h.x.r.XenServer56Resource] 
> (DirectAgent-95:ctx-70fed5e6) Failed to get network usage stats due to
> java.lang.Exception:  vpc network usage plugin call failed
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.VPCNetworkUsage(XenServer56Resource.java:183)
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.execute(XenServer56Resource.java:194)
> at 
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:58)
> at 
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93)
> at 
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.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)
> 2014-05-08 04:29:48,229 DEBUG [c.c.a.m.DirectAgentAttache] 
> (DirectAgent-95:ctx-70fed5e6) Seq 1-126100789566377982: Response Received:
> 2014-05-08 04:29:48,231 DEBUG [c.c.a.t.Request] (DirectAgent-95:ctx-70fed5e6) 
> Seq 1-126100789566377982: Processing:  { Ans: , MgmtId: 7672522866886, via: 
> 1, Ver: v1, Flags: 110, 
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":10,"name":"r-10-VM","bootloader":"PyGrub","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian
>  GNU/Linux 7(32-bit)","bootArgs":" vpccidr=10.0.0.0/16 
> domain=cs2cloud.internal dns1=10.140.50.6 template=domP name=r-10-VM 
> eth0ip=169.254.1.131 eth0mask=255.255.0.0 type=vpcrouter 
> disable_rp_filter=true","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"91408a0b18abbc99","params":{},"uuid":"6e38c35d-7c5d-4982-bddf-f21b7063e1db","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"c8cf4a4d-e552-4b82-943e-af3df990a445","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"c040ab5c-6f99-3d0b-9377-dcf76c5798de","id":1,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/manasa/primaryxen","port":2049,"url":"NetworkFilesystem://10.147.28.7/export/home/manasa/primaryxen/?ROLE=Primary&STOREUUID=c040ab5c-6f99-3d0b-9377-dcf76c5798de"}},"name":"ROOT-10","size":262144,"path":"e6ed1394-ee6b-44d5-8599-688e5efe30a7","volumeId":11,"vmName":"r-10-VM","accountId":2,"format":"VHD","id":11,"deviceId":0,"hypervisorType":"XenServer"}},"diskSeq":0,"path":"e6ed1394-ee6b-44d5-8599-688e5efe30a7","type":"ROOT","_details":{"managed":"false","storagePort":"2049","storageHost":"10.147.28.7","volumeSize":"262144"}}],"nics":[{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"55d14c0b-b7ff-4698-9387-ec3e16034d36","ip":"169.254.1.131","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:01:83","broadcastType":"LinkLoc

[jira] [Resolved] (CLOUDSTACK-5501) Unable to create more than one vpnConnection per vpn customer gateway

2014-05-12 Thread Sheng Yang (JIRA)

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

Sheng Yang resolved CLOUDSTACK-5501.


Resolution: Fixed

> Unable to create more than one vpnConnection per vpn customer gateway
> -
>
> Key: CLOUDSTACK-5501
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5501
> 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
>Reporter: Alena Prokharchyk
>Assignee: Sheng Yang
>Priority: Critical
> Fix For: 4.4.0
>
>
> There is currently a limitation in the CS code when you can't create more 
> than one vpn connection per customer gateway. There are no technical reasons 
> for this kind of limitation, so we should remove it as the customers might 
> want to use his customer gateway cross zones if he owns VPCs in diff zones.



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


[jira] [Created] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error "Can only support create Private VLAN network with IPv4!"

2014-05-12 Thread Rayees Namathponnan (JIRA)
Rayees Namathponnan created CLOUDSTACK-6627:
---

 Summary: [Automation] createNetwork API failing with error "Can 
only support create Private VLAN network with IPv4!"
 Key: CLOUDSTACK-6627
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6627
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Controller
Affects Versions: 4.4.0
 Environment: KVM and vmware
build 4.4-forward
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.4.0
 Attachments: management-server.rar

integration.smoke.test_pvlan.TestPVLAN.test_create_pvlan_network  failing 
latest run 

2014-05-09 14:37:36,948 DEBUG [c.c.a.ApiServlet] 
(catalina-exec-11:ctx-80f69f30) ===START===  10.223.240.194 -- GET  
apiKey=PqBwvR5XGUP5UMkcchdzGW9QtWAexG7mh
0JjGFlcpg7Vf6Xazb9RhhL4j7RAY-bGWpqt_IjM2W3Oy0ukiFF_3Q&startipv6=fc00%3A1234%3A%3A10&zoneid=8ec43c1f-ee32-4b1e-90d2-fce40313aafc&isolatedpvlan=567&displaytext
=pvlan+network&ip6gateway=fc00%3A1234%3A%3A1&gateway=10.10.10.20&endipv6=fc00%3A1234%3A%3A20&networkofferingid=7&vlan=1234&netmask=255.255.255.0&response=jso
n&name=pvlan+network&startip=10.10.10.10&ip6cidr=fc00%3A1234%3A%3A%2F64&command=createNetwork&signature=mHKCVFL1AM4NkVrEr%2FiW%2FdIj2NE%3D


API failing with error "Can only support create Private VLAN network with IPv4!"


2014-05-09 14:37:36,971 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
(catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) IAM access check for 
2-null-nu
ll-SystemCapability from cache: false
2014-05-09 14:37:36,971 DEBUG [c.c.u.AccountManagerImpl] 
(catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Root Access granted 
to Acct[e853580a-d7ae-
11e3-a7c8-1a6f7bb0d0a8-admin] by AffinityGroupAccessChecker
2014-05-09 14:37:37,011 INFO  [c.c.a.ApiServer] (catalina-exec-11:ctx-80f69f30 
ctx-39ae4a70 ctx-13ff8562) Can only support create Private VLAN network with 
IPv4!
2014



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


[jira] [Resolved] (CLOUDSTACK-6614) systemvm template build failed since src iso link is broken

2014-05-12 Thread Yoshikazu Nojima (JIRA)

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

Yoshikazu Nojima resolved CLOUDSTACK-6614.
--

   Resolution: Fixed
Fix Version/s: 4.4.0
   Future

> systemvm template build failed since src iso link is broken
> ---
>
> Key: CLOUDSTACK-6614
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6614
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: Future, 4.4.0
>Reporter: Yoshikazu Nojima
>  Labels: systemvm
> Fix For: Future, 4.4.0
>
>
> at least master is affected.
> build log:
> ==
> We did not find an isofile here : 
> /var/lib/jenkins/workspace/cloudstack-master-systemvm64/tools/appliance/iso/debian-7.4.0-amd64-netinst.iso.
>  
> The definition provided the following download information:
> - Download url: 
> http://ftp.acc.umu.se/mirror/cdimage/release/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso
> - Md5 Checksum: e7e9433973f082a297793c3c5010b2c5
> Checking if isofile debian-7.4.0-amd64-netinst.iso already exists.
> Full path: 
> /var/lib/jenkins/workspace/cloudstack-master-systemvm64/tools/appliance/iso/debian-7.4.0-amd64-netinst.iso
> There was an error downloading 
> http://ftp.acc.umu.se/mirror/cdimage/release/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso:
> 404 Not Found
> There was an error downloading 
> http://ftp.acc.umu.se/mirror/cdimage/release/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso:
> 404 Not Found



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


[jira] [Resolved] (CLOUDSTACK-6617) [Automation] detach / resize volume test cases failing with permission error

2014-05-12 Thread Min Chen (JIRA)

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

Min Chen resolved CLOUDSTACK-6617.
--

Resolution: Fixed

> [Automation] detach / resize volume test cases failing  with permission error 
> --
>
> Key: CLOUDSTACK-6617
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6617
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes, Xen
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Assignee: Min Chen
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> This issue is observed in 4.4-forward automation in Xen, test case 
> integration.smoke.test_volumes.TestVolumes.test_06_download_detached_volume 
> failing with permission error 
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 
> Execute cmd: attachvolume failed, due to: errorCode: 531, 
> errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources
>  >> begin captured stdout << -
> === TestName: test_06_download_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
>  >> begin captured logging << 
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: STARTED : 
> TC: test_06_download_detached_volume :::
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Extract detached Volume 
> ID: 885ac921-4728-4903-9621-b07c5353e9bc
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Payload: {'apiKey': 
> u'WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ',
>  'virtualmachineid': u'2e1ef913-b207-4688-bbaa-408797810d3a', 'id': 
> u'885ac921-4728-4903-9621-b07c5353e9bc', 'command': 'attachVolume', 
> 'signature': 'hnLR1wCmFp5EtwMZRaS1e3J75S8=', 'response': 'json'}
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Sending GET Cmd 
> : attachVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
> (1): 10.220.76.63
> requests.packages.urllib3.connectionpool: DEBUG: "GET 
> /client/api?apiKey=WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ&virtualmachineid=2e1ef913-b207-4688-bbaa-408797810d3a&id=885ac921-4728-4903-9621-b07c5353e9bc&command=attachVolume&signature=hnLR1wCmFp5EtwMZRaS1e3J75S8%3D&response=json
>  HTTP/1.1" 531 212
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): ERROR: Exception:['Traceback 
> (most recent call last):\n', '  File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>  line 313, in __parseAndGetResponse\nresponse_cls)\n', '  File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py",
>  line 151, in getResultObj\nraise 
> cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
> 'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode: 
> 531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources\n']
> Traceback (most recent call last):
>   File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>  line 313, in __parseAndGetResponse
> response_cls)
>   File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py",
>  line 151, in getResultObj
> raise cloudstackException.CloudstackAPIException(respname, errMsg)
> CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode: 
> 531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): ERROR: marvinRequest : CmdName: 
>  
> Exception: ['Traceback (most recent call last):\n', '  File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>  line 380, in marvinRequest\nraise self.__lastError\n', 
> 'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode: 
> 531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on 

[jira] [Created] (CLOUDSTACK-6603) [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to 4.4

2014-05-12 Thread manasaveloori (JIRA)
manasaveloori created CLOUDSTACK-6603:
-

 Summary: [Upgrade]DB Exception while Autoscale monitoring after 
upgrading from 4.3 to 4.4
 Key: CLOUDSTACK-6603
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6603
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Upgrade
Affects Versions: 4.4.0
Reporter: manasaveloori
Priority: Blocker
 Fix For: 4.4.0


1. Deploy CS 4.3 with 2 zones using xen 6.1 and KVM hypervisor.
2. Configured LB rules,firewall rules.
3. Registered the template for 4.4 (using the naming convention 
systemvm-xenserver-4.4,systemvm-kvm-4.4)
4. Upgraded to 4.4

Start the management server:

Below are the observations:

2014-05-05 05:05:13,567 DEBUG [c.c.s.StatsCollector] 
(StatsCollector-4:ctx-e36f20e1) AutoScaling Monitor is running...
2014-05-05 05:05:13,577 ERROR [c.c.s.StatsCollector] 
(StatsCollector-4:ctx-e36f20e1) Error trying to monitor autoscaling
com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
com.mysql.jdbc.JDBC4PreparedStatement@5b140551: SELECT autoscale_vmgroups.id, 
autoscale_vmgroups.uuid, autoscale_vmgroups.zone_id, 
autoscale_vmgroups.domain_id, autoscale_vmgroups.account_id, 
autoscale_vmgroups.load_balancer_id, autoscale_vmgroups.min_members, 
autoscale_vmgroups.max_members, autoscale_vmgroups.member_port, 
autoscale_vmgroups.interval, autoscale_vmgroups.last_interval, 
autoscale_vmgroups.profile_id, autoscale_vmgroups.removed, 
autoscale_vmgroups.created, autoscale_vmgroups.state, 
autoscale_vmgroups.display FROM autoscale_vmgroups WHERE 
autoscale_vmgroups.removed IS NULL
at com.cloud.utils.db.GenericDaoBase.executeList(GenericDaoBase.java:1127)
at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1150)
at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at 
com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy220.listAll(Unknown Source)
at 
com.cloud.server.StatsCollector$AutoScaleMonitor.runInContext(StatsCollector.java:673)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
column 'autoscale_vmgroups.last_interval' in 'field list'
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:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:38

[jira] [Resolved] (CLOUDSTACK-6647) Appending instance name with custom supplied info that contains - character can break vmsync

2014-05-12 Thread Kelven Yang (JIRA)

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

Kelven Yang resolved CLOUDSTACK-6647.
-

Resolution: Fixed

> Appending instance name with custom supplied info that contains - character 
> can break vmsync
> 
>
> Key: CLOUDSTACK-6647
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6647
> 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: Kelven Yang
>Assignee: Kelven Yang
>Priority: Critical
>




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


[jira] [Commented] (CLOUDSTACK-6608) OVS distributed firewall: default ACL rule is not getting applied when a tier in VPC is created.

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit 0ba00ec24dab00702b09ad9c3cdb407b68b8901f in cloudstack's branch 
refs/heads/4.4 from [~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0ba00ec ]

CLOUDSTACK-6608:OVS distributed firewall: default ACL rule is not
getting applied when a tier in VPC is created.

fix ensures, VpcRoutingPolicyUpdate is send when network rules are
programmed when network tier in VPC is created


> OVS distributed firewall: default ACL rule is not getting applied when a tier 
> in VPC is created.
> 
>
> Key: CLOUDSTACK-6608
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6608
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Murali Reddy
>Assignee: Murali Reddy
> Fix For: 4.4.0
>
>
> OVS distributed firewall: default ACL rule is not getting applied when a tier 
> in VPC is created. Current logic in OVS tunnel manager is updating ACL table 
> on the host only when ACL is replace, but not for the default ACL that gets 
> applied when network is created.
> Fix should ensure OvsVpcRoutingPolicyConfigCommand update is send to the 
> hosts on which VPC spans when tier is created.



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


[jira] [Created] (CLOUDSTACK-6647) Appending instance name with custom supplied info that contains - character can break vmsync

2014-05-12 Thread Kelven Yang (JIRA)
Kelven Yang created CLOUDSTACK-6647:
---

 Summary: Appending instance name with custom supplied info that 
contains - character can break vmsync
 Key: CLOUDSTACK-6647
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6647
 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: Kelven Yang
Assignee: Kelven Yang
Priority: Critical






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


[jira] [Created] (CLOUDSTACK-6644) Unable to attach Volume to a VM as a System User

2014-05-12 Thread Chandan Purushothama (JIRA)
Chandan Purushothama created CLOUDSTACK-6644:


 Summary: Unable to attach Volume to a VM as a System User
 Key: CLOUDSTACK-6644
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6644
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: IAM
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Priority: Critical
 Fix For: 4.4.0


As System User, tried to attach a Volume belonging to an account to a VM 
belonging to the same account. Failed with the following error.

"Acct[4f0e5b12-d6d8-11e3-952f-06098c000757-system] does not have permission to 
perform this operation on these resources"

mysql> select account_id, uuid from vm_instance where uuid like '%56a4%';
++--+
| account_id | uuid |
++--+
|  3 | 56a488ce-9baf-4d99-8e25-002d565f6731 |
++--+
1 row in set (0.00 sec)

mysql> select account_id, uuid from volumes where uuid like '%00585b50%';
++--+
| account_id | uuid |
++--+
|  3 | 00585b50-8c65-4e5b-95ee-853489e5499c |
++--+
1 row in set (0.00 sec)

2014-05-12 13:40:48,618 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) submit async job-190, 
details: AsyncJobVO {id:190, userId: 1, accountId: 1, instanceType: Volume, 
instanceId: 11, cmd: 
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin, cmdInfo: 
{"virtualmachineid":"56a488ce-9baf-4d99-8e25-002d565f6731","cmdEventType":"VOLUME.ATTACH","ctxUserId":"1","httpmethod":"GET","deviceid":"1","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","id":"00585b50-8c65-4e5b-95ee-853489e5499c","response":"json","ctxDetails":"{\"com.cloud.storage.Volume\":11,\"Volume\":\"00585b50-8c65-4e5b-95ee-853489e5499c\",\"com.cloud.vm.VirtualMachine\":8}","ctxAccountId":"1","uuid":"00585b50-8c65-4e5b-95ee-853489e5499c","ctxStartEventId":"448","signature":"euszCT397/kGpCM1fN+GQhTJCe8\u003d"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-05-12 13:40:48,619 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-c551e67e 
ctx-2b2b4ddd ctx-4beab6a0) ===END===  127.0.0.1 -- GET  
apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=attachVolume&deviceid=1&id=00585b50-8c65-4e5b-95ee-853489e5499c&response=json&virtualmachineid=56a488ce-9baf-4d99-8e25-002d565f6731&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=euszCT397%2FkGpCM1fN%2BGQhTJCe8%3D
2014-05-12 13:40:48,621 DEBUG [c.c.a.ApiServlet] (catalina-exec-3:ctx-9e956cd7) 
===START===  127.0.0.1 -- GET  
apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=queryAsyncJobResult&jobId=2ef19e77-29af-416f-bc16-f27df1b58e7f&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=O1vnDPmstm6Xa2lEazduvETJkXk%3D
2014-05-12 13:40:48,627 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(API-Job-Executor-45:job-190) Add job-190 into job monitoring
2014-05-12 13:40:48,627 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-45:job-190) Executing AsyncJobVO {id:190, userId: 1, 
accountId: 1, instanceType: Volume, instanceId: 11, cmd: 
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin, cmdInfo: 
{"virtualmachineid":"56a488ce-9baf-4d99-8e25-002d565f6731","cmdEventType":"VOLUME.ATTACH","ctxUserId":"1","httpmethod":"GET","deviceid":"1","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","id":"00585b50-8c65-4e5b-95ee-853489e5499c","response":"json","ctxDetails":"{\"com.cloud.storage.Volume\":11,\"Volume\":\"00585b50-8c65-4e5b-95ee-853489e5499c\",\"com.cloud.vm.VirtualMachine\":8}","ctxAccountId":"1","uuid":"00585b50-8c65-4e5b-95ee-853489e5499c","ctxStartEventId":"448","signature":"euszCT397/kGpCM1fN+GQhTJCe8\u003d"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-05-12 13:40:48,642 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
(catalina-exec-3:ctx-9e956cd7 ctx-6c73263d ctx-4e50fbeb) IAM access check for 
1-null-null-DomainCapability from cache
2014-05-12 13:40:48,645 DEBUG [o.a.c.i.RoleBasedEntityA

[jira] [Updated] (CLOUDSTACK-6562) [Automation] [XenServer] Secondary Storage count for account shows double the value of the desired count

2014-05-12 Thread Abhinandan Prateek (JIRA)

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

Abhinandan Prateek updated CLOUDSTACK-6562:
---

Assignee: Harikrishna Patnala  (was: Bharat Kumar)

> [Automation] [XenServer] Secondary Storage count for account shows double the 
> value of the desired count
> 
>
> Key: CLOUDSTACK-6562
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6562
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation, Storage Controller, Template
>Affects Versions: 4.4.0
> Environment: XenServer
> No problem on KVM and VMware
>Reporter: Ashutosk Kelkar
>Assignee: Harikrishna Patnala
>  Labels: automation
> Fix For: 4.4.0
>
>
> Create an account.
> Register a template and download it.
> if the template size is "X", then the secondarystoragetotal for the account 
> shows it as "2X". Desired value is X.



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


[jira] [Created] (CLOUDSTACK-6646) Conntrackd is started on non-redundant virtual router

2014-05-12 Thread Sheng Yang (JIRA)
Sheng Yang created CLOUDSTACK-6646:
--

 Summary: Conntrackd is started on non-redundant virtual router
 Key: CLOUDSTACK-6646
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6646
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Virtual Router
Affects Versions: 4.3.0, 4.4.0
Reporter: Sheng Yang
Assignee: Sheng Yang
Priority: Critical
 Fix For: 4.4.0


Conntrackd should be only start on RvR, but it shows up in other VRs as well.  
And it may generate in tons of logs in /var/log/conntrackd-stats.log, which 
would possibly fill up all VR's disk space. Logrotate.d need to be tweaked in 
this case.





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


[jira] [Closed] (CLOUDSTACK-6630) [Automation] Failed to create PF rule with error "does not have permission to access resource"

2014-05-12 Thread Rayees Namathponnan (JIRA)

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

Rayees Namathponnan closed CLOUDSTACK-6630.
---


Verified with latest automation runs

> [Automation] Failed to create PF rule with error "does not have permission to 
> access resource"
> --
>
> Key: CLOUDSTACK-6630
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6630
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: IAM
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: CLOUDSTACK-6630.rar
>
>
> Run  BVT suite volume.py
> test case 
> 1) creating user account with domian ROOT
> 2)  deploying vm with new network
> 3)  obtain new IP, apply firewall rule
> 4) apply PF rule  
> Result
> PF rule creation failed with below exception 
> 2014-05-10 23:58:48,482 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-23:ctx-bc32f45f ctx-1c7a9889 ctx-d99c5930) IAM access c
> heck for 2-null-null-DomainCapability from cache: false
> 2014-05-10 23:58:48,493 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-23:ctx-bc32f45f ctx-1c7a9889 ctx-d99c5930) ===END===  
> 10.223.240.194 -- GET
>   
> signature=gD6OYRiz6Jd%2FZz7M7emIaancCr0%3D&apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&
> command=queryAsyncJobResult&response=json&jobid=3b680c4e-8508-4691-9d89-87dfeb400dec
> 2014-05-10 23:58:48,499 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-22:ctx-7e9bd8bb) ===START===  10.223.240.194 -- GET  
> apiKey=leb8qPblUzbfXRS
> pfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&virtualmachineid=eabab3fc-5229-47fe-b4b5-ae1d47c119fc&ipaddressid=3
> a2642c3-4c04-47f3-a5a5-a5446673223d&signature=fIvJyw2UfV2Y9mTnxmx7eMick6w%3D&command=createPortForwardingRule&privateport=22&protocol=TCP&p
> ublicport=&response=json
> 2014-05-10 23:58:48,532 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentManager-Handler-3:null) SeqA 6-221: Processing Seq 6-221:  { Cmd , 
> MgmtId: -
> 1, via: 6, Ver: v1, Flags: 11, 
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":4,"_loadInfo":"{\n
>   \"connections\": []\
> n}","wait":0}}] }
> 2014-05-10 23:58:48,536 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentManager-Handler-3:null) SeqA 6-221: Sending Seq 6-221:  { Ans: , 
> MgmtId: 290
> 66118877352, via: 6, Ver: v1, Flags: 100010, 
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2014-05-10 23:58:48,598 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
> heck for 2-null-null-SystemCapability from cache: true
> 2014-05-10 23:58:48,599 DEBUG [c.c.u.AccountManagerImpl] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Root Access granted 
> to A
> cct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] by 
> RoleBasedEntityAccessChecker
> 2014-05-10 23:58:48,601 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
> heck for 2-null-null-DomainCapability from cache: false
> 2014-05-10 23:58:48,606 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
> heck for 2-null-null-DomainResourceCapability from cache: false
> 2014-05-10 23:58:48,627 DEBUG [o.a.c.i.s.IAMServiceImpl] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Put IAM access 
> check for
>  2-VirtualMachine8-OperateEntry-createPortForwardingRule in cache
> 2014-05-10 23:58:48,650 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Account 
> Acct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] does not have permission to 
> access resource Ip[10.223.122.71-1] for access type: OperateEntry
> 2014-05-10 23:58:48,650 DEBUG [o.a.c.i.s.IAMServiceImpl] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Put IAM access 
> check for 2-IpAddress6-OperateEntry-createPortForwardingRule in cache
> 2014-05-10 23:58:48,651 INFO  [c.c.a.ApiServer] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) PermissionDenied: 
> Account Acct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] does not have 
> permission to access resource Ip[10.223.122.71-1] for access type: 
> OperateEntry on objs: []
> 2014-05-10 23:58:48,654 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) ===END===  
> 10.223.240.194 -- GET  
> apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&virtualmachineid=eabab3fc-5229-47fe-b4b5-ae1d47c119fc&ipa

[jira] [Resolved] (CLOUDSTACK-6379) UI:MS: Unable to create a user type Admin under a domain; No API being fired

2014-05-12 Thread Jessica Wang (JIRA)

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

Jessica Wang resolved CLOUDSTACK-6379.
--

Resolution: Fixed

> UI:MS: Unable to create a user type Admin under a domain; No API being fired
> 
>
> Key: CLOUDSTACK-6379
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6379
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, UI
>Affects Versions: 4.4.0
> Environment: 4.4
>Reporter: Parth Jagirdar
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.4.0
>
> Attachments: domain admin.jpg
>
>
> Create a domain, then create a user under it of type Admin. Observe no API 
> being fired upon clicking OK.
> Also observe Reference Error: rootDomainId not defined.



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


[jira] [Commented] (CLOUDSTACK-6606) create network offering dailog box has greyed out (not selectable) providers for the connectivity service.

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6606: Fixed: create network offering dailog box has greyed out (not 
selectable) providers for the connectivity service.


> create network offering dailog box has greyed out (not selectable) providers 
> for the connectivity service.
> --
>
> Key: CLOUDSTACK-6606
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6606
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Murali Reddy
>Assignee: Gabor Apati-Nagy
> Fix For: 4.4.0
>
> Attachments: Screen Shot 2014-05-07 at 3.05.09 PM.png
>
>
> create network offering dailog box has greyed out (not selectable) providers 
> for the connectivity service.



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


[jira] [Resolved] (CLOUDSTACK-6606) create network offering dailog box has greyed out (not selectable) providers for the connectivity service.

2014-05-12 Thread Jessica Wang (JIRA)

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

Jessica Wang resolved CLOUDSTACK-6606.
--

Resolution: Fixed

> create network offering dailog box has greyed out (not selectable) providers 
> for the connectivity service.
> --
>
> Key: CLOUDSTACK-6606
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6606
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Murali Reddy
>Assignee: Gabor Apati-Nagy
> Fix For: 4.4.0
>
> Attachments: Screen Shot 2014-05-07 at 3.05.09 PM.png
>
>
> create network offering dailog box has greyed out (not selectable) providers 
> for the connectivity service.



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


[jira] [Commented] (CLOUDSTACK-6606) create network offering dailog box has greyed out (not selectable) providers for the connectivity service.

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6606: Fixed: create network offering dailog box has greyed out (not 
selectable) providers for the connectivity service.


> create network offering dailog box has greyed out (not selectable) providers 
> for the connectivity service.
> --
>
> Key: CLOUDSTACK-6606
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6606
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Murali Reddy
>Assignee: Gabor Apati-Nagy
> Fix For: 4.4.0
>
> Attachments: Screen Shot 2014-05-07 at 3.05.09 PM.png
>
>
> create network offering dailog box has greyed out (not selectable) providers 
> for the connectivity service.



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


[jira] [Commented] (CLOUDSTACK-6485) [vpc] new private gateway network is registered wrong in network table

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

Revert "CLOUDSTACK-6485: private gateway network should not be associated with 
vpc"

This reverts commit c37df38c834a7cfc075228c697fc6d358a70f574.


> [vpc] new private gateway network is registered wrong in network table
> --
>
> Key: CLOUDSTACK-6485
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6485
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.2.1, 4.3.0, 4.4.0, 4.3.1
>Reporter: Anton Opgenoort
>Assignee: Daan Hoogland
>
> When creating a private gateway for a VPC router on a network not yet known 
> to Cloudstack, Cloudstack ‘documents’ this network in the networks table.
> For normal guest networks, which should be associated with a single VPC, 
> Cloudstack includes the VPC_ID in the database. The VPC_ID field is used to 
> provision all networks and nics on a VPC router when it is created. Since 
> this table is all about network provisioning it makes sense to ‘document’ the 
> network cidr and gateway present in that nework. For guest tiers this usually 
> is the VPC router itself, so the interface IP’s on a VPC router are the 
> gateway IP’s found in the networks table.
> Unfortunately the VPC_ID is also recorded for the private gateway network 
> when it is first created. So the first VPC to be plugged on the private 
> gateway network also has that same network associated as a guest network 
> tier, instead of just a private gateway network.
> This by itself will not quickly become a problem, because private gateways 
> are first plugged on a running vpc router which is not likely to be recreated 
> any time soon after that.
> But as soon as this first ever VPC router on the private gateway network is 
> recreated due to a destroy of the VPC Router, all associated networks are 
> looked up in the networks table. 
> Because the private gateway network is ‘documented’ with the actual upstream 
> gateway used by the VPC router defintion, the VPC router provisions a NIC on 
> the private gateway network using the IP address of the actual upstream 
> gateway creating an IP conflict on the private gateway network, effectively 
> breaking down the upstream gateway functionality for all attached private 
> gateways of other vpc's.



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


[jira] [Issue Comment Deleted] (CLOUDSTACK-5943) [doc] Palo Alto Firewall

2014-05-12 Thread Will Stevens (JIRA)

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

Will Stevens updated CLOUDSTACK-5943:
-

Comment: was deleted

(was: I have submitted a github pull request for this documentation...

https://github.com/apache/cloudstack-docs-admin/pull/9)

> [doc] Palo Alto Firewall
> 
>
> Key: CLOUDSTACK-5943
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5943
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.3.0
>Reporter: Radhika Nair
> Fix For: 4.3.0
>
>




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


[jira] [Commented] (CLOUDSTACK-5943) [doc] Palo Alto Firewall

2014-05-12 Thread Will Stevens (JIRA)

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

Will Stevens commented on CLOUDSTACK-5943:
--

I have submitted a github pull request for this documentation...

https://github.com/apache/cloudstack-docs-admin/pull/9

> [doc] Palo Alto Firewall
> 
>
> Key: CLOUDSTACK-5943
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5943
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.3.0
>Reporter: Radhika Nair
> Fix For: 4.3.0
>
>




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


[jira] [Commented] (CLOUDSTACK-6628) [Automation] Create PF rulw API failing with error "database id can only provided by VO objects"

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6628: Fix IpAddress import typo.


> [Automation] Create PF rulw API failing with error "database id can only 
> provided by VO objects"
> 
>
> Key: CLOUDSTACK-6628
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6628
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Network Controller
>Affects Versions: 4.4.0
> Environment: RHEL 6.3
> build 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> This issue is observed with latest automation run 
> BVT template test cases failed, while creating PF rules
> 2014-05-09 15:26:29,565 DEBUG [c.c.n.v.VpcManagerImpl] 
> (catalina-exec-12:ctx-d540a3b7 ctx-b040fadc ctx-9a73d98c) IP address 
> Ip[10.223.122.75-1] is no longer associated with the network inside vpc id=2
> 2014-05-09 15:26:29,565 DEBUG [c.c.n.v.VpcManagerImpl] 
> (catalina-exec-12:ctx-d540a3b7 ctx-b040fadc ctx-9a73d98c) Successfully 
> released VPC ip address Ip[10.223.122.75-1] back to VPC pool
> 2014-05-09 15:26:29,587 ERROR [c.c.a.ApiServer] 
> (catalina-exec-12:ctx-d540a3b7 ctx-b040fadc ctx-9a73d98c) unhandled exception 
> executing api command: [Ljava.lang.String;@66d6a3
> java.lang.UnsupportedOperationException: database id can only provided by VO 
> objects
> at 
> org.apache.cloudstack.api.command.user.firewall.CreatePortForwardingRuleCmd.getId(CreatePortForwardingRuleCmd.java:241)
> at 
> org.apache.cloudstack.iam.RoleBasedEntityAccessChecker.buildAccessCacheKey(RoleBasedEntityAccessChecker.java:70)
> at 
> org.apache.cloudstack.iam.RoleBasedEntityAccessChecker.checkAccess(RoleBasedEntityAccessChecker.java:94)
> at 
> org.apache.cloudstack.iam.RoleBasedEntityAccessChecker.checkAccess(RoleBasedEntityAccessChecker.java:202)
> at 
> com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:554)
> at 
> com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:485)
> at sun.reflect.GeneratedMethodAccessor290.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy100.checkAccess(Unknown Source)
> at 
> com.cloud.network.rules.RulesManagerImpl.checkRuleAndUserVm(RulesManagerImpl.java:192)
> at 
> com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:271)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at 
> com.cloud.event.Acti

[jira] [Commented] (CLOUDSTACK-6565) [UI] New Zones tab for Templates and ISOs

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6565: [UI] New Zones tab for Templates and ISOs


> [UI] New Zones tab for Templates and ISOs
> -
>
> Key: CLOUDSTACK-6565
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6565
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Reporter: Gabor Apati-Nagy
>Assignee: Gabor Apati-Nagy
> Fix For: 4.4.0
>
>
> Display templates and ISOs only once, even if they are for multiple zones. 
> Instead of showing redundant list, one item for each zone, show zone list in 
> a new tab. (Current UI shows templates and ISOs as many times as many zones 
> they are in.)
> Show the new Zones tab right next to the currently existing Details tab, show 
> the per-zone related user actions in the Zones list.
> Having this view would eliminate the long list of Templates and ISOs when 
> there are many zones available. This feature does not need API changes.



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


[jira] [Assigned] (CLOUDSTACK-6630) [Automation] Failed to create PF rule with error "does not have permission to access resource"

2014-05-12 Thread Min Chen (JIRA)

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

Min Chen reassigned CLOUDSTACK-6630:


Assignee: Min Chen

> [Automation] Failed to create PF rule with error "does not have permission to 
> access resource"
> --
>
> Key: CLOUDSTACK-6630
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6630
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: IAM
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: CLOUDSTACK-6630.rar
>
>
> Run  BVT suite volume.py
> test case 
> 1) creating user account with domian ROOT
> 2)  deploying vm with new network
> 3)  obtain new IP, apply firewall rule
> 4) apply PF rule  
> Result
> PF rule creation failed with below exception 
> 2014-05-10 23:58:48,482 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-23:ctx-bc32f45f ctx-1c7a9889 ctx-d99c5930) IAM access c
> heck for 2-null-null-DomainCapability from cache: false
> 2014-05-10 23:58:48,493 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-23:ctx-bc32f45f ctx-1c7a9889 ctx-d99c5930) ===END===  
> 10.223.240.194 -- GET
>   
> signature=gD6OYRiz6Jd%2FZz7M7emIaancCr0%3D&apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&
> command=queryAsyncJobResult&response=json&jobid=3b680c4e-8508-4691-9d89-87dfeb400dec
> 2014-05-10 23:58:48,499 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-22:ctx-7e9bd8bb) ===START===  10.223.240.194 -- GET  
> apiKey=leb8qPblUzbfXRS
> pfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&virtualmachineid=eabab3fc-5229-47fe-b4b5-ae1d47c119fc&ipaddressid=3
> a2642c3-4c04-47f3-a5a5-a5446673223d&signature=fIvJyw2UfV2Y9mTnxmx7eMick6w%3D&command=createPortForwardingRule&privateport=22&protocol=TCP&p
> ublicport=&response=json
> 2014-05-10 23:58:48,532 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentManager-Handler-3:null) SeqA 6-221: Processing Seq 6-221:  { Cmd , 
> MgmtId: -
> 1, via: 6, Ver: v1, Flags: 11, 
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":4,"_loadInfo":"{\n
>   \"connections\": []\
> n}","wait":0}}] }
> 2014-05-10 23:58:48,536 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentManager-Handler-3:null) SeqA 6-221: Sending Seq 6-221:  { Ans: , 
> MgmtId: 290
> 66118877352, via: 6, Ver: v1, Flags: 100010, 
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2014-05-10 23:58:48,598 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
> heck for 2-null-null-SystemCapability from cache: true
> 2014-05-10 23:58:48,599 DEBUG [c.c.u.AccountManagerImpl] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Root Access granted 
> to A
> cct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] by 
> RoleBasedEntityAccessChecker
> 2014-05-10 23:58:48,601 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
> heck for 2-null-null-DomainCapability from cache: false
> 2014-05-10 23:58:48,606 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
> heck for 2-null-null-DomainResourceCapability from cache: false
> 2014-05-10 23:58:48,627 DEBUG [o.a.c.i.s.IAMServiceImpl] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Put IAM access 
> check for
>  2-VirtualMachine8-OperateEntry-createPortForwardingRule in cache
> 2014-05-10 23:58:48,650 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Account 
> Acct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] does not have permission to 
> access resource Ip[10.223.122.71-1] for access type: OperateEntry
> 2014-05-10 23:58:48,650 DEBUG [o.a.c.i.s.IAMServiceImpl] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Put IAM access 
> check for 2-IpAddress6-OperateEntry-createPortForwardingRule in cache
> 2014-05-10 23:58:48,651 INFO  [c.c.a.ApiServer] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) PermissionDenied: 
> Account Acct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] does not have 
> permission to access resource Ip[10.223.122.71-1] for access type: 
> OperateEntry on objs: []
> 2014-05-10 23:58:48,654 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) ===END===  
> 10.223.240.194 -- GET  
> apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&virtualmachineid=eabab3fc-5229-47fe-b4b5-ae1d47c119fc&ipaddressid=3a2642c3-4c04-47f3-a

[jira] [Closed] (CLOUDSTACK-6626) UI - fix a bug that g_userid was not declared

2014-05-12 Thread Jessica Wang (JIRA)

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

Jessica Wang closed CLOUDSTACK-6626.



> UI - fix a bug that g_userid was not declared
> -
>
> Key: CLOUDSTACK-6626
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6626
> 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
>




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


[jira] [Commented] (CLOUDSTACK-6599) Template/Volume URLs expiration functionality not working

2014-05-12 Thread Nitin Mehta (JIRA)

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

Nitin Mehta commented on CLOUDSTACK-6599:
-

Look for reference of the global config extract.url.expiration.interval in 4.2 
and you can trace back the functionality.

> Template/Volume URLs expiration functionality not working
> -
>
> Key: CLOUDSTACK-6599
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6599
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Mehta
>Assignee: Nitin Mehta
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Template / Volume Donwload URLs should expire - functionality is missing
> We have the functionality where we create download urls for volumes and 
> templates for the users. For security reasons we should expire these urls and 
> this functionality existed since 3.0.x. But it doesnt exist in 4.4 and that 
> needs to be implemented. Look at 4.2 for reference.



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


[jira] [Created] (CLOUDSTACK-6608) OVS distributed firewall: default ACL rule is not getting applied when a tier in VPC is created.

2014-05-12 Thread Murali Reddy (JIRA)
Murali Reddy created CLOUDSTACK-6608:


 Summary: OVS distributed firewall: default ACL rule is not getting 
applied when a tier in VPC is created.
 Key: CLOUDSTACK-6608
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6608
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.4.0
Reporter: Murali Reddy
Assignee: Murali Reddy
 Fix For: 4.4.0


OVS distributed firewall: default ACL rule is not getting applied when a tier 
in VPC is created. Current logic in OVS tunnel manager is updating ACL table on 
the host only when ACL is replace, but not for the default ACL that gets 
applied when network is created.

Fix should ensure OvsVpcRoutingPolicyConfigCommand update is send to the hosts 
on which VPC spans when tier is created.



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


[jira] [Commented] (CLOUDSTACK-3272) EventBus: add global config parameters to specify which category of events are published on event bus.

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit 882bf079fa1886c9feab0948066a02c1cb6cd86a in cloudstack's branch 
refs/heads/4.4 from [~Sonal]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=882bf07 ]

CLOUDSTACK-3272 Fixing NullPointerException for alerts

Signed-off-by: Daan Hoogland 


> EventBus: add global config parameters to specify which category of events 
> are published on event bus.
> --
>
> Key: CLOUDSTACK-3272
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3272
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.1.0
>Reporter: Murali Reddy
>Assignee: Sonal Ojha
> Fix For: 4.4.0
>
>
> EventBus: add global config parameters to specify which category of events 
> are published on event bus.
> Fix would need a boolean global config for each event category.
> For e.g, if global config 'publish.action.events' is set to false then on 
> event bug action events are not published.



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


[jira] [Updated] (CLOUDSTACK-4872) VM provisioned using a registered Windows Server 2012 template will show as other os in VCenter.

2014-05-12 Thread prashant kumar mishra (JIRA)

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

prashant kumar mishra updated CLOUDSTACK-4872:
--

Description: 
1. Register a windows 2012 template by choosing guest os type as Windows Server 
2012.
2. Provision VM using the template.
3. In VCenter, it shows as other os..

  was:
1. Register a windows 2012 template by choosing guest os type as Windows Server 
2012.
2. Provision VM using the template.
3. In VCenter, it shows as other os.


> VM provisioned using a registered Windows Server 2012 template will show as 
> other os in VCenter.
> 
>
> Key: CLOUDSTACK-4872
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4872
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.0
>Reporter: Min Chen
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.2.1
>
>
> 1. Register a windows 2012 template by choosing guest os type as Windows 
> Server 2012.
> 2. Provision VM using the template.
> 3. In VCenter, it shows as other os..



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


[jira] [Updated] (CLOUDSTACK-6637) IAM : Integration test cases

2014-05-12 Thread Meghna Kale (JIRA)

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

Meghna Kale updated CLOUDSTACK-6637:


Issue Type: Test  (was: Task)

> IAM : Integration test cases
> 
>
> Key: CLOUDSTACK-6637
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6637
> Project: CloudStack
>  Issue Type: Test
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: IAM
>Reporter: Meghna Kale
>Priority: Minor
>
> Integration test cases for IAM module.



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


[jira] [Created] (CLOUDSTACK-6640) Test case : listAutoScalePolicy

2014-05-12 Thread Meghna Kale (JIRA)
Meghna Kale created CLOUDSTACK-6640:
---

 Summary: Test case : listAutoScalePolicy
 Key: CLOUDSTACK-6640
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6640
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Meghna Kale
Priority: Minor






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


[jira] [Commented] (CLOUDSTACK-6592) OVS distributed routing: make populate flooding rules transactional

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit 0adf8924e28dc9bc1af5a2e04d5146d97e60fced in cloudstack's branch 
refs/heads/4.4 from [~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0adf892 ]

CLOUDSTACK-6592: OVS distributed routing: make populate flooding rules
transactional

creats a file with all openflow rules updates and using ovs-ofctl file
option updates the brige in one go


> OVS distributed routing: make populate flooding rules transactional
> ---
>
> Key: CLOUDSTACK-6592
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6592
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Murali Reddy
>Assignee: Murali Reddy
> Fix For: 4.4.0
>
>
> Currently when a tunnel port or vif is created/destroyed, L2 flooding table 
> is updated with new set of flooding rules which reflect the current set of 
> VIF's and tunnel ports that needed to be in the broadcast domain of tier. But 
> way its done is sequential with ovs-ofctl getting executed with each update.
> This bug is to club all the flow rule updates in to a single file and use 
> file option of ovs-ofctl to update the bridge.



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


[jira] [Commented] (CLOUDSTACK-6572) [Hyper-V] Deploy VM inside VPC tier fails due to VR unable to find nic

2014-05-12 Thread Daan Hoogland (JIRA)

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

Daan Hoogland commented on CLOUDSTACK-6572:
---

Rajesh, it does not cherry-pick without conflicts.




-- 
Daan


> [Hyper-V] Deploy VM inside VPC tier fails due to VR unable to find nic
> --
>
> Key: CLOUDSTACK-6572
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6572
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Hypervisor Controller, Network Controller
>Affects Versions: 4.4.0
> Environment: 4.4, Hyper-V Advanced zone, VPC
>Reporter: Sowmya Krishnan
>Assignee: Rajesh Battala
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Create a VPC offering with all services provided by VPCVR
> Create a VPC using this offering
> Configure a tier in the VPC with all services enabled including LB
> Launch a VM in the tier
> Fails to deploy VM since VR is unable to find a nic. VR has allocated all 8 
> nics but only eth0 has acquired private IP
> Here's ifconfig output of VR:
> eth0  Link encap:Ethernet  HWaddr 02:00:02:2d:00:01
>   inet addr:10.102.195.179  Bcast:10.102.195.255  Mask:255.255.252.0
>   inet6 addr: fe80::2ff:fe2d:1/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:25785 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:431 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:2160968 (2.0 MiB)  TX bytes:79183 (77.3 KiB)
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:16436  Metric:1
>   RX packets:2 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:214 (214.0 B)  TX bytes:214 (214.0 B)
> mysql> select * from domain_router where id = 3\G
>  id: 3
>  element_id: 2
>  public_mac_address: 06:4b:c6:00:00:0e
>   public_ip_address: 10.102.196.237
>  public_netmask: 255.255.255.0
>   guest_netmask: NULL
>guest_ip_address: NULL
> is_redundant_router: 0
>priority: 0
>  is_priority_bumpup: 0
> redundant_state: UNKNOWN
>stop_pending: 0
>role: VIRTUAL_ROUTER
>template_version: Cloudstack Release 4.4.0 Fri Apr 11 18:25:32 UTC 2014
> scripts_version: 16486954f5bda9ef9254913c0d692bd0
>  vpc_id: 1
> 1 row in set (0.00 sec)
> mysql> select * from nics where vm_type = 'DomainRouter';
> | id | uuid | instance_id | mac_address   
> | ip4_address| netmask | gateway  | ip_type | broadcast_uri | 
> network_id | mode   | state| strategy | reserver_name| 
> reservation_id   | device_id | update_time | 
> isolation_uri | ip6_address | default_nic | vm_type  | created
>  | removed | ip6_gateway | ip6_cidr | secondary_ip | display_nic |
> ++--+-+---++-+--+-+---+++--+--+--+--+---+-+---+-+-+--+-+-+-+--+--+-+
> |  8 | a218f142-213f-4dff-9b43-7d9c2b577ea4 |   3 | 02:00:02:2d:00:01 
> | 10.102.195.179 | 255.255.252.0   | 10.102.192.1 | Ip4 | NULL  | 
>202 | Static | Reserved | Start| ControlNetworkGuru   | 
> 09a63fe0-a914-4a76-ab47-54558b82d900 | 0 | 2014-05-05 09:14:39 | NULL 
>  | NULL|   0 | DomainRouter | 2014-05-05 03:44:39 | 
> NULL| NULL| NULL |0 |   1 |
> |  9 | 79883821-1efe-4a52-9af9-1f4a8413ed8f |   3 | 06:4b:c6:00:00:0e 
> | 10.102.196.237 | 255.255.255.0   | 10.102.196.1 | NULL| vlan://100| 
>200 | Static | Reserved | Managed  | PublicNetworkGuru| NULL   
>   | 1 | 2014-05-05 09:14:39 | vlan://100  
>   | NULL|   1 | DomainRouter | 2014-05-05 03:44:39 | NULL
> | NULL| NULL |0 |   1 |
> | 11 | fd7db89a-f5a8-4653-aab8-c7c2621546bf |   3 | 02:00:6c:8a:00:02 
> | 10.10.1.1  | 255.255.255.240 | 10.10.1.1| Ip4 | vlan://850| 
>204 | Dhcp   | Reserved 

[jira] [Updated] (CLOUDSTACK-6637) IAM : Integration test cases

2014-05-12 Thread Meghna Kale (JIRA)

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

Meghna Kale updated CLOUDSTACK-6637:


Component/s: IAM

> IAM : Integration test cases
> 
>
> Key: CLOUDSTACK-6637
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6637
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: IAM
>Reporter: Meghna Kale
>Priority: Minor
>
> Integration test cases for IAM module.



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


[jira] [Created] (CLOUDSTACK-6637) IAM : Integration test cases

2014-05-12 Thread Meghna Kale (JIRA)
Meghna Kale created CLOUDSTACK-6637:
---

 Summary: IAM : Integration test cases
 Key: CLOUDSTACK-6637
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6637
 Project: CloudStack
  Issue Type: Task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Meghna Kale
Priority: Minor


Integration test cases for IAM module.



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


[jira] [Commented] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error "Can only support create Private VLAN network with IPv4!"

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit afd9d4e7567007604e15761a33ce9314149f7e21 in cloudstack's branch 
refs/heads/4.4-forward from santhosh
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=afd9d4e ]

CLOUDSTACK-6627 catch exception instead of checking response

Signed-off-by: santhosh 
Signed-off-by: Daan Hoogland 


> [Automation] createNetwork API failing with error "Can only support create 
> Private VLAN network with IPv4!"
> ---
>
> Key: CLOUDSTACK-6627
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6627
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.4.0
> Environment: KVM and vmware
> build 4.4-forward
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> integration.smoke.test_pvlan.TestPVLAN.test_create_pvlan_network  failing 
> latest run 
> 2014-05-09 14:37:36,948 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-11:ctx-80f69f30) ===START===  10.223.240.194 -- GET  
> apiKey=PqBwvR5XGUP5UMkcchdzGW9QtWAexG7mh
> 0JjGFlcpg7Vf6Xazb9RhhL4j7RAY-bGWpqt_IjM2W3Oy0ukiFF_3Q&startipv6=fc00%3A1234%3A%3A10&zoneid=8ec43c1f-ee32-4b1e-90d2-fce40313aafc&isolatedpvlan=567&displaytext
> =pvlan+network&ip6gateway=fc00%3A1234%3A%3A1&gateway=10.10.10.20&endipv6=fc00%3A1234%3A%3A20&networkofferingid=7&vlan=1234&netmask=255.255.255.0&response=jso
> n&name=pvlan+network&startip=10.10.10.10&ip6cidr=fc00%3A1234%3A%3A%2F64&command=createNetwork&signature=mHKCVFL1AM4NkVrEr%2FiW%2FdIj2NE%3D
> API failing with error "Can only support create Private VLAN network with 
> IPv4!"
> 2014-05-09 14:37:36,971 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) IAM access check 
> for 2-null-nu
> ll-SystemCapability from cache: false
> 2014-05-09 14:37:36,971 DEBUG [c.c.u.AccountManagerImpl] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Root Access granted 
> to Acct[e853580a-d7ae-
> 11e3-a7c8-1a6f7bb0d0a8-admin] by AffinityGroupAccessChecker
> 2014-05-09 14:37:37,011 INFO  [c.c.a.ApiServer] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Can only support 
> create Private VLAN network with IPv4!
> 2014



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


[jira] [Created] (CLOUDSTACK-6638) Test case : listVolumes

2014-05-12 Thread Meghna Kale (JIRA)
Meghna Kale created CLOUDSTACK-6638:
---

 Summary: Test case : listVolumes
 Key: CLOUDSTACK-6638
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6638
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Meghna Kale
Priority: Minor






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


[jira] [Commented] (CLOUDSTACK-6617) [Automation] detach / resize volume test cases failing with permission error

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit f447a2c38c15ad5b7844237e72ab551149f46bfb in cloudstack's branch 
refs/heads/4.4-forward from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f447a2c ]

CLOUDSTACK-6617: [Automation] detach / resize volume test cases failing
with permission error.


> [Automation] detach / resize volume test cases failing  with permission error 
> --
>
> Key: CLOUDSTACK-6617
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6617
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes, Xen
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Assignee: Min Chen
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> This issue is observed in 4.4-forward automation in Xen, test case 
> integration.smoke.test_volumes.TestVolumes.test_06_download_detached_volume 
> failing with permission error 
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 
> Execute cmd: attachvolume failed, due to: errorCode: 531, 
> errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources
>  >> begin captured stdout << -
> === TestName: test_06_download_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
>  >> begin captured logging << 
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: STARTED : 
> TC: test_06_download_detached_volume :::
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Extract detached Volume 
> ID: 885ac921-4728-4903-9621-b07c5353e9bc
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Payload: {'apiKey': 
> u'WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ',
>  'virtualmachineid': u'2e1ef913-b207-4688-bbaa-408797810d3a', 'id': 
> u'885ac921-4728-4903-9621-b07c5353e9bc', 'command': 'attachVolume', 
> 'signature': 'hnLR1wCmFp5EtwMZRaS1e3J75S8=', 'response': 'json'}
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Sending GET Cmd 
> : attachVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
> (1): 10.220.76.63
> requests.packages.urllib3.connectionpool: DEBUG: "GET 
> /client/api?apiKey=WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ&virtualmachineid=2e1ef913-b207-4688-bbaa-408797810d3a&id=885ac921-4728-4903-9621-b07c5353e9bc&command=attachVolume&signature=hnLR1wCmFp5EtwMZRaS1e3J75S8%3D&response=json
>  HTTP/1.1" 531 212
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): ERROR: Exception:['Traceback 
> (most recent call last):\n', '  File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>  line 313, in __parseAndGetResponse\nresponse_cls)\n', '  File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py",
>  line 151, in getResultObj\nraise 
> cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
> 'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode: 
> 531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources\n']
> Traceback (most recent call last):
>   File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>  line 313, in __parseAndGetResponse
> response_cls)
>   File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py",
>  line 151, in getResultObj
> raise cloudstackException.CloudstackAPIException(respname, errMsg)
> CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode: 
> 531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): ERROR: marvinRequest : CmdName: 
>  
> Exception: ['Traceback (most recent call last):\n', '  File 
> "/local/jenkins/workspace/xenrt

[jira] [Assigned] (CLOUDSTACK-6628) [Automation] Create PF rulw API failing with error "database id can only provided by VO objects"

2014-05-12 Thread Min Chen (JIRA)

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

Min Chen reassigned CLOUDSTACK-6628:


Assignee: Min Chen

> [Automation] Create PF rulw API failing with error "database id can only 
> provided by VO objects"
> 
>
> Key: CLOUDSTACK-6628
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6628
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Network Controller
>Affects Versions: 4.4.0
> Environment: RHEL 6.3
> build 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> This issue is observed with latest automation run 
> BVT template test cases failed, while creating PF rules
> 2014-05-09 15:26:29,565 DEBUG [c.c.n.v.VpcManagerImpl] 
> (catalina-exec-12:ctx-d540a3b7 ctx-b040fadc ctx-9a73d98c) IP address 
> Ip[10.223.122.75-1] is no longer associated with the network inside vpc id=2
> 2014-05-09 15:26:29,565 DEBUG [c.c.n.v.VpcManagerImpl] 
> (catalina-exec-12:ctx-d540a3b7 ctx-b040fadc ctx-9a73d98c) Successfully 
> released VPC ip address Ip[10.223.122.75-1] back to VPC pool
> 2014-05-09 15:26:29,587 ERROR [c.c.a.ApiServer] 
> (catalina-exec-12:ctx-d540a3b7 ctx-b040fadc ctx-9a73d98c) unhandled exception 
> executing api command: [Ljava.lang.String;@66d6a3
> java.lang.UnsupportedOperationException: database id can only provided by VO 
> objects
> at 
> org.apache.cloudstack.api.command.user.firewall.CreatePortForwardingRuleCmd.getId(CreatePortForwardingRuleCmd.java:241)
> at 
> org.apache.cloudstack.iam.RoleBasedEntityAccessChecker.buildAccessCacheKey(RoleBasedEntityAccessChecker.java:70)
> at 
> org.apache.cloudstack.iam.RoleBasedEntityAccessChecker.checkAccess(RoleBasedEntityAccessChecker.java:94)
> at 
> org.apache.cloudstack.iam.RoleBasedEntityAccessChecker.checkAccess(RoleBasedEntityAccessChecker.java:202)
> at 
> com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:554)
> at 
> com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:485)
> at sun.reflect.GeneratedMethodAccessor290.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy100.checkAccess(Unknown Source)
> at 
> com.cloud.network.rules.RulesManagerImpl.checkRuleAndUserVm(RulesManagerImpl.java:192)
> at 
> com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:271)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at 
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java

[jira] [Updated] (CLOUDSTACK-6599) Template/Volume URLs expiration functionality not working

2014-05-12 Thread Nitin Mehta (JIRA)

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

Nitin Mehta updated CLOUDSTACK-6599:


Description: 
Template / Volume Donwload URLs should expire - functionality is missing

We have the functionality where we create download urls for volumes and 
templates for the users. For security reasons we should expire these urls and 
this functionality existed since 3.0.x. But it doesnt exist in 4.4 and that 
needs to be implemented. Look at 4.2 for reference.


  was:Template / Volume Donwload URLs should expire - functionality is missing


> Template/Volume URLs expiration functionality not working
> -
>
> Key: CLOUDSTACK-6599
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6599
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Mehta
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Template / Volume Donwload URLs should expire - functionality is missing
> We have the functionality where we create download urls for volumes and 
> templates for the users. For security reasons we should expire these urls and 
> this functionality existed since 3.0.x. But it doesnt exist in 4.4 and that 
> needs to be implemented. Look at 4.2 for reference.



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


[jira] [Commented] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error "Can only support create Private VLAN network with IPv4!"

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6627 catch exception instead of checking response

Signed-off-by: santhosh 
Signed-off-by: Daan Hoogland 


> [Automation] createNetwork API failing with error "Can only support create 
> Private VLAN network with IPv4!"
> ---
>
> Key: CLOUDSTACK-6627
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6627
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.4.0
> Environment: KVM and vmware
> build 4.4-forward
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> integration.smoke.test_pvlan.TestPVLAN.test_create_pvlan_network  failing 
> latest run 
> 2014-05-09 14:37:36,948 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-11:ctx-80f69f30) ===START===  10.223.240.194 -- GET  
> apiKey=PqBwvR5XGUP5UMkcchdzGW9QtWAexG7mh
> 0JjGFlcpg7Vf6Xazb9RhhL4j7RAY-bGWpqt_IjM2W3Oy0ukiFF_3Q&startipv6=fc00%3A1234%3A%3A10&zoneid=8ec43c1f-ee32-4b1e-90d2-fce40313aafc&isolatedpvlan=567&displaytext
> =pvlan+network&ip6gateway=fc00%3A1234%3A%3A1&gateway=10.10.10.20&endipv6=fc00%3A1234%3A%3A20&networkofferingid=7&vlan=1234&netmask=255.255.255.0&response=jso
> n&name=pvlan+network&startip=10.10.10.10&ip6cidr=fc00%3A1234%3A%3A%2F64&command=createNetwork&signature=mHKCVFL1AM4NkVrEr%2FiW%2FdIj2NE%3D
> API failing with error "Can only support create Private VLAN network with 
> IPv4!"
> 2014-05-09 14:37:36,971 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) IAM access check 
> for 2-null-nu
> ll-SystemCapability from cache: false
> 2014-05-09 14:37:36,971 DEBUG [c.c.u.AccountManagerImpl] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Root Access granted 
> to Acct[e853580a-d7ae-
> 11e3-a7c8-1a6f7bb0d0a8-admin] by AffinityGroupAccessChecker
> 2014-05-09 14:37:37,011 INFO  [c.c.a.ApiServer] 
> (catalina-exec-11:ctx-80f69f30 ctx-39ae4a70 ctx-13ff8562) Can only support 
> create Private VLAN network with IPv4!
> 2014



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


[jira] [Resolved] (CLOUDSTACK-6086) [Automation] Failed to restart network

2014-05-12 Thread Murali Reddy (JIRA)

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

Murali Reddy resolved CLOUDSTACK-6086.
--

Resolution: Cannot Reproduce

I am successfully able to restart network both with and without cleanup 
options. But i do see that test has been failing 
(http://jenkins.buildacloud.org/view/cloudstack-qa-4.4/job/test-smoke-matrix-4.4/lastCompletedBuild/suite=test_routers/testReport/integration.smoke.test_routers/TestRouterServices/test_03_restart_network_cleanup/).
 

Please attach the management server logs before reopening the bugs. Link 
mentioned in the bug does not work.

> [Automation] Failed to restart network
> --
>
> Key: CLOUDSTACK-6086
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6086
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.4.0
> Environment: xenserver 6.2 , advanced zone
>Reporter: Srikanteswararao Talluri
>Assignee: Murali Reddy
>Priority: Critical
> Fix For: 4.4.0
>
>
> Following tests failed during BVT run on latest master:
> http://jenkins.buildacloud.org/job/test-smoke-matrix-master/2/suite=test_routers/testReport/integration.smoke.test_routers/TestRouterServices/test_03_restart_network_cleanup/
> http://jenkins.buildacloud.org/job/test-smoke-matrix-master/2/suite=test_routers/testReport/integration.smoke.test_routers/TestRouterServices/test_04_restart_network_wo_cleanup/
> Logs: 
> http://jenkins.buildacloud.org/view/cloudstack-qa-master/job/test-matrix-master/3/distro=centos63,hypervisor=xen,profile=xen62/artifact/3.tar.bz2



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


[jira] [Created] (CLOUDSTACK-6636) [Windows] Can not create Template from ROOT snapshot

2014-05-12 Thread Damodar Reddy T (JIRA)
Damodar Reddy T created CLOUDSTACK-6636:
---

 Summary: [Windows] Can not create Template from ROOT snapshot
 Key: CLOUDSTACK-6636
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6636
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: Future, 4.5.0
Reporter: Damodar Reddy T


Steps to reproduce the issue

1. Create a snapshot from ROOT disk
2. Goto the above created snapshot
3. Try to create template out of it.

It is failing with the following trace.

014-05-12 04:02:01,813 WARN  [c.c.h.x.r.XenServerStorageProcessor] 
(DirectAgent-428:ctx-2ece4baa) null due to Illegal character in path at index 
47: 
nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd
java.net.URISyntaxException: Illegal character in path at index 47: 
nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd
at java.net.URI$Parser.fail(Unknown Source)
at java.net.URI$Parser.checkChars(Unknown Source)
at java.net.URI$Parser.parseHierarchical(Unknown Source)
at java.net.URI$Parser.parse(Unknown Source)
at java.net.URI.(Unknown Source)
at 
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.createVolumeFromSnapshot(XenServerStorageProcessor.java:1617)
at 
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:96)
at 
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542)
at 
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60)
at 
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown
 Source)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
 Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)



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


[jira] [Commented] (CLOUDSTACK-6518) [Hyper-V] Efficient way of finding the empty nic in VR

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit 70a3e581ee5939b524778d52f52c13760aaed6c3 in cloudstack's branch 
refs/heads/4.4 from [~rajesh_battala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=70a3e58 ]

CLOUDSTACK-6518 [Hyper-V] Efficient way of finding the empty nic in VR/VpcVR to 
configure VPC entities fixed windows line ending issues

Conflicts:

plugins/hypervisors/hyperv/DotNet/ServerResource/HypervResource/WmiCallsV2.cs


> [Hyper-V] Efficient way of finding the empty nic in VR 
> ---
>
> Key: CLOUDSTACK-6518
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6518
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Rajesh Battala
>Assignee: Rajesh Battala
>Priority: Critical
> Fix For: 4.4.0
>
>




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


[jira] [Updated] (CLOUDSTACK-6615) 4.4 build is failing due to commit 882bf079fa1886c9feab0948066a02c1cb6cd86a

2014-05-12 Thread Anshul Gangwar (JIRA)

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

Anshul Gangwar updated CLOUDSTACK-6615:
---

Affects Version/s: 4.4.0

> 4.4 build is failing due to commit 882bf079fa1886c9feab0948066a02c1cb6cd86a
> ---
>
> Key: CLOUDSTACK-6615
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6615
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Anshul Gangwar
>Priority: Blocker
>
> 4.4 build is failing due to commit 882bf079fa1886c9feab0948066a02c1cb6cd86a. 
> There is compilation failure as s_configDao variable is not declared in 
> AlertGenerator class.



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


[jira] [Created] (CLOUDSTACK-6616) systemvm template build failed since install dialog prevents automation

2014-05-12 Thread Yoshikazu Nojima (JIRA)
Yoshikazu Nojima created CLOUDSTACK-6616:


 Summary: systemvm template build failed since install dialog 
prevents automation
 Key: CLOUDSTACK-6616
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6616
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: SystemVM
Affects Versions: Future
Reporter: Yoshikazu Nojima



log:
=

Executing command: ./base.sh


0% [Working]

Hit http://http.us.debian.org wheezy Release.gpg


20% [Waiting for headers] [Waiting for headers]
   
Hit http://security.debian.org wheezy/updates Release.gpg

   
33% [Waiting for headers]
 
Hit http://http.us.debian.org wheezy-updates Release.gpg

43% [Waiting for headers]
 
Hit http://security.debian.org wheezy/updates Release

43% [Waiting for headers]
 
Hit http://http.us.debian.org wheezy Release

 
43% [Working]
 
43% [Release gpgv 102 kB] [Waiting for headers]
   
40% [Waiting for headers]
 
40% [Release gpgv 168 kB] [Waiting for headers] [Waiting for headers]
 
38% [Waiting for headers] [Waiting for headers]
   
Hit http://http.us.debian.org wheezy-updates Release

   
38% [Waiting for headers]
 
38% [Release gpgv 124 kB] [Waiting for headers] [Waiting for headers]
 
38% [Waiting for headers] [Waiting for headers]
   
Hit http://security.debian.org wheezy/updates/main Sources

   
44% [Waiting for headers]
 
Hit http://http.us.debian.org wheezy/main Sources

 
50% [Waiting for headers] [Waiting for headers]
   
Hit http://http.us.debian.org wheezy/main amd64 Packages

   
Hit http://security.debian.org wheezy/updates/main amd64 Packages

62% [Waiting for headers] [Waiting for headers]
   
Hit http://http.us.debian.org wheezy/main Translation-en

69% [Waiting for headers] [Waiting for headers]
   
Hit http://security.debian.org wheezy/updates/main Translation-en

   
75% [Waiting for headers]
 
Hit http://http.us.debian.org wheezy-updates/main Sources

81% [Waiting for headers]
 
Hit http://http.us.debian.org wheezy-updates/main amd64 Packages/DiffIndex

88% [Waiting for headers]
 
Hit http://http.us.debian.org wheezy-updates/main Translation-en/DiffIndex

 
94% [Working]
 

Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 1%

Reading package lists... 32%

Reading package lists... 58%

Reading package lists... 58%

Reading package lists... 59%

Reading package lists... 96%

Reading package lists... 96%

Reading package lists... 98%

Reading package lists... 98%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... Done


Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree   


Reading state information... 0%

Reading state information... 1%

Reading state information... Done

The following extra packages will be installed:
  ca-certificates libcurl3 libldap-2.4-2 librtmp0 libsasl2-2 libsasl2-modules
  libssh2-1 libssl1.0.0 openssl
Suggested packages:
  libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql
  libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal zip
The following NEW packages will be installed:
  ca-certificates curl libcurl3 libldap-2.4-2 librtmp0 libsasl2-2
  libsasl2-modules libssh2-1 openssl unzip
The following packages will be upgraded:
  libssl1.0.0
1 upgraded, 10 newly installed, 0 to remove and 5 not upgraded.
Need to get 3,609 kB of archives.
After this operation, 4,158 kB of additional disk space will be used.


0% [Working]

Get:1 http://http.us.debian.org/debian/ wheezy/main libssl1.0.0 amd64 
1.0.1e

[jira] [Updated] (CLOUDSTACK-6635) more details required in Alert generated in MS from router vm

2014-05-12 Thread prashant kumar mishra (JIRA)

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

prashant kumar mishra updated CLOUDSTACK-6635:
--

Attachment: cloudtest.dmp

> more details required in Alert generated in MS from router vm 
> --
>
> Key: CLOUDSTACK-6635
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6635
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Virtual Router
>Affects Versions: 4.4.0
> Environment: N/A
>Reporter: prashant kumar mishra
>Priority: Critical
> Fix For: 4.4.0
>
> Attachments: cloudtest.dmp
>
>
> More details are needed in alert messages:
> Expectation:subject should contain atleast service name and status
> Example: dhcp service stopped : r-6-vm
> DB:
> ===
> mysql> select subject, name from alert  where id >13;
> +-++
> | subject | name   |
> +-++
> | Monitoring Service on VR r-6-VM | ALERT.SERVICE.DOMAINROUTER |
> | Monitoring Service on VR r-6-VM | ALERT.SERVICE.DOMAINROUTER |
> | Monitoring Service on VR r-6-VM | ALERT.SERVICE.DOMAINROUTER |
> | Monitoring Service on VR r-6-VM | ALERT.SERVICE.DOMAINROUTER |
> +-++
> 4 rows in set (0.00 sec)



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


[jira] [Created] (CLOUDSTACK-6635) more details required in Alert generated in MS from router vm

2014-05-12 Thread prashant kumar mishra (JIRA)
prashant kumar mishra created CLOUDSTACK-6635:
-

 Summary: more details required in Alert generated in MS from 
router vm 
 Key: CLOUDSTACK-6635
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6635
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server, Virtual Router
Affects Versions: 4.4.0
 Environment: N/A
Reporter: prashant kumar mishra
Priority: Critical
 Fix For: 4.4.0


More details are needed in alert messages:
Expectation:subject should contain atleast service name and status
Example: dhcp service stopped : r-6-vm

DB:
===
mysql> select subject, name from alert  where id >13;
+-++
| subject | name   |
+-++
| Monitoring Service on VR r-6-VM | ALERT.SERVICE.DOMAINROUTER |
| Monitoring Service on VR r-6-VM | ALERT.SERVICE.DOMAINROUTER |
| Monitoring Service on VR r-6-VM | ALERT.SERVICE.DOMAINROUTER |
| Monitoring Service on VR r-6-VM | ALERT.SERVICE.DOMAINROUTER |
+-++
4 rows in set (0.00 sec)




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


[jira] [Updated] (CLOUDSTACK-6630) [Automation] Failed to create PF rule with error "does not have permission to access resource"

2014-05-12 Thread Rayees Namathponnan (JIRA)

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

Rayees Namathponnan updated CLOUDSTACK-6630:


Description: 
Run  BVT suite volume.py

test case 


1) creating user account with domian ROOT

2)  deploying vm with new network

3)  obtain new IP, apply firewall rule

4) apply PF rule  

Result


PF rule creation failed with below exception 


2014-05-10 23:58:48,482 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
(catalina-exec-23:ctx-bc32f45f ctx-1c7a9889 ctx-d99c5930) IAM access c
heck for 2-null-null-DomainCapability from cache: false
2014-05-10 23:58:48,493 DEBUG [c.c.a.ApiServlet] (catalina-exec-23:ctx-bc32f45f 
ctx-1c7a9889 ctx-d99c5930) ===END===  10.223.240.194 -- GET
  
signature=gD6OYRiz6Jd%2FZz7M7emIaancCr0%3D&apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&
command=queryAsyncJobResult&response=json&jobid=3b680c4e-8508-4691-9d89-87dfeb400dec
2014-05-10 23:58:48,499 DEBUG [c.c.a.ApiServlet] 
(catalina-exec-22:ctx-7e9bd8bb) ===START===  10.223.240.194 -- GET  
apiKey=leb8qPblUzbfXRS
pfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&virtualmachineid=eabab3fc-5229-47fe-b4b5-ae1d47c119fc&ipaddressid=3
a2642c3-4c04-47f3-a5a5-a5446673223d&signature=fIvJyw2UfV2Y9mTnxmx7eMick6w%3D&command=createPortForwardingRule&privateport=22&protocol=TCP&p
ublicport=&response=json
2014-05-10 23:58:48,532 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentManager-Handler-3:null) SeqA 6-221: Processing Seq 6-221:  { Cmd , 
MgmtId: -
1, via: 6, Ver: v1, Flags: 11, 
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":4,"_loadInfo":"{\n
  \"connections\": []\
n}","wait":0}}] }
2014-05-10 23:58:48,536 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentManager-Handler-3:null) SeqA 6-221: Sending Seq 6-221:  { Ans: , MgmtId: 
290
66118877352, via: 6, Ver: v1, Flags: 100010, 
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2014-05-10 23:58:48,598 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
(catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
heck for 2-null-null-SystemCapability from cache: true
2014-05-10 23:58:48,599 DEBUG [c.c.u.AccountManagerImpl] 
(catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Root Access granted 
to A
cct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] by RoleBasedEntityAccessChecker
2014-05-10 23:58:48,601 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
(catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
heck for 2-null-null-DomainCapability from cache: false
2014-05-10 23:58:48,606 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
(catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) IAM access c
heck for 2-null-null-DomainResourceCapability from cache: false
2014-05-10 23:58:48,627 DEBUG [o.a.c.i.s.IAMServiceImpl] 
(catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Put IAM access check 
for
 2-VirtualMachine8-OperateEntry-createPortForwardingRule in cache
2014-05-10 23:58:48,650 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
(catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Account 
Acct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] does not have permission to 
access resource Ip[10.223.122.71-1] for access type: OperateEntry
2014-05-10 23:58:48,650 DEBUG [o.a.c.i.s.IAMServiceImpl] 
(catalina-exec-22:ctx-7e9bd8bb ctx-34961f5e ctx-f2fd7c7d) Put IAM access check 
for 2-IpAddress6-OperateEntry-createPortForwardingRule in cache
2014-05-10 23:58:48,651 INFO  [c.c.a.ApiServer] (catalina-exec-22:ctx-7e9bd8bb 
ctx-34961f5e ctx-f2fd7c7d) PermissionDenied: Account 
Acct[9b57332c-d8d1-11e3-a7c8-1a6f7bb0d0a8-admin] does not have permission to 
access resource Ip[10.223.122.71-1] for access type: OperateEntry on objs: []
2014-05-10 23:58:48,654 DEBUG [c.c.a.ApiServlet] (catalina-exec-22:ctx-7e9bd8bb 
ctx-34961f5e ctx-f2fd7c7d) ===END===  10.223.240.194 -- GET  
apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&virtualmachineid=eabab3fc-5229-47fe-b4b5-ae1d47c119fc&ipaddressid=3a2642c3-4c04-47f3-a5a5-a5446673223d&signature=fIvJyw2UfV2Y9mTnxmx7eMick6w%3D&command=createPortForwardingRule&privateport=22&protocol=TCP&publicport=&response=json
2014-05-10 23:58:48,809 DEBUG [c.c.a.ApiServlet] 
(catalina-exec-16:ctx-75c2ca30) ===START===  10.223.240.194 -- GET  
apiKey=leb8qPblUzbfXRSpfWRZzvgKTo1pAd3Z9S7gkvok9BGpFEm1DsuPCjMeETvbMkjOEeoNX8wgMtK7K0S7ywd5cA&command=listDomains&signature=vw1816eP4qADj2X%2FbYUVXDSnoXA%3D&response=json


  

  was:
Run  BVT suite volume.py

test case creating account, deploying vm and configuring SNAT with PF rule,

Result

PF rule creation failed with below exception 


2014-05-10 23:58:48,482 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker] 
(catalina-exec-23:ctx-bc32f45f ctx-1c7a9889 ctx-d99c5930) IAM access c
heck for 2-null-null-DomainCapability from cache: false
2014-05-10 23:

[jira] [Resolved] (CLOUDSTACK-6399) [Hyper-V][VMSync] VMSync thread does not run if all the VMs on a host are stopped from outside CS

2014-05-12 Thread Anshul Gangwar (JIRA)

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

Anshul Gangwar resolved CLOUDSTACK-6399.


Resolution: Fixed

> [Hyper-V][VMSync] VMSync thread does not run if all the VMs on a host are 
> stopped from outside CS
> -
>
> Key: CLOUDSTACK-6399
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6399
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
>Priority: Critical
>
> [Hyper-V][VMSync] VMSync thread does not run if all the VMs on a host are 
> stopped from outside CS



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


[jira] [Updated] (CLOUDSTACK-6547) [Automation] Failed to download volume in Xen with error "Failed to copy the volume from pri stor pool to sec stor pool"

2014-05-12 Thread Nitin Mehta (JIRA)

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

Nitin Mehta updated CLOUDSTACK-6547:


Assignee: edison su  (was: Nitin Mehta)

> [Automation] Failed to download volume in Xen with error "Failed to copy the 
> volume from pri stor pool to sec stor pool"
> 
>
> Key: CLOUDSTACK-6547
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6547
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes, XenServer
>Affects Versions: 4.4.0
> Environment: Branch 4.4-forward
> env xen 6.2
>Reporter: Rayees Namathponnan
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> Steps to reproduce 
> 1) Create advanced zone in xen 
> 2) Deploy a VM 
> 3) Stoped the vm and download the root volume 
> Result
> Failed to download root volume with below error 
> 2014-05-01 04:40:03,160 WARN  [o.a.c.s.d.ObjectInDataStoreManagerImpl] 
> (API-Job-Executor-38:job-490 ctx-4880d846) Unsupported data object (VO
> LUME, org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@2f9161ed), 
> no need to delete from object in store ref table
> 2014-05-01 04:40:03,162 DEBUG [c.c.v.VmWorkJobHandlerProxy] 
> (Work-Job-Executor-5:job-488/job-489 ctx-46360720) Execute VM work job: 
> com.cloud
> .vm.VmWorkStart{"dcId":1,"podId":1,"clusterId":1,"hostId":1,"rawParams":{"VmPassword":"rO0ABXQADnNhdmVkX3Bhc3N3b3Jk"},"userId":2,"accountId":2,"vmId":70,"handlerName":"VirtualMachineManagerImpl"}
> 2014-05-01 04:40:03,189 ERROR [c.c.a.ApiAsyncJobDispatcher] 
> (API-Job-Executor-38:job-490) Unexpected exception while executing 
> org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume 
> from the source primary storage pool to secondary storage.
> at 
> com.cloud.storage.VolumeApiServiceImpl.extractVolume(VolumeApiServiceImpl.java:1897)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at 
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy181.extractVolume(Unknown Source)
> at 
> org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd.execute(ExtractVolumeCmd.java:137)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:119)
> at 
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:495)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:452)
> at java.util.concurre

[jira] [Commented] (CLOUDSTACK-6617) [Automation] detach / resize volume test cases failing with permission error

2014-05-12 Thread Min Chen (JIRA)

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

Min Chen commented on CLOUDSTACK-6617:
--

Can you please attach DB dump as well?

> [Automation] detach / resize volume test cases failing  with permission error 
> --
>
> Key: CLOUDSTACK-6617
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6617
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes, Xen
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Assignee: Min Chen
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> This issue is observed in 4.4-forward automation in Xen, test case 
> integration.smoke.test_volumes.TestVolumes.test_06_download_detached_volume 
> failing with permission error 
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 
> Execute cmd: attachvolume failed, due to: errorCode: 531, 
> errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources
>  >> begin captured stdout << -
> === TestName: test_06_download_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
>  >> begin captured logging << 
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: STARTED : 
> TC: test_06_download_detached_volume :::
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Extract detached Volume 
> ID: 885ac921-4728-4903-9621-b07c5353e9bc
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Payload: {'apiKey': 
> u'WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ',
>  'virtualmachineid': u'2e1ef913-b207-4688-bbaa-408797810d3a', 'id': 
> u'885ac921-4728-4903-9621-b07c5353e9bc', 'command': 'attachVolume', 
> 'signature': 'hnLR1wCmFp5EtwMZRaS1e3J75S8=', 'response': 'json'}
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): DEBUG: Sending GET Cmd 
> : attachVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
> (1): 10.220.76.63
> requests.packages.urllib3.connectionpool: DEBUG: "GET 
> /client/api?apiKey=WnMdlxbiBLwGB6wX4NfasgbMfoaHqAiiY9oHcyYSpo6sGXsioEZbYjX7CQpMG3vJe-eCMHn_uffuYKoPpOQRuQ&virtualmachineid=2e1ef913-b207-4688-bbaa-408797810d3a&id=885ac921-4728-4903-9621-b07c5353e9bc&command=attachVolume&signature=hnLR1wCmFp5EtwMZRaS1e3J75S8%3D&response=json
>  HTTP/1.1" 531 212
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): ERROR: Exception:['Traceback 
> (most recent call last):\n', '  File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>  line 313, in __parseAndGetResponse\nresponse_cls)\n', '  File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py",
>  line 151, in getResultObj\nraise 
> cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
> 'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode: 
> 531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources\n']
> Traceback (most recent call last):
>   File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>  line 313, in __parseAndGetResponse
> response_cls)
>   File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py",
>  line 151, in getResultObj
> raise cloudstackException.CloudstackAPIException(respname, errMsg)
> CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode: 
> 531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815ad18c770-admin] does not have 
> permission to perform this operation on these resources
> test_06_download_detached_volume 
> (integration.smoke.test_volumes.TestVolumes): ERROR: marvinRequest : CmdName: 
>  
> Exception: ['Traceback (most recent call last):\n', '  File 
> "/local/jenkins/workspace/xenrt-bvt-basic-xs/work.41/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>  line 380, in marvinRequest\nraise self.__lastError\n', 
> 'CloudstackAPIException: Execute cmd: attachvolume failed, due to: errorCode: 
> 531, errorText:Acct[c0a951a5-6a6c-4845-8d0e-f815a

[jira] [Resolved] (CLOUDSTACK-6597) Updatevm - root admin should be allowed to change instance name

2014-05-12 Thread Nitin Mehta (JIRA)

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

Nitin Mehta resolved CLOUDSTACK-6597.
-

Resolution: Fixed

> Updatevm - root admin should be allowed to change instance name
> ---
>
> Key: CLOUDSTACK-6597
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6597
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Mehta
>Assignee: Nitin Mehta
> Fix For: 4.5.0
>
>
> Updatevm - Root admin should be allowed to change instance name



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


[jira] [Commented] (CLOUDSTACK-6518) [Hyper-V] Efficient way of finding the empty nic in VR

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit 4cb6c66f7568013586d0e66691aa10f9d34233ee in cloudstack's branch 
refs/heads/hyper_vpc_patches from [~rajesh_battala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4cb6c66 ]

CLOUDSTACK-6518 [Hyper-V] Efficient way of finding the empty nic in VR/VpcVR to 
configure VPC entities fixed windows line ending issues

Conflicts:

plugins/hypervisors/hyperv/DotNet/ServerResource/HypervResource/WmiCallsV2.cs


> [Hyper-V] Efficient way of finding the empty nic in VR 
> ---
>
> Key: CLOUDSTACK-6518
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6518
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Rajesh Battala
>Assignee: Rajesh Battala
>Priority: Critical
> Fix For: 4.4.0
>
>




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


[jira] [Closed] (CLOUDSTACK-6573) Multiple exceptions after upgrading from 4.3 to 4.4

2014-05-12 Thread manasaveloori (JIRA)

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

manasaveloori closed CLOUDSTACK-6573.
-

Resolution: Fixed

Closing this issue. Will open 2 separate issues for issue2 and issue3.
Issue 1 is only a Warning message in logs.

> Multiple exceptions after upgrading from 4.3 to 4.4
> ---
>
> Key: CLOUDSTACK-6573
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6573
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Upgrade
>Affects Versions: 4.4.0
> Environment: upgrade from 4.3 to 4.4
>Reporter: manasaveloori
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar, mysqldump43.dmp, mysqldump44.dmp
>
>
> 1. Deploy CS 4.3 with 2 zones using xen 6.1 and KVM hypervisor.
> 2. Configured LB rules,firewall rules.
> 3. Registered the template for 4.4 (using the naming convention  
> systemvm-xenserver-4.4,systemvm-kvm-4.4)
> 4. Upgraded to 4.4
> Start the management server:
> Below are the observations:
> Issue1:
> 2014-05-05 05:04:17,699 INFO  [c.c.s.ConfigurationServerImpl] (main:null) SSL 
> keystore located at /etc/cloudstack/management/cloud.keystore
> 2014-05-05 05:04:17,712 DEBUG [c.c.u.s.Script] (main:null) Executing: sudo 
> keytool -genkey -keystore /etc/cloudstack/management/cloud.keystore 
> -storepass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname 
> cn="Cloudstack User",ou="RHEL63test",o="RHEL63test",c="Unknown"
> 2014-05-05 05:04:17,947 DEBUG [c.c.u.s.Script] (main:null) Exit value is 1
> 2014-05-05 05:04:17,948 DEBUG [c.c.u.s.Script] (main:null) sudo: no tty 
> present and no askpass program specified
> 2014-05-05 05:04:17,950 WARN  [c.c.s.ConfigurationServerImpl] (main:null) 
> Would use fail-safe keystore to continue.
> java.io.IOException: Fail to generate certificate!: sudo: no tty present and 
> no askpass program specified
> at 
> com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:595)
> at 
> com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:623)
> at 
> com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:299)
> at 
> com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:164)
> at 
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114)
> at 
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153)
> Issue 2:
> 2014-05-05 05:05:13,567 DEBUG [c.c.s.StatsCollector] 
> (StatsCollector-4:ctx-e36f20e1) AutoScaling Monitor is running...
> 2014-05-05 05:05:13,577 ERROR [c.c.s.StatsCollector] 
> (StatsCollector-4:ctx-e36f20e1) Error trying to monitor autoscaling
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
> com.mysql.jdbc.JDBC4PreparedStatement@5b140551: SELECT autoscale_vmgroups.id, 
> autoscale_vmgroups.uuid, autoscale_vmgroups.zone_id, 
> autoscale_vmgroups.domain_id, autoscale_vmgroups.account_id, 
> autoscale_vmgroups.load_balancer_id, autoscale_vmgroups.min_members, 
> autoscale_vmgroups.max_members, autoscale_vmgroups.member_port, 
> autoscale_vmgroups.interval, autoscale_vmgroups.last_interval, 
> autoscale_vmgroups.profile_id, autoscale_vmgroups.removed, 
> autoscale_vmgroups.created, autoscale_vmgroups.state, 
> autoscale_vmgroups.display FROM autoscale_vmgroups WHERE 
> autoscale_vmgroups.removed IS NULL
> at 
> com.cloud.utils.db.GenericDaoBase.executeList(GenericDaoBase.java:1127)
> at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1150)
> at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)

[jira] [Commented] (CLOUDSTACK-6551) [Automation] Failed to revert vm snapshot in xen

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit f784f274be8aec7c8d07bcb4b569df1c6c3380af in cloudstack's branch 
refs/heads/4.4-forward from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f784f27 ]

CLOUDSTACK-6551: [Automation] Failed to revert vm snapshot in xen


> [Automation] Failed to revert vm snapshot in xen 
> -
>
> Key: CLOUDSTACK-6551
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6551
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Snapshot, XenServer
>Affects Versions: 4.4.0
> Environment: Xen 6.2
> build 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Harikrishna Patnala
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> Steps to reproduce 
> Step 1) Create advanced zone on xen 
> Step 2)  Deploy a vm 
> Step 3) create vm snapshot without memory 
> step 4) revert the snapshot 
> Result 
> Revert snapshot failed with below exception 
> 2014-05-01 06:22:19,439 DEBUG [c.c.n.NetworkModelImpl] 
> (Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Service SecurityGroup is 
> not supported in the network id=241
> 2014-05-01 06:22:19,464 DEBUG [c.c.a.t.Request] 
> (Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Seq 
> 2-5867345889533626796: Sending  { Cmd , MgmtId: 6631563722783, via: 
> 2(Rack1Pod1Host15), Ver: v1, Flags: 100011, 
> [{"com.cloud.agent.api.RevertToVMSnapshotCommand":{"reloadVm":false,"volumeTOs":[{"uuid":"ee4093bf-e6f0-49e3-be37-3b5c05fd6845","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"cb8c6c62-71ea-3269-94b9-b1c0a4055d45","id":3,"poolType":"NetworkFilesystem","host":"10.147.28.8","path":"/vol/dgVol/automation/adv/pri_3","port":2049,"url":"NetworkFilesystem://10.147.28.8/vol/dgVol/automation/adv/pri_3/?ROLE=Primary&STOREUUID=cb8c6c62-71ea-3269-94b9-b1c0a4055d45"}},"name":"ROOT-77","size":21474836480,"path":"75f283c8-db97-4b95-96c2-72d981bc7f0c","volumeId":83,"vmName":"i-2-77-VM","accountId":2,"format":"VHD","id":83,"deviceId":0,"hypervisorType":"XenServer"}],"target":{"id":3,"snapshotName":"i-2-77-VM_VS_20140501005100","type":"Disk","createTime":139890546,"current":true,"description":"Test
>  ","quiescevm":true},"vmName":"i-2-77-VM","guestOSType":"CentOS 5.6 
> (64-bit)","wait":0}}] }
> 2014-05-01 06:22:19,464 DEBUG [c.c.a.t.Request] 
> (Work-Job-Executor-32:job-541/job-542 ctx-52a5f490) Seq 
> 2-5867345889533626796: Executing:  { Cmd , MgmtId: 6631563722783, via: 
> 2(Rack1Pod1Host15), Ver: v1, Flags: 100011, 
> [{"com.cloud.agent.api.RevertToVMSnapshotCommand":{"reloadVm":false,"volumeTOs":[{"uuid":"ee4093bf-e6f0-49e3-be37-3b5c05fd6845","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"cb8c6c62-71ea-3269-94b9-b1c0a4055d45","id":3,"poolType":"NetworkFilesystem","host":"10.147.28.8","path":"/vol/dgVol/automation/adv/pri_3","port":2049,"url":"NetworkFilesystem://10.147.28.8/vol/dgVol/automation/adv/pri_3/?ROLE=Primary&STOREUUID=cb8c6c62-71ea-3269-94b9-b1c0a4055d45"}},"name":"ROOT-77","size":21474836480,"path":"75f283c8-db97-4b95-96c2-72d981bc7f0c","volumeId":83,"vmName":"i-2-77-VM","accountId":2,"format":"VHD","id":83,"deviceId":0,"hypervisorType":"XenServer"}],"target":{"id":3,"snapshotName":"i-2-77-VM_VS_20140501005100","type":"Disk","createTime":139890546,"current":true,"description":"Test
>  ","quiescevm":true},"vmName":"i-2-77-VM","guestOSType":"CentOS 5.6 
> (64-bit)","wait":0}}] }
> 2014-05-01 06:22:19,465 DEBUG [c.c.a.m.DirectAgentAttache] 
> (DirectAgent-233:ctx-acc9e792) Seq 2-5867345889533626796: Executing request
> 2014-05-01 06:22:20,084 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentManager-Handler-2:null) SeqA 8-4288: Processing Seq 8-4288:  { Cmd , 
> MgmtId: -1, via: 8, Ver: v1, Flags: 11, 
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":3,"_loadInfo":"{\n
>   \"connections\": []\n}","wait":0}}] }
> 2014-05-01 06:22:20,089 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentManager-Handler-2:null) SeqA 8-4288: Sending Seq 8-4288:  { Ans: , 
> MgmtId: 6631563722783, via: 8, Ver: v1, Flags: 100010, 
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2014-05-01 06:22:20,524 WARN  [c.c.h.x.r.CitrixResourceBase] 
> (DirectAgent-233:ctx-acc9e792) Task failed! Task record: 
> uuid: 1affb5ba-5bcf-4e86-f866-c3cbba89dff8
>nameLabel: Async.host.call_plugin
>  nameDescription:
>allowedOperations: []
>

[jira] [Commented] (CLOUDSTACK-6601) listLoadBalancers: add forDisplay parameter to the API request

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6601: added "forDisplay" parameter to listLoadBalancerRules API


> listLoadBalancers: add forDisplay parameter to the API request
> --
>
> Key: CLOUDSTACK-6601
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6601
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.4.0
>Reporter: Alena Prokharchyk
>Assignee: Alena Prokharchyk
> Fix For: 4.4.0
>
>
> As LoadBalancer rule has display flag that can be set during the 
> create/update operations, we should be able to filter enabled/disabled rules 
> via listLoadBalancers API by implementing forDisplay parameter.



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


[jira] [Commented] (CLOUDSTACK-6633) listVolumes should return template/iso info for root volumes

2014-05-12 Thread ASF subversion and git services (JIRA)

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

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

Commit 5ead629ce721a5d3291944da13ebc079f6074f91 in cloudstack's branch 
refs/heads/4.4 from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5ead629 ]

CLOUDSTACK-6633: listVolumes should return template/iso info for root volumes


> listVolumes should return template/iso info for root volumes
> 
>
> Key: CLOUDSTACK-6633
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6633
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Mehta
>Assignee: Nitin Mehta
>Priority: Critical
> Fix For: 4.4.0, 4.5.0
>
>
> listVolumes should return template/iso info for root volumes



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


[jira] [Assigned] (CLOUDSTACK-6599) Template/Volume URLs expiration functionality not working

2014-05-12 Thread Nitin Mehta (JIRA)

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

Nitin Mehta reassigned CLOUDSTACK-6599:
---

Assignee: Nitin Mehta

> Template/Volume URLs expiration functionality not working
> -
>
> Key: CLOUDSTACK-6599
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6599
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Mehta
>Assignee: Nitin Mehta
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Template / Volume Donwload URLs should expire - functionality is missing
> We have the functionality where we create download urls for volumes and 
> templates for the users. For security reasons we should expire these urls and 
> this functionality existed since 3.0.x. But it doesnt exist in 4.4 and that 
> needs to be implemented. Look at 4.2 for reference.



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