[jira] [Updated] (CLOUDSTACK-7707) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7707: Assignee: Santhosh Kumar Edukulla (was: Jayapal Reddy) > Triage and fix Coverity defects > --- > > Key: CLOUDSTACK-7707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.5.0 > > > 1. We have Coverity setup available, running as scheduled and individual > owners are assigned with analyzed bugs. > 2. As part of this bug, please triage and fix the relevant Coverity bugs > assigned. It could be a count as small as 25 bugs. > 3. First start with high impact in order to others later. > 4. We can either triage them accordingly as fix required or false positive or > not a bug accordingly. But, triage and fix accordingly wherever relevant and > applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7707) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-7707. - Resolution: Fixed Fixed resource leaks, null de references, invalid boxing unboxing issues. > Triage and fix Coverity defects > --- > > Key: CLOUDSTACK-7707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.5.0 > > > 1. We have Coverity setup available, running as scheduled and individual > owners are assigned with analyzed bugs. > 2. As part of this bug, please triage and fix the relevant Coverity bugs > assigned. It could be a count as small as 25 bugs. > 3. First start with high impact in order to others later. > 4. We can either triage them accordingly as fix required or false positive or > not a bug accordingly. But, triage and fix accordingly wherever relevant and > applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7707) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-7707. --- > Triage and fix Coverity defects > --- > > Key: CLOUDSTACK-7707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.6.0 > > > 1. We have Coverity setup available, running as scheduled and individual > owners are assigned with analyzed bugs. > 2. As part of this bug, please triage and fix the relevant Coverity bugs > assigned. It could be a count as small as 25 bugs. > 3. First start with high impact in order to others later. > 4. We can either triage them accordingly as fix required or false positive or > not a bug accordingly. But, triage and fix accordingly wherever relevant and > applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7707) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7707: Component/s: Management Server > Triage and fix Coverity defects > --- > > Key: CLOUDSTACK-7707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.6.0 > > > 1. We have Coverity setup available, running as scheduled and individual > owners are assigned with analyzed bugs. > 2. As part of this bug, please triage and fix the relevant Coverity bugs > assigned. It could be a count as small as 25 bugs. > 3. First start with high impact in order to others later. > 4. We can either triage them accordingly as fix required or false positive or > not a bug accordingly. But, triage and fix accordingly wherever relevant and > applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7707) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7707: Fix Version/s: (was: 4.5.0) 4.6.0 > Triage and fix Coverity defects > --- > > Key: CLOUDSTACK-7707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.6.0 > > > 1. We have Coverity setup available, running as scheduled and individual > owners are assigned with analyzed bugs. > 2. As part of this bug, please triage and fix the relevant Coverity bugs > assigned. It could be a count as small as 25 bugs. > 3. First start with high impact in order to others later. > 4. We can either triage them accordingly as fix required or false positive or > not a bug accordingly. But, triage and fix accordingly wherever relevant and > applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7707) Triage and fix Coverity defects
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209668#comment-14209668 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-7707: - ef6ec7b27675ea44d45c68b30eb2f508655703be > Triage and fix Coverity defects > --- > > Key: CLOUDSTACK-7707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.6.0 > > > 1. We have Coverity setup available, running as scheduled and individual > owners are assigned with analyzed bugs. > 2. As part of this bug, please triage and fix the relevant Coverity bugs > assigned. It could be a count as small as 25 bugs. > 3. First start with high impact in order to others later. > 4. We can either triage them accordingly as fix required or false positive or > not a bug accordingly. But, triage and fix accordingly wherever relevant and > applicable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6870) getDomainId implementation returns invalid value at places
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Kumar Edukulla updated CLOUDSTACK-6870:
Fix Version/s: (was: 4.5.0)
Future
> getDomainId implementation returns invalid value at places
> --
>
> Key: CLOUDSTACK-6870
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6870
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.4.0
>Reporter: Santhosh Kumar Edukulla
>Assignee: Santhosh Kumar Edukulla
> Fix For: Future
>
>
> Few classes implementing getDomainId derived from the below interface, seems
> to have invalid value returned for domainid. EX: VMTemplateVO, implementing
> this method returns -1. This behavior is creating issues at some places in
> code.
> The respective tables EX: vm_template dont have column say domainid and so
> it returns -1.
> Though the domainid information is available with account and domain tables,
> it is not able to retrieve this information because of some api semantics.
> This bug is logged to track and provide fix for this issue. We can discuss as
> either adding a column is apt way or a better way to refactor few apis to get
> this information done with out adding extra columns.
> */
> public interface PartOf {
> /**
> * @return domain id that the object belongs to.
> */
> long getDomainId();
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6648) [Automation]: vm ha cases were failing in 4.4-forward
[ 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] [Created] (CLOUDSTACK-6648) [Automation]: vm ha cases were failing in 4.4-forward
Santhosh Kumar Edukulla created CLOUDSTACK-6648: --- Summary: [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 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] [Resolved] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error "Can only support create Private VLAN network with IPv4!"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6627. - Resolution: Fixed Issue is now fixed. > [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-6550) [Automation] list**** API return empty list if you are not passing listall=true, many testcases failed due to this
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996087#comment-13996087 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6550: - Added changes for cases where listAll is required as per new design. This was discussed with team and changes were made. As such no decision to revert or add the listall on product side is done, testcases were getting effected. Added those changes. > [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] [Closed] (CLOUDSTACK-6648) [Automation]: vm ha cases were failing in 4.4-forward
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6648. --- > [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] [Commented] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error "Can only support create Private VLAN network with IPv4!"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994997#comment-13994997
]
Santhosh Kumar Edukulla commented on CLOUDSTACK-6627:
-
Looking at this bug, I didn't see any issue in the CS code for this.
1. Here we are verifying to create a ipv6 network with isolated pvlan support,
and product is appropriately reporting that creating pvlan with ipv6 is not
supported under NetworkServiceImpl.java( line 1201)
if (isolatedPvlan != null && ipv6) {
throw new InvalidParameterValueException("Can only support create
Private VLAN network with IPv4!");
}
2. The issue is with test case, we should verify for exception from CS. Here,
at below line, it need to be verified for exception instead of return status
(line 85) under test_pvlan.py.
self.assertEqual(createNetworkResponse, FAILED, "Creating PVLAN with IPv6
should fail").
3. Fixed TC and tested, It now works.
> [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] [Closed] (CLOUDSTACK-6627) [Automation] createNetwork API failing with error "Can only support create Private VLAN network with IPv4!"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6627. --- > [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-6562) [Automation] [XenServer] Secondary Storage count for account shows double the value of the desired count
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996299#comment-13996299 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6562: - Hello Ashutosh, Looking at the bug, i didnt see the issue. Where exactly we see the size to double for account when template is downloaded? Did we mean on dashboard, secondary storage allocated value for a given zone ? https://issues.apache.org/jira/browse/CLOUDSTACK-6562 Please add some steps to reproduce as well snapshot explaining the issue. Let me know. Santhosh > [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] [Resolved] (CLOUDSTACK-6550) [Automation] list**** API return empty list if you are not passing listall=true, many testcases failed due to this
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6550. - Resolution: Fixed > [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] [Created] (CLOUDSTACK-6708) [Automation]: Few suites were failing on simulator run
Santhosh Kumar Edukulla created CLOUDSTACK-6708: --- Summary: [Automation]: Few suites were failing on simulator run Key: CLOUDSTACK-6708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6708 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure integration.smoke.test_hosts.TestHosts.test_01_clusters integration.smoke.test_network.TestDeleteAccount.test_delete_account integration.smoke.test_network.TestPublicIP.test_public_ip_admin_account integration.smoke.test_network.TestReleaseIP.test_releaseIP integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_08_migrate_vm integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6736) [Automation]: Fix few script issues.
Santhosh Kumar Edukulla created CLOUDSTACK-6736: --- Summary: [Automation]: Fix few script issues. Key: CLOUDSTACK-6736 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6736 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.4.0 Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla 1. ParsedConfig is getting corrupted when used in tests. 2. setup.py does not have minimal version requirements for various packages. Added that. 3. Fixed few misc script issues and removed print statements. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6736) [Automation]: Fix few script issues.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-6736: Description: 1. ParsedConfig is getting corrupted when used in tests. Fixed now. 2. setup.py does not have minimal version requirements for various packages. Added that. 3. Fixed few misc script issues and removed print statements. 4. Added bug information to failed cases. was: 1. ParsedConfig is getting corrupted when used in tests. 2. setup.py does not have minimal version requirements for various packages. Added that. 3. Fixed few misc script issues and removed print statements. > [Automation]: Fix few script issues. > - > > Key: CLOUDSTACK-6736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > 1. ParsedConfig is getting corrupted when used in tests. Fixed now. > 2. setup.py does not have minimal version requirements for various packages. > Added that. > 3. Fixed few misc script issues and removed print statements. > 4. Added bug information to failed cases. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6158) [Marvin]: DeployDataCenter Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6158. - Resolution: Fixed > [Marvin]: DeployDataCenter Enhancements > --- > > Key: CLOUDSTACK-6158 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6158 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Following are the issues with deploy data center: > 1. There is no way to delete a data center created earlier. Added a new > DeleteDataCenter Interface to delete the earlier created datacenter. If user > wants to delete a datacenter created and recreate, deleting has to be manual > earlier. With this change, he can delete a data center created earlier. It > will be useful at many places for testing to destroy and recreate with new > settings etc. > 2. when deploy data center runs, it does not adequately verifies whether a > given entry is created or not, it just continues. Added checks to see if an > entry is not successful, it reports, dumps to log and exit gracefully. > 3. DataCenter creation as Transaction : At any given point of time during > deploy data center, if an issue happens half way through, earlier created > entries were still available in CS, it wont clean up i.e., data center is > half created, Again, if tried to recreate , the earlier existing entries > wont allow to recreate. Now, data center works as transaction, either all > entries are created as part of data center or none, added a clean up to > delete the half created data center. > 4. Export the created Data Center so that user can use it to further delete > the data center with these exported entries etc. > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6736) [Automation]: Fix few script issues.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6736. - Resolution: Fixed > [Automation]: Fix few script issues. > - > > Key: CLOUDSTACK-6736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > 1. ParsedConfig is getting corrupted when used in tests. Fixed now. > 2. setup.py does not have minimal version requirements for various packages. > Added that. > 3. Fixed few misc script issues and removed print statements. > 4. Added bug information to failed cases. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5973) [Automation]: Exceptions for resource clean up under test_add_remove_network.py
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Kumar Edukulla closed CLOUDSTACK-5973.
---
> [Automation]: Exceptions for resource clean up under
> test_add_remove_network.py
> ---
>
> Key: CLOUDSTACK-5973
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5973
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, marvin
>Reporter: Santhosh Kumar Edukulla
>Assignee: Santhosh Kumar Edukulla
> Fix For: 4.3.0
>
>
> 2014-01-21 17:06:33,812 - CRITICAL - test_24_add_nw_different_domain
> (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine)
> - EXCEPTION: test_24_add_nw_different_domain: Traceback (most recent call
> last):
> File "/usr/local/lib/python2.7/unittest/case.py", line 356, in run
> self.tearDown()
> File
> "/DataDisk/temp/cloudstack/test/integration/component/test_add_remove_network.py",
> line 259, in tearDown
> raise Exception("Warning: Exception during cleanup : %s" % e)
> Exception: Warning: Exception during cleanup : Execute cmd: asyncquery
> failed, due to: {errorcode : 530, errortext : u"Can't delete the domain yet
> because it has 1 accounts to cleanup"}
> 2014-01-21 17:12:30,046 - CRITICAL - test_25_add_nw_above_account_limit
> (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine)
> - EXCEPTION: test_25_add_nw_above_account_limit: Traceback (most recent call
> last):
> File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 227, in run
> self.tearDown()
> File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 350, in tearDown
> self.teardownContext(ancestor)
> File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 366, in teardownContext
> try_run(context, names)
> File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/util.py",
> line 469, in try_run
> return func()
> File
> "/DataDisk/temp/cloudstack/test/integration/component/test_add_remove_network.py",
> line 273, in tearDownClass
> raise Exception("Warning: Exception during cleanup : %s" % e)
> Exception: Warning: Exception during cleanup : Execute cmd:
> deletenetworkoffering failed, due to: errorCode: 431, errorText:Can't delete
> network offering 47 as its used by 2 networks. To make the network offering
> unavaiable, disable it
> 2014-01-21 17:16:59,203 - CRITICAL - test_17_add_nic_different_zone
> (integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM)
> - EXCEPTION: test_17_add_nic_different_zone: Traceback (most recent call
> last):
> File "/usr/local/lib/python2.7/unittest/case.py", line 356, in run
> self.tearDown()
> File
> "/DataDisk/temp/cloudstack/test/integration/component/test_add_remove_network.py",
> line 1135, in tearDown
> raise Exception("Warning: Exception during cleanup : %s" % e)
> Exception: Warning: Exception during cleanup : Execute cmd: asyncquery
> failed, due to: {errorcode : 530, errortext : u'Failed to delete network'}
> 2014-01-21 17:17:50,915 - CRITICAL - test_26_add_nic_insufficient_permission
> (integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM)
> - EXCEPTION: test_26_add_nic_insufficient_permission: Traceback (most recent
> call last):
> File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 227, in run
> self.tearDown()
> File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 350, in tearDown
> self.teardownContext(ancestor)
> File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 366, in teardownContext
> try_run(context, names)
> File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/util.py",
> line 469, in try_run
> return func()
> File
> "/DataDisk/temp/cloudstack/test/integration/component/test_add_remove_network.py",
> line 1147, in tearDownClass
> raise Exception("Warning: Exception during cleanup : %s" % e)
> Exception: Warning: Exception during cleanup : Execute cmd:
> deletenetworkoffering failed, due to: errorCode: 431, errorText:Can't delete
> network offering 51 as its used by 1 networks. To make the network offering
> unavaiable, disable it
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6529) deployDatacCenter.py script fails when there is more than one host in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-6529: --- Assignee: Santhosh Kumar Edukulla > deployDatacCenter.py script fails when there is more than one host in a > cluster. > > > Key: CLOUDSTACK-6529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Bharat kumar >Assignee: Santhosh Kumar Edukulla > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6529) deployDatacCenter.py script fails when there is more than one host in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007097#comment-14007097 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6529: - It was mentioned that for xenserver addition, where a cluster with list of hosts in a pool, we need to add just master to add all hosts to CS. If post master host addition, any other host addition will fail. In deployDataCenter when a host addition fails, it is not continuing further. Added a change, to continue adding all hosts, even if any addition fails. Do a cleanup only when all host addition fails. Tested the changes on local setup Thanks! Santhosh > deployDatacCenter.py script fails when there is more than one host in a > cluster. > > > Key: CLOUDSTACK-6529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Bharat kumar >Assignee: Santhosh Kumar Edukulla > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6529) deployDatacCenter.py script fails when there is more than one host in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007097#comment-14007097 ] Santhosh Kumar Edukulla edited comment on CLOUDSTACK-6529 at 5/23/14 12:36 PM: --- In deployDataCenter when a host addition fails, it is not continuing further. Added a change, to continue adding all hosts, even if any addition fails. Do a cleanup only when all host addition fails. Tested the changes on local setup Thanks! Santhosh was (Author: santhoshe): It was mentioned that for xenserver addition, where a cluster with list of hosts in a pool, we need to add just master to add all hosts to CS. If post master host addition, any other host addition will fail. In deployDataCenter when a host addition fails, it is not continuing further. Added a change, to continue adding all hosts, even if any addition fails. Do a cleanup only when all host addition fails. Tested the changes on local setup Thanks! Santhosh > deployDatacCenter.py script fails when there is more than one host in a > cluster. > > > Key: CLOUDSTACK-6529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Bharat kumar >Assignee: Santhosh Kumar Edukulla > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of iso retrieval path
Santhosh Kumar Edukulla created CLOUDSTACK-6794:
---
Summary: [Automation]: test_iso suite is failing because of iso
retrieval path
Key: CLOUDSTACK-6794
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6794
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation
Reporter: Santhosh Kumar Edukulla
>From the environment, where bvt is running, the path to download iso was not
>reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
>downloading iso and the setup either need to have access to the this url or
>url path for local share has to be used, still otherwise these suites will
>fail.
"iso": {
"displaytext": "Test ISO",
"name": "ISO",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"bootable": False,
"ispublic": False,
"ostype": "CentOS 5.6 (64-bit)",
},
"iso1": {
"displaytext": "Test ISO 1",
"name": "ISO 1",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"isextractable": True,
"isfeatured": True,
"ispublic": True,
"ostype": "CentOS 5.6 (64-bit)",
},
"iso2": {
"displaytext": "Test ISO 2",
"name": "ISO 2",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"isextractable": True,
"isfeatured": True,
"ispublic": True,
"ostype": "CentOS 5.6 (64-bit)",
"mode": 'HTTP_DOWNLOAD',
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of no path to iso retrieval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Kumar Edukulla updated CLOUDSTACK-6794:
Summary: [Automation]: test_iso suite is failing because of no path to iso
retrieval (was: [Automation]: test_iso suite is failing because of iso
retrieval path)
> [Automation]: test_iso suite is failing because of no path to iso retrieval
> ---
>
> Key: CLOUDSTACK-6794
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6794
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Santhosh Kumar Edukulla
>
> From the environment, where bvt is running, the path to download iso was not
> reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
> downloading iso and the setup either need to have access to the this url or
> url path for local share has to be used, still otherwise these suites will
> fail.
> "iso": {
> "displaytext": "Test ISO",
> "name": "ISO",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "bootable": False,
> "ispublic": False,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso1": {
> "displaytext": "Test ISO 1",
> "name": "ISO 1",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso2": {
> "displaytext": "Test ISO 2",
> "name": "ISO 2",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> "mode": 'HTTP_DOWNLOAD',
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of no path to iso retrieval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Kumar Edukulla reassigned CLOUDSTACK-6794:
---
Assignee: Abhinandan Prateek
> [Automation]: test_iso suite is failing because of no path to iso retrieval
> ---
>
> Key: CLOUDSTACK-6794
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6794
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Santhosh Kumar Edukulla
>Assignee: Abhinandan Prateek
>
> From the environment, where bvt is running, the path to download iso was not
> reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
> downloading iso and the setup either need to have access to the this url or
> url path for local share has to be used, still otherwise these suites will
> fail.
> "iso": {
> "displaytext": "Test ISO",
> "name": "ISO",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "bootable": False,
> "ispublic": False,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso1": {
> "displaytext": "Test ISO 1",
> "name": "ISO 1",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso2": {
> "displaytext": "Test ISO 2",
> "name": "ISO 2",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> "mode": 'HTTP_DOWNLOAD',
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of no path to iso retrieval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Kumar Edukulla updated CLOUDSTACK-6794:
Description:
>From the environment, where bvt is running, the path to download iso was not
>reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
>downloading iso and the setup either need to have access to the this url or
>url path for local share has to be used, still otherwise these suites will
>fail.
"iso": {
"displaytext": "Test ISO",
"name": "ISO",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"bootable": False,
"ispublic": False,
"ostype": "CentOS 5.6 (64-bit)",
},
"iso1": {
"displaytext": "Test ISO 1",
"name": "ISO 1",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"isextractable": True,
"isfeatured": True,
"ispublic": True,
"ostype": "CentOS 5.6 (64-bit)",
},
"iso2": {
"displaytext": "Test ISO 2",
"name": "ISO 2",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"isextractable": True,
"isfeatured": True,
"ispublic": True,
"ostype": "CentOS 5.6 (64-bit)",
"mode": 'HTTP_DOWNLOAD',
Test Suite Exception Trace:
File
"/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
line 208, in run
self.setUp()
File
"/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
line 291, in setUp
self.setupContext(ancestor)
File
"/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
line 314, in setupContext
try_run(context, names)
File
"/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/util.py",
line 470, in try_run
return func()
File
"/automation/virtenv/00-16-3e-5d-4a-0e/306/test/integration/smoke/test_iso.py",
line 188, in setUpClass
% (cls.iso_1.id, e))
'Exception while downloading ISO d64c0284-8a03-42a1-8ce6-e6d2c53724ea: Error In
Downloading ISO: ISO Status - No route to host\n >> begin
captured stdout << -\n=== TestName: None | Status :
EXCEPTION ===\n\n
was:
>From the environment, where bvt is running, the path to download iso was not
>reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
>downloading iso and the setup either need to have access to the this url or
>url path for local share has to be used, still otherwise these suites will
>fail.
"iso": {
"displaytext": "Test ISO",
"name": "ISO",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"bootable": False,
"ispublic": False,
"ostype": "CentOS 5.6 (64-bit)",
},
"iso1": {
"displaytext": "Test ISO 1",
"name": "ISO 1",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"isextractable": True,
"isfeatured": True,
"ispublic": True,
"ostype": "CentOS 5.6 (64-bit)",
},
"iso2": {
"displaytext": "Test ISO 2",
"name": "ISO 2",
"url": "http://people.apache.org/~tsp/dummy.iso";,
"isextractable": True,
"isfeatured": True,
"ispublic": True,
"ostype": "CentOS 5.6 (64-bit)",
"mode": 'HTTP_DOWNLOAD',
> [Automation]: test_iso suite is failing because of no path to iso retrieval
> ---
>
> Key: CLOUDSTACK-6794
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6794
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Santhosh Kumar Edukulla
>Assignee: Abhinandan Prateek
>
> From the environment, where bvt is running, the path to download iso was not
> reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
> downloading iso and the setup either need to have access to the this url or
> url path for local share has to be used, still otherwise these suites will
> fail.
> "iso": {
> "displaytext": "Test ISO",
> "name": "ISO",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "bootable": False,
> "ispublic": False,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso1": {
> "displaytext": "Test ISO 1",
> "name": "ISO 1",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso2": {
> "d
[jira] [Resolved] (CLOUDSTACK-6529) deployDatacCenter.py script fails when there is more than one host in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6529. - Resolution: Fixed > deployDatacCenter.py script fails when there is more than one host in a > cluster. > > > Key: CLOUDSTACK-6529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Bharat kumar >Assignee: Santhosh Kumar Edukulla > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6389) test__01_nic requires advanced zone but it tagged as basic test case
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Kumar Edukulla resolved CLOUDSTACK-6389.
-
Resolution: Fixed
> test__01_nic requires advanced zone but it tagged as basic test case
>
>
> Key: CLOUDSTACK-6389
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6389
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Chethan Krishnappa
>Assignee: Santhosh Kumar Edukulla
>
> test_nic.py which is under smoke tests is tagged as basic mode test but test
> runs only if the zone is advanced.
> if zone.networktype != 'Advanced':
> self.skipTest("Cannot run this test with a basic zone, please
> use advanced!")
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6708) [Automation]: Few suites were failing on simulator run
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6708. - Resolution: Fixed > [Automation]: Few suites were failing on simulator run > -- > > Key: CLOUDSTACK-6708 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6708 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure > integration.smoke.test_hosts.TestHosts.test_01_clusters > integration.smoke.test_network.TestDeleteAccount.test_delete_account > integration.smoke.test_network.TestPublicIP.test_public_ip_admin_account > integration.smoke.test_network.TestReleaseIP.test_releaseIP > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_08_migrate_vm > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6389) test__01_nic requires advanced zone but it tagged as basic test case
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Kumar Edukulla closed CLOUDSTACK-6389.
---
> test__01_nic requires advanced zone but it tagged as basic test case
>
>
> Key: CLOUDSTACK-6389
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6389
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Chethan Krishnappa
>Assignee: Santhosh Kumar Edukulla
>
> test_nic.py which is under smoke tests is tagged as basic mode test but test
> runs only if the zone is advanced.
> if zone.networktype != 'Advanced':
> self.skipTest("Cannot run this test with a basic zone, please
> use advanced!")
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6529) deployDatacCenter.py script fails when there is more than one host in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6529. --- > deployDatacCenter.py script fails when there is more than one host in a > cluster. > > > Key: CLOUDSTACK-6529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Bharat kumar >Assignee: Santhosh Kumar Edukulla > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6708) [Automation]: Few suites were failing on simulator run
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6708. --- > [Automation]: Few suites were failing on simulator run > -- > > Key: CLOUDSTACK-6708 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6708 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > integration.smoke.test_deploy_vm.TestDeployVMStartFailure.test_deploy_vm_start_failure > integration.smoke.test_hosts.TestHosts.test_01_clusters > integration.smoke.test_network.TestDeleteAccount.test_delete_account > integration.smoke.test_network.TestPublicIP.test_public_ip_admin_account > integration.smoke.test_network.TestReleaseIP.test_releaseIP > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_08_migrate_vm > integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_09_expunge_vm -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-6793: --- Assignee: Santhosh Kumar Edukulla (was: Amogh Vasekar) > [Automation] CreateTagsCmd fails with db exceptions > > > Key: CLOUDSTACK-6793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: KVM >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar > > > Steps to reproduce > Execute the test case integration.component.test_tags.TestResourceTags > Test case perform below steps > # 1. Create a tag on template/ISO using createTags API > # 2. Delete above created tag using deleteTags API > 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] > (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END=== > 10.223.240.193 -- GET > apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd > EQ&resourcetype=Template&resourceIds=35e10eef-7980-4085-8b6c-c68174f1b529&command=createTags&signature=pIJSk7ekg0Tlf > RN%2FWfdp8U42Bgs%3D&tags%5B0%5D.key=OS&response=json&tags%5B0%5D.value=CentOS > 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin > g back the transaction: Time = 4 Name = API-Job-Executor-89; called by > -TransactionLegacy.rollback:903-TransactionL > egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation. > proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2 > 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn > Transaction:25-Transaction$2.doInTransaction:49 > 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] > (catalina-exec-22:ctx-dbbc3135) ===START=== 10.223.240.193 -- GET > > jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642&apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z > 1t-oO1g9F4-EiUZx9BdEQ&command=queryAsyncJobResult&response=json&signature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D > 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while > executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags > (resource_tags.uuid, resource_tags.key, resource_tags.value, > resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, > resource_tags.resource_uuid, resource_tags.resource_type, > resource_tags.customer) VALUES > (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', > -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null) > at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400) > at sun.reflect.GeneratedMethodAccessor98.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 > 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.$Proxy52.persist(Unknown Source) > at > com.cloud.tags.TaggedResourceManagerImpl$1.doInTransactionWithoutResult(TaggedResourceManagerImpl.java:245) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transa
[jira] [Assigned] (CLOUDSTACK-6791) [Automation] DeleteNetworkCmd fails with NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-6791: --- Assignee: Santhosh Kumar Edukulla > [Automation] DeleteNetworkCmd fails with NullPointerException > - > > Key: CLOUDSTACK-6791 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6791 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: Automation > 4.4-forward > vmware 5.0 >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > > This issue is observed with automation run , while executing test > integration.component.test_multiple_ips_per_nic.TestBasicOperations.test_add_ip_to_nic_2_SHARED > Test case performs below operations > 225 # Steps: > 226 # 1. Create Account and create network in it (isoalted/ shared/ > vpc) > 227 # 2. Deploy a VM in this network and account > 228 # 3. Add secondary IP to the default nic of VM > 229 # 4. Try to add the same IP again > 230 # 5. Try to add secondary IP providing wrong virtual machine id > 231 # 6. Try to add secondary IP with correct virtual machine id but > wrong IP address > # 7 Destroy account > 232 > 233 # Validations: > 234 # 1. Step 3 should succeed > 235 # 2. Step 4 should fail > 236 # 3. Step 5 should should fail > 237 # 4. Step 6 should fail > This issue observed during account deletion > 2014-05-26 19:18:52,169 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Network id=616 is > destroyed successfully, cleaning up corresponding resources now. > 2014-05-26 19:18:52,170 DEBUG [c.c.n.g.DirectNetworkGuru] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Releasing ip > 172.16.27.1 of placeholder nic Nic[1645-null-null-172.16.27.1] > 2014-05-26 19:18:52,171 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Rolling back the > transaction: Time = 2 Name = API-Job-Executor-41; called by > -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-Transaction.execute:46-DirectNetworkGuru.trash:327-NetworkOrchestrator$10.doInTransactionWithoutResult:2226-TransactionCallbackNoReturn.doInTransaction:25-Transaction$2.doInTransaction:49-Transaction.execute:37-Transaction.execute:46-NetworkOrchestrator.destroyNetwork:2221 > 2014-05-26 19:18:52,183 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-41:ctx-b247339e job-5716) Unexpected exception while > executing org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd > java.lang.NullPointerException > at > com.cloud.network.guru.DirectNetworkGuru$3.doInTransactionWithoutResult(DirectNetworkGuru.java:334) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > com.cloud.network.guru.DirectNetworkGuru.trash(DirectNetworkGuru.java:327) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransactionWithoutResult(NetworkOrchestrator.java:2226) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2221) > at > com.cloud.network.NetworkServiceImpl.deleteNetwork(NetworkServiceImpl.java:1828) > at sun.reflect.GeneratedMethodAccessor729.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.ja
[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019735#comment-14019735 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6793: - 1. Added fix to retrieve the correct domain id for a given accountid. vm_template table and respective vo, does not have a domain id information. 2. Added logic to retrieve correct domainid for a given accountid when an invalid domainid is retrieved. Now, creation of tags is getting successful post the fix. We have to add more enhancements for implementation of getDomainId under VmTemplateVO, required to add proper schema changes and dao persist and usage changes for vm_template table. This can be enhanced in future. > [Automation] CreateTagsCmd fails with db exceptions > > > Key: CLOUDSTACK-6793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: KVM >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar > > > Steps to reproduce > Execute the test case integration.component.test_tags.TestResourceTags > Test case perform below steps > # 1. Create a tag on template/ISO using createTags API > # 2. Delete above created tag using deleteTags API > 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] > (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END=== > 10.223.240.193 -- GET > apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd > EQ&resourcetype=Template&resourceIds=35e10eef-7980-4085-8b6c-c68174f1b529&command=createTags&signature=pIJSk7ekg0Tlf > RN%2FWfdp8U42Bgs%3D&tags%5B0%5D.key=OS&response=json&tags%5B0%5D.value=CentOS > 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin > g back the transaction: Time = 4 Name = API-Job-Executor-89; called by > -TransactionLegacy.rollback:903-TransactionL > egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation. > proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2 > 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn > Transaction:25-Transaction$2.doInTransaction:49 > 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] > (catalina-exec-22:ctx-dbbc3135) ===START=== 10.223.240.193 -- GET > > jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642&apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z > 1t-oO1g9F4-EiUZx9BdEQ&command=queryAsyncJobResult&response=json&signature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D > 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while > executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags > (resource_tags.uuid, resource_tags.key, resource_tags.value, > resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, > resource_tags.resource_uuid, resource_tags.resource_type, > resource_tags.customer) VALUES > (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', > -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null) > at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400) > at sun.reflect.GeneratedMethodAccessor98.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 > 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.framewor
[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019785#comment-14019785 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6793: - Commit Information: https://reviews.apache.org/r/19874/ > [Automation] CreateTagsCmd fails with db exceptions > > > Key: CLOUDSTACK-6793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: KVM >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar > > > Steps to reproduce > Execute the test case integration.component.test_tags.TestResourceTags > Test case perform below steps > # 1. Create a tag on template/ISO using createTags API > # 2. Delete above created tag using deleteTags API > 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] > (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END=== > 10.223.240.193 -- GET > apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd > EQ&resourcetype=Template&resourceIds=35e10eef-7980-4085-8b6c-c68174f1b529&command=createTags&signature=pIJSk7ekg0Tlf > RN%2FWfdp8U42Bgs%3D&tags%5B0%5D.key=OS&response=json&tags%5B0%5D.value=CentOS > 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin > g back the transaction: Time = 4 Name = API-Job-Executor-89; called by > -TransactionLegacy.rollback:903-TransactionL > egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation. > proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2 > 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn > Transaction:25-Transaction$2.doInTransaction:49 > 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] > (catalina-exec-22:ctx-dbbc3135) ===START=== 10.223.240.193 -- GET > > jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642&apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z > 1t-oO1g9F4-EiUZx9BdEQ&command=queryAsyncJobResult&response=json&signature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D > 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while > executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags > (resource_tags.uuid, resource_tags.key, resource_tags.value, > resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, > resource_tags.resource_uuid, resource_tags.resource_type, > resource_tags.customer) VALUES > (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', > -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null) > at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400) > at sun.reflect.GeneratedMethodAccessor98.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 > 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.$Proxy52.persist(Unknown Source) > at > com.cloud.tags.TaggedResourceManagerImpl$1.doInTransactionWithoutResult(TaggedResourceManagerImpl.java:245) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java
[jira] [Created] (CLOUDSTACK-6856) Fixed few TCs failing in master.
Santhosh Kumar Edukulla created CLOUDSTACK-6856: --- Summary: Fixed few TCs failing in master. Key: CLOUDSTACK-6856 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6856 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, marvin Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. Fixed few cases failing because of some data corruption. 2. Added proper to retries to few cases where check is done immediately after operation. 3. Added setup.py changes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020258#comment-14020258 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6793: - Nitin, First thing, we are not masking the surface of current bug again nor is the intention, when getDomainId concrete implementation was adde earlier, with a return of -1, i believe people were aware of its consequences. It seems these were failing since earlier versions as well, nor it was made a blocker any time. We are aware of schema change required for vm_template table, respective implementation under its respective ORM entity and its references when a new column is added. So is the reason to mention a note here that more enhancements will be done with few relevant info. I mentioned the same note in the group as well, when thinking of applying it to master. Now, another question was, is it the right way to add a column wherever required, then we are not making any use of proper relational mapping of tables, EX: account and domain are properly related, so a simple relation through a cross between multiple entities should fetch domain id required( provided getDomainid for vmtemplatevo has a definite meaning). i.e., Expect domain id to be retrieved based upon account id only, rather than adding domain_id to template table, if we see domainid column is not the proper mapping to vm_template table. Now, the question was to add a column to the table and respective reference changes for DML,DDL in code or make the interface changes for getDomainid or alter its original purpose for this derived class of vmtemplatevo, so is the reason of mentioning a note here to the bug with more changes post the release will be taken care. The current fix in a way will not counter effect any existing workflows, nor it breaks. Lastly, I was ready to do the above mentioned changes as well, but after discussing here, only realized that its not proper to make schema and its reference changes now during the time of near to release for ASF. I agree with you that the current issue, i believe is taken care, now more better way as mentioned will be added in future releases. We as well discussed to log a separate bug to track the similar issue, so is the reason for not closing this bug as well. > [Automation] CreateTagsCmd fails with db exceptions > > > Key: CLOUDSTACK-6793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: KVM >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar > > > Steps to reproduce > Execute the test case integration.component.test_tags.TestResourceTags > Test case perform below steps > # 1. Create a tag on template/ISO using createTags API > # 2. Delete above created tag using deleteTags API > 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] > (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END=== > 10.223.240.193 -- GET > apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd > EQ&resourcetype=Template&resourceIds=35e10eef-7980-4085-8b6c-c68174f1b529&command=createTags&signature=pIJSk7ekg0Tlf > RN%2FWfdp8U42Bgs%3D&tags%5B0%5D.key=OS&response=json&tags%5B0%5D.value=CentOS > 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin > g back the transaction: Time = 4 Name = API-Job-Executor-89; called by > -TransactionLegacy.rollback:903-TransactionL > egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation. > proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2 > 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn > Transaction:25-Transaction$2.doInTransaction:49 > 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] > (catalina-exec-22:ctx-dbbc3135) ===START=== 10.223.240.193 -- GET > > jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642&apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z > 1t-oO1g9F4-EiUZx9BdEQ&command=queryAsyncJobResult&response=json&signature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D > 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while > executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd > com.cloud.uti
[jira] [Created] (CLOUDSTACK-6860) DataCenter creation is failing DevCloud in 4.4 with error failing initialize agent.
Santhosh Kumar Edukulla created CLOUDSTACK-6860: --- Summary: DataCenter creation is failing DevCloud in 4.4 with error failing initialize agent. Key: CLOUDSTACK-6860 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6860 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: DevCloud Affects Versions: 4.4.0 Reporter: Santhosh Kumar Edukulla Deploying a datacenter in devcloud is failing, few of the exceptions seen in log are below, 1. com.cloud.utils.exception.CloudRuntimeException: Cannot create directory /opt/cloud/bin on XenServer hosts com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4846) 2. 014-06-03 18:08:20,790 WARN [c.c.r.ResourceManagerImpl] (ApiServer-3:ctx-f7cfbcb4 ctx-a1a82b64) Unable to connect due to com.cloud.exception.ConnectionException: Reinitialize agent after setup. com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:656) Steps: 1. Import Devcloud image 2. Run deploy DataCenter script to create a data center -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6860) DataCenter creation is failing DevCloud in 4.4, failing to initialize agent.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-6860: Summary: DataCenter creation is failing DevCloud in 4.4, failing to initialize agent. (was: DataCenter creation is failing DevCloud in 4.4 with error failing initialize agent. ) > DataCenter creation is failing DevCloud in 4.4, failing to initialize agent. > - > > Key: CLOUDSTACK-6860 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6860 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: DevCloud >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla > > Deploying a datacenter in devcloud is failing, few of the exceptions seen in > log are below, > 1. com.cloud.utils.exception.CloudRuntimeException: Cannot create directory > /opt/cloud/bin on XenServer hosts > com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4846) > 2. 014-06-03 18:08:20,790 WARN [c.c.r.ResourceManagerImpl] > (ApiServer-3:ctx-f7cfbcb4 ctx-a1a82b64) Unable to connect due to > com.cloud.exception.ConnectionException: Reinitialize agent after setup. > > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:656) > > Steps: > 1. Import Devcloud image > 2. Run deploy DataCenter script to create a data center -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6860) DataCenter creation is failing in DevCloud in 4.4,errors out with failing to initialize agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-6860: Summary: DataCenter creation is failing in DevCloud in 4.4,errors out with failing to initialize agent (was: DataCenter creation is failing DevCloud in 4.4, failing to initialize agent. ) > DataCenter creation is failing in DevCloud in 4.4,errors out with failing to > initialize agent > - > > Key: CLOUDSTACK-6860 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6860 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: DevCloud >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Deploying a datacenter in devcloud is failing, few of the exceptions seen in > log are below, > 1. com.cloud.utils.exception.CloudRuntimeException: Cannot create directory > /opt/cloud/bin on XenServer hosts > com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4846) > 2. 014-06-03 18:08:20,790 WARN [c.c.r.ResourceManagerImpl] > (ApiServer-3:ctx-f7cfbcb4 ctx-a1a82b64) Unable to connect due to > com.cloud.exception.ConnectionException: Reinitialize agent after setup. > > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:656) > > Steps: > 1. Import Devcloud image > 2. Run deploy DataCenter script to create a data center -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6860) DataCenter creation is failing DevCloud in 4.4, failing to initialize agent.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-6860: --- Assignee: Santhosh Kumar Edukulla > DataCenter creation is failing DevCloud in 4.4, failing to initialize agent. > - > > Key: CLOUDSTACK-6860 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6860 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: DevCloud >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Deploying a datacenter in devcloud is failing, few of the exceptions seen in > log are below, > 1. com.cloud.utils.exception.CloudRuntimeException: Cannot create directory > /opt/cloud/bin on XenServer hosts > com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4846) > 2. 014-06-03 18:08:20,790 WARN [c.c.r.ResourceManagerImpl] > (ApiServer-3:ctx-f7cfbcb4 ctx-a1a82b64) Unable to connect due to > com.cloud.exception.ConnectionException: Reinitialize agent after setup. > > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:656) > > Steps: > 1. Import Devcloud image > 2. Run deploy DataCenter script to create a data center -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6860) DataCenter creation is failing in DevCloud in 4.4,errors out with failing to initialize agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-6860: Attachment: vmops.log Management Server Log > DataCenter creation is failing in DevCloud in 4.4,errors out with failing to > initialize agent > - > > Key: CLOUDSTACK-6860 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6860 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: DevCloud >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Attachments: vmops.log > > > Deploying a datacenter in devcloud is failing, few of the exceptions seen in > log are below, > 1. com.cloud.utils.exception.CloudRuntimeException: Cannot create directory > /opt/cloud/bin on XenServer hosts > com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4846) > 2. 014-06-03 18:08:20,790 WARN [c.c.r.ResourceManagerImpl] > (ApiServer-3:ctx-f7cfbcb4 ctx-a1a82b64) Unable to connect due to > com.cloud.exception.ConnectionException: Reinitialize agent after setup. > > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:656) > > Steps: > 1. Import Devcloud image > 2. Run deploy DataCenter script to create a data center -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021131#comment-14021131 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6793: - 1. I believe, adding a column is as well not a right solution. Domainid information is available and can be retrieved easily, from other tables like account and domain, its a question of designing our interfaces to retrieve with out adding additional columns. The current fix is decent enough to retrieve "correct" domainid properly. 2. I have seen some other places as well where getDomainid was added to return an invalid value, so its not only limited to one table i believe. So, need to refactor other table schemas and interfaces as well. Iam in general averse to add unnecessary columns, just to fix a solution. Its unnecessary maintenance, as well not an apt solution and fix. 3. I will log a separate bug to track the changes related to effective implementation of getDomainid with out adding columns altogether. Will close this bug for now. > [Automation] CreateTagsCmd fails with db exceptions > > > Key: CLOUDSTACK-6793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: KVM >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar > > > Steps to reproduce > Execute the test case integration.component.test_tags.TestResourceTags > Test case perform below steps > # 1. Create a tag on template/ISO using createTags API > # 2. Delete above created tag using deleteTags API > 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] > (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END=== > 10.223.240.193 -- GET > apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd > EQ&resourcetype=Template&resourceIds=35e10eef-7980-4085-8b6c-c68174f1b529&command=createTags&signature=pIJSk7ekg0Tlf > RN%2FWfdp8U42Bgs%3D&tags%5B0%5D.key=OS&response=json&tags%5B0%5D.value=CentOS > 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin > g back the transaction: Time = 4 Name = API-Job-Executor-89; called by > -TransactionLegacy.rollback:903-TransactionL > egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation. > proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2 > 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn > Transaction:25-Transaction$2.doInTransaction:49 > 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] > (catalina-exec-22:ctx-dbbc3135) ===START=== 10.223.240.193 -- GET > > jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642&apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z > 1t-oO1g9F4-EiUZx9BdEQ&command=queryAsyncJobResult&response=json&signature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D > 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while > executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags > (resource_tags.uuid, resource_tags.key, resource_tags.value, > resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, > resource_tags.resource_uuid, resource_tags.resource_type, > resource_tags.customer) VALUES > (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', > -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null) > at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400) > at sun.reflect.GeneratedMethodAccessor98.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 > com.cloud.utils.db.TransactionContextInterceptor.inv
[jira] [Commented] (CLOUDSTACK-6860) DataCenter creation is failing in DevCloud in 4.4,errors out with failing to initialize agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021245#comment-14021245 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6860: - This bug is logged to track the DevCloud issue mentioned and try fixing it. > DataCenter creation is failing in DevCloud in 4.4,errors out with failing to > initialize agent > - > > Key: CLOUDSTACK-6860 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6860 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: DevCloud >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Attachments: vmops.log > > > Deploying a datacenter in devcloud is failing, few of the exceptions seen in > log are below, > 1. com.cloud.utils.exception.CloudRuntimeException: Cannot create directory > /opt/cloud/bin on XenServer hosts > com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4846) > 2. 014-06-03 18:08:20,790 WARN [c.c.r.ResourceManagerImpl] > (ApiServer-3:ctx-f7cfbcb4 ctx-a1a82b64) Unable to connect due to > com.cloud.exception.ConnectionException: Reinitialize agent after setup. > > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:656) > > Steps: > 1. Import Devcloud image > 2. Run deploy DataCenter script to create a data center -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6791) [Automation] DeleteNetworkCmd fails with NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021312#comment-14021312 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6791: - Rayees, Can i get the setup details to verify this? Thanks! Santhosh > [Automation] DeleteNetworkCmd fails with NullPointerException > - > > Key: CLOUDSTACK-6791 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6791 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: Automation > 4.4-forward > vmware 5.0 >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > > This issue is observed with automation run , while executing test > integration.component.test_multiple_ips_per_nic.TestBasicOperations.test_add_ip_to_nic_2_SHARED > Test case performs below operations > 225 # Steps: > 226 # 1. Create Account and create network in it (isoalted/ shared/ > vpc) > 227 # 2. Deploy a VM in this network and account > 228 # 3. Add secondary IP to the default nic of VM > 229 # 4. Try to add the same IP again > 230 # 5. Try to add secondary IP providing wrong virtual machine id > 231 # 6. Try to add secondary IP with correct virtual machine id but > wrong IP address > # 7 Destroy account > 232 > 233 # Validations: > 234 # 1. Step 3 should succeed > 235 # 2. Step 4 should fail > 236 # 3. Step 5 should should fail > 237 # 4. Step 6 should fail > This issue observed during account deletion > 2014-05-26 19:18:52,169 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Network id=616 is > destroyed successfully, cleaning up corresponding resources now. > 2014-05-26 19:18:52,170 DEBUG [c.c.n.g.DirectNetworkGuru] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Releasing ip > 172.16.27.1 of placeholder nic Nic[1645-null-null-172.16.27.1] > 2014-05-26 19:18:52,171 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Rolling back the > transaction: Time = 2 Name = API-Job-Executor-41; called by > -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-Transaction.execute:46-DirectNetworkGuru.trash:327-NetworkOrchestrator$10.doInTransactionWithoutResult:2226-TransactionCallbackNoReturn.doInTransaction:25-Transaction$2.doInTransaction:49-Transaction.execute:37-Transaction.execute:46-NetworkOrchestrator.destroyNetwork:2221 > 2014-05-26 19:18:52,183 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-41:ctx-b247339e job-5716) Unexpected exception while > executing org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd > java.lang.NullPointerException > at > com.cloud.network.guru.DirectNetworkGuru$3.doInTransactionWithoutResult(DirectNetworkGuru.java:334) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > com.cloud.network.guru.DirectNetworkGuru.trash(DirectNetworkGuru.java:327) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransactionWithoutResult(NetworkOrchestrator.java:2226) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2221) > at > com.cloud.network.NetworkServiceImpl.deleteNetwork(NetworkServiceImpl.java:1828) > at sun.reflect.GeneratedMethodAccessor729.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.springfram
[jira] [Created] (CLOUDSTACK-6870) getDomainId implementation returns invalid value at places
Santhosh Kumar Edukulla created CLOUDSTACK-6870:
---
Summary: getDomainId implementation returns invalid value at places
Key: CLOUDSTACK-6870
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6870
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Santhosh Kumar Edukulla
Assignee: Santhosh Kumar Edukulla
Fix For: 4.5.0
Few classes implementing getDomainId derived from the below interface, seems to
have invalid value returned for domainid. EX: VMTemplateVO, implementing this
method returns -1. This behavior is creating issues at some places in code.
The respective tables EX: vm_template dont have column say domainid and so it
returns -1.
Though the domainid information is available with account and domain tables, it
is not able to retrieve this information because of some api semantics. This
bug is logged to track and provide fix for this issue. We can discuss as either
adding a column is apt way or a better way to refactor few apis to get this
information done with out adding extra columns.
*/
public interface PartOf {
/**
* @return domain id that the object belongs to.
*/
long getDomainId();
}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6793. - Resolution: Fixed > [Automation] CreateTagsCmd fails with db exceptions > > > Key: CLOUDSTACK-6793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: KVM >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar > > > Steps to reproduce > Execute the test case integration.component.test_tags.TestResourceTags > Test case perform below steps > # 1. Create a tag on template/ISO using createTags API > # 2. Delete above created tag using deleteTags API > 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] > (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END=== > 10.223.240.193 -- GET > apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd > EQ&resourcetype=Template&resourceIds=35e10eef-7980-4085-8b6c-c68174f1b529&command=createTags&signature=pIJSk7ekg0Tlf > RN%2FWfdp8U42Bgs%3D&tags%5B0%5D.key=OS&response=json&tags%5B0%5D.value=CentOS > 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin > g back the transaction: Time = 4 Name = API-Job-Executor-89; called by > -TransactionLegacy.rollback:903-TransactionL > egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation. > proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2 > 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn > Transaction:25-Transaction$2.doInTransaction:49 > 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] > (catalina-exec-22:ctx-dbbc3135) ===START=== 10.223.240.193 -- GET > > jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642&apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z > 1t-oO1g9F4-EiUZx9BdEQ&command=queryAsyncJobResult&response=json&signature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D > 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while > executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags > (resource_tags.uuid, resource_tags.key, resource_tags.value, > resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, > resource_tags.resource_uuid, resource_tags.resource_type, > resource_tags.customer) VALUES > (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', > -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null) > at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400) > at sun.reflect.GeneratedMethodAccessor98.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 > 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.$Proxy52.persist(Unknown Source) > at > com.cloud.tags.TaggedResourceManagerImpl$1.doInTransactionWithoutResult(TaggedResourceManagerImpl.java:245) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49
[jira] [Resolved] (CLOUDSTACK-6791) [Automation] DeleteNetworkCmd fails with NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6791. - Resolution: Fixed Fixed the issue > [Automation] DeleteNetworkCmd fails with NullPointerException > - > > Key: CLOUDSTACK-6791 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6791 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.4.0 > Environment: Automation > 4.4-forward > vmware 5.0 >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Fix For: 4.4.0 > > > This issue is observed with automation run , while executing test > integration.component.test_multiple_ips_per_nic.TestBasicOperations.test_add_ip_to_nic_2_SHARED > Test case performs below operations > 225 # Steps: > 226 # 1. Create Account and create network in it (isoalted/ shared/ > vpc) > 227 # 2. Deploy a VM in this network and account > 228 # 3. Add secondary IP to the default nic of VM > 229 # 4. Try to add the same IP again > 230 # 5. Try to add secondary IP providing wrong virtual machine id > 231 # 6. Try to add secondary IP with correct virtual machine id but > wrong IP address > # 7 Destroy account > 232 > 233 # Validations: > 234 # 1. Step 3 should succeed > 235 # 2. Step 4 should fail > 236 # 3. Step 5 should should fail > 237 # 4. Step 6 should fail > This issue observed during account deletion > 2014-05-26 19:18:52,169 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Network id=616 is > destroyed successfully, cleaning up corresponding resources now. > 2014-05-26 19:18:52,170 DEBUG [c.c.n.g.DirectNetworkGuru] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Releasing ip > 172.16.27.1 of placeholder nic Nic[1645-null-null-172.16.27.1] > 2014-05-26 19:18:52,171 DEBUG [c.c.u.d.T.Transaction] > (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Rolling back the > transaction: Time = 2 Name = API-Job-Executor-41; called by > -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-Transaction.execute:46-DirectNetworkGuru.trash:327-NetworkOrchestrator$10.doInTransactionWithoutResult:2226-TransactionCallbackNoReturn.doInTransaction:25-Transaction$2.doInTransaction:49-Transaction.execute:37-Transaction.execute:46-NetworkOrchestrator.destroyNetwork:2221 > 2014-05-26 19:18:52,183 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-41:ctx-b247339e job-5716) Unexpected exception while > executing org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd > java.lang.NullPointerException > at > com.cloud.network.guru.DirectNetworkGuru$3.doInTransactionWithoutResult(DirectNetworkGuru.java:334) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > com.cloud.network.guru.DirectNetworkGuru.trash(DirectNetworkGuru.java:327) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransactionWithoutResult(NetworkOrchestrator.java:2226) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2221) > at > com.cloud.network.NetworkServiceImpl.deleteNetwork(NetworkServiceImpl.java:1828) > at sun.reflect.GeneratedMethodAccessor729.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:
[jira] [Assigned] (CLOUDSTACK-6896) Dynamically added OS Type throws NoSuchElement Exception on Xen
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-6896: --- Assignee: Santhosh Kumar Edukulla > Dynamically added OS Type throws NoSuchElement Exception on Xen > --- > > Key: CLOUDSTACK-6896 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6896 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.4.0 > Environment: Managment Server: 4.4.0 > Host: XenServer Hypervisor 6.2 >Reporter: Pavan Kumar Bandarupally >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Fix For: 4.4.0 > > Attachments: management-server.log > > > A dynamically added OS is used as OS type for an ISO registered in > cloudstack. An instance deployed using that ISO doesn't get created throwing > an exception. > MS Exception trace excerpt: > = > 2014-06-12 02:03:45,707 DEBUG [c.c.a.m.DirectAgentAttache] > (DirectAgent-281:ctx-c47880f2) Seq 1-5437252125119752015: Executing request > 2014-06-12 02:03:45,720 DEBUG [c.c.h.x.r.CitrixResourceBase] > (DirectAgent-281:ctx-c47880f2) 1. The VM i-2-8-VM is in Starting state. > 2014-06-12 02:03:45,723 WARN [c.c.h.x.r.XenServer620Resource] > (DirectAgent-281:ctx-c47880f2) XenServer 6.2.0 DOES NOT support Guest OS type > centospavan > 2014-06-12 02:03:45,726 DEBUG [c.c.h.x.r.CitrixResourceBase] > (DirectAgent-281:ctx-c47880f2) Cannot find template : null on XS version: > com.cloud.hypervisor.xen.resource.XenServer620Resource > 2014-06-12 02:03:45,727 WARN [c.c.h.x.r.CitrixResourceBase] > (DirectAgent-281:ctx-c47880f2) Catch Exception: class > java.util.NoSuchElementException due to java.util.NoSuchElementException > java.util.NoSuchElementException > at > java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:396) > at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1359) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1787) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:504) > at > com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:61) > at > com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102) > at > com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > 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-06-12 02:03:45,729 WARN [c.c.h.x.r.CitrixResourceBase] > (DirectAgent-281:ctx-c47880f2) Unable to start i-2-8-VM due to > java.util.NoSuchElementException > at > java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:396) > at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1359) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1787) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:504) > at > com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(Xen
[jira] [Commented] (CLOUDSTACK-6910) [CI] Phase 1: tagging of test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030502#comment-14030502 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6910: - 1. First add hypervisor = ["xenserver","kvm",...] tags to each test case under bvt, based upon its applicabillity. 2. Once finished, let us know the changes with test suites, so we can test and check the other point 2 can be achieved with out any further changes. If required, then we need to go ahead with that as well. > [CI] Phase 1: tagging of test cases > --- > > Key: CLOUDSTACK-6910 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6910 > 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: Abhinandan Prateek >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6910) [CI] Phase 1: tagging of test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030502#comment-14030502 ] Santhosh Kumar Edukulla edited comment on CLOUDSTACK-6910 at 6/13/14 11:49 AM: --- 1. First add hypervisor = ["xenserver","kvm",...] tags to each test case under bvt, based upon a test case applicabillity to work on a given hypervisor. 2. Once finished, let us know the changes with test suites, so we can test and check the other point 2 can be achieved with out any further changes. If required, then we need to go ahead with that as well. was (Author: santhoshe): 1. First add hypervisor = ["xenserver","kvm",...] tags to each test case under bvt, based upon its applicabillity. 2. Once finished, let us know the changes with test suites, so we can test and check the other point 2 can be achieved with out any further changes. If required, then we need to go ahead with that as well. > [CI] Phase 1: tagging of test cases > --- > > Key: CLOUDSTACK-6910 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6910 > 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: Abhinandan Prateek >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6914) The present way of tagging the test cases has issues and is not usable. Need to modify this.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-6914: Summary: The present way of tagging the test cases has issues and is not usable. Need to modify this. (was: The present way of tagging the test cases as provisioning and simulator is not usable. Need to modify this.) > The present way of tagging the test cases has issues and is not usable. Need > to modify this. > > > Key: CLOUDSTACK-6914 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6914 > 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: Bharat Kumar >Assignee: Santhosh Kumar Edukulla > Fix For: 4.4.0 > > > Currently we add all the test meta data in a single tag called tags, as a > result we cannot use proper nosetest conditions to filter the simulator test > cases from provisioning. > Also some tests have both simulator and provisioning tags added to the same > test case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6914) The present way of tagging the test cases has issues and is not usable. Need to modify this.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-6914: Description: Currently we add all the test meta data in a single tag called tags, as a result we cannot use proper nosetest conditions to filter the simulator test cases from provisioning. Also some tests have both simulator and provisioning tags added to the same test case.Some test cases have simulator, selfservice tags and others. Tracking this bug to clean up the tags. was: Currently we add all the test meta data in a single tag called tags, as a result we cannot use proper nosetest conditions to filter the simulator test cases from provisioning. Also some tests have both simulator and provisioning tags added to the same test case. > The present way of tagging the test cases has issues and is not usable. Need > to modify this. > > > Key: CLOUDSTACK-6914 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6914 > 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: Bharat Kumar >Assignee: Santhosh Kumar Edukulla > Fix For: 4.4.0 > > > Currently we add all the test meta data in a single tag called tags, as a > result we cannot use proper nosetest conditions to filter the simulator test > cases from provisioning. > Also some tests have both simulator and provisioning tags added to the same > test case.Some test cases have simulator, selfservice tags and others. > Tracking this bug to clean up the tags. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6914) The present way of tagging the test cases has issues and is not usable. Need to modify this.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6914. - Resolution: Fixed > The present way of tagging the test cases has issues and is not usable. Need > to modify this. > > > Key: CLOUDSTACK-6914 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6914 > 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: Bharat Kumar >Assignee: Santhosh Kumar Edukulla > Fix For: 4.4.0 > > > Currently we add all the test meta data in a single tag called tags, as a > result we cannot use proper nosetest conditions to filter the simulator test > cases from provisioning. > Also some tests have both simulator and provisioning tags added to the same > test case.Some test cases have simulator, selfservice tags and others. > Tracking this bug to clean up the tags. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6910) [CI] Phase 1: tagging of test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-6910: --- Assignee: Santhosh Kumar Edukulla > [CI] Phase 1: tagging of test cases > --- > > Key: CLOUDSTACK-6910 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6910 > 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: Abhinandan Prateek >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6910) [CI] Phase 1: tagging of test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036155#comment-14036155 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-6910: - 1. required_hardware="true" or required_hardware="false" tags were added to all bvt cases. 2. simulator, selfservice, tags were added at many places, these are same. Removed them as part of clean up. 3. There were few tags say "test", and few misc tags added, cleaned up them. 4. There were few places where zone type information like advanced or basic was missing. Added them now. 5. Need to change marvin/pom.xml where references to simulator tag was there. Need to remove references here, along with it load option has to be removed. 6. Next, add hypervisor attribute with various hypervisor information, such that they can be picked up based upon the hypervisor we are running upon. This, we will discuss inside community before proceeding. > [CI] Phase 1: tagging of test cases > --- > > Key: CLOUDSTACK-6910 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6910 > 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: Abhinandan Prateek >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6910) Phase 1: tagging of test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-6910: Summary: Phase 1: tagging of test cases (was: [CI] Phase 1: tagging of test cases) > Phase 1: tagging of test cases > -- > > Key: CLOUDSTACK-6910 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6910 > 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: Abhinandan Prateek >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6910) [CI] Phase 1: tagging of test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036155#comment-14036155 ] Santhosh Kumar Edukulla edited comment on CLOUDSTACK-6910 at 6/18/14 7:12 PM: -- 1. required_hardware="true" or required_hardware="false" tags were added to all bvt cases. 2. simulator, selfservice, tags earlier added were redundant, at many places, these are same. Removed them as part of clean up. 3. There were few tags say "test", and few misc tags available which are not much useful, cleaned up them. 4. There were few places where zone type information like advanced or basic was missing. Added them now. 5. Need to change marvin/pom.xml where references to simulator tag was there. Need to remove references here, along with it load option has to be removed. 6. Next, add hypervisor attribute with various hypervisor information, such that they can be picked up based upon the hypervisor we are running upon. This, we will discuss inside community before proceeding. was (Author: santhoshe): 1. required_hardware="true" or required_hardware="false" tags were added to all bvt cases. 2. simulator, selfservice, tags were added at many places, these are same. Removed them as part of clean up. 3. There were few tags say "test", and few misc tags added, cleaned up them. 4. There were few places where zone type information like advanced or basic was missing. Added them now. 5. Need to change marvin/pom.xml where references to simulator tag was there. Need to remove references here, along with it load option has to be removed. 6. Next, add hypervisor attribute with various hypervisor information, such that they can be picked up based upon the hypervisor we are running upon. This, we will discuss inside community before proceeding. > [CI] Phase 1: tagging of test cases > --- > > Key: CLOUDSTACK-6910 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6910 > 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: Abhinandan Prateek >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6966) Attach volume causes unexpected exception intermittently
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Kumar Edukulla reassigned CLOUDSTACK-6966:
---
Assignee: Santhosh Kumar Edukulla
> Attach volume causes unexpected exception intermittently
>
>
> Key: CLOUDSTACK-6966
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6966
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Girish Shilamkar
>Assignee: Santhosh Kumar Edukulla
>
> test_09_delete_detached_volume test fails sometimes while attaching the
> volume. Upon investigating it was found that unexpected exception is thrown
> by management server.
> Log:
> 2014-06-19 07:43:09,198 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Unexpected exception while
> executing org.apache.cloudstack.api.
> command.admin.volume.AttachVolumeCmdByAdmin
> java.lang.RuntimeException: Unexpected exception
> at
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1045)
> at sun.reflect.GeneratedMethodAccessor669.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.$Proxy182.attachVolumeToVM(Unknown Source)
> at
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin.execute(AttachVolumeCmdByAdmin.java:38)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
> at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> 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:460)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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: java.lang.RuntimeException: Job failed due to exception Failed to
> attach volume Test Volume to VM VM-43cf6765-bf73-4c3f-a1b3-24214d7dee93;
> org.libvirt.Libvi
> rtException: internal error unable to execute QEMU command
> '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
> ... 25 more
> 2014-06-19 07:43:09,199 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Complete async job-7728,
> jobStatus: FAILED, resultCode: 530
> , result: org.apache.cloudstack.api.response.ExceptionResponse/null/
> {"uuidList":[],"errorcode":530,"errortext":"Unexpected exception"}
> 2014-06-19 07:43:09,199 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Work-Job-Executor-80:ctx-830fcb84 job-7728/job-7729) Remove job-7729 from
> job monitoring
> 2014-06-19 07:43:09,203 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Done executing
> org.apache.cloudstack.api.command.admin.volu
> me.AttachVolumeCmdByAdmin for job-7728
> 2014-06-19 07:43:09,207 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Remove job-7728 from job
> monitoring
> 2014-06-19 07:43:09,655 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-6:null) SeqA 9-9704: Processing Seq 9-9704: { Cmd ,
> MgmtId: -1, via: 9, Ver: v1, Flags:
> 11,
> [{"com
[jira] [Closed] (CLOUDSTACK-5073) Added installation of marvin along with packaging to mvn build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-5073. --- Resolution: Not a Problem > Added installation of marvin along with packaging to mvn build > -- > > Key: CLOUDSTACK-5073 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5073 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > > Currently, we dont install the Marvin packages with default > mvn install. As part of this command currently, we just source > distribute the Marvin. For marvin,We assume user to have run its > own installation of packages post distribution. > This way, some times if any new addition of package changes happens, > user has to explicitly run installation of marvin. > If not installed,the changes are not > available to tests and other code. With this change, we package and > install them as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6976) Support for "SecStorageFirewallCfgCommand" for simulator.
Santhosh Kumar Edukulla created CLOUDSTACK-6976: --- Summary: Support for "SecStorageFirewallCfgCommand" for simulator. Key: CLOUDSTACK-6976 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6976 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Simulator Affects Versions: 4.4.0 Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.4.0, 4.5.0 Simulator currently, does not support SecStorageFirewallCfgCommand and throws up below error. Added support for this command now. [c.c.a.m.AgentManagerImpl] (Simulator-Agent-Mgr-1:ctx-6381ef3d) Unsupported Command: Unsupported command issued:com.cloud.agent.api.SecStorageFirewallCfgCommand. Are you sure you got the right type of server? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6966) Attach volume causes unexpected exception intermittently
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040648#comment-14040648
]
Santhosh Kumar Edukulla commented on CLOUDSTACK-6966:
-
Girish,
1. Is this bug, specific to few hypervisors or is reproducible with any
hypervisor?
2. Iam just trying to fix the bug. Will the bug mentioned requires hardware, or
can be verified against simulator?
Santhosh
> Attach volume causes unexpected exception intermittently
>
>
> Key: CLOUDSTACK-6966
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6966
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Girish Shilamkar
>Assignee: Santhosh Kumar Edukulla
>
> test_09_delete_detached_volume test fails sometimes while attaching the
> volume. Upon investigating it was found that unexpected exception is thrown
> by management server.
> Log:
> 2014-06-19 07:43:09,198 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Unexpected exception while
> executing org.apache.cloudstack.api.
> command.admin.volume.AttachVolumeCmdByAdmin
> java.lang.RuntimeException: Unexpected exception
> at
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1045)
> at sun.reflect.GeneratedMethodAccessor669.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.$Proxy182.attachVolumeToVM(Unknown Source)
> at
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin.execute(AttachVolumeCmdByAdmin.java:38)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
> at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> 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:460)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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: java.lang.RuntimeException: Job failed due to exception Failed to
> attach volume Test Volume to VM VM-43cf6765-bf73-4c3f-a1b3-24214d7dee93;
> org.libvirt.Libvi
> rtException: internal error unable to execute QEMU command
> '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
> ... 25 more
> 2014-06-19 07:43:09,199 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Complete async job-7728,
> jobStatus: FAILED, resultCode: 530
> , result: org.apache.cloudstack.api.response.ExceptionResponse/null/
> {"uuidList":[],"errorcode":530,"errortext":"Unexpected exception"}
> 2014-06-19 07:43:09,199 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Work-Job-Executor-80:ctx-830fcb84 job-7728/job-7729) Remove job-7729 from
> job monitoring
> 2014-06-19 07:43:09,203 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Done executing
> org.apache.cloudstack.api.command.admin.volu
> me.AttachVolumeCmdByAdmin for job-7728
> 2014-06-19 07:43:09,207 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-40:ctx-c775dc91 job
[jira] [Commented] (CLOUDSTACK-6966) Attach volume causes unexpected exception intermittently
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040690#comment-14040690
]
Santhosh Kumar Edukulla commented on CLOUDSTACK-6966:
-
I just ran the below case twice and both the times it was successful.
Delete a Volume unattached to an VM ... === TestName:
test_09_delete_detached_volume | Status : SUCCESS ===
ok
--
Ran 1 test in 73.340s
OK
~
> Attach volume causes unexpected exception intermittently
>
>
> Key: CLOUDSTACK-6966
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6966
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Girish Shilamkar
>Assignee: Santhosh Kumar Edukulla
>
> test_09_delete_detached_volume test fails sometimes while attaching the
> volume. Upon investigating it was found that unexpected exception is thrown
> by management server.
> Log:
> 2014-06-19 07:43:09,198 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Unexpected exception while
> executing org.apache.cloudstack.api.
> command.admin.volume.AttachVolumeCmdByAdmin
> java.lang.RuntimeException: Unexpected exception
> at
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1045)
> at sun.reflect.GeneratedMethodAccessor669.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.$Proxy182.attachVolumeToVM(Unknown Source)
> at
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin.execute(AttachVolumeCmdByAdmin.java:38)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
> at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> 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:460)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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: java.lang.RuntimeException: Job failed due to exception Failed to
> attach volume Test Volume to VM VM-43cf6765-bf73-4c3f-a1b3-24214d7dee93;
> org.libvirt.Libvi
> rtException: internal error unable to execute QEMU command
> '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
> ... 25 more
> 2014-06-19 07:43:09,199 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Complete async job-7728,
> jobStatus: FAILED, resultCode: 530
> , result: org.apache.cloudstack.api.response.ExceptionResponse/null/
> {"uuidList":[],"errorcode":530,"errortext":"Unexpected exception"}
> 2014-06-19 07:43:09,199 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Work-Job-Executor-80:ctx-830fcb84 job-7728/job-7729) Remove job-7729 from
> job monitoring
> 2014-06-19 07:43:09,203 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-40:ctx-c775dc91 job-7728) Done executing
> org.apache.cloudstack.api.command.admin.volu
> me.AttachVolumeCmdByAdmin for job-7728
> 2014-06-19 07:43:09,207 INFO [o.a.c
[jira] [Resolved] (CLOUDSTACK-6976) Support for "SecStorageFirewallCfgCommand" for simulator.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6976. - Resolution: Fixed > Support for "SecStorageFirewallCfgCommand" for simulator. > - > > Key: CLOUDSTACK-6976 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6976 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Simulator >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.4.0, 4.5.0 > > > Simulator currently, does not support SecStorageFirewallCfgCommand and throws > up below error. Added support for this command now. > [c.c.a.m.AgentManagerImpl] (Simulator-Agent-Mgr-1:ctx-6381ef3d) Unsupported > Command: Unsupported command > issued:com.cloud.agent.api.SecStorageFirewallCfgCommand. Are you sure you > got the right type of server? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6976) Support for "SecStorageFirewallCfgCommand" for simulator.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6976. --- > Support for "SecStorageFirewallCfgCommand" for simulator. > - > > Key: CLOUDSTACK-6976 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6976 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Simulator >Affects Versions: 4.4.0 >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.4.0, 4.5.0 > > > Simulator currently, does not support SecStorageFirewallCfgCommand and throws > up below error. Added support for this command now. > [c.c.a.m.AgentManagerImpl] (Simulator-Agent-Mgr-1:ctx-6381ef3d) Unsupported > Command: Unsupported command > issued:com.cloud.agent.api.SecStorageFirewallCfgCommand. Are you sure you > got the right type of server? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6856) Fixed few TCs failing in master.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6856. - Resolution: Fixed > Fixed few TCs failing in master. > > > Key: CLOUDSTACK-6856 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6856 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > Fix For: 4.5.0 > > > 1. Fixed few cases failing because of some data corruption. > 2. Added proper to retries to few cases where check is done immediately after > operation. > 3. Added setup.py changes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5937) Exception When running Simulator
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-5937. - Resolution: Fixed This is fixed. > Exception When running Simulator > > > Key: CLOUDSTACK-5937 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5937 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Infra >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Exception when running simulator : > ERROR [c.c.c.AgentHookBase] (AgentConnectTaskPool-29:ctx-7e568cd1) Unexpected > exception when sending http handling startup command(time out) to the console > proxy resource for proxy:37 > java.lang.NullPointerException > at > com.cloud.consoleproxy.AgentHookBase.startAgentHttpHandlerInVM(AgentHookBase.java:218) > at > com.cloud.consoleproxy.ConsoleProxyListener.processConnect(ConsoleProxyListener.java:71) > at > com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:495) > at > com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:999) > at > com.cloud.agent.manager.AgentManagerImpl.access$000(AgentManagerImpl.java:117) > at > com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.runInContext(AgentManagerImpl.java:1082) > 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5937) Exception When running Simulator
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-5937. --- > Exception When running Simulator > > > Key: CLOUDSTACK-5937 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5937 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Infra >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Exception when running simulator : > ERROR [c.c.c.AgentHookBase] (AgentConnectTaskPool-29:ctx-7e568cd1) Unexpected > exception when sending http handling startup command(time out) to the console > proxy resource for proxy:37 > java.lang.NullPointerException > at > com.cloud.consoleproxy.AgentHookBase.startAgentHttpHandlerInVM(AgentHookBase.java:218) > at > com.cloud.consoleproxy.ConsoleProxyListener.processConnect(ConsoleProxyListener.java:71) > at > com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:495) > at > com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:999) > at > com.cloud.agent.manager.AgentManagerImpl.access$000(AgentManagerImpl.java:117) > at > com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.runInContext(AgentManagerImpl.java:1082) > 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7079) 'update:Exception:Invalid cluster session detected' error thrown after MS restart
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055116#comment-14055116
]
Santhosh Kumar Edukulla commented on CLOUDSTACK-7079:
-
I was just seeing the mentioned commit and for DbUtil.java, its just a log
error message, where it was dereferencing a possible null value for rs. I ran
the build post the changes along with creating a new datacenter.
Are we sure it is related to DbUtils.java? As well, we are running CI
automation on master daily, so far no issue was reported. Can you please check
before if there could be some other action, causing this issue, so that i can
look through those steps? Thanks again for reporting the issue.
return rs.getInt(1) > 0;
-s_logger.error("RELEASE_LOCK() returns unexpected result : " +
rs.getInt(1));
+s_logger.error("releaseGlobalLock:RELEASE_LOCK() returns
unexpected result");
Santhosh
> 'update:Exception:Invalid cluster session detected' error thrown after MS
> restart
> -
>
> Key: CLOUDSTACK-7079
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7079
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Likitha Shetty
>Assignee: Santhosh Kumar Edukulla
>Priority: Critical
> Fix For: 4.5.0
>
>
> After an MS restart the following error is observed in the logs-
> {noformat}
> 2014-07-08 21:27:54,548 WARN [c.c.c.d.ManagementServerHostDaoImpl]
> (Cluster-Heartbeat-1:ctx-d357302f) update:Exception:Invalid cluster session
> detected
> com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session
> detected
> at
> com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147)
> 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.$Proxy160.update(Unknown Source)
> at
> com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545)
> 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.cloud.cluster.ClusterInvalidSessionException: runid
> 1404835017785 is no longer valid
> at
> com.cloud.cluster.dao.ManagementServe
[jira] [Comment Edited] (CLOUDSTACK-7079) 'update:Exception:Invalid cluster session detected' error thrown after MS restart
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055116#comment-14055116
]
Santhosh Kumar Edukulla edited comment on CLOUDSTACK-7079 at 7/8/14 4:51 PM:
-
I just saw the mentioned commit, and for DbUtil.java, its just a log error
message, where it was dereferencing a possible null value for rs. I ran the
build post the changes along with creating a new datacenter.
Are we sure it is related to DbUtils.java? As well, we are running CI
automation on master daily, so far no issue was reported. Can you please check
before if there could be some other action, causing this issue, so that i can
look through those steps? Thanks again for reporting the issue.
return rs.getInt(1) > 0;
-s_logger.error("RELEASE_LOCK() returns unexpected result : " +
rs.getInt(1));
+s_logger.error("releaseGlobalLock:RELEASE_LOCK() returns
unexpected result");
Santhosh
was (Author: santhoshe):
I was just seeing the mentioned commit and for DbUtil.java, its just a log
error message, where it was dereferencing a possible null value for rs. I ran
the build post the changes along with creating a new datacenter.
Are we sure it is related to DbUtils.java? As well, we are running CI
automation on master daily, so far no issue was reported. Can you please check
before if there could be some other action, causing this issue, so that i can
look through those steps? Thanks again for reporting the issue.
return rs.getInt(1) > 0;
-s_logger.error("RELEASE_LOCK() returns unexpected result : " +
rs.getInt(1));
+s_logger.error("releaseGlobalLock:RELEASE_LOCK() returns
unexpected result");
Santhosh
> 'update:Exception:Invalid cluster session detected' error thrown after MS
> restart
> -
>
> Key: CLOUDSTACK-7079
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7079
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Likitha Shetty
>Assignee: Santhosh Kumar Edukulla
>Priority: Critical
> Fix For: 4.5.0
>
>
> After an MS restart the following error is observed in the logs-
> {noformat}
> 2014-07-08 21:27:54,548 WARN [c.c.c.d.ManagementServerHostDaoImpl]
> (Cluster-Heartbeat-1:ctx-d357302f) update:Exception:Invalid cluster session
> detected
> com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session
> detected
> at
> com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147)
> 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.$Proxy160.update(Unknown Source)
> at
> com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545)
> 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)
>
[jira] [Comment Edited] (CLOUDSTACK-7079) 'update:Exception:Invalid cluster session detected' error thrown after MS restart
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055116#comment-14055116
]
Santhosh Kumar Edukulla edited comment on CLOUDSTACK-7079 at 7/8/14 4:52 PM:
-
I just saw the mentioned commit, and for DbUtil.java, its just a log error
message change, where it was dereferencing a possible null value for rs. I ran
the build post the changes along with creating a new datacenter.
Are we sure it is related to DbUtils.java? As well, we are running CI
automation on master daily, so far no issue was reported. Can you please check
before if there could be some other action, causing this issue, so that i can
look through those steps? Thanks again for reporting the issue.
return rs.getInt(1) > 0;
-s_logger.error("RELEASE_LOCK() returns unexpected result : " +
rs.getInt(1));
+s_logger.error("releaseGlobalLock:RELEASE_LOCK() returns
unexpected result");
Santhosh
was (Author: santhoshe):
I just saw the mentioned commit, and for DbUtil.java, its just a log error
message, where it was dereferencing a possible null value for rs. I ran the
build post the changes along with creating a new datacenter.
Are we sure it is related to DbUtils.java? As well, we are running CI
automation on master daily, so far no issue was reported. Can you please check
before if there could be some other action, causing this issue, so that i can
look through those steps? Thanks again for reporting the issue.
return rs.getInt(1) > 0;
-s_logger.error("RELEASE_LOCK() returns unexpected result : " +
rs.getInt(1));
+s_logger.error("releaseGlobalLock:RELEASE_LOCK() returns
unexpected result");
Santhosh
> 'update:Exception:Invalid cluster session detected' error thrown after MS
> restart
> -
>
> Key: CLOUDSTACK-7079
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7079
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Likitha Shetty
>Assignee: Santhosh Kumar Edukulla
>Priority: Critical
> Fix For: 4.5.0
>
>
> After an MS restart the following error is observed in the logs-
> {noformat}
> 2014-07-08 21:27:54,548 WARN [c.c.c.d.ManagementServerHostDaoImpl]
> (Cluster-Heartbeat-1:ctx-d357302f) update:Exception:Invalid cluster session
> detected
> com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session
> detected
> at
> com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147)
> 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.$Proxy160.update(Unknown Source)
> at
> com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545)
> 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)
>
[jira] [Assigned] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-7070: --- Assignee: Santhosh Kumar Edukulla > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > ... 26 more > 2014-07-07 15:14:40,046 ERROR [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) Unexpected exception in cluster heartbeat > java.lang.RuntimeException: update:Exception:Invalid cluster session detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:155) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.Delegati
[jira] [Commented] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056069#comment-14056069 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-7070: - Commit was called before roll back, fixed the issue. Commitid: d51e8f44aecd192acb3bb6f2195819e1b4c43dd0 > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > ... 26 more > 2014-07-07 15:14:40,046 ERROR [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) Unexpected exception in cluster heartbeat > java.lang.RuntimeException: update:Exception:Invalid cluster session detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:155) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at
[jira] [Resolved] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-7070. - Resolution: Fixed Commit was called and then rollback for a given transaction. Fixed to remove the commit when rollback was called. > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > ... 26 more > 2014-07-07 15:14:40,046 ERROR [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) Unexpected exception in cluster heartbeat > java.lang.RuntimeException: update:Exception:Invalid cluster session detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:155) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.Native
[jira] [Resolved] (CLOUDSTACK-6021) Segregating Current Tests into Self Service Test Cases and Provisioning Test Cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6021. - Resolution: Fixed Added required_hardware=true and required_hardware=false for all tests under bvt > Segregating Current Tests into Self Service Test Cases and Provisioning Test > Cases > -- > > Key: CLOUDSTACK-6021 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6021 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > We have to segregate current integration tests available into below two broad > categories. > The goal is to run self service tests on simulator with out any actual > requirement of hardware. > 1. Self Service Tests: Tests that tests our self service business logic. > EX: Vm placement > snapshot policies > resource limits > usage > resource cleanups > dedication > acl > 2. Provisioning Tests: Tests that require actual hardware EX: Start\Stop VM > on ESX, XS and KVM > Create\Remove rules on VR or network equipment > Create Snapshot on storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6022) [Automation]: Modifications to self service tests.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6022. --- > [Automation]: Modifications to self service tests. > -- > > Key: CLOUDSTACK-6022 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6022 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > 1. This is related to CLOUDSTACK-6021 > 2. Once tests are segregated as mentioned in above note. We may have to do > enhancements to self service tests, so that they can accommodate and run > against the simulator. > 3. Changes in simulator with new changes for making it to behave dynamically > or inject behavior should be driven from tests. > 4. Any changes to be done to tests for incorporating these should be tracked > as part of this bug. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6022) [Automation]: Modifications to self service tests.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6022. - Resolution: Fixed > [Automation]: Modifications to self service tests. > -- > > Key: CLOUDSTACK-6022 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6022 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > 1. This is related to CLOUDSTACK-6021 > 2. Once tests are segregated as mentioned in above note. We may have to do > enhancements to self service tests, so that they can accommodate and run > against the simulator. > 3. Changes in simulator with new changes for making it to behave dynamically > or inject behavior should be driven from tests. > 4. Any changes to be done to tests for incorporating these should be tracked > as part of this bug. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-7070. --- > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > ... 26 more > 2014-07-07 15:14:40,046 ERROR [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) Unexpected exception in cluster heartbeat > java.lang.RuntimeException: update:Exception:Invalid cluster session detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:155) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
[jira] [Reopened] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reopened CLOUDSTACK-7070: - > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > ... 26 more > 2014-07-07 15:14:40,046 ERROR [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) Unexpected exception in cluster heartbeat > java.lang.RuntimeException: update:Exception:Invalid cluster session detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:155) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
[jira] [Commented] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058365#comment-14058365 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-7070: - Please dont cross post across bugs, thats a bad practice, open a different bug for different issue. This bug is resolved. > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > ... 26 more > 2014-07-07 15:14:40,046 ERROR [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) Unexpected exception in cluster heartbeat > java.lang.RuntimeException: update:Exception:Invalid cluster session detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:155) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Met
[jira] [Resolved] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-7070. - Resolution: Fixed > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > ... 26 more > 2014-07-07 15:14:40,046 ERROR [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) Unexpected exception in cluster heartbeat > java.lang.RuntimeException: update:Exception:Invalid cluster session detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:155) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.
[jira] [Commented] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058409#comment-14058409 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-7070: - There was an issue where TransactionLegacy interface used has got some issues because of recent fixes. We reverted the changes done to one such class ManagementHostDaoImpl.java and tested, issue is no longer reproducible. Please check the mail on devlist. > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > ... 26 more > 2014-07-07 15:14:40,046 ERROR [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) Unexpected exception in cluster heartbeat > java.lang.RuntimeException: update:Exception:Invalid cluster session detected > at > com.cloud.cluster.dao.Manag
[jira] [Resolved] (CLOUDSTACK-4899) Providing Configuration support for Marvin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-4899. - Resolution: Fixed We added a ConfigManager interface and moved relevant data to config. > Providing Configuration support for Marvin > -- > > Key: CLOUDSTACK-4899 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4899 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Providing Configuration support to Marvin. Currently, there is no way to > provide and drive a uniform configuraiton support to Marvin. The framework > currently does not have the support to retrieve and provide a uniform object > as dictionary to test features under marvin. All features should be removed > of hard coded strings. Move all hard coded and configuration settings to one > config directory. This way, we can have a confiugration module and use > uniform object provided as part of TestClient, so that user can segregate > code from config and maintain config at single place. This is good and > maintain readability -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058409#comment-14058409 ] Santhosh Kumar Edukulla edited comment on CLOUDSTACK-7070 at 7/11/14 5:26 PM: -- There was an issue where TransactionLegacy interface when closed, has got some issues. We reverted the changes done to one such file ManagementHostDaoImpl.java and tested, now issue is no longer reproducible. Please check the mail on devlist. Commitid for revert: 1f3d02b38acbd269a65e2a9b0a1d0233b69a7598 was (Author: santhoshe): There was an issue where TransactionLegacy interface used has got some issues because of recent fixes. We reverted the changes done to one such class ManagementHostDaoImpl.java and tested, issue is no longer reproducible. Please check the mail on devlist. > Continuous Error messages" Invalid cluster session detected" in MS logs after > starting the management server > > > Key: CLOUDSTACK-7070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: manasaveloori >Assignee: Santhosh Kumar Edukulla >Priority: Blocker > Attachments: management-server.rar > > > Observed DB exception in logs which is mentioned in bug CLOUDSTACK-7041 > After this DB exception observing the follwoing continuous ERROR messages in > logs: > 2014-07-07 15:14:40,043 WARN [c.c.c.d.ManagementServerHostDaoImpl] > (Cluster-Heartbeat-1:ctx-49fa7a77) update:Exception:Invalid cluster session > detected > com.cloud.utils.exception.CloudRuntimeException: Invalid cluster session > detected > at > com.cloud.cluster.dao.ManagementServerHostDaoImpl.update(ManagementServerHostDaoImpl.java:147) > 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.$Proxy150.update(Unknown Source) > at > com.cloud.cluster.ClusterManagerImpl$4.runInContext(ClusterManagerImpl.java:545) > 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.cloud.cluster.ClusterInvalidSessionException: runid > 1404760440284 is no longer valid >
[jira] [Resolved] (CLOUDSTACK-4986) Analysing and implementing Code Coverage for Integration Tests
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-4986. - Resolution: Fixed > Analysing and implementing Code Coverage for Integration Tests > -- > > Key: CLOUDSTACK-4986 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4986 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Infra >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Currently, we have facility to use and run sonar for analyzing code > coverage numbers for CS using unit tests. We need to enhance it to support > analysis for integration tests coverage as well. Basically, this will give > coverage numbers for both integration and unit tests. > 1.It seems we already have a code coverage numbers using sonar as below. It > currently shows only the numbers for unit tests. > https://analysis.apache.org/dashboard/index/100206 > 2. The below link has an explanation for using it for both for integration > and unit tests. > http://docs.codehaus.org/display/SONAR/Code+Coverage+by+Integration+Tests+for+Java+Project > 3. Many links suggests it has good decision coverage facility compared to > other coverage tools. > http://onlysoftware.wordpress.com/2012/12/19/code-coverage-tools-jacoco-cobertura-emma-comparison-in-sonar/ > Logging this bug to track this effort and changes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6910) Phase 1: tagging of test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6910. --- > Phase 1: tagging of test cases > -- > > Key: CLOUDSTACK-6910 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6910 > 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: Abhinandan Prateek >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-4986) Analysing and implementing Code Coverage for Integration Tests
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-4986. --- > Analysing and implementing Code Coverage for Integration Tests > -- > > Key: CLOUDSTACK-4986 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4986 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Infra >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Currently, we have facility to use and run sonar for analyzing code > coverage numbers for CS using unit tests. We need to enhance it to support > analysis for integration tests coverage as well. Basically, this will give > coverage numbers for both integration and unit tests. > 1.It seems we already have a code coverage numbers using sonar as below. It > currently shows only the numbers for unit tests. > https://analysis.apache.org/dashboard/index/100206 > 2. The below link has an explanation for using it for both for integration > and unit tests. > http://docs.codehaus.org/display/SONAR/Code+Coverage+by+Integration+Tests+for+Java+Project > 3. Many links suggests it has good decision coverage facility compared to > other coverage tools. > http://onlysoftware.wordpress.com/2012/12/19/code-coverage-tools-jacoco-cobertura-emma-comparison-in-sonar/ > Logging this bug to track this effort and changes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6910) Phase 1: tagging of test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6910. - Resolution: Fixed > Phase 1: tagging of test cases > -- > > Key: CLOUDSTACK-6910 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6910 > 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: Abhinandan Prateek >Assignee: Santhosh Kumar Edukulla >Priority: Critical > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7204) Simulator on master is broken
Santhosh Kumar Edukulla created CLOUDSTACK-7204: --- Summary: Simulator on master is broken Key: CLOUDSTACK-7204 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7204 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Santhosh Kumar Edukulla Assignee: Anthony Xu Below errors are seen when building simulator. -- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation failure: [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[230,8] error: 'try' without 'catch', 'finally' or resource declarations [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[251,8] error: 'try' without 'catch', 'finally' or resource declarations === Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation failure: [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/ha/SimulatorInvestigator.java:[93,40] error: incomparable types: PowerState and State [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockVmManagerImpl.java:[357,19] error: no suitable constructor found for CheckVirtualMachineAnswer(CheckVirtualMachineCommand,State,int) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,String) is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,PowerState,Integer) is not applicable [ERROR] (actual argument State cannot be converted to PowerState by method invocation conversion) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,PowerState,Integer,String) is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer() is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockVmManagerImpl.java:[507,15] error: no suitable constructor found for RevertToVMSnapshotAnswer(RevertToVMSnapshotCommand,List,State) [ERROR] -> [Help 1] [ERROR] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7204) Simulator on master is broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7204: Priority: Blocker (was: Major) > Simulator on master is broken > - > > Key: CLOUDSTACK-7204 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7204 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Santhosh Kumar Edukulla >Assignee: Anthony Xu >Priority: Blocker > > Below errors are seen when building simulator. > -- > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile > (default-compile) on project cloud-plugin-hypervisor-simulator: Compilation > failure: Compilation failure: > [ERROR] > /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[230,8] > error: 'try' without 'catch', 'finally' or resource declarations > [ERROR] > /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[251,8] > error: 'try' without 'catch', 'finally' or resource declarations > === > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile > (default-compile) on project cloud-plugin-hypervisor-simulator: Compilation > failure: Compilation failure: > [ERROR] > /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/ha/SimulatorInvestigator.java:[93,40] > error: incomparable types: PowerState and State > [ERROR] > /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockVmManagerImpl.java:[357,19] > error: no suitable constructor found for > CheckVirtualMachineAnswer(CheckVirtualMachineCommand,State,int) > [ERROR] constructor > CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,String) > is not applicable > [ERROR] (actual and formal argument lists differ in length) > [ERROR] constructor > CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,PowerState,Integer) > is not applicable > [ERROR] (actual argument State cannot be converted to PowerState by method > invocation conversion) > [ERROR] constructor > CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,PowerState,Integer,String) > is not applicable > [ERROR] (actual and formal argument lists differ in length) > [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer() is > not applicable > [ERROR] (actual and formal argument lists differ in length) > [ERROR] > /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockVmManagerImpl.java:[507,15] > error: no suitable constructor found for > RevertToVMSnapshotAnswer(RevertToVMSnapshotCommand,List,State) > [ERROR] -> [Help 1] > [ERROR] > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7204) Simulator on master is broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-7204: Description: Below errors are seen when building simulator. Possible commit "330c4ba57856c161d34b81b2ae4e59877e28eb19" causing the issue, if it is not related to you, please reassign accordingly. -- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation failure: [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[230,8] error: 'try' without 'catch', 'finally' or resource declarations [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[251,8] error: 'try' without 'catch', 'finally' or resource declarations === Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation failure: [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/ha/SimulatorInvestigator.java:[93,40] error: incomparable types: PowerState and State [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockVmManagerImpl.java:[357,19] error: no suitable constructor found for CheckVirtualMachineAnswer(CheckVirtualMachineCommand,State,int) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,String) is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,PowerState,Integer) is not applicable [ERROR] (actual argument State cannot be converted to PowerState by method invocation conversion) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,PowerState,Integer,String) is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer() is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockVmManagerImpl.java:[507,15] error: no suitable constructor found for RevertToVMSnapshotAnswer(RevertToVMSnapshotCommand,List,State) [ERROR] -> [Help 1] [ERROR] was: Below errors are seen when building simulator. -- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation failure: [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[230,8] error: 'try' without 'catch', 'finally' or resource declarations [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/resource/AgentRoutingResource.java:[251,8] error: 'try' without 'catch', 'finally' or resource declarations === Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project cloud-plugin-hypervisor-simulator: Compilation failure: Compilation failure: [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/ha/SimulatorInvestigator.java:[93,40] error: incomparable types: PowerState and State [ERROR] /home/santhosh/softwares/cs_new_master/cloudstack/plugins/hypervisors/simulator/src/com/cloud/agent/manager/MockVmManagerImpl.java:[357,19] error: no suitable constructor found for CheckVirtualMachineAnswer(CheckVirtualMachineCommand,State,int) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,String) is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,PowerState,Integer) is not applicable [ERROR] (actual argument State cannot be converted to PowerState by method invocation conversion) [ERROR] constructor CheckVirtualMachineAnswer.CheckVirtualMachineAnswer(CheckVirtualMachineCommand,PowerState,Integer,String) is not applicable [ERROR] (actual and formal argument lists differ in length) [ERROR] constructor CheckVirtualM
[jira] [Resolved] (CLOUDSTACK-5121) cloudstackConnection was called with invalid arguments and so test cases are failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-5121. - Resolution: Fixed > cloudstackConnection was called with invalid arguments and so test cases are > failing > > > Key: CLOUDSTACK-5121 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5121 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Reporter: Santhosh Kumar Edukulla >Assignee: Santhosh Kumar Edukulla > > Many Test Cases are failing with below trace because of invalid > initialization of user connection object. > Traceback (most recent call last): > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File "/root/cloudstack/test/integration/component/test_volumes.py", line > 1108, in test_create_volume_under_domain > domapiclient = self.testClient.getUserApiClient(account=domuser.name, > domain=dom.name) > File > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackTestClient.py", line > 195, in getUserApiClient > self.createUserApiClient(account, domain, type) > :q > self.connection.logging) > TypeError: __init__() takes at most 6 arguments (9 given) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-5269) [Automation] test_shared_networks failed to import "get_free_vlan" and failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla reassigned CLOUDSTACK-5269: --- Assignee: Santhosh Kumar Edukulla > [Automation] test_shared_networks failed to import "get_free_vlan" and failed > -- > > Key: CLOUDSTACK-5269 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5269 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.3.0 > Environment: Basic zone > Automation >Reporter: Rayees Namathponnan >Assignee: Santhosh Kumar Edukulla > Fix For: 4.3.0 > > > Steps to reproduce > execute test_shared_networks.py in basic zone; test case failed to execute > with below error > + nosetests --with-xunit --xunit-file=test_shared_networks.xml --with-marvin > --marvin-config=/hudson/scripts/bvt_basic_sg_kvm.cfg > /Repo_30X/ipcl/cloudstack/test//integration/component/test_shared_networks.py > --load -a tags=sg -a tags=basic > ERROR > == > ERROR: Failure: ImportError (cannot import name get_free_vlan) > -- > Traceback (most recent call last): > File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 132, in run > self.beforeTest(result) > File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 74, in > beforeTest > beforeTest(self.test) > File "/usr/local/lib/python2.7/site-packages/nose/proxy.py", line 117, in > beforeTest > self.plugins.beforeTest(self.test) > File "/usr/local/lib/python2.7/site-packages/nose/plugins/manager.py", line > 99, in __call__ > return self.call(*arg, **kw) > File "/usr/local/lib/python2.7/site-packages/nose/plugins/manager.py", line > 167, in simple > result = meth(*arg, **kw) > File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py", line > 130, in beforeTest > self.testclient.identifier = '-'.join([self.identifier, self.testName]) > TypeError: sequence item 0: expected string, NoneType found > -- > Ran 0 tests in 0.023s > FAILED (errors=1) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5411) [Automation]: Moving Build Scripts maintained in separate repo to cloudstack repo
Santhosh Kumar Edukulla created CLOUDSTACK-5411: --- Summary: [Automation]: Moving Build Scripts maintained in separate repo to cloudstack repo Key: CLOUDSTACK-5411 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5411 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, marvin Reporter: Santhosh Kumar Edukulla Currently, there were few build scripts used for CI and other build automation purposes. These also uses marvin features sometimes. These scripts are existing in separate repo. Moving them to marvin folder under cloudstack repo. Any change in marvin currently has to be looked up for referneces in another repo for refactoring. With this, all build scripts are available under cloudstack repo and easy for maintenance. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5411) [Automation]: Moving Build Scripts maintained in separate repo to cloudstack repo
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla updated CLOUDSTACK-5411: Description: Currently, there were few build scripts used for CI and other build automation purposes. These also uses marvin features sometimes. These scripts are existing in separate repo. Moving them to marvin folder under cloudstack repo. Any change in marvin currently has to be looked up for referneces in another repo for refactoring. With this, all build scripts are available under cloudstack repo and easy for maintenance. Build scripts currently are available here: https://github.com/vogxn/cloud-autodeploy/tree/acs-infra-fmt was: Currently, there were few build scripts used for CI and other build automation purposes. These also uses marvin features sometimes. These scripts are existing in separate repo. Moving them to marvin folder under cloudstack repo. Any change in marvin currently has to be looked up for referneces in another repo for refactoring. With this, all build scripts are available under cloudstack repo and easy for maintenance. > [Automation]: Moving Build Scripts maintained in separate repo to cloudstack > repo > - > > Key: CLOUDSTACK-5411 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5411 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, marvin >Reporter: Santhosh Kumar Edukulla > > Currently, there were few build scripts used for CI and other build > automation purposes. These also uses marvin features sometimes. These scripts > are existing in separate repo. Moving them to marvin folder under cloudstack > repo. > Any change in marvin currently has to be looked up for referneces in another > repo for refactoring. With this, all build scripts are available under > cloudstack repo and easy for maintenance. > Build scripts currently are available here: > https://github.com/vogxn/cloud-autodeploy/tree/acs-infra-fmt -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5413) [Automation]: Misc Changes
Santhosh Kumar Edukulla created CLOUDSTACK-5413: --- Summary: [Automation]: Misc Changes Key: CLOUDSTACK-5413 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5413 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, marvin Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla 1. Currently, there was an issue with logging formatter under marvin. Proper format messages are not getting printed. Fixed that. 2. There were few references in existing cfg files for earlier used logger node. Removed them and added new logger node as part of pending clean up. 3. Added TestCase started and the result accordingly to runlog. This will simplify to see the test case starting , sequence of steps and final result including timestamps for test case run. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
