[jira] [Commented] (CLOUDSTACK-6673) cloudstack-setup-management make a chmod 777 on /root
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010838#comment-14010838
]
Milamber commented on CLOUDSTACK-6673:
--
Yes seems related only on Ubuntu platform.
The name of python class is:
class ubuntuFirewallConfigServer(firewallConfigServer):
[...]
#FIXME: urgly make /root writable
bash("sudo chmod 0777 /root")
Deployment of CloudStack on Ubuntu 14.04 with this last line commented works
well...
> cloudstack-setup-management make a chmod 777 on /root
> -
>
> Key: CLOUDSTACK-6673
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6673
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.4.0
> Environment: Ubuntu 14.04 / KVM
> CS 4.4.0 snapshot 20140513
>Reporter: Milamber
>Priority: Blocker
> Labels: security
>
> Before run cloudstack-setup-management, /root directory permissions are:
> drwx-- 4 root root 4096 mai 14 15:05 root
> After the runs of cloudstack-setup-management, /root directory permissions
> are:
> drwxrwxrwx 4 root root 4096 mai 14 15:05 root
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6774) [Automation]: Test case failure in test_iso.py
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010836#comment-14010836
]
ASF subversion and git services commented on CLOUDSTACK-6774:
-
Commit 80b9849981a608e46945da1ab813cd78f4bb8bcc in cloudstack's branch
refs/heads/4.4-forward from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=80b9849 ]
Disabling the failed test cases mentioned in the following tickets
integration.smoke.test_iso - CLOUDSTACK-6769, CLOUDSTACK-6774
Signed-off-by: Abhinandan Prateek
> [Automation]: Test case failure in test_iso.py
> --
>
> Key: CLOUDSTACK-6774
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6774
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, KVM
>Affects Versions: 4.4.0
>Reporter: Harikrishna Patnala
> Fix For: 4.4.0
>
> Attachments: vmops.log
>
>
> There is test case failure in test_iso.py
> 1) integration.smoke.test_iso.TestCreateIso.test_01_create_iso
> Error Message
> Exception while downloading ISO 39ce3b8d-8109-4eb5-8720-29335498a7b2: Error
> In Downloading ISO: ISO Status - No route to host
> >> begin captured stdout << -
> === TestName: test_01_create_iso | Status : FAILED ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> STARTED : TC: test_01_create_iso :::
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'apiKey':
> u'bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA',
> 'command': 'listDomains', 'signature': 'M4lkquS9SDTaPx3/CRHhYFhuLeo=',
> 'response': 'json'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : listDomains===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.22
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA&command=listDomains&response=json&signature=M4lkquS9SDTaPx3%2FCRHhYFhuLeo%3D
> HTTP/1.1" 200 159
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : [{path : u'ROOT', haschild : False, id :
> u'4046979a-e504-11e3-af30-00163e5d4a0e', name : u'ROOT', level : 0}]
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'apiKey':
> u'bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA',
> 'name': 'zone-kvm', 'command': 'listZones', 'signature':
> 'AX8BnIVOj5rL7itUP3tDkthh1BI=', 'response': 'json'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.22
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?response=json&apiKey=bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA&command=listZones&name=zone-kvm&signature=AX8BnIVOj5rL7itUP3tDkthh1BI%3D
> HTTP/1.1" 200 429
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : [{localstorageenabled : False, name : u'zone-kvm',
> guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken :
> u'd3d20165-3111-34e9-99f0-2ff502b11e2e', dns1 : u'8.8.8.8',
> securitygroupsenabled : False, allocationstate : u'Enabled', internaldns1 :
> u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype : u'Advanced',
> id : u'c9d7f436-6a58-4818-a41f-7e4ace012473', internaldns2 : u'172.16.88.7'}]
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'username': 'test-account-TestISO-test_01_create_iso-QT75TB',
> 'domainid': u'4046979a-e504-11e3-af30-00163e5d4a0e', 'firstname': 'test',
> 'lastname': 'test', 'response': 'json', 'apiKey':
> u'bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA',
> 'command': 'createAccount', 'accounttype': 0, 'signature':
> 'fqs9teBsE6BUQc0sfKQ8AIgwKhI=', 'password': 'password', 'email':
> 'test-acco...@test.com'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : createAccount===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.22
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?username=test-account-TestISO-test_01_cr
[jira] [Commented] (CLOUDSTACK-6769) [Automation]: Test case failure in test_iso.py
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010835#comment-14010835
]
ASF subversion and git services commented on CLOUDSTACK-6769:
-
Commit 80b9849981a608e46945da1ab813cd78f4bb8bcc in cloudstack's branch
refs/heads/4.4-forward from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=80b9849 ]
Disabling the failed test cases mentioned in the following tickets
integration.smoke.test_iso - CLOUDSTACK-6769, CLOUDSTACK-6774
Signed-off-by: Abhinandan Prateek
> [Automation]: Test case failure in test_iso.py
> --
>
> Key: CLOUDSTACK-6769
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6769
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, XenServer
>Affects Versions: 4.4.0
>Reporter: Harikrishna Patnala
> Fix For: 4.4.0
>
>
> There is test case failure in test_iso.py
>1) integration.smoke.test_iso.TestCreateIso.test_01_create_iso
> Error Message
> Exception while downloading ISO 06f0617c-4605-4a8f-855b-085486a1fd4b: Error
> In Downloading ISO: ISO Status - Network is unreachable
> === TestName: test_01_create_iso | Status : FAILED ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> STARTED : TC: test_01_create_iso :::
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'apiKey':
> u'kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w',
> 'command': 'listDomains', 'signature': 'Or2nHFPqukzhTba7v4PyKSS2Obc=',
> 'response': 'json'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : listDomains===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w&command=listDomains&response=json&signature=Or2nHFPqukzhTba7v4PyKSS2Obc%3D
> HTTP/1.1" 200 159
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : [{path : u'ROOT', haschild : False, id :
> u'45612b7c-e49c-11e3-a141-00163e189e44', name : u'ROOT', level : 0}]
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'apiKey':
> u'kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w',
> 'name': 'zone-xen', 'command': 'listZones', 'signature':
> '77O72WZATq83Kw9J9yK0yKsjlHM=', 'response': 'json'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?response=json&apiKey=kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w&command=listZones&name=zone-xen&signature=77O72WZATq83Kw9J9yK0yKsjlHM%3D
> HTTP/1.1" 200 446
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : [{localstorageenabled : False, name : u'zone-xen',
> guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken :
> u'921064dc-f25a-3393-94b7-7ba269fa1f82', dns2 : u'8.8.4.4', dns1 :
> u'8.8.8.8', securitygroupsenabled : False, allocationstate : u'Enabled',
> internaldns1 : u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype :
> u'Advanced', id : u'5c872b2f-53eb-46bd-8d7f-f9654f509b39', internaldns2 :
> u'172.16.88.7'}]
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'username': 'test-account-TestISO-test_01_create_iso-UI4FTT',
> 'domainid': u'45612b7c-e49c-11e3-a141-00163e189e44', 'firstname': 'test',
> 'lastname': 'test', 'response': 'json', 'apiKey':
> u'kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w',
> 'command': 'createAccount', 'accounttype': 0, 'signature':
> 'q5ftoGqB/V1+Q+L3FGbYsOWsON0=', 'password': 'password', 'email':
> 'test-acco...@test.com'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : createAccount===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?username=test-account-TestISO-test_01_create_iso-UI4FTT&domainid=45612b7c-e49c-11e3-a141-00163e189e44&firstna
[jira] [Created] (CLOUDSTACK-6795) [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
Sanjeev N created CLOUDSTACK-6795:
-
Summary: [OVS]Faile to upgrade network from vlan isolation to
network with ovs provider
Key: CLOUDSTACK-6795
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6795
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.4.0
Environment: Latest build from 4.4 with commit
d130530bd3e1cd6d8249d5045e00e4e4e2201521
Reporter: Sanjeev N
Assignee: Murali Reddy
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.rar
[OVS]Faile to upgrade network from vlan isolation to network with ovs provider
Steps to reproduce:
==
1.Bring up CS in advanced zone with xen cluster
2.Create physical network with GRE isolation
3.Create an isolated network offering with default offering
"DefaultIsolatedNetworkOfferingWithSourceNatService"
4.Deploy one vm using above network offering
5.Create another guest network with Virtual networking and OVS as the
connectivity service provider
6.Stop the vm and upgrade network with above network offering
Result:
=
Failed to upgrade network with the offering which has connectivity service and
ovs as the provider
Observations:
==
Following is the log snippet from MS log:
2014-05-28 07:27:28,419 DEBUG [c.c.a.t.Request]
(API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Seq
4-1333065489701674831: Received: { Ans: , MgmtId: 7332683579487, via: 4, Ver:
v1, Flags: 10, { Answer } }
2014-05-28 07:27:28,429 INFO [o.a.c.s.v.VolumeServiceImpl]
(API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Volume 26 is not
referred anywhere, remove it from volumes table
2014-05-28 07:27:28,435 DEBUG [c.c.v.VirtualMachineManagerImpl]
(API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Expunged
VM[DomainRouter|r-26-VM]
2014-05-28 07:27:28,458 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-b2ec9be1) Zone 1 is ready to launch console proxy
2014-05-28 07:27:28,480 DEBUG [c.c.n.NetworkServiceImpl]
(API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Implementing the
network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
resources as a part of network update
2014-05-28 07:27:28,486 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Asking Ovs to
implemenet Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15]
2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
(API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) entering OvsElement
implement function for network vlan1 (state Implemented)
2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
(API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Checking if OvsElement
can handle service Connectivity on network vlan1
2014-05-28 07:27:28,487 WARN [c.c.n.NetworkServiceImpl]
(API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Failed to implement
network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
resources as a part of network update due to
com.cloud.utils.exception.CloudRuntimeException: Failed to implement provider
Ovs for network with specified id
at
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1081)
at
com.cloud.network.NetworkServiceImpl.updateGuestNetwork(NetworkServiceImpl.java:2303)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy
[jira] [Updated] (CLOUDSTACK-6795) [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N updated CLOUDSTACK-6795:
--
Attachment: management-server.rar
Attached MS log file
> [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
> --
>
> Key: CLOUDSTACK-6795
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6795
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.4.0
> Environment: Latest build from 4.4 with commit
> d130530bd3e1cd6d8249d5045e00e4e4e2201521
>Reporter: Sanjeev N
>Assignee: Murali Reddy
>Priority: Critical
> Labels: ovs
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> [OVS]Faile to upgrade network from vlan isolation to network with ovs provider
> Steps to reproduce:
> ==
> 1.Bring up CS in advanced zone with xen cluster
> 2.Create physical network with GRE isolation
> 3.Create an isolated network offering with default offering
> "DefaultIsolatedNetworkOfferingWithSourceNatService"
> 4.Deploy one vm using above network offering
> 5.Create another guest network with Virtual networking and OVS as the
> connectivity service provider
> 6.Stop the vm and upgrade network with above network offering
> Result:
> =
> Failed to upgrade network with the offering which has connectivity service
> and ovs as the provider
> Observations:
> ==
> Following is the log snippet from MS log:
> 2014-05-28 07:27:28,419 DEBUG [c.c.a.t.Request]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Seq
> 4-1333065489701674831: Received: { Ans: , MgmtId: 7332683579487, via: 4,
> Ver: v1, Flags: 10, { Answer } }
> 2014-05-28 07:27:28,429 INFO [o.a.c.s.v.VolumeServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Volume 26 is not
> referred anywhere, remove it from volumes table
> 2014-05-28 07:27:28,435 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Expunged
> VM[DomainRouter|r-26-VM]
> 2014-05-28 07:27:28,458 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-b2ec9be1) Zone 1 is ready to launch console proxy
> 2014-05-28 07:27:28,480 DEBUG [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Implementing the
> network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
> resources as a part of network update
> 2014-05-28 07:27:28,486 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Asking Ovs to
> implemenet Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15]
> 2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) entering OvsElement
> implement function for network vlan1 (state Implemented)
> 2014-05-28 07:27:28,486 DEBUG [c.c.n.e.OvsElement]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Checking if
> OvsElement can handle service Connectivity on network vlan1
> 2014-05-28 07:27:28,487 WARN [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-62:ctx-3460d0b7 job-119 ctx-672875b5) Failed to implement
> network Ntwk[f803e17f-b59b-4229-9e70-5bb4fcfc2570|Guest|15] elements and
> resources as a part of network update due to
> com.cloud.utils.exception.CloudRuntimeException: Failed to implement provider
> Ovs for network with specified id
> at
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1081)
> at
> com.cloud.network.NetworkServiceImpl.updateGuestNetwork(NetworkServiceImpl.java:2303)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEven
[jira] [Commented] (CLOUDSTACK-6392) system template always create with name "master" instead of specific branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010830#comment-14010830 ] ASF subversion and git services commented on CLOUDSTACK-6392: - Commit 63090434b1cb4e7b87f0e024fbbc644faee863f7 in cloudstack's branch refs/heads/4.4-forward from rayeesn [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6309043 ] CLOUDSTACK-6392: system template always create with name master instead of specific branch Signed-off-by: Abhinandan Prateek > system template always create with name "master" instead of specific branch > --- > > Key: CLOUDSTACK-6392 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6392 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.4.0 >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Critical > Fix For: 4.4.0 > > > Create system vm from jenkins.buildacloud.org > in 4.4 System vm always create with same name > "systemvm64template-master-xen.vhd" > it should be create with name "systemvm64template-4.4-xen.vhd" -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6392) system template always create with name "master" instead of specific branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010829#comment-14010829 ] ASF subversion and git services commented on CLOUDSTACK-6392: - Commit 5f11c2e0be06ff1580ee7898b6316a4d61412db8 in cloudstack's branch refs/heads/master from rayeesn [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5f11c2e ] CLOUDSTACK-6392: system template always create with name master instead of specific branch Signed-off-by: Abhinandan Prateek > system template always create with name "master" instead of specific branch > --- > > Key: CLOUDSTACK-6392 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6392 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.4.0 >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Critical > Fix For: 4.4.0 > > > Create system vm from jenkins.buildacloud.org > in 4.4 System vm always create with same name > "systemvm64template-master-xen.vhd" > it should be create with name "systemvm64template-4.4-xen.vhd" -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6771) [LOG] Received unknown parameters for command createVolume. Unknown parameters : ctxdetails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010831#comment-14010831
]
prashant kumar mishra commented on CLOUDSTACK-6771:
---
seeing same worming for detach volume .
ocessStatus: 0, resultCode: 0, result: null, initMsid: 7204337877055,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-05-28 07:24:25,139 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-19:ctx-affde0fb job-64 ctx-e36128eb) Received unknown
parameters for command detachVolume. Unknown parameters : ctxdetails
2014-05-28 07:24:25,175 INFO [c.c.s.VolumeApiServiceImpl]
(API-Job-Executor-19:ctx-affde0fb job-64 ctx-e36128eb) Trying to attaching
volume 10to vm instance:6, update async job-64 progress status
> [LOG] Received unknown parameters for command createVolume. Unknown
> parameters : ctxdetails
> ---
>
> Key: CLOUDSTACK-6771
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6771
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.4.0
>Reporter: prashant kumar mishra
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: Logs.rar
>
>
> created a new volume of 55GB with custom disk offering. task was successful
> but is see warning in logs
> snippet
> ==
> 2014-05-27 09:47:00,482 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-1:ctx-56ac812a job-37 ctx-34d4dbfc) Received unknown
> parameters for command createVolume. Unknown parameters : ctxdetails
> 2
> complete Log
> =
> 2014-05-27 09:47:00,448 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-7:ctx-bc4bb164 ctx-6f7e282f) submit async job-37, details:
> AsyncJobVO {id:37, userId: 2, accountId: 2, instanceType: Volume, instanceId:
> 8, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"sessionkey":"ROQyTEQqnW7tUMyOC8boj6np4PE\u003d","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","httpmethod":"GET","zoneId":"ae6be023-91c9-47d0-9ce1-0898c4429ed4","size":"55","response":"json","id":"8","ctxDetails":"{\"com.cloud.storage.Volume\":8,\"Volume\":\"a13739c0-e2c6-4a67-b438-c931dcf6241f\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":6}","diskOfferingId":"97f6ed25-1296-45d5-a5f7-e2b87741086d","name":"fifty","_":"1401179180263","ctxAccountId":"2","uuid":"a13739c0-e2c6-4a67-b438-c931dcf6241f","ctxStartEventId":"76"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7204337877055, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-27 09:47:00,451 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-7:ctx-bc4bb164 ctx-6f7e282f) ===END=== 10.252.192.60 -- GET
> command=createVolume&response=json&sessionkey=ROQyTEQqnW7tUMyOC8boj6np4PE%3D&name=fifty&zoneId=ae6be023-91c9-47d0-9ce1-0898c4429ed4&diskOfferingId=97f6ed25-1296-45d5-a5f7-e2b87741086d&size=55&_=1401179180263
> 2014-05-27 09:47:00,460 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-1:ctx-56ac812a job-37) Add job-37 into job monitoring
> 2014-05-27 09:47:00,462 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-1:ctx-56ac812a job-37) Executing AsyncJobVO {id:37, userId:
> 2, accountId: 2, instanceType: Volume, instanceId: 8, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"sessionkey":"ROQyTEQqnW7tUMyOC8boj6np4PE\u003d","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","httpmethod":"GET","zoneId":"ae6be023-91c9-47d0-9ce1-0898c4429ed4","size":"55","response":"json","id":"8","ctxDetails":"{\"com.cloud.storage.Volume\":8,\"Volume\":\"a13739c0-e2c6-4a67-b438-c931dcf6241f\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":6}","diskOfferingId":"97f6ed25-1296-45d5-a5f7-e2b87741086d","name":"fifty","_":"1401179180263","ctxAccountId":"2","uuid":"a13739c0-e2c6-4a67-b438-c931dcf6241f","ctxStartEventId":"76"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7204337877055, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-27 09:47:00,482 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-1:ctx-56ac812a job-37 ctx-34d4dbfc) Received unknown
> parameters for command createVolume. Unknown parameters : ctxdetails
> 2014-05-27 09:47:00,539 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-1:ctx-56ac812a job-37 ctx-34d4dbfc) Complete async job-37,
> jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.VolumeResponse/volume/{"id":"a13739c0-e2c6-4a67-b43
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010826#comment-14010826
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit 825929d7e98cbd680c57ff424f987bbb0b0aff62 in cloudstack's branch
refs/heads/4.3.0-forward from ilya
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=825929d ]
CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic
> [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
> --
>
> Key: CLOUDSTACK-6317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6317
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.3.0, 4.4.0
> Environment: VMware vCenter 5.1, ESXi 5.0 hosts
> MS with ACS 4.3.0
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.4.0, 4.3.1
>
>
> Prior to ACS 4.3.0 CloudStack used to support tagged VLAN for management /
> storage / control traffic via traffic label, where admin would specify the
> VLAN in comma separated string of vmware network traffic label. E.g.
> vSwitch0,100 - This means management traffic would use standard vSwitch port
> group tagged with VLAN 100 which sits on vSwitch0 existing on ESXi host.
> This is functionality was broken since below commit in ACS 4.3 branch,
> Commit 7c4831df9292115466fb9e01fcba952a5dad31c1 in branch refs/heads/4.3 from
> Hugo Trippaers
> [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7c4831d ]
> This commit overwrites the parsed vSwitch name, from traffic label, with
> traffic label specified by admin resulting into below error during deployment
> of SSVM (or any VM that needs management/storage traffic)
> 2014-04-01 08:23:19,866 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-9:ctx-862d86ff 10.102.192.3) VM v-2-VM will be started with NIC
> device type: E1000
> 2014-04-01 08:23:19,866 INFO [c.c.h.v.r.VmwareResource]
> (DirectAgent-9:ctx-862d86ff 10.102.192.3) Prepare NIC device based on NicTO:
> {"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"07c38800-6da3-4596-b0ea-09047d45970e","mac":"02:00:63:46:00:02","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false,"name":"vSwitch0,100"}
> 2014-04-01 08:23:21,150 ERROR [c.c.h.v.m.HypervisorHostHelper]
> (DirectAgent-6:ctx-a6062e05 10.102.192.3) Unable to find vSwitchvSwitch0,100
> 2014-04-01 08:23:21,151 WARN [c.c.h.v.r.VmwareResource]
> (DirectAgent-6:ctx-a6062e05 10.102.192.3) StartCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find vSwitchvSwitch0,100
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010825#comment-14010825
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit 869b2535b72af3c0f6d77425f1416d245041aa3a in cloudstack's branch
refs/heads/4.3.0-forward from root
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=869b253 ]
Revert "CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic"
This reverts commit f0a98baa0c3258954a4fc4424d8c2f22a50d9ed4.
> [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
> --
>
> Key: CLOUDSTACK-6317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6317
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.3.0, 4.4.0
> Environment: VMware vCenter 5.1, ESXi 5.0 hosts
> MS with ACS 4.3.0
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.4.0, 4.3.1
>
>
> Prior to ACS 4.3.0 CloudStack used to support tagged VLAN for management /
> storage / control traffic via traffic label, where admin would specify the
> VLAN in comma separated string of vmware network traffic label. E.g.
> vSwitch0,100 - This means management traffic would use standard vSwitch port
> group tagged with VLAN 100 which sits on vSwitch0 existing on ESXi host.
> This is functionality was broken since below commit in ACS 4.3 branch,
> Commit 7c4831df9292115466fb9e01fcba952a5dad31c1 in branch refs/heads/4.3 from
> Hugo Trippaers
> [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7c4831d ]
> This commit overwrites the parsed vSwitch name, from traffic label, with
> traffic label specified by admin resulting into below error during deployment
> of SSVM (or any VM that needs management/storage traffic)
> 2014-04-01 08:23:19,866 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-9:ctx-862d86ff 10.102.192.3) VM v-2-VM will be started with NIC
> device type: E1000
> 2014-04-01 08:23:19,866 INFO [c.c.h.v.r.VmwareResource]
> (DirectAgent-9:ctx-862d86ff 10.102.192.3) Prepare NIC device based on NicTO:
> {"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"07c38800-6da3-4596-b0ea-09047d45970e","mac":"02:00:63:46:00:02","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false,"name":"vSwitch0,100"}
> 2014-04-01 08:23:21,150 ERROR [c.c.h.v.m.HypervisorHostHelper]
> (DirectAgent-6:ctx-a6062e05 10.102.192.3) Unable to find vSwitchvSwitch0,100
> 2014-04-01 08:23:21,151 WARN [c.c.h.v.r.VmwareResource]
> (DirectAgent-6:ctx-a6062e05 10.102.192.3) StartCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find vSwitchvSwitch0,100
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6754) SSVM not responding with S3 secondary sotre
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010821#comment-14010821 ] Pavan Kumar Bandarupally commented on CLOUDSTACK-6754: -- Since the storage is S3, i haven't manually seeded the system VM template. The template was picked up from the URL mentioned in vm_template table [http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2] it seems. So , we need to update that URL location in order for this to work. I am reopening the bug to track and fix this. If a new bug is needed to fix the same let me know will open another one or if you feel the fix can be associated with this only please update accordingly. > SSVM not responding with S3 secondary sotre > --- > > Key: CLOUDSTACK-6754 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6754 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, SystemVM, Template >Affects Versions: 4.4.0 > Environment: Host: Xenserver > Secondary Store: Image store with S3 as provider >Reporter: Pavan Kumar Bandarupally >Assignee: Min Chen >Priority: Blocker > Fix For: 4.4.0 > > Attachments: cloud.log, cloudoutfile.zip, management-server.log > > > A new zone is created and systemVMs are up. The systemvm template is > downloaded to S3 bucket. Once the SSVMs are up, the default BUILTIN centos > template or any other template that we try to register manually are not > getting downloaded to SSVM. There is no exception generated as well. > The registerTemplate API call is just listed in the MS traces and no further > action happens. Attaching the MS logs and SSVM log. There is no trace of any > exception in SSVM log as well. Attaching the /var/log/cloud/cloud.out , which > is the only file that has some exception listed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CLOUDSTACK-6754) SSVM not responding with S3 secondary sotre
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavan Kumar Bandarupally reopened CLOUDSTACK-6754: -- > SSVM not responding with S3 secondary sotre > --- > > Key: CLOUDSTACK-6754 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6754 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, SystemVM, Template >Affects Versions: 4.4.0 > Environment: Host: Xenserver > Secondary Store: Image store with S3 as provider >Reporter: Pavan Kumar Bandarupally >Assignee: Min Chen >Priority: Blocker > Fix For: 4.4.0 > > Attachments: cloud.log, cloudoutfile.zip, management-server.log > > > A new zone is created and systemVMs are up. The systemvm template is > downloaded to S3 bucket. Once the SSVMs are up, the default BUILTIN centos > template or any other template that we try to register manually are not > getting downloaded to SSVM. There is no exception generated as well. > The registerTemplate API call is just listed in the MS traces and no further > action happens. Attaching the MS logs and SSVM log. There is no trace of any > exception in SSVM log as well. Attaching the /var/log/cloud/cloud.out , which > is the only file that has some exception listed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6781) [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010801#comment-14010801 ] ASF subversion and git services commented on CLOUDSTACK-6781: - Commit 9cd6c4f2ae0f822d018afa627f7f07cb11afccdc in cloudstack's branch refs/heads/master from [~aprateek] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9cd6c4f ] Revert "CLOUDSTACK-6781: Disabling failing test corresponding to this bug" This reverts commit 7bc7377a175260f1efcd79bb77ad64bc9bb93d26. > [Automation] > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > failing on 4.4 > --- > > Key: CLOUDSTACK-6781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6781 > 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: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > is failing > There are two test cases which test the functionality by creating an ip range > and then deleting it. > The delete isnt happening in the first test case which is causing the second > test case to fail. > This is surfaced after the commit 2ab7bcade2f37cb17e071a6154fdae1d80e4ff99 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6781) [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek resolved CLOUDSTACK-6781. Resolution: Fixed > [Automation] > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > failing on 4.4 > --- > > Key: CLOUDSTACK-6781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6781 > 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: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > is failing > There are two test cases which test the functionality by creating an ip range > and then deleting it. > The delete isnt happening in the first test case which is causing the second > test case to fail. > This is surfaced after the commit 2ab7bcade2f37cb17e071a6154fdae1d80e4ff99 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6781) [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010799#comment-14010799 ] ASF subversion and git services commented on CLOUDSTACK-6781: - Commit a3dd5d1522bd73484b58af0013157c8bbdec4126 in cloudstack's branch refs/heads/4.4-forward from [~aprateek] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a3dd5d1 ] Revert "CLOUDSTACK-6781: Disabling failing test corresponding to this bug" This reverts commit 5c30809a7de8f8e45012e0afb0ae081973d137e8. > [Automation] > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > failing on 4.4 > --- > > Key: CLOUDSTACK-6781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6781 > 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: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > is failing > There are two test cases which test the functionality by creating an ip range > and then deleting it. > The delete isnt happening in the first test case which is causing the second > test case to fail. > This is surfaced after the commit 2ab7bcade2f37cb17e071a6154fdae1d80e4ff99 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6781) [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010798#comment-14010798 ] ASF subversion and git services commented on CLOUDSTACK-6781: - Commit b0c797c62896c77405077fc9490f04912b8766e5 in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b0c797c ] FIXED CLOUDSTACK-6781 [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4 Signed-off-by: Abhinandan Prateek > [Automation] > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > failing on 4.4 > --- > > Key: CLOUDSTACK-6781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6781 > 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: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > is failing > There are two test cases which test the functionality by creating an ip range > and then deleting it. > The delete isnt happening in the first test case which is causing the second > test case to fail. > This is surfaced after the commit 2ab7bcade2f37cb17e071a6154fdae1d80e4ff99 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6781) [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010796#comment-14010796 ] ASF subversion and git services commented on CLOUDSTACK-6781: - Commit c91780449ae13d40ba9a2acfc5e0e6176f1beaee in cloudstack's branch refs/heads/4.4-forward from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c917804 ] FIXED CLOUDSTACK-6781 [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4 Signed-off-by: Abhinandan Prateek > [Automation] > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > failing on 4.4 > --- > > Key: CLOUDSTACK-6781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6781 > 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: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > is failing > There are two test cases which test the functionality by creating an ip range > and then deleting it. > The delete isnt happening in the first test case which is causing the second > test case to fail. > This is surfaced after the commit 2ab7bcade2f37cb17e071a6154fdae1d80e4ff99 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6774) [Automation]: Test case failure in test_iso.py
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6774:
Issue Type: Test (was: Bug)
> [Automation]: Test case failure in test_iso.py
> --
>
> Key: CLOUDSTACK-6774
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6774
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, KVM
>Affects Versions: 4.4.0
>Reporter: Harikrishna Patnala
> Fix For: 4.4.0
>
> Attachments: vmops.log
>
>
> There is test case failure in test_iso.py
> 1) integration.smoke.test_iso.TestCreateIso.test_01_create_iso
> Error Message
> Exception while downloading ISO 39ce3b8d-8109-4eb5-8720-29335498a7b2: Error
> In Downloading ISO: ISO Status - No route to host
> >> begin captured stdout << -
> === TestName: test_01_create_iso | Status : FAILED ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> STARTED : TC: test_01_create_iso :::
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'apiKey':
> u'bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA',
> 'command': 'listDomains', 'signature': 'M4lkquS9SDTaPx3/CRHhYFhuLeo=',
> 'response': 'json'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : listDomains===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.22
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA&command=listDomains&response=json&signature=M4lkquS9SDTaPx3%2FCRHhYFhuLeo%3D
> HTTP/1.1" 200 159
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : [{path : u'ROOT', haschild : False, id :
> u'4046979a-e504-11e3-af30-00163e5d4a0e', name : u'ROOT', level : 0}]
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'apiKey':
> u'bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA',
> 'name': 'zone-kvm', 'command': 'listZones', 'signature':
> 'AX8BnIVOj5rL7itUP3tDkthh1BI=', 'response': 'json'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.22
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?response=json&apiKey=bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA&command=listZones&name=zone-kvm&signature=AX8BnIVOj5rL7itUP3tDkthh1BI%3D
> HTTP/1.1" 200 429
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : [{localstorageenabled : False, name : u'zone-kvm',
> guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken :
> u'd3d20165-3111-34e9-99f0-2ff502b11e2e', dns1 : u'8.8.8.8',
> securitygroupsenabled : False, allocationstate : u'Enabled', internaldns1 :
> u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype : u'Advanced',
> id : u'c9d7f436-6a58-4818-a41f-7e4ace012473', internaldns2 : u'172.16.88.7'}]
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'username': 'test-account-TestISO-test_01_create_iso-QT75TB',
> 'domainid': u'4046979a-e504-11e3-af30-00163e5d4a0e', 'firstname': 'test',
> 'lastname': 'test', 'response': 'json', 'apiKey':
> u'bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA',
> 'command': 'createAccount', 'accounttype': 0, 'signature':
> 'fqs9teBsE6BUQc0sfKQ8AIgwKhI=', 'password': 'password', 'email':
> 'test-acco...@test.com'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : createAccount===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.22
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?username=test-account-TestISO-test_01_create_iso-QT75TB&domainid=4046979a-e504-11e3-af30-00163e5d4a0e&firstname=test&lastname=test&email=test-account%40test.com&apiKey=bzV60R-UeAfL_TWX3IRsCG96vBO3QQE6bc10nxhra8xW_Szc7hiB7adMEWEzT_MBs1X-9Uek94CSx5EdScX3TA&command=createAccount&accounttype=0&signature=fqs9teBsE6BUQc0sfKQ8AIgwKhI%3D&password=password&response=json
> HTTP/1.1" 200 1650
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso):
[jira] [Updated] (CLOUDSTACK-6770) [Automation]: Test case failure in test_primary_storage.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6770: Issue Type: Test (was: Bug) > [Automation]: Test case failure in test_primary_storage.py > -- > > Key: CLOUDSTACK-6770 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6770 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.4.0 >Reporter: Harikrishna Patnala > Fix For: 4.4.0 > > Attachments: test_01_primary_storage_iscsi_REPORT.rtf, > test_01_primary_storage_nfs_REPORT.rtf, vmops.log > > > There are test case failures in test_primary_storage.py > 1) > integration.smoke.test_primary_storage.TestPrimaryStorageServices.test_01_primary_storage_iscsi > 2) > integration.smoke.test_primary_storage.TestPrimaryStorageServices.test_01_primary_storage_nfs > Attached test reports and management server logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6776) [Automation]: Test case failure in test_non_contigiousvlan.py
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6776:
Issue Type: Test (was: Bug)
> [Automation]: Test case failure in test_non_contigiousvlan.py
> -
>
> Key: CLOUDSTACK-6776
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6776
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, KVM
>Affects Versions: 4.4.0
>Reporter: Harikrishna Patnala
> Fix For: 4.4.0
>
> Attachments: test_extendPhysicalNetworkVlan .rtf, vmops.log
>
>
> There is test case failure in test_non_contigiousvlan.py
> 1)
> integration.smoke.test_non_contigiousvlan.TestUpdatePhysicalNetwork.test_extendPhysicalNetworkVlan
> Error Message
> Job failed: {jobprocstatus : 0, created : u'2014-05-26T13:36:06-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd',
> userid : u'40470752-e504-11e3-af30-00163e5d4a0e', jobstatus : 2, jobid :
> u'168af076-cd18-44f2-997d-bbb55b7c12ad', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'physicalnetwork 200
> has allocated vnets in the range 4090-4095'}, accountid :
> u'4046c30a-e504-11e3-af30-00163e5d4a0e'}
> Attached Test Report and management server logs
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6777) [Automation]: Test case failure in test_secondary_storage.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6777: Issue Type: Test (was: Bug) > [Automation]: Test case failure in test_secondary_storage.py > > > Key: CLOUDSTACK-6777 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6777 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, KVM >Affects Versions: 4.4.0 >Reporter: Harikrishna Patnala > Fix For: 4.4.0 > > Attachments: KVM_test_02_sys_template_ready_REPORT.rtf, vmops.log > > > There is test case failure in test_secondary_storage.py > 1) > integration.smoke.test_secondary_storage.TestSecStorageServices.test_02_sys_template_ready > Error Message > Builtin template is not ready No route to host in zone > 9459d36e-a477-4a60-890b-2bc48edf1410 > >> begin captured stdout << - > === TestName: test_02_sys_template_ready | Status : FAILED === > Attached Test reports and Management server logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6775) [Automation]: Test case failure in test_iso.py
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6775:
Issue Type: Test (was: Bug)
> [Automation]: Test case failure in test_iso.py
> --
>
> Key: CLOUDSTACK-6775
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6775
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, KVM
>Affects Versions: 4.4.0
>Reporter: Harikrishna Patnala
> Fix For: 4.4.0
>
>
> There is test case failure in test_non_contigiousvlan.py
> 1)integration.smoke.test_non_contigiousvlan.TestUpdatePhysicalNetwork.test_extendPhysicalNetworkVlan
> Error Message
> Job failed: {jobprocstatus : 0, created : u'2014-05-26T13:36:06-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd',
> userid : u'40470752-e504-11e3-af30-00163e5d4a0e', jobstatus : 2, jobid :
> u'168af076-cd18-44f2-997d-bbb55b7c12ad', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'physicalnetwork 200
> has allocated vnets in the range 4090-4095'}, accountid :
> u'4046c30a-e504-11e3-af30-00163e5d4a0e'}
> Attached Test report and management server logs
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6773) [Automation]: Test case failure in test_secondary_storage.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6773: Issue Type: Test (was: Bug) > [Automation]: Test case failure in test_secondary_storage.py > > > Key: CLOUDSTACK-6773 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6773 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.4.0 >Reporter: Harikrishna Patnala > Fix For: 4.4.0 > > Attachments: test_02_sys_template_ready_REPORT.rtf, vmops.log > > > There is test case failure in test_secondary_storage.py > 1) > integration.smoke.test_secondary_storage.TestSecStorageServices.test_02_sys_template_ready > Attached Test reports and Management server logs -- 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] [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] [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] [Resolved] (CLOUDSTACK-6106) Support of VPC in HyperV
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-6106. Resolution: Fixed > Support of VPC in HyperV > > > Key: CLOUDSTACK-6106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6106 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.4.0 >Reporter: Rajesh Battala >Assignee: Rajesh Battala > Fix For: 4.4.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6143) Storage Live-Migration support for Hyper-V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala updated CLOUDSTACK-6143: --- Assignee: Devdeep Singh > Storage Live-Migration support for Hyper-V > -- > > Key: CLOUDSTACK-6143 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6143 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.4.0 >Reporter: Rajesh Battala >Assignee: Devdeep Singh > Fix For: 4.4.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6143) Storage Live-Migration support for Hyper-V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-6143. Resolution: Fixed > Storage Live-Migration support for Hyper-V > -- > > Key: CLOUDSTACK-6143 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6143 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.4.0 >Reporter: Rajesh Battala >Assignee: Devdeep Singh > Fix For: 4.4.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6109) Support of iSCSI as primary store in Hyper-V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala updated CLOUDSTACK-6109: --- Fix Version/s: (was: 4.4.0) 4.5.0 > Support of iSCSI as primary store in Hyper-V > > > Key: CLOUDSTACK-6109 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6109 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.4.0 >Reporter: Rajesh Battala >Assignee: Devdeep Singh > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (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 ] Rayees Namathponnan updated CLOUDSTACK-6793: Attachment: management-server.rar > [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 >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) > at com.cloud.utils.db.Transac
[jira] [Created] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions
Rayees Namathponnan created CLOUDSTACK-6793: --- Summary: [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 Priority: Blocker Fix For: 4.4.0 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) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.utils.db.Transaction.execute(Transaction.java:46) at com.cloud.tags.TaggedResourceManagerImpl.createTags(TaggedResourceManagerImpl.java:214) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.
[jira] [Updated] (CLOUDSTACK-6105) Windowsfication of CloudStack Management Server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6105: Fix Version/s: (was: 4.4.0) 4.5.0 > Windowsfication of CloudStack Management Server > --- > > Key: CLOUDSTACK-6105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6105 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 >Reporter: Damodar Reddy T >Assignee: Damodar Reddy T > Labels: features > Fix For: 4.5.0 > > > Currently Management Server runs on Linux based operating systems. Though it > runs on windows under cygwin terminal, there is a need to run it on windows > without dependency on cygwin. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010751#comment-14010751
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit f0a98baa0c3258954a4fc4424d8c2f22a50d9ed4 in cloudstack's branch
refs/heads/4.3.0-forward from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0a98ba ]
CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic
Check if switch name detected from traffic label for management, storage,
control traffic is null before falling back to default value.
Signed-off-by: Sateesh Chodapuneedi
> [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
> --
>
> Key: CLOUDSTACK-6317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6317
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.3.0, 4.4.0
> Environment: VMware vCenter 5.1, ESXi 5.0 hosts
> MS with ACS 4.3.0
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.4.0, 4.3.1
>
>
> Prior to ACS 4.3.0 CloudStack used to support tagged VLAN for management /
> storage / control traffic via traffic label, where admin would specify the
> VLAN in comma separated string of vmware network traffic label. E.g.
> vSwitch0,100 - This means management traffic would use standard vSwitch port
> group tagged with VLAN 100 which sits on vSwitch0 existing on ESXi host.
> This is functionality was broken since below commit in ACS 4.3 branch,
> Commit 7c4831df9292115466fb9e01fcba952a5dad31c1 in branch refs/heads/4.3 from
> Hugo Trippaers
> [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7c4831d ]
> This commit overwrites the parsed vSwitch name, from traffic label, with
> traffic label specified by admin resulting into below error during deployment
> of SSVM (or any VM that needs management/storage traffic)
> 2014-04-01 08:23:19,866 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-9:ctx-862d86ff 10.102.192.3) VM v-2-VM will be started with NIC
> device type: E1000
> 2014-04-01 08:23:19,866 INFO [c.c.h.v.r.VmwareResource]
> (DirectAgent-9:ctx-862d86ff 10.102.192.3) Prepare NIC device based on NicTO:
> {"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"07c38800-6da3-4596-b0ea-09047d45970e","mac":"02:00:63:46:00:02","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false,"name":"vSwitch0,100"}
> 2014-04-01 08:23:21,150 ERROR [c.c.h.v.m.HypervisorHostHelper]
> (DirectAgent-6:ctx-a6062e05 10.102.192.3) Unable to find vSwitchvSwitch0,100
> 2014-04-01 08:23:21,151 WARN [c.c.h.v.r.VmwareResource]
> (DirectAgent-6:ctx-a6062e05 10.102.192.3) StartCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find vSwitchvSwitch0,100
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5891) [VMware] Template detail cpu.corespersocket's value is not honoured
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010750#comment-14010750 ] ASF subversion and git services commented on CLOUDSTACK-5891: - Commit d7c6e798278b1dab372f6b9800fc4b4cc724bf11 in cloudstack's branch refs/heads/4.3.0-forward from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d7c6e79 ] CLOUDSTACK-5891.[VMware] If a template has been registered and "cpu.corespersocket=X" template details have been added for it, then any instance deployed from that template should have X cores per socket > [VMware] Template detail cpu.corespersocket's value is not honoured > --- > > Key: CLOUDSTACK-5891 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5891 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.3.0 >Reporter: Likitha Shetty >Assignee: Likitha Shetty > Fix For: 4.4.0 > > > If a template has been registered and "cpu.corespersocket=X" template details > have been added for it, then any instance deployed from that template should > have X cores per socket. > This allows creation of an instance with multiple cores per socket in > Xenserver. Allow the same for VMware. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-4364) Restore VM - needs to log usage event for volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-4364: --- Fix Version/s: (was: Future) 4.4.0 > Restore VM - needs to log usage event for volume > > > Key: CLOUDSTACK-4364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4364 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.4.0 > > > Restore VM - needs to log usage event for volume so that any customer can > charge for the newly creat4ed volume -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010706#comment-14010706 ] Bob Vanderford commented on CLOUDSTACK-6464: Regarding my earlier comment, I tried the patch provided by E. Anders Lannerbäck. It did not resolve the issue I reported earlier today. Maybe my problem is different but the symptoms seem the same. Also, after installing the patch on the compute nodes, I could no longer use the console tool (clicking on view console gave an error about not able to find /ajax, 404 error. After removing the patch and putting back the original .jar file, I could again access the console. > [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are > plugged to default bridge even though trafiic labels are being used > -- > > Key: CLOUDSTACK-6464 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 >Reporter: sadhu suresh >Priority: Critical > Fix For: 4.4.0 > > > Steps: > 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) > 2.use cloudbr0 for management and cloudbr1 for guest by specifying the > traffic labels in the physical networks. > 3.deploy few vms > 4.upgrade to felton GA build as per the Upgrade instructions. > actual result: > Upgrade successful but all the vnets that were attached to cloudbr1 before > upgrade are attached to cloudbr0. > Due to this network connectivity is lost. > Expected result: > Even after upgrade ,all the vnets should be attached to the same bridge as > before upgrade. > ex: > before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after > upgrade and VM stop/start. > the network rules are getting programmed in cloudbr0 .check below output > ,984 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) Executing: > /usr/share/cloudstack-common/scripts/vm/network/security_group.py > default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac > 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: > dumpxml output for i-5-616-VM after upgrade(& after VM restart) > * > virsh # dumpxml 38 > > i-5-616-VM > 87557942-1393-49b3-a73e-ae24c40541d1 > Other CentOS (64-bit) > 2097152 > 2097152 > 1 > > 1000 > > > hvm > > > > > > > > > > > > destroy > restart > destroy > > /usr/libexec/qemu-kvm > > > file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6792) [Automation] test_escalations_ipaddresses : Assert error during list IP address and network
Rayees Namathponnan created CLOUDSTACK-6792: --- Summary: [Automation] test_escalations_ipaddresses : Assert error during list IP address and network Key: CLOUDSTACK-6792 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6792 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.4.0 Test case failing from suite integration.component.test_escalations_ipaddresses integration.component.test_escalations_ipaddresses.TestIpAddresses.test_07_assign_remove_lbrule_toinstance IP Addresses listed for newly created User >> begin captured stdout << - === TestName: test_07_assign_remove_lbrule_toinstance | Status : FAILED === integration.component.test_escalations_ipaddresses.TestIpAddresses.test_15_enable_disable_staticnat_forvpc (from nosetests) Failing for the past 4 builds (Since Unstable#168 ) Took 17 ms. Error Message VPC's Listed for newly Created User >> begin captured stdout << - === TestName: test_15_enable_disable_staticnat_forvpc | Status : FAILED === integration.component.test_escalations_ipaddresses.TestIpAddresses.test_16_create_delete_ipforwardingrule (from nosetests) Failing for the past 4 builds (Since Unstable#168 ) Took 29 ms. Error Message Networks listed for newly created User >> begin captured stdout << - === TestName: test_16_create_delete_ipforwardingrule | Status : FAILED === - >> end captured stdout << -- -- 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=14010534#comment-14010534 ] Rayees Namathponnan commented on CLOUDSTACK-6791: - Logs and DB dump in https://citrix.sharefile.com/d/s556cc6c6335436fa > [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 >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(R
[jira] [Created] (CLOUDSTACK-6791) [Automation] DeleteNetworkCmd fails with NullPointerException
Rayees Namathponnan created CLOUDSTACK-6791: --- Summary: [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 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:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Reflect
[jira] [Updated] (CLOUDSTACK-6760) [Automation] integration.smoke.test_scale_vm.TestScaleVm.test_01_scale_vm is failing for KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-6760: Issue Type: Test (was: Bug) > [Automation] integration.smoke.test_scale_vm.TestScaleVm.test_01_scale_vm is > failing for KVM > > > Key: CLOUDSTACK-6760 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6760 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.4.0 >Reporter: Koushik Das >Assignee: Srikanteswararao Talluri > Fix For: 4.4.0 > > > Scale VM is only supported for XS and Vmware. So test > integration.smoke.test_scale_vm.TestScaleVm.test_01_scale_vm always fails on > KVM. > The test should be fixed to handle this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6768) [Automation]: Test case failure in test_scale_vm.py
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6768:
Issue Type: Test (was: Bug)
> [Automation]: Test case failure in test_scale_vm.py
> ---
>
> Key: CLOUDSTACK-6768
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6768
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, XenServer
>Affects Versions: 4.4.0
>Reporter: Harikrishna Patnala
> Fix For: 4.4.0
>
>
> There is test case failure in test_scale_vm.py
> integration.smoke.test_scale_vm.TestScaleVm.test_01_scale_vm
> Error Message:
> Job failed: {jobprocstatus : 0, created : u'2014-05-25T23:32:18-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.vm.ScaleVMCmdByAdmin', userid :
> u'4564901e-e49c-11e3-a141-00163e189e44', jobstatus : 2, jobid :
> u'f1a26b8c-2f9d-44ea-a416-3161f48ebc29', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Dynamically scaling
> virtual machines is disabled for this zone, please contact your admin'},
> accountid : u'45646896-e49c-11e3-a141-00163e189e44'}
> >> begin captured stdout << -
> === TestName: test_01_scale_vm | Status : EXCEPTION ===
> Management Server log Error Message:
> 2014-05-25 23:32:18,719 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-67:ctx-93e7a535 job-140) Executing AsyncJobVO {id:140,
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.vm.ScaleVMCmdByAdmin, cmdInfo:
> {"response":"json","id":"58b294b4-5f45-4a29-a175-628a0ebb5b8f","serviceofferingid":"f0779c9b-ed1d-47bd-b006-05fc0d78bc0c","ctxDetails":"{\"com.cloud.vm.VirtualMachine\":6,\"VirtualMachine\":\"58b294b4-5f45-4a29-a175-628a0ebb5b8f\",\"com.cloud.offering.ServiceOffering\":19}","cmdEventType":"VM.UPGRADE","ctxUserId":"2","httpmethod":"GET","uuid":"58b294b4-5f45-4a29-a175-628a0ebb5b8f","ctxAccountId":"2","ctxStartEventId":"421","apiKey":"kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w","signature":"UrhuP7QKItf4GumSa8BHToytHm0\u003d"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 95531081284, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-25 23:32:18,726 DEBUG [c.c.a.ApiServlet]
> (1336641565@qtp-217245839-11:ctx-ea2448f1) ===START=== 172.16.88.7 -- GET
> jobid=f1a26b8c-2f9d-44ea-a416-3161f48ebc29&apiKey=kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w&command=queryAsyncJobResult&response=json&signature=50XUcypSsgXBwxlx%2F6RoQ4tK97o%3D
> 2014-05-25 23:32:18,732 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-67:ctx-93e7a535 job-140 ctx-928b66be) Received unknown
> parameters for command scaleVirtualMachine. Unknown parameters : ctxdetails
> 2014-05-25 23:32:18,745 DEBUG [c.c.a.ApiServlet]
> (1336641565@qtp-217245839-11:ctx-ea2448f1 ctx-4e31fedb ctx-3b5a1616)
> ===END=== 172.16.88.7 -- GET
> jobid=f1a26b8c-2f9d-44ea-a416-3161f48ebc29&apiKey=kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w&command=queryAsyncJobResult&response=json&signature=50XUcypSsgXBwxlx%2F6RoQ4tK97o%3D
> 2014-05-25 23:32:18,762 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-67:ctx-93e7a535 job-140) Unexpected exception while
> executing org.apache.cloudstack.api.command.admin.vm.ScaleVMCmdByAdmin
> com.cloud.exception.PermissionDeniedException: Dynamically scaling virtual
> machines is disabled for this zone, please contact your admin
> at
> com.cloud.vm.UserVmManagerImpl.upgradeRunningVirtualMachine(UserVmManagerImpl.java:1348)
> at
> com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1287)
> at
> com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1223)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.apache.cloudstack.network.c
[jira] [Updated] (CLOUDSTACK-6769) [Automation]: Test case failure in test_iso.py
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6769:
Issue Type: Test (was: Bug)
> [Automation]: Test case failure in test_iso.py
> --
>
> Key: CLOUDSTACK-6769
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6769
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, XenServer
>Affects Versions: 4.4.0
>Reporter: Harikrishna Patnala
> Fix For: 4.4.0
>
>
> There is test case failure in test_iso.py
>1) integration.smoke.test_iso.TestCreateIso.test_01_create_iso
> Error Message
> Exception while downloading ISO 06f0617c-4605-4a8f-855b-085486a1fd4b: Error
> In Downloading ISO: ISO Status - Network is unreachable
> === TestName: test_01_create_iso | Status : FAILED ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> STARTED : TC: test_01_create_iso :::
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'apiKey':
> u'kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w',
> 'command': 'listDomains', 'signature': 'Or2nHFPqukzhTba7v4PyKSS2Obc=',
> 'response': 'json'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : listDomains===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w&command=listDomains&response=json&signature=Or2nHFPqukzhTba7v4PyKSS2Obc%3D
> HTTP/1.1" 200 159
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : [{path : u'ROOT', haschild : False, id :
> u'45612b7c-e49c-11e3-a141-00163e189e44', name : u'ROOT', level : 0}]
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'apiKey':
> u'kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w',
> 'name': 'zone-xen', 'command': 'listZones', 'signature':
> '77O72WZATq83Kw9J9yK0yKsjlHM=', 'response': 'json'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : listZones===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?response=json&apiKey=kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w&command=listZones&name=zone-xen&signature=77O72WZATq83Kw9J9yK0yKsjlHM%3D
> HTTP/1.1" 200 446
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : [{localstorageenabled : False, name : u'zone-xen',
> guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken :
> u'921064dc-f25a-3393-94b7-7ba269fa1f82', dns2 : u'8.8.4.4', dns1 :
> u'8.8.8.8', securitygroupsenabled : False, allocationstate : u'Enabled',
> internaldns1 : u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype :
> u'Advanced', id : u'5c872b2f-53eb-46bd-8d7f-f9654f509b39', internaldns2 :
> u'172.16.88.7'}]
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Payload: {'username': 'test-account-TestISO-test_01_create_iso-UI4FTT',
> 'domainid': u'45612b7c-e49c-11e3-a141-00163e189e44', 'firstname': 'test',
> 'lastname': 'test', 'response': 'json', 'apiKey':
> u'kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w',
> 'command': 'createAccount', 'accounttype': 0, 'signature':
> 'q5ftoGqB/V1+Q+L3FGbYsOWsON0=', 'password': 'password', 'email':
> 'test-acco...@test.com'}
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Sending GET Cmd : createAccount===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.21
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?username=test-account-TestISO-test_01_create_iso-UI4FTT&domainid=45612b7c-e49c-11e3-a141-00163e189e44&firstname=test&lastname=test&email=test-account%40test.com&apiKey=kDUSTcbO-_FZ70vm6gGrUqsX7vkomsJKI8HBWK4J8rQNPwQ0WbDjlejsKcq3Mmj5zsEKk8pf7Z8nK3ebpNDM6w&command=createAccount&accounttype=0&signature=q5ftoGqB%2FV1%2BQ%2BL3FGbYsOWsON0%3D&password=password&response=json
> HTTP/1.1" 200 1650
> test_01_create_iso (integration.smoke.test_iso.TestCreateIso): DEBUG:
> Response : {primarystorageavailable : u'Unlimited',
[jira] [Updated] (CLOUDSTACK-6767) [Automation] integration.smoke.test_volumes.TestVolumes.test_07_resize_fail is failing on simulator
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-6767:
Issue Type: Test (was: Bug)
> [Automation] integration.smoke.test_volumes.TestVolumes.test_07_resize_fail
> is failing on simulator
> ---
>
> Key: CLOUDSTACK-6767
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6767
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
>Reporter: Koushik Das
>Assignee: Koushik Das
> Fix For: 4.4.0
>
>
> The test is not suppose to run on simulator. There is explicit check in code
> to not allow resize volume for simulator HV.
> Exception: Job failed: {jobprocstatus : 0, created :
> u'2014-05-25T20:19:27-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin',
> userid : u'338d28d4-e482-11e3-a86b-00163e0af42c', jobstatus : 2, jobid :
> u'cb3ef976-6aed-4137-a393-8f90cd1cff58', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Cloudstack currently
> only supports volumes marked as KVM, VMware, XenServer hypervisor for
> resize'}, accountid : u'338d026e-e482-11e3-a86b-00163e0af42c'}
> test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): CRITICAL:
> FAILED: test_07_resize_fail: ['Traceback (most recent call last):\n', ' File
> "/usr/local/lib/python2.7/unittest/case.py", line 331, in run\n
> testMethod()\n', ' File
> "/automation/virtenv/00-16-3e-0a-f4-2c/261/test/integration/smoke/test_volumes.py",
> line 552, in test_07_resize_fail\n"ResizeVolume - verify root disks
> cannot be resized by disk offering id")\n', ' File
> "/usr/local/lib/python2.7/unittest/case.py", line 515, in assertEqual\n
> assertion_func(first, second, msg=msg)\n', ' File
> "/usr/local/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual\n
> raise self.failureException(msg)\n', 'AssertionError: ResizeVolume - verify
> root disks cannot be resized by disk offering id\n']
> Earlier the test was incorrectly checking for wrong error and so was passing
> even for simulator. As part of the below commit the test case was fixed to
> check correct error and so started failing.
> commit 8eca37056f5bb1eee10f0bedee785142d7c3437a
> Author: Gaurav Aradhye
> Date: Thu May 15 23:19:06 2014 -0400
> CLOUDSTACK-6657: Adding condition for checking error code 530 across test
> cases
>
> Signed-off-by: SrikanteswaraRao Talluri
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6790) Disable PXE ROM for system vm nics, speed up boot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010457#comment-14010457 ] ASF subversion and git services commented on CLOUDSTACK-6790: - Commit 7ce303429921e6a60a941c8476ba891baa80f04c in cloudstack's branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7ce3034 ] CLOUDSTACK-6790: Disable PXE ROM for system vm nics > Disable PXE ROM for system vm nics, speed up boot > - > > Key: CLOUDSTACK-6790 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6790 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Reporter: Marcus Sorensen >Assignee: Marcus Sorensen > Fix For: 4.5.0 > > > Most VMs don't need PXE (We may be able to add a PXE server to the VPC router > someday, however). Especially system VM nics have no need for PXE. System VMs > have many nics, slowing down boot significantly while the nics load the ROMs, > therefore, disable PXE ROMs for system vm nics. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6790) Disable PXE ROM for system vm nics, speed up boot
Marcus Sorensen created CLOUDSTACK-6790: --- Summary: Disable PXE ROM for system vm nics, speed up boot Key: CLOUDSTACK-6790 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6790 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.5.0 Most VMs don't need PXE (We may be able to add a PXE server to the VPC router someday, however). Especially system VM nics have no need for PXE. System VMs have many nics, slowing down boot significantly while the nics load the ROMs, therefore, disable PXE ROMs for system vm nics. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-4578) [vmware]SSVM is not getting created if one host down from a cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4578. - Resolution: Won't Fix Not planned to fix the problem yet. When VM's host VM is in accessible state (host down), VM will be marked as disabled in vCenter, currently CloudStack does not handle this case automatically due to unsafe operation to vCenter about this VM at disabled state. Recommended way to work around the problem is to always enable vCenter HA. > [vmware]SSVM is not getting created if one host down from a cluster > --- > > Key: CLOUDSTACK-4578 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4578 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 > Environment: Vmware > 4.2.-forward >Reporter: Rayees Namathponnan >Assignee: Kelven Yang >Priority: Critical > Fix For: 4.4.0 > > Attachments: CLOUDSTACK-4578.rar > > > Steps to reproduce > Step 1 : Create vmware advanced zone with 2 host in a cluster (HA not > enabled ) > Step 2 : Check SSVM, in which host is running > Step 3 : Shutdown the host, in where SSVM is running > Expected Result > > New SSVM should be created on second host (Running Host) > Actual result > -- > SSVM is not getting created on second host; > Work around > -- > You need to force fully stop SSVM trough API, then new SSVM gets created on > second host > We need to document this -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6789) Domain Admin User is unable to delete other domain admin users under same domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-6789. -- Resolution: Fixed > Domain Admin User is unable to delete other domain admin users under same > domain > > > Key: CLOUDSTACK-6789 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6789 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6789) Domain Admin User is unable to delete other domain admin users under same domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-6789. > Domain Admin User is unable to delete other domain admin users under same > domain > > > Key: CLOUDSTACK-6789 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6789 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6789) Domain Admin User is unable to delete other domain admin users under same domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010447#comment-14010447 ] ASF subversion and git services commented on CLOUDSTACK-6789: - Commit 021a60449325d5a6eaf48755a323237b832ed5a4 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=021a604 ] CLOUDSTACK-6789: UI > User page > fix a bug that a domain-admin was unable to delete other domain-admin in the same domain. > Domain Admin User is unable to delete other domain admin users under same > domain > > > Key: CLOUDSTACK-6789 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6789 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6789) Domain Admin User is unable to delete other domain admin users under same domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010445#comment-14010445 ] ASF subversion and git services commented on CLOUDSTACK-6789: - Commit 3d1bbeb262cad98d1b591b42ff5f0e2103dcb1b4 in cloudstack's branch refs/heads/4.4-forward from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3d1bbeb ] CLOUDSTACK-6789: UI > User page > fix a bug that a domain-admin was unable to delete other domain-admin in the same domain. > Domain Admin User is unable to delete other domain admin users under same > domain > > > Key: CLOUDSTACK-6789 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6789 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6789) Domain Admin User is unable to delete other domain admin users under same domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010437#comment-14010437 ] Jessica Wang commented on CLOUDSTACK-6789: -- http://bugs-ccp.citrix.com/i#browse/CS-20099 > Domain Admin User is unable to delete other domain admin users under same > domain > > > Key: CLOUDSTACK-6789 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6789 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6789) Domain Admin User is unable to delete other domain admin users under same domain
Jessica Wang created CLOUDSTACK-6789: Summary: Domain Admin User is unable to delete other domain admin users under same domain Key: CLOUDSTACK-6789 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6789 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6673) cloudstack-setup-management make a chmod 777 on /root
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010435#comment-14010435 ] Rayees Namathponnan commented on CLOUDSTACK-6673: - is it specific to Ubuntu alone ? I tried with centos 6.3, see the root folder permission before and after dr-xr-x---. 2 root root 4096 May 13 2013 root [root@cs-nightly-ms2 /]# cloudstack-setup-management Starting to configure CloudStack Management Server: Configure sudoers ... [OK] Configure Firewall ...[OK] Configure CloudStack Management Server ...[OK] CloudStack Management Server setup is Done! dr-xr-x---. 2 root root 4096 May 13 2013 root > cloudstack-setup-management make a chmod 777 on /root > - > > Key: CLOUDSTACK-6673 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6673 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.4.0 > Environment: Ubuntu 14.04 / KVM > CS 4.4.0 snapshot 20140513 >Reporter: Milamber >Priority: Blocker > Labels: security > > Before run cloudstack-setup-management, /root directory permissions are: > drwx-- 4 root root 4096 mai 14 15:05 root > After the runs of cloudstack-setup-management, /root directory permissions > are: > drwxrwxrwx 4 root root 4096 mai 14 15:05 root -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6730) [Automation] test_egress_fw_rules test case failing while applying FW rule
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010411#comment-14010411
]
Rayees Namathponnan commented on CLOUDSTACK-6730:
-
Test script issue https://issues.apache.org/jira/browse/CLOUDSTACK-6786 need to
be resolved to check this
> [Automation] test_egress_fw_rules test case failing while applying FW rule
> ---
>
> Key: CLOUDSTACK-6730
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6730
> 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: Rayees Namathponnan
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Test case
> integration.component.test_egress_fw_rules.TestEgressFWRules.test_07_1_egress_fr7
> failing with latest run.
> This test case performing below steps
> 658 # Validate the following:
> 659 # 1. deploy VM using network offering with egress policy true.
> 660 # 2. create egress rule without specific end port.
> 661 # 3. login to VM.
> 662 # 4. access to public network for tcp port 80 is blocked.
> SetFirewallRulesCommand failing with error "No chain/target/match by that
> name.\niptables: No chain/target/match by that"
> 2014-05-19 21:52:27,304 DEBUG [c.c.a.t.Request] (API-Job-Executor-99:job-7298
> ctx-93fb812a) Seq 2-453737662457584256: Executing: { Cmd , MgmtId:
> 90928106758
> 026, via: 2(10.223.250.131), Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.routing.SetFirewallRulesCommand":{"rules":[{"id":562,"srcIp":"","protocol":"tcp",
> "srcPortRange":[80,80],"revoked":false,"alreadyAdded":false,"sourceCidrList":["10.1.1.0/24"],"purpose":"Firewall","trafficType":"Egress","defaultEgressPolicy
> ":true}],"accessDetails":{"router.guest.ip":"10.1.1.13","firewall.egress.default":"true","zone.network.type":"Advanced","router.ip":"10.223.250.182","router.
> name":"r-1086-TestVM"},"wait":0}}] }
> 2014-05-19 21:52:27,304 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-120:ctx-15d72251) Seq 2-453737662457584256: Executing request
> 2014-05-19 21:52:27,304 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-120:ctx-15d72251 10.223.250.131) Use router's private IP for SSH
> control. IP : 10.223.2
> 50.182
> 2014-05-19 21:52:27,304 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-120:ctx-15d72251 10.223.250.131) Run command on VR:
> 10.223.250.182, script: firewall_eg
> ress.sh with args: -F -E -P 1 -a :tcp:80:80:10.1.1.0/24:,
> 2014-05-19 21:52:27,759 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-120:ctx-15d72251 10.223.250.131) firewall_egress.sh execution
> result: true
> 2014-05-19 21:52:27,759 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-120:ctx-15d72251) Seq 2-453737662457584256: Response Received:
> 2014-05-19 21:52:27,759 DEBUG [c.c.a.t.Request]
> (DirectAgent-120:ctx-15d72251) Seq 2-453737662457584256: Processing: { Ans:
> , MgmtId: 90928106758026, via: 2
> , Ver: v1, Flags: 0,
> [{"com.cloud.agent.api.Answer":{"result":true,"details":"iptables v1.4.14:
> Couldn't load target `_FW_EGRESS_RULES':No such file or direc
> tory\n\nTry `iptables -h' or 'iptables --help' for more
> information.\niptables: No chain/target/match by that name.\niptables: No
> chain/target/match by that
> name.\n","wait":0}}] }
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6788) add kvmclock agent tunable
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010406#comment-14010406 ] ASF subversion and git services commented on CLOUDSTACK-6788: - Commit f3a0d257b8c2323783f7af7d5532f38858436400 in cloudstack's branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f3a0d25 ] CLOUDSTACK-6788: Add agent property to optionally disable kvmclock on guests > add kvmclock agent tunable > -- > > Key: CLOUDSTACK-6788 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6788 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Reporter: Marcus Sorensen >Assignee: Marcus Sorensen > Fix For: 4.5.0 > > > KVM clock can cause migrations to lock up the guest under some newer linux > kernels. This bug has been known for a few months, but has not been fixed. > Add an agent property that allows the admin to disable kvmclock on guest > deployments on a per-host basis. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6787) Event Bus - Publishing uuids missing in some cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010392#comment-14010392 ] Nitin Mehta commented on CLOUDSTACK-6787: - Note its the same commit as in masterbut with wrong commit message commit 18c6ae07961f0cf787fe695da4b25b8d8f955acc Author: Nitin Mehta Date: Tue May 27 14:55:22 2014 -0700 CLOUDSTACK-6597: Updatevm - root admin should be allowed to change instance name > Event Bus - Publishing uuids missing in some cases > -- > > Key: CLOUDSTACK-6787 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6787 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.4.0, 4.5.0 > > > Event Bus - Publishing uuids was missing in some cases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6787) Event Bus - Publishing uuids missing in some cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010382#comment-14010382 ] ASF subversion and git services commented on CLOUDSTACK-6787: - Commit a8140ff58c73be36e56a17b938e6c602e05f0685 in cloudstack's branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a8140ff ] CLOUDSTACK-6787: Event Bus - uuids missing in some cases due to various reasons > Event Bus - Publishing uuids missing in some cases > -- > > Key: CLOUDSTACK-6787 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6787 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.4.0, 4.5.0 > > > Event Bus - Publishing uuids was missing in some cases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6597) Updatevm - root admin should be allowed to change instance name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010377#comment-14010377 ] ASF subversion and git services commented on CLOUDSTACK-6597: - Commit 18c6ae07961f0cf787fe695da4b25b8d8f955acc in cloudstack's branch refs/heads/4.4-forward from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=18c6ae0 ] CLOUDSTACK-6597: Updatevm - root admin should be allowed to change instance name > Updatevm - root admin should be allowed to change instance name > --- > > Key: CLOUDSTACK-6597 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6597 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.5.0 > > > Updatevm - Root admin should be allowed to change instance name -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6392) system template always create with name "master" instead of specific branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010347#comment-14010347 ] Rayees Namathponnan commented on CLOUDSTACK-6392: - Submitted patch https://reviews.apache.org/r/21946/diff/#index_header > system template always create with name "master" instead of specific branch > --- > > Key: CLOUDSTACK-6392 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6392 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.4.0 >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Critical > Fix For: 4.4.0 > > > Create system vm from jenkins.buildacloud.org > in 4.4 System vm always create with same name > "systemvm64template-master-xen.vhd" > it should be create with name "systemvm64template-4.4-xen.vhd" -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6785) Allow API callers to provide a job id where cloudstack is a part of a larger system
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010345#comment-14010345 ] ASF subversion and git services commented on CLOUDSTACK-6785: - Commit 96055058b05e024dc62621ab99cea7d8f998076b in cloudstack's branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9605505 ] CLOUDSTACK-6785: changed async job param injectedjobid to customjobid and check for unique/uuid > Allow API callers to provide a job id where cloudstack is a part of a larger > system > --- > > Key: CLOUDSTACK-6785 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6785 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Marcus Sorensen >Assignee: Marcus Sorensen > Fix For: 4.5.0 > > > It can be advantageous in some systems to be able to choose the job id that > cloudstack uses, when cloudstack is just a portion of a larger system. e.g. > when we are listening for events we can match an event's job id to something > created by the caller rather than having a race condition of waiting for the > cloudstack job id and listening for the event completion. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6785) Allow API callers to provide a job id where cloudstack is a part of a larger system
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010344#comment-14010344 ] ASF subversion and git services commented on CLOUDSTACK-6785: - Commit 2a5bf65c783fe9770a43727cfff695422c4f873d in cloudstack's branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2a5bf65 ] CLOUDSTACK-6785: Allow async jobs to supply an injectedjobid > Allow API callers to provide a job id where cloudstack is a part of a larger > system > --- > > Key: CLOUDSTACK-6785 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6785 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Marcus Sorensen >Assignee: Marcus Sorensen > Fix For: 4.5.0 > > > It can be advantageous in some systems to be able to choose the job id that > cloudstack uses, when cloudstack is just a portion of a larger system. e.g. > when we are listening for events we can match an event's job id to something > created by the caller rather than having a race condition of waiting for the > cloudstack job id and listening for the event completion. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6784) Allow API/marvin to know about parameter data types
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010346#comment-14010346 ] ASF subversion and git services commented on CLOUDSTACK-6784: - Commit 20a31b43d6c0b395c7f2c449ce2f486665a2b55a in cloudstack's branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=20a31b4 ] CLOUDSTACK-6784: Expose data types via API so consumers of API can validate data > Allow API/marvin to know about parameter data types > --- > > Key: CLOUDSTACK-6784 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6784 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Reporter: Marcus Sorensen >Assignee: Marcus Sorensen > Fix For: 4.5.0 > > > We can waterfall down datatypes for parameters through the API and Marvin, > which will help applications that programatically consume the API to validate > parameters. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6788) add kvmclock agent tunable
Marcus Sorensen created CLOUDSTACK-6788: --- Summary: add kvmclock agent tunable Key: CLOUDSTACK-6788 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6788 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.5.0 KVM clock can cause migrations to lock up the guest under some newer linux kernels. This bug has been known for a few months, but has not been fixed. Add an agent property that allows the admin to disable kvmclock on guest deployments on a per-host basis. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6787) Event Bus - Publishing uuids missing in some cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6787: Affects Version/s: 4.4.0 > Event Bus - Publishing uuids missing in some cases > -- > > Key: CLOUDSTACK-6787 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6787 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.4.0, 4.5.0 > > > Event Bus - Publishing uuids was missing in some cases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6787) Event Bus - Publishing uuids missing in some cases
Nitin Mehta created CLOUDSTACK-6787: --- Summary: Event Bus - Publishing uuids missing in some cases Key: CLOUDSTACK-6787 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6787 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta Event Bus - Publishing uuids was missing in some cases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6787) Event Bus - Publishing uuids missing in some cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6787: Fix Version/s: 4.5.0 4.4.0 > Event Bus - Publishing uuids missing in some cases > -- > > Key: CLOUDSTACK-6787 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6787 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.4.0, 4.5.0 > > > Event Bus - Publishing uuids was missing in some cases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6360) Usage server failed to start with 4.4 build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan resolved CLOUDSTACK-6360. - Resolution: Fixed Fixed in https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=d0c249bc9eb194b81b75865ecda56e353435eeb8 > Usage server failed to start with 4.4 build > --- > > Key: CLOUDSTACK-6360 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6360 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.3.0, 4.4.0 > Environment: 4.4 Build >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Critical > Fix For: 4.4.0 > > > step 1 : Create 4.4 build and install usage server > step 2 : start usage sever > Result > Failed to start usage server with below error > java.lang.UnsupportedClassVersionError: com/cloud/usage/UsageServer : > Unsupported major.minor version 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:634) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) > at java.net.URLClassLoader.access$000(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:212) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:205) > at java.lang.ClassLoader.loadClass(ClassLoader.java:321) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) > at java.lang.ClassLoader.loadClass(ClassLoader.java:266) > at > org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:151) > 08/04/2014 12:32:19 5982 jsvc.exec error: Cannot load daemon > 08/04/2014 12:32:19 5980 jsvc.exec error: Service exit with a return value of > 3 > cloudstack-usage.err (END) > We already defined 4.4 support with JAVA IP, but usage server trying to start > with 1.6 > we need to fix this in vi /etc/rc.d/init.d/cloudstack-usage > # The first existing directory is used for JAVA_HOME (if JAVA_HOME is not > defined in $DEFAULT) > JDK_DIRS="/usr/lib/jvm/java-6-openjdk /usr/lib/jvm/java-6-openjdk-i386 > /usr/lib/jvm/java-6-openjdk-amd64 /usr/lib/jvm/java-6-sun > /usr/lib/jvm/jre-1.6.0 /usr/lib/j2sdk1.5-sun /usr/lib/jre-openjdk" -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010199#comment-14010199 ] Bob Vanderford commented on CLOUDSTACK-6464: We also have had trouble similar to this issue. We did not upgrade, just started with version 4.3 in a prototype environment using advanced networking. Here is were we got in troubleshooting this. We found what seems to be a redundant interface on the virtual router for the network (isolated), eth3. Eth2 is the public interface but eth3 has the same public ip address assigned as eth2. Now we see the following iptables rule on the virtual router: iptables -t nat -A POSTROUTING -j SNAT -o eth3 --to-source= We delete this rule using the -D form of the iptables command and then added the rule back but using eth2 instead of eth3, like this: iptables -t nat -A POSTROUTING -j SNAT -o eth2 --to-source= After that the instance(s) on that network have egress and can access the public internet. This is not an acceptable workaround, however, since users won't have access to the virtual router. But, it does demonstrate the nature of the issue. So, either the eth3 interface shouldn't be there at all or the iptables rule needs to apply its rule to eth2 rather than eth3. This issue essentially makes version 4.3 unusable for us. To have an effect instance it must be able to access the Internet for patch updates, downloading files, etc. We would consider this a blocking issue and deserving of a patch or a quick release for 4.3.1 if such a thing is possible. If there is another workaround in meantime, we would be happy to use it. Also, note, this is a prototype environment and we can provide access to the management portal to anyone that would be interested in debugging or trying a patch. > [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are > plugged to default bridge even though trafiic labels are being used > -- > > Key: CLOUDSTACK-6464 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 >Reporter: sadhu suresh >Priority: Critical > Fix For: 4.4.0 > > > Steps: > 1. create a KVM basic zone with 2 nics on host (pre 4.3 build) > 2.use cloudbr0 for management and cloudbr1 for guest by specifying the > traffic labels in the physical networks. > 3.deploy few vms > 4.upgrade to felton GA build as per the Upgrade instructions. > actual result: > Upgrade successful but all the vnets that were attached to cloudbr1 before > upgrade are attached to cloudbr0. > Due to this network connectivity is lost. > Expected result: > Even after upgrade ,all the vnets should be attached to the same bridge as > before upgrade. > ex: > before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after > upgrade and VM stop/start. > the network rules are getting programmed in cloudbr0 .check below output > ,984 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) Executing: > /usr/share/cloudstack-common/scripts/vm/network/security_group.py > default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac > 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0: > dumpxml output for i-5-616-VM after upgrade(& after VM restart) > * > virsh # dumpxml 38 > > i-5-616-VM > 87557942-1393-49b3-a73e-ae24c40541d1 > Other CentOS (64-bit) > 2097152 > 2097152 > 1 > > 1000 > > > hvm > > > > > > > > > > > > destroy > restart > destroy > > /usr/libexec/qemu-kvm > > > file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > its also applicable to new vm deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6744) UI > zone wizard > baremetal > change it to support EIP ELB feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010088#comment-14010088 ] ASF subversion and git services commented on CLOUDSTACK-6744: - Commit af8e83b410f7698e736b68cdd065d4ab11958e24 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=af8e83b ] CLOUDSTACK-6744 > UI > zone wizard > baremetal hypervisor > support EIP ELB feature. This reverts commit d36c731f795e3d709d830c58936accfadc4277d8. > UI > zone wizard > baremetal > change it to support EIP ELB feature > --- > > Key: CLOUDSTACK-6744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6644) Unable to attach Volume to a VM as a System User
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010082#comment-14010082
]
Min Chen commented on CLOUDSTACK-6644:
--
Yes, Chandan, please retest this with latest 4.4 code to see if it can be
reproduced. On latest 4.4, IAM is already disabled, and the logic should be the
same as before.
> Unable to attach Volume to a VM as a System User
>
>
> Key: CLOUDSTACK-6644
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6644
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: IAM
>Affects Versions: 4.4.0
>Reporter: Chandan Purushothama
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.4.0
>
>
> As System User, tried to attach a Volume belonging to an account to a VM
> belonging to the same account. Failed with the following error.
> "Acct[4f0e5b12-d6d8-11e3-952f-06098c000757-system] does not have permission
> to perform this operation on these resources"
> mysql> select account_id, uuid from vm_instance where uuid like '%56a4%';
> ++--+
> | account_id | uuid |
> ++--+
> | 3 | 56a488ce-9baf-4d99-8e25-002d565f6731 |
> ++--+
> 1 row in set (0.00 sec)
> mysql> select account_id, uuid from volumes where uuid like '%00585b50%';
> ++--+
> | account_id | uuid |
> ++--+
> | 3 | 00585b50-8c65-4e5b-95ee-853489e5499c |
> ++--+
> 1 row in set (0.00 sec)
> 2014-05-12 13:40:48,618 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) submit async
> job-190, details: AsyncJobVO {id:190, userId: 1, accountId: 1, instanceType:
> Volume, instanceId: 11, cmd:
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
> cmdInfo:
> {"virtualmachineid":"56a488ce-9baf-4d99-8e25-002d565f6731","cmdEventType":"VOLUME.ATTACH","ctxUserId":"1","httpmethod":"GET","deviceid":"1","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","id":"00585b50-8c65-4e5b-95ee-853489e5499c","response":"json","ctxDetails":"{\"com.cloud.storage.Volume\":11,\"Volume\":\"00585b50-8c65-4e5b-95ee-853489e5499c\",\"com.cloud.vm.VirtualMachine\":8}","ctxAccountId":"1","uuid":"00585b50-8c65-4e5b-95ee-853489e5499c","ctxStartEventId":"448","signature":"euszCT397/kGpCM1fN+GQhTJCe8\u003d"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-12 13:40:48,619 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) ===END=== 127.0.0.1
> -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=attachVolume&deviceid=1&id=00585b50-8c65-4e5b-95ee-853489e5499c&response=json&virtualmachineid=56a488ce-9baf-4d99-8e25-002d565f6731&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=euszCT397%2FkGpCM1fN%2BGQhTJCe8%3D
> 2014-05-12 13:40:48,621 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-3:ctx-9e956cd7) ===START=== 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=queryAsyncJobResult&jobId=2ef19e77-29af-416f-bc16-f27df1b58e7f&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=O1vnDPmstm6Xa2lEazduvETJkXk%3D
> 2014-05-12 13:40:48,627 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-45:job-190) Add job-190 into job monitoring
> 2014-05-12 13:40:48,627 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-45:job-190) Executing AsyncJobVO {id:190, userId: 1,
> accountId: 1, instanceType: Volume, instanceId: 11, cmd:
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
> cmdInfo:
> {"virtualmachineid":"56a488ce-9baf-4d99-8e25-002d565f6731","cmdEventType":"VOLUME.ATTACH","ctxUserId":"1","httpmethod":"GET","deviceid":"1","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","id":"00585b50-8c65-4e5b-95ee-853489e5499c","response":"json","ctxDetails":"{\"com.cloud.storage.Volume\":11,\"Volume\":\"00585b50-8c65-4e5b-95ee-853489e5499c\",\"com.cloud.vm.VirtualMachine\":8}","ctxAccountId":"1","uuid":"00585b50-8c65-4e5b-95ee-853489e5499c","
[jira] [Commented] (CLOUDSTACK-6744) UI > zone wizard > baremetal > change it to support EIP ELB feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010083#comment-14010083 ] ASF subversion and git services commented on CLOUDSTACK-6744: - Commit a553bb516dccb637985dadc91d8eb5ec16d55ab5 in cloudstack's branch refs/heads/4.4-forward from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a553bb5 ] CLOUDSTACK-6744 > UI > zone wizard > baremetal hypervisor > support EIP ELB feature. This reverts commit 65bb733a4237242e7f800956840c1a09be18fbb5. > UI > zone wizard > baremetal > change it to support EIP ELB feature > --- > > Key: CLOUDSTACK-6744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6754) SSVM not responding with S3 secondary sotre
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen resolved CLOUDSTACK-6754. -- Resolution: Invalid > SSVM not responding with S3 secondary sotre > --- > > Key: CLOUDSTACK-6754 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6754 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, SystemVM, Template >Affects Versions: 4.4.0 > Environment: Host: Xenserver > Secondary Store: Image store with S3 as provider >Reporter: Pavan Kumar Bandarupally >Assignee: Min Chen >Priority: Blocker > Fix For: 4.4.0 > > Attachments: cloud.log, cloudoutfile.zip, management-server.log > > > A new zone is created and systemVMs are up. The systemvm template is > downloaded to S3 bucket. Once the SSVMs are up, the default BUILTIN centos > template or any other template that we try to register manually are not > getting downloaded to SSVM. There is no exception generated as well. > The registerTemplate API call is just listed in the MS traces and no further > action happens. Attaching the MS logs and SSVM log. There is no trace of any > exception in SSVM log as well. Attaching the /var/log/cloud/cloud.out , which > is the only file that has some exception listed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6405) Observed SQL exceptions during db upgrade from 4.0.0 to 4.4.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010078#comment-14010078 ] Animesh Chaturvedi commented on CLOUDSTACK-6405: Abhinandan I see it is assigned back to Abhinav. Should this be resolved as "Cannot Reproduce" > Observed SQL exceptions during db upgrade from 4.0.0 to 4.4.0 > - > > Key: CLOUDSTACK-6405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6405 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 > Environment: Latest build from 4.4 with commit > 098324aa84d3835d2eca24d41f0266128d2d4f29 >Reporter: Sanjeev N >Assignee: Abhinav Roy >Priority: Critical > Fix For: 4.4.0 > > Attachments: catalina.rar, management-server.rar > > > Observed SQL Exceptions during db upgrade from 4.0.0 to 4.4.0 > Steps to Reproduce: > > 1.Install MS with latest build from 4.4 > 2.Observe log file after cloudstack-setup-management > During MS start we upgrade DB from 4.0.0 to latest version which is 4.4.0 > Found some SQL exceptions during this db upgrade. Following is one of them: > INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.0.0 Code > Version = 4.4.0-SNAPSHOT > INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be > performed from 4.0.0 to 4.4.0-SNAPSHOT > WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when > trying to drop key last_sent on table alert > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP > 'last_sent'; check that column/key exists > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) > at com.mysql.jdbc.Util.getInstance(Util.java:386) > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) > at > com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) > at > com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) > at > com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) > at > com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) > at > org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) > at > org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) > at > com.cloud.upgrade.dao.DatabaseAccessObject.dropKey(DatabaseAccessObject.java:37) > at > com.cloud.upgrade.dao.DbUpgradeUtils.dropKeysIfExist(DbUpgradeUtils.java:28) > at > com.cloud.upgrade.dao.Upgrade410to420.addIndexForAlert(Upgrade410to420.java:543) > at > com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:98) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:310) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:432) > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) > at > org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6754) SSVM not responding with S3 secondary sotre
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010075#comment-14010075 ] Min Chen commented on CLOUDSTACK-6754: -- >From MS log, I can see that your SSVM agent is not running at all, that is why >you saw "There is no secondary storage VM for downloading template to image >store s3perfgolstore" in registering a template. Since SSVM agent is not >running, it will not send back commands to management server to sync default >centos template. Also from cloud.out, you can see that SSVM agent failed to start due to this error: Exception in thread "main" java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) Could not find the main class: com.cloud.agent.AgentShell. Program will exit. This error indicates that you are using Java 6 to run Java 7 code on SSVM, you should use the new system vm template that is upgraded to use Java 7. > SSVM not responding with S3 secondary sotre > --- > > Key: CLOUDSTACK-6754 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6754 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, SystemVM, Template >Affects Versions: 4.4.0 > Environment: Host: Xenserver > Secondary Store: Image store with S3 as provider >Reporter: Pavan Kumar Bandarupally >Assignee: Min Chen >Priority: Blocker > Fix For: 4.4.0 > > Attachments: cloud.log, cloudoutfile.zip, management-server.log > > > A new zone is created and systemVMs are up. The systemvm template is > downloaded to S3 bucket. Once the SSVMs are up, the default BUILTIN centos > template or any other template that we try to register manually are not > getting downloaded to SSVM. There is no exception generated as well. > The registerTemplate API call is just listed in the MS traces and no further > action happens. Attaching the MS logs and SSVM log. There is no trace of any > exception in SSVM log as well. Attaching the /var/log/cloud/cloud.out , which > is the only file that has some exception listed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6392) system template always create with name "master" instead of specific branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010074#comment-14010074 ] Animesh Chaturvedi commented on CLOUDSTACK-6392: Rayees are your working on this issue? > system template always create with name "master" instead of specific branch > --- > > Key: CLOUDSTACK-6392 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6392 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.4.0 >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Critical > Fix For: 4.4.0 > > > Create system vm from jenkins.buildacloud.org > in 4.4 System vm always create with same name > "systemvm64template-master-xen.vhd" > it should be create with name "systemvm64template-4.4-xen.vhd" -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6360) Usage server failed to start with 4.4 build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010070#comment-14010070 ] Animesh Chaturvedi commented on CLOUDSTACK-6360: Frank can you help review and merge it in master branch > Usage server failed to start with 4.4 build > --- > > Key: CLOUDSTACK-6360 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6360 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.3.0, 4.4.0 > Environment: 4.4 Build >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Critical > Fix For: 4.4.0 > > > step 1 : Create 4.4 build and install usage server > step 2 : start usage sever > Result > Failed to start usage server with below error > java.lang.UnsupportedClassVersionError: com/cloud/usage/UsageServer : > Unsupported major.minor version 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:634) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) > at java.net.URLClassLoader.access$000(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:212) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:205) > at java.lang.ClassLoader.loadClass(ClassLoader.java:321) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) > at java.lang.ClassLoader.loadClass(ClassLoader.java:266) > at > org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:151) > 08/04/2014 12:32:19 5982 jsvc.exec error: Cannot load daemon > 08/04/2014 12:32:19 5980 jsvc.exec error: Service exit with a return value of > 3 > cloudstack-usage.err (END) > We already defined 4.4 support with JAVA IP, but usage server trying to start > with 1.6 > we need to fix this in vi /etc/rc.d/init.d/cloudstack-usage > # The first existing directory is used for JAVA_HOME (if JAVA_HOME is not > defined in $DEFAULT) > JDK_DIRS="/usr/lib/jvm/java-6-openjdk /usr/lib/jvm/java-6-openjdk-i386 > /usr/lib/jvm/java-6-openjdk-amd64 /usr/lib/jvm/java-6-sun > /usr/lib/jvm/jre-1.6.0 /usr/lib/j2sdk1.5-sun /usr/lib/jre-openjdk" -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6333) [Automation] NPE observed while deleting account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010065#comment-14010065 ] Animesh Chaturvedi commented on CLOUDSTACK-6333: Sanjay please provide an update on this issue? > [Automation] NPE observed while deleting account > > > Key: CLOUDSTACK-6333 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6333 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 > Environment: KVM >Reporter: Rayees Namathponnan >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.4.0 > > Attachments: management-server.rar > > > This issue observed in automation run, there are many account clean up > failures with NPE > Also In Log observed "VM state transitted from :Expunging to Expunging", why > we are changing state "Expunging to Expunging" > 2014-04-02 17:19:45,664 DEBUG [c.c.v.VirtualMachineManagerImpl] > (AccountChecker-1:ctx-633521d3) Cleaning up NICS > 2014-04-02 17:19:45,664 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (AccountChecker-1:ctx-633521d3) Cleaning network for vm: 455 > 2014-04-02 17:19:45,665 DEBUG [c.c.v.VirtualMachineManagerImpl] > (AccountChecker-1:ctx-633521d3) Cleaning up hypervisor data s > tructures (ex. SRs in XenServer) for managed storage > 2014-04-02 17:19:45,669 WARN [c.c.u.AccountManagerImpl] > (AccountChecker-1:ctx-633521d3) Failed to cleanup account Acct[10b43 > b95-f6e0-445f-acff-9c5cc450f59b-test-TestBaseImageUpdate-6JJ7ST] due to > java.lang.NullPointerException > at > org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.disconnectVolumesFromHost(VolumeOrchestrator.java:867) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:527) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:463) > at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1654) > at sun.reflect.GeneratedMethodAccessor555.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.$Proxy205.expunge(Unknown Source) > at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:651) > at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1575) > 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) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4578) [vmware]SSVM is not getting created if one host down from a cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010059#comment-14010059 ] Animesh Chaturvedi commented on CLOUDSTACK-4578: Rayees can you check if this is still an issue > [vmware]SSVM is not getting created if one host down from a cluster > --- > > Key: CLOUDSTACK-4578 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4578 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 > Environment: Vmware > 4.2.-forward >Reporter: Rayees Namathponnan >Assignee: Kelven Yang >Priority: Critical > Fix For: 4.4.0 > > Attachments: CLOUDSTACK-4578.rar > > > Steps to reproduce > Step 1 : Create vmware advanced zone with 2 host in a cluster (HA not > enabled ) > Step 2 : Check SSVM, in which host is running > Step 3 : Shutdown the host, in where SSVM is running > Expected Result > > New SSVM should be created on second host (Running Host) > Actual result > -- > SSVM is not getting created on second host; > Work around > -- > You need to force fully stop SSVM trough API, then new SSVM gets created on > second host > We need to document this -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6786) [Automation] test_egress_fw_rules test cases failing due to unicode error
Rayees Namathponnan created CLOUDSTACK-6786: --- Summary: [Automation] test_egress_fw_rules test cases failing due to unicode error Key: CLOUDSTACK-6786 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6786 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Run the test case suite "integration.component.test_egress_fw_rules.TestEgressFWRules" Test cases failing with below error integration.component.test_egress_fw_rules.TestEgressFWRules.test_01_egress_fr1 Script result is [u'0'] is not matching with ['0'] >> begin captured stdout << - === TestName: test_01_egress_fr1 | Status : FAILED === integration.component.test_egress_fw_rules.TestEgressFWRules.test_02_egress_fr2 Script result is [u'100'] is not matching with ['100'] >> begin captured stdout << - === TestName: test_02_egress_fr2 | Status : FAILED === -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-3968) [VMWAREDVS] Distributed Portgroups are not deleted when guest networks are removed/User Account of this network is removed from cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010056#comment-14010056 ] Animesh Chaturvedi commented on CLOUDSTACK-3968: Sateesh this is an old issue can you review it again > [VMWAREDVS] Distributed Portgroups are not deleted when guest networks are > removed/User Account of this network is removed from cloudstack > -- > > Key: CLOUDSTACK-3968 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3968 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Sateesh Chodapuneedi >Priority: Critical > Fix For: 4.4.0 > > Attachments: dvswitchsnap.png > > > Setup: VMWARE with DVSwitch > 1. Configure Adv Zone with DVSwitch enabled VMWARE cluster > 2. Create an account and deploy VM using default offering guest network. > 3. Delete this account. With this all the resources of this account gets > removed from cloudstack > Observation: > But from vCenter dv Switch, the distributed port groups configured for this > account guest networks will not get removed. > Expected results: > All the configurations created by cloudstack should get cleaned up as part of > smooth removal. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6730) [Automation] test_egress_fw_rules test case failing while applying FW rule
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi resolved CLOUDSTACK-6730.
Resolution: Cannot Reproduce
Rayees please check on this again
> [Automation] test_egress_fw_rules test case failing while applying FW rule
> ---
>
> Key: CLOUDSTACK-6730
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6730
> 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: Rayees Namathponnan
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Test case
> integration.component.test_egress_fw_rules.TestEgressFWRules.test_07_1_egress_fr7
> failing with latest run.
> This test case performing below steps
> 658 # Validate the following:
> 659 # 1. deploy VM using network offering with egress policy true.
> 660 # 2. create egress rule without specific end port.
> 661 # 3. login to VM.
> 662 # 4. access to public network for tcp port 80 is blocked.
> SetFirewallRulesCommand failing with error "No chain/target/match by that
> name.\niptables: No chain/target/match by that"
> 2014-05-19 21:52:27,304 DEBUG [c.c.a.t.Request] (API-Job-Executor-99:job-7298
> ctx-93fb812a) Seq 2-453737662457584256: Executing: { Cmd , MgmtId:
> 90928106758
> 026, via: 2(10.223.250.131), Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.routing.SetFirewallRulesCommand":{"rules":[{"id":562,"srcIp":"","protocol":"tcp",
> "srcPortRange":[80,80],"revoked":false,"alreadyAdded":false,"sourceCidrList":["10.1.1.0/24"],"purpose":"Firewall","trafficType":"Egress","defaultEgressPolicy
> ":true}],"accessDetails":{"router.guest.ip":"10.1.1.13","firewall.egress.default":"true","zone.network.type":"Advanced","router.ip":"10.223.250.182","router.
> name":"r-1086-TestVM"},"wait":0}}] }
> 2014-05-19 21:52:27,304 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-120:ctx-15d72251) Seq 2-453737662457584256: Executing request
> 2014-05-19 21:52:27,304 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-120:ctx-15d72251 10.223.250.131) Use router's private IP for SSH
> control. IP : 10.223.2
> 50.182
> 2014-05-19 21:52:27,304 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-120:ctx-15d72251 10.223.250.131) Run command on VR:
> 10.223.250.182, script: firewall_eg
> ress.sh with args: -F -E -P 1 -a :tcp:80:80:10.1.1.0/24:,
> 2014-05-19 21:52:27,759 DEBUG [c.c.h.v.r.VmwareResource]
> (DirectAgent-120:ctx-15d72251 10.223.250.131) firewall_egress.sh execution
> result: true
> 2014-05-19 21:52:27,759 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-120:ctx-15d72251) Seq 2-453737662457584256: Response Received:
> 2014-05-19 21:52:27,759 DEBUG [c.c.a.t.Request]
> (DirectAgent-120:ctx-15d72251) Seq 2-453737662457584256: Processing: { Ans:
> , MgmtId: 90928106758026, via: 2
> , Ver: v1, Flags: 0,
> [{"com.cloud.agent.api.Answer":{"result":true,"details":"iptables v1.4.14:
> Couldn't load target `_FW_EGRESS_RULES':No such file or direc
> tory\n\nTry `iptables -h' or 'iptables --help' for more
> information.\niptables: No chain/target/match by that name.\niptables: No
> chain/target/match by that
> name.\n","wait":0}}] }
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010040#comment-14010040
]
Animesh Chaturvedi commented on CLOUDSTACK-6710:
Likitha are you working on this issue. Can you provide an update? and set
status to InProgress
> [Automation] VM snapshot failing with NPE in vmware
> ---
>
> Key: CLOUDSTACK-6710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
> Environment: Vmware 5.0
> 4.4-forward
>Reporter: Rayees Namathponnan
>Assignee: Likitha Shetty
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> Execute BVT
> integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
> This test case creating VM snapshot in VMware; this is failing with below NPE
> 2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-130:job-390/job-391) Run VM work job:
> com.cloud.vm.snapshot.VmWorkCreateVMSn
> apshot for VM 62, job origin: 390
> 2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job:
> com.cloud.vm.snapsh
> ot.VmWorkCreateVMSnapshot{"vmSnapshotId":1,"quiesceVm":false,"userId":2,"accountId":2,"vmId":62,"handlerName":"VMSnapshotManagerImpl"}
> 2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl]
> (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm
> snapshot: 1
> java.lang.NullPointerException
> at
> org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
> 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
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.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.handleVmWorkJob(Unknown Source)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
> 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:453)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.r
[jira] [Resolved] (CLOUDSTACK-6675) NPE while executing updatePortForwardingRule
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi resolved CLOUDSTACK-6675.
Resolution: Fixed
> NPE while executing updatePortForwardingRule
>
>
> Key: CLOUDSTACK-6675
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6675
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.4.0
>Reporter: Chandan Purushothama
>Assignee: Alena Prokharchyk
>Priority: Blocker
> Fix For: 4.4.0
>
>
> NPE hit while executing updatePortForwardingRule CS API. I am blocked on
> executing a Use Case which is based on this API.
> =
> NullPointerException:
> =
> 2014-05-14 11:44:45,215 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-10:ctx-d408ed7f) ===START=== 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=updatePortForwardingRule&fordisplay=false&id=b767a533-e3ed-45ad-ab2b-68ea806438f6&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=jF8MpXvj4u4NKyajmbuFBPAcw2M%3D
> 2014-05-14 11:44:45,286 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-10:ctx-d408ed7f ctx-3df22ad6 ctx-84f5b16f) submit async
> job-886, details: AsyncJobVO {id:886, userId: 1, accountId: 1, instanceType:
> None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.firewall.UpdatePortForwardingRuleCmd,
> cmdInfo:
> {"response":"json","id":"b767a533-e3ed-45ad-ab2b-68ea806438f6","ctxDetails":"{\"Network\":\"b767a533-e3ed-45ad-ab2b-68ea806438f6\",\"com.cloud.network.rules.FirewallRule\":23}","cmdEventType":"NET.RULEMODIFY","ctxUserId":"1","httpmethod":"GET","uuid":"b767a533-e3ed-45ad-ab2b-68ea806438f6","ctxAccountId":"1","ctxStartEventId":"1859","signature":"jF8MpXvj4u4NKyajmbuFBPAcw2M\u003d","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","fordisplay":"false"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-14 11:44:45,287 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-10:ctx-d408ed7f ctx-3df22ad6 ctx-84f5b16f) ===END===
> 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=updatePortForwardingRule&fordisplay=false&id=b767a533-e3ed-45ad-ab2b-68ea806438f6&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=jF8MpXvj4u4NKyajmbuFBPAcw2M%3D
> 2014-05-14 11:44:45,288 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-110:job-886) Add job-886 into job monitoring
> 2014-05-14 11:44:45,292 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-11:ctx-3d255b35) ===START=== 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=queryAsyncJobResult&jobId=0571d334-e071-4073-b404-1e388195733b&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=EKX465Tc%2B3NvETQRtvhWEynB%2Faw%3D
> 2014-05-14 11:44:45,295 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-110:job-886) Executing AsyncJobVO {id:886, userId: 1,
> accountId: 1, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.firewall.UpdatePortForwardingRuleCmd,
> cmdInfo:
> {"response":"json","id":"b767a533-e3ed-45ad-ab2b-68ea806438f6","ctxDetails":"{\"Network\":\"b767a533-e3ed-45ad-ab2b-68ea806438f6\",\"com.cloud.network.rules.FirewallRule\":23}","cmdEventType":"NET.RULEMODIFY","ctxUserId":"1","httpmethod":"GET","uuid":"b767a533-e3ed-45ad-ab2b-68ea806438f6","ctxAccountId":"1","ctxStartEventId":"1859","signature":"jF8MpXvj4u4NKyajmbuFBPAcw2M\u003d","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","fordisplay":"false"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-14 11:44:45,308 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-a4771a58) Zone 1 is ready to launch console proxy
> 2014-05-14 11:44:45,308 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-110:job-886 ctx-0ab7a373) Received unknown parameters for
> command updatePortForwardingRule. Unknown parameters : ctxdetails
> 2014-05-14 11:44:45,314 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-110:job-886) Unexpe
[jira] [Commented] (CLOUDSTACK-6675) NPE while executing updatePortForwardingRule
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010039#comment-14010039
]
Animesh Chaturvedi commented on CLOUDSTACK-6675:
Based on the commit I will resolve this issue. Chandan can you reopen if this
is still an issue?
> NPE while executing updatePortForwardingRule
>
>
> Key: CLOUDSTACK-6675
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6675
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.4.0
>Reporter: Chandan Purushothama
>Assignee: Alena Prokharchyk
>Priority: Blocker
> Fix For: 4.4.0
>
>
> NPE hit while executing updatePortForwardingRule CS API. I am blocked on
> executing a Use Case which is based on this API.
> =
> NullPointerException:
> =
> 2014-05-14 11:44:45,215 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-10:ctx-d408ed7f) ===START=== 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=updatePortForwardingRule&fordisplay=false&id=b767a533-e3ed-45ad-ab2b-68ea806438f6&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=jF8MpXvj4u4NKyajmbuFBPAcw2M%3D
> 2014-05-14 11:44:45,286 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-10:ctx-d408ed7f ctx-3df22ad6 ctx-84f5b16f) submit async
> job-886, details: AsyncJobVO {id:886, userId: 1, accountId: 1, instanceType:
> None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.firewall.UpdatePortForwardingRuleCmd,
> cmdInfo:
> {"response":"json","id":"b767a533-e3ed-45ad-ab2b-68ea806438f6","ctxDetails":"{\"Network\":\"b767a533-e3ed-45ad-ab2b-68ea806438f6\",\"com.cloud.network.rules.FirewallRule\":23}","cmdEventType":"NET.RULEMODIFY","ctxUserId":"1","httpmethod":"GET","uuid":"b767a533-e3ed-45ad-ab2b-68ea806438f6","ctxAccountId":"1","ctxStartEventId":"1859","signature":"jF8MpXvj4u4NKyajmbuFBPAcw2M\u003d","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","fordisplay":"false"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-14 11:44:45,287 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-10:ctx-d408ed7f ctx-3df22ad6 ctx-84f5b16f) ===END===
> 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=updatePortForwardingRule&fordisplay=false&id=b767a533-e3ed-45ad-ab2b-68ea806438f6&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=jF8MpXvj4u4NKyajmbuFBPAcw2M%3D
> 2014-05-14 11:44:45,288 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-110:job-886) Add job-886 into job monitoring
> 2014-05-14 11:44:45,292 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-11:ctx-3d255b35) ===START=== 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=queryAsyncJobResult&jobId=0571d334-e071-4073-b404-1e388195733b&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=EKX465Tc%2B3NvETQRtvhWEynB%2Faw%3D
> 2014-05-14 11:44:45,295 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-110:job-886) Executing AsyncJobVO {id:886, userId: 1,
> accountId: 1, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.firewall.UpdatePortForwardingRuleCmd,
> cmdInfo:
> {"response":"json","id":"b767a533-e3ed-45ad-ab2b-68ea806438f6","ctxDetails":"{\"Network\":\"b767a533-e3ed-45ad-ab2b-68ea806438f6\",\"com.cloud.network.rules.FirewallRule\":23}","cmdEventType":"NET.RULEMODIFY","ctxUserId":"1","httpmethod":"GET","uuid":"b767a533-e3ed-45ad-ab2b-68ea806438f6","ctxAccountId":"1","ctxStartEventId":"1859","signature":"jF8MpXvj4u4NKyajmbuFBPAcw2M\u003d","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","fordisplay":"false"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-14 11:44:45,308 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-a4771a58) Zone 1 is ready to launch console proxy
> 2014-05-14 11:44:45,308 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-110:job-886 ctx-0ab7a373) Received unknown parameters for
> command updatePortForwardingRule. Unk
[jira] [Commented] (CLOUDSTACK-6644) Unable to attach Volume to a VM as a System User
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010031#comment-14010031
]
Animesh Chaturvedi commented on CLOUDSTACK-6644:
Min can you check on if this is IAM related, Now that it is reverted it should
not be an issue. Chandan can you retest?
> Unable to attach Volume to a VM as a System User
>
>
> Key: CLOUDSTACK-6644
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6644
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: IAM
>Affects Versions: 4.4.0
>Reporter: Chandan Purushothama
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.4.0
>
>
> As System User, tried to attach a Volume belonging to an account to a VM
> belonging to the same account. Failed with the following error.
> "Acct[4f0e5b12-d6d8-11e3-952f-06098c000757-system] does not have permission
> to perform this operation on these resources"
> mysql> select account_id, uuid from vm_instance where uuid like '%56a4%';
> ++--+
> | account_id | uuid |
> ++--+
> | 3 | 56a488ce-9baf-4d99-8e25-002d565f6731 |
> ++--+
> 1 row in set (0.00 sec)
> mysql> select account_id, uuid from volumes where uuid like '%00585b50%';
> ++--+
> | account_id | uuid |
> ++--+
> | 3 | 00585b50-8c65-4e5b-95ee-853489e5499c |
> ++--+
> 1 row in set (0.00 sec)
> 2014-05-12 13:40:48,618 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) submit async
> job-190, details: AsyncJobVO {id:190, userId: 1, accountId: 1, instanceType:
> Volume, instanceId: 11, cmd:
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
> cmdInfo:
> {"virtualmachineid":"56a488ce-9baf-4d99-8e25-002d565f6731","cmdEventType":"VOLUME.ATTACH","ctxUserId":"1","httpmethod":"GET","deviceid":"1","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","id":"00585b50-8c65-4e5b-95ee-853489e5499c","response":"json","ctxDetails":"{\"com.cloud.storage.Volume\":11,\"Volume\":\"00585b50-8c65-4e5b-95ee-853489e5499c\",\"com.cloud.vm.VirtualMachine\":8}","ctxAccountId":"1","uuid":"00585b50-8c65-4e5b-95ee-853489e5499c","ctxStartEventId":"448","signature":"euszCT397/kGpCM1fN+GQhTJCe8\u003d"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-12 13:40:48,619 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) ===END=== 127.0.0.1
> -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=attachVolume&deviceid=1&id=00585b50-8c65-4e5b-95ee-853489e5499c&response=json&virtualmachineid=56a488ce-9baf-4d99-8e25-002d565f6731&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=euszCT397%2FkGpCM1fN%2BGQhTJCe8%3D
> 2014-05-12 13:40:48,621 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-3:ctx-9e956cd7) ===START=== 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=queryAsyncJobResult&jobId=2ef19e77-29af-416f-bc16-f27df1b58e7f&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=O1vnDPmstm6Xa2lEazduvETJkXk%3D
> 2014-05-12 13:40:48,627 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-45:job-190) Add job-190 into job monitoring
> 2014-05-12 13:40:48,627 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-45:job-190) Executing AsyncJobVO {id:190, userId: 1,
> accountId: 1, instanceType: Volume, instanceId: 11, cmd:
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
> cmdInfo:
> {"virtualmachineid":"56a488ce-9baf-4d99-8e25-002d565f6731","cmdEventType":"VOLUME.ATTACH","ctxUserId":"1","httpmethod":"GET","deviceid":"1","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","id":"00585b50-8c65-4e5b-95ee-853489e5499c","response":"json","ctxDetails":"{\"com.cloud.storage.Volume\":11,\"Volume\":\"00585b50-8c65-4e5b-95ee-853489e5499c\",\"com.cloud.vm.VirtualMachine\":8}","ctxAccountId":"1","uuid":"00585b50-8c65-4e5b-95ee-853489e5499c","ctxStartEventId":"448","signatu
[jira] [Updated] (CLOUDSTACK-6644) Unable to attach Volume to a VM as a System User
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-6644:
---
Assignee: Min Chen (was: edison su)
> Unable to attach Volume to a VM as a System User
>
>
> Key: CLOUDSTACK-6644
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6644
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: IAM
>Affects Versions: 4.4.0
>Reporter: Chandan Purushothama
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.4.0
>
>
> As System User, tried to attach a Volume belonging to an account to a VM
> belonging to the same account. Failed with the following error.
> "Acct[4f0e5b12-d6d8-11e3-952f-06098c000757-system] does not have permission
> to perform this operation on these resources"
> mysql> select account_id, uuid from vm_instance where uuid like '%56a4%';
> ++--+
> | account_id | uuid |
> ++--+
> | 3 | 56a488ce-9baf-4d99-8e25-002d565f6731 |
> ++--+
> 1 row in set (0.00 sec)
> mysql> select account_id, uuid from volumes where uuid like '%00585b50%';
> ++--+
> | account_id | uuid |
> ++--+
> | 3 | 00585b50-8c65-4e5b-95ee-853489e5499c |
> ++--+
> 1 row in set (0.00 sec)
> 2014-05-12 13:40:48,618 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) submit async
> job-190, details: AsyncJobVO {id:190, userId: 1, accountId: 1, instanceType:
> Volume, instanceId: 11, cmd:
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
> cmdInfo:
> {"virtualmachineid":"56a488ce-9baf-4d99-8e25-002d565f6731","cmdEventType":"VOLUME.ATTACH","ctxUserId":"1","httpmethod":"GET","deviceid":"1","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","id":"00585b50-8c65-4e5b-95ee-853489e5499c","response":"json","ctxDetails":"{\"com.cloud.storage.Volume\":11,\"Volume\":\"00585b50-8c65-4e5b-95ee-853489e5499c\",\"com.cloud.vm.VirtualMachine\":8}","ctxAccountId":"1","uuid":"00585b50-8c65-4e5b-95ee-853489e5499c","ctxStartEventId":"448","signature":"euszCT397/kGpCM1fN+GQhTJCe8\u003d"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-12 13:40:48,619 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) ===END=== 127.0.0.1
> -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=attachVolume&deviceid=1&id=00585b50-8c65-4e5b-95ee-853489e5499c&response=json&virtualmachineid=56a488ce-9baf-4d99-8e25-002d565f6731&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=euszCT397%2FkGpCM1fN%2BGQhTJCe8%3D
> 2014-05-12 13:40:48,621 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-3:ctx-9e956cd7) ===START=== 127.0.0.1 -- GET
> apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&command=queryAsyncJobResult&jobId=2ef19e77-29af-416f-bc16-f27df1b58e7f&response=json&apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ&signature=O1vnDPmstm6Xa2lEazduvETJkXk%3D
> 2014-05-12 13:40:48,627 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-45:job-190) Add job-190 into job monitoring
> 2014-05-12 13:40:48,627 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-45:job-190) Executing AsyncJobVO {id:190, userId: 1,
> accountId: 1, instanceType: Volume, instanceId: 11, cmd:
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
> cmdInfo:
> {"virtualmachineid":"56a488ce-9baf-4d99-8e25-002d565f6731","cmdEventType":"VOLUME.ATTACH","ctxUserId":"1","httpmethod":"GET","deviceid":"1","apikey":"dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ","id":"00585b50-8c65-4e5b-95ee-853489e5499c","response":"json","ctxDetails":"{\"com.cloud.storage.Volume\":11,\"Volume\":\"00585b50-8c65-4e5b-95ee-853489e5499c\",\"com.cloud.vm.VirtualMachine\":8}","ctxAccountId":"1","uuid":"00585b50-8c65-4e5b-95ee-853489e5499c","ctxStartEventId":"448","signature":"euszCT397/kGpCM1fN+GQhTJCe8\u003d"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMs
[jira] [Commented] (CLOUDSTACK-6603) [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010021#comment-14010021 ] Animesh Chaturvedi commented on CLOUDSTACK-6603: rajesh please provide update on this issue. > [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to > 4.4 > > > Key: CLOUDSTACK-6603 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6603 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.4.0 >Reporter: manasaveloori >Assignee: Rajesh Battala >Priority: Blocker > Fix For: 4.4.0 > > Attachments: management-server.rar, mysqldump43.dmp, mysqldump44.dmp > > > 1. Deploy CS 4.3 with 2 zones using xen 6.1 and KVM hypervisor. > 2. Configured LB rules,firewall rules. > 3. Registered the template for 4.4 (using the naming convention > systemvm-xenserver-4.4,systemvm-kvm-4.4) > 4. Upgraded to 4.4 > Start the management server: > Below are the observations: > 2014-05-05 05:05:13,567 DEBUG [c.c.s.StatsCollector] > (StatsCollector-4:ctx-e36f20e1) AutoScaling Monitor is running... > 2014-05-05 05:05:13,577 ERROR [c.c.s.StatsCollector] > (StatsCollector-4:ctx-e36f20e1) Error trying to monitor autoscaling > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@5b140551: SELECT autoscale_vmgroups.id, > autoscale_vmgroups.uuid, autoscale_vmgroups.zone_id, > autoscale_vmgroups.domain_id, autoscale_vmgroups.account_id, > autoscale_vmgroups.load_balancer_id, autoscale_vmgroups.min_members, > autoscale_vmgroups.max_members, autoscale_vmgroups.member_port, > autoscale_vmgroups.interval, autoscale_vmgroups.last_interval, > autoscale_vmgroups.profile_id, autoscale_vmgroups.removed, > autoscale_vmgroups.created, autoscale_vmgroups.state, > autoscale_vmgroups.display FROM autoscale_vmgroups WHERE > autoscale_vmgroups.removed IS NULL > at com.cloud.utils.db.GenericDaoBase.executeList(GenericDaoBase.java:1127) > at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1150) > at com.cloud.utils.db.GenericDaoBase.listAll(GenericDaoBase.java:1136) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at com.sun.proxy.$Proxy220.listAll(Unknown Source) > at > com.cloud.server.StatsCollector$AutoScaleMonitor.runInContext(StatsCollector.java:673) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744)
[jira] [Commented] (CLOUDSTACK-6599) Template/Volume URLs expiration functionality not working
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010020#comment-14010020 ] Animesh Chaturvedi commented on CLOUDSTACK-6599: Is there an update on it? > Template/Volume URLs expiration functionality not working > - > > Key: CLOUDSTACK-6599 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6599 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Mehta >Assignee: Nitin Mehta >Priority: Blocker > Fix For: 4.4.0 > > > Template / Volume Donwload URLs should expire - functionality is missing > We have the functionality where we create download urls for volumes and > templates for the users. For security reasons we should expire these urls and > this functionality existed since 3.0.x. But it doesnt exist in 4.4 and that > needs to be implemented. Look at 4.2 for reference. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6785) Allow API callers to provide a job id where cloudstack is a part of a larger system
Marcus Sorensen created CLOUDSTACK-6785: --- Summary: Allow API callers to provide a job id where cloudstack is a part of a larger system Key: CLOUDSTACK-6785 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6785 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.5.0 It can be advantageous in some systems to be able to choose the job id that cloudstack uses, when cloudstack is just a portion of a larger system. e.g. when we are listening for events we can match an event's job id to something created by the caller rather than having a race condition of waiting for the cloudstack job id and listening for the event completion. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6784) Allow API/marvin to know about parameter data types
Marcus Sorensen created CLOUDSTACK-6784: --- Summary: Allow API/marvin to know about parameter data types Key: CLOUDSTACK-6784 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6784 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: API Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.5.0 We can waterfall down datatypes for parameters through the API and Marvin, which will help applications that programatically consume the API to validate parameters. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6667) Can't provision a site-to-site VPN with multiple CIDRs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009847#comment-14009847 ] Alex Hitchins commented on CLOUDSTACK-6667: --- Created patch against 4.4, submitting to review board. > Can't provision a site-to-site VPN with multiple CIDRs > -- > > Key: CLOUDSTACK-6667 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6667 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: Future, 4.2.1 > Environment: CloudStack 4.2.1 >Reporter: Paul Angus >Assignee: Alex Hitchins >Priority: Critical > > When attempting to create a site-to-site VPN with multiple remote CIDRs ie: > 172.1.0.0/16,172.11.0.0/16 > CloudStack reports that "172.1.0.0/16,172.11.0.0/16" is an invalid CIDR. > CloudStack code does not appear to be enumerating the string as two comma > separated CIDRs. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6092) Storage OverProvisioning as a Per Primary Basis
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saksham Srivastava resolved CLOUDSTACK-6092. Resolution: Fixed Resolving as the feature has been merged in 4.4 > Storage OverProvisioning as a Per Primary Basis > --- > > Key: CLOUDSTACK-6092 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6092 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Storage Controller >Affects Versions: 4.4.0 >Reporter: Saksham Srivastava >Assignee: Saksham Srivastava > Labels: Storage > Fix For: 4.4.0 > > > The current scenario is to set the global parameter > storage.overprovisioning.factor that is inherently applicable for any > qualified primary store to leverage over provision of the underlying storage. > Cloud Deployments can have different combinations of primary storage either > for different vendors or from the same vendor but different products > Depending on the storage capability, CloudStack admins need the flexibility > to determine what the over-provisioning factor should be for each primary > storage. > FS link - > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+OverProvisioning+as+Per+Primary+Basis -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4992) Domain/Account/User Sync Up Among Multiple Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009813#comment-14009813 ] Alex Ough commented on CLOUDSTACK-4992: --- I hope it is, but there is one issue to be resolved with Alena/Alex Huang. Alena is on vacation now and she will be back the end of this month, I believe. > Domain/Account/User Sync Up Among Multiple Regions > -- > > Key: CLOUDSTACK-4992 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4992 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 >Reporter: Alex Ough >Assignee: Alex Ough > Labels: features > Fix For: 4.4.0 > > > Currently, under the environment of cloudstack with multiple regions, each > region has its own management server running with a separate database. So if > we want to support multiple regions and provide one point of entry for a > customer, we need to duplicate domain/account/user information of that > customer to all of the databases of regions the customer accesses, which will > cause data discrepancies when users update those data independently in each > management server. > So I'd like to provide a way to sync up the data using the messaging system > introduced in 4.1.0. Using the events from each management server, updates > from each region can be propagated to the rest regions and they can be > executed accordingly. > Discussion > http://markmail.org/thread/k4x63ef55chcj4y5 > Wiki page > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain-Account-User+Sync+Up+Among+Multiple+Regions > The implementation > https://github.com/alexoughsg/Albatross/tree/albatross -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-1597) Convert "Storage Setup" section to XML and update in Install Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009809#comment-14009809 ] gavin lee commented on CLOUDSTACK-1597: --- Hi, Daan What I know is the review request did not get any responses for a very long time. This part of doc (storage section) may be out-of-date, but the commit is already in master, 4.2 and 4.3 branch. > Convert "Storage Setup" section to XML and update in Install Guide > -- > > Key: CLOUDSTACK-1597 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1597 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0, 4.1.0 >Reporter: Jessica Tomechak >Assignee: gavin lee >Priority: Minor > Fix For: 4.4.0 > > Attachments: Apache_CloudStack-4.2.0-Installation_Guide-en-US.pdf, > StorageSetup.docx > > > The section "Storage Setup" was missed when converting the installation guide > to XML. The section is attached to this bug in the original format. This > section will need to be reviewed and updated as well as converted to XML, > since storage support has changed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6781) [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009794#comment-14009794 ] Rajani Karuturi commented on CLOUDSTACK-6781: - patch is on review board https://reviews.apache.org/r/21927/ > [Automation] > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > failing on 4.4 > --- > > Key: CLOUDSTACK-6781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6781 > 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: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > is failing > There are two test cases which test the functionality by creating an ip range > and then deleting it. > The delete isnt happening in the first test case which is causing the second > test case to fail. > This is surfaced after the commit 2ab7bcade2f37cb17e071a6154fdae1d80e4ff99 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4197) Allow creating a VM without virtual CD-ROM drive
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009792#comment-14009792 ] Marcus Sorensen commented on CLOUDSTACK-4197: - May want to consider making it a property of service offering. Just a checkbox on whether or not the deployments of that service offering should have a CD drive, then you could choose not to have cd drive with any and all templates, and you wouldn't have to create multiple OS types. There are also the new 'details' parameters that are being used by the VMware devs where they choose their template hardware based on 'details' parameters: register template format=ova hypervisor=vmware name=OL63-26-TMPLT url=http://reposerver.example.com/6.3-26/ol-6.3-26.ova ispublic=true isfeatured=true passwordenabled=false details[0].rootDiskController=scsi details[0].nicAdapter=E1000 details[0].keyboard=us ostypeid=148 zoneid=-1 displaytext=OL63-26-TMPLT A details parameter specifying whether or not CDROM should be deployed with the template could be easily added, the work would be primarily on the hypervisor side to pay attention to those parameters, since whatever you pass in as details just passes through on the mgmt server. > Allow creating a VM without virtual CD-ROM drive > > > Key: CLOUDSTACK-4197 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4197 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.2.0 >Reporter: Kirk Kosinski >Assignee: Anthony Xu >Priority: Minor > Labels: hypervisor, netscaler > Fix For: 4.4.0 > > > Currently all VMs that CloudStack creates will include a virtual CD-ROM > drive. In some cases, such as with virtual appliances (e.g. NetScaler VPX), a > CD-ROM drive is not needed or even unsupported. It would be useful if > CloudStack could deploy a VM without a CD-ROM drive to allow such cases. > Perhaps such functionality could be added using new OS Types, for example: > Other - No CD-ROM (32-bit) > Other - No CD-ROM (64-bit) > Other PV - No CD-ROM (32-bit) > Other PV - No CD-ROM (64-bit) > Or maybe it could be added on a per VM or per template basis with a new > configuration parameter. This might be more flexible since some customers > might want to use arbitrary OS types for VMs with no CD-ROM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6781) [Automation] integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange failing on 4.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-6781: Status: Reviewable (was: In Progress) > [Automation] > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > failing on 4.4 > --- > > Key: CLOUDSTACK-6781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6781 > 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: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > integration.smoke.test_portable_publicip.TestPortablePublicIPRange.test_createPortablePublicIPRange > is failing > There are two test cases which test the functionality by creating an ip range > and then deleting it. > The delete isnt happening in the first test case which is causing the second > test case to fail. > This is surfaced after the commit 2ab7bcade2f37cb17e071a6154fdae1d80e4ff99 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6105) Windowsfication of CloudStack Management Server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009784#comment-14009784 ] Daan Hoogland commented on CLOUDSTACK-6105: --- Damodar, Can you resolve or close this issue? > Windowsfication of CloudStack Management Server > --- > > Key: CLOUDSTACK-6105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6105 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 >Reporter: Damodar Reddy T >Assignee: Damodar Reddy T > Labels: features > Fix For: 4.4.0 > > > Currently Management Server runs on Linux based operating systems. Though it > runs on windows under cygwin terminal, there is a need to run it on windows > without dependency on cygwin. -- This message was sent by Atlassian JIRA (v6.2#6252)
