[jira] [Created] (CLOUDSTACK-3389) Documentation nTier Apps 2.0 : KVM Hypervisor support
Radhika Nair created CLOUDSTACK-3389: Summary: Documentation nTier Apps 2.0 : KVM Hypervisor support Key: CLOUDSTACK-3389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3389 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 https://issues.apache.org/jira/browse/CLOUDSTACK-750 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3209) Mixed zone management feature missing in branch refs/heads/master-6-17-stable.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori updated CLOUDSTACK-3209: -- Attachment: RE BlockerMixed zone management.msg Mixed zone management feature missing in branch refs/heads/master-6-17-stable. -- Key: CLOUDSTACK-3209 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3209 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: manasaveloori Priority: Blocker Fix For: 4.2.0 Attachments: RE BlockerMixed zone management.msg -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3209) Mixed zone management feature missing in branch refs/heads/master-6-17-stable.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701804#comment-13701804 ] manasaveloori commented on CLOUDSTACK-3209: --- As per the mail from Brian Federle ,it is removed from Stable branch.. Attaching the mail thread Mixed zone management feature missing in branch refs/heads/master-6-17-stable. -- Key: CLOUDSTACK-3209 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3209 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: manasaveloori Priority: Blocker Fix For: 4.2.0 Attachments: RE BlockerMixed zone management.msg -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-847) [DOC] Document the ability to use multiple IP ranges
[ https://issues.apache.org/jira/browse/CLOUDSTACK-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-847. - Resolution: Fixed [DOC] Document the ability to use multiple IP ranges Key: CLOUDSTACK-847 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-847 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: David Nalley Assignee: Radhika Nair Fix For: 4.2.0 Document the ability to make use of multiple IP ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3390) Documentation for Mapping CloudStack Zone and VMWare Datacenter
Radhika Nair created CLOUDSTACK-3390: Summary: Documentation for Mapping CloudStack Zone and VMWare Datacenter Key: CLOUDSTACK-3390 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3390 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Radhika Nair -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2547) Should not allow to create VLAN beyond 4095
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-2547: Summary: Should not allow to create VLAN beyond 4095 (was: [Automation] Should not allow to create VLAN beyond 4095 ) Should not allow to create VLAN beyond 4095 - Key: CLOUDSTACK-2547 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2547 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Rayees Namathponnan Priority: Minor There are a maximum of 4096 possible values ranging from 0 to 4095 for VLAN, but cloudstack allowing more then this. Steps to reproduce Run below automation test case test/integration/smoke/test_public_ip_range.py -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3259) integration.component.test_routers test cases failed with ssh connection error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701821#comment-13701821 ] Rayees Namathponnan commented on CLOUDSTACK-3259: - 3) test_routers.TestRouterStopCreatePF.test_01_RouterStopCreatePF; failed with below error SSH Access failed for 10.1.1.76: [Errno 113] No route to host begin captured logging testclient.testcase.TestRouterStopCreatePF: DEBUG: Stopping router ID: 57e6c9be-7deb-4020-be3e-6d2ec8e04ba6 testclient.testcase.TestRouterStopCreatePF: DEBUG: Creating NAT rule for VM ID: c509eb0f-ec83-44ec-b167-ba680eea33cd testclient.testcase.TestRouterStopCreatePF: DEBUG: Starting router ID: 57e6c9be-7deb-4020-be3e-6d2ec8e04ba6 testclient.testcase.TestRouterStopCreatePF: DEBUG: SSH into VM with ID: 10.223.243.23 integration.component.test_routers test cases failed with ssh connection error --- Key: CLOUDSTACK-3259 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3259 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Environment: Automation : Vmware Reporter: Rayees Namathponnan Fix For: 4.2.0 Test cases failed with ssh connection error in vmware integration.component.test_routers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3259) integration.component.test_routers test cases failed with ssh connection error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701820#comment-13701820
]
Rayees Namathponnan commented on CLOUDSTACK-3259:
-
1) Test case test_routers.TestRouterStopCreateFW.test_01_RouterStopCreateFW
failed with below error
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
testMethod()
File /data/Repo2/qa/cloudstack/test/integration/component/test_routers.py,
line 1220, in test_01_RouterStopCreateFW
'iptables -t nat -L'
File
/usr/local/lib/python2.7/site-packages/marvin/integration/lib/utils.py, line
161, in get_process_status
ssh = remoteSSHClient(hostip, port, username, password)
File /usr/local/lib/python2.7/site-packages/marvin/remoteSSHClient.py, line
45, in __init__
self.ssh.connect(str(host), int(port), user, passwd)
File /usr/local/lib/python2.7/site-packages/paramiko/client.py, line 300,
in connect
retry_on_signal(lambda: sock.connect(addr))
File /usr/local/lib/python2.7/site-packages/paramiko/util.py, line 278, in
retry_on_signal
return function()
File /usr/local/lib/python2.7/site-packages/paramiko/client.py, line 300,
in lambda
retry_on_signal(lambda: sock.connect(addr))
File /usr/local/lib/python2.7/socket.py, line 222, in meth
return getattr(self._sock,name)(*args)
[Errno 111] Connection refused
2) test_routers.TestRouterStopCreateLB.test_01_RouterStopCreateLB
SSH Access failed for 10.1.1.112: SSHException('Error reading SSH protocol
banner',)
begin captured logging
testclient.testcase.TestRouterStopCreateLB: DEBUG: Stopping router with ID:
86a7faad-534b-43b2-856c-81df98fccc62
testclient.testcase.TestRouterStopCreateLB: DEBUG: Creating LB rule for public
IP: 9d26f268-ca6c-419a-894f-1eb62586fef9
testclient.testcase.TestRouterStopCreateLB: DEBUG: Assigning VM
c38b246f-65fa-48c9-8403-6ce40fb525d4 to LB rule:
a1e6e9d1-3cff-4f1a-aa11-497fd1b590e6
testclient.testcase.TestRouterStopCreateLB: DEBUG: SSH into VM with IP:
10.223.243.53
paramiko.transport: DEBUG: starting thread (client mode): 0x150b9e10L
paramiko.transport: ERROR: Exception: Error reading SSH protocol banner
paramiko.transport: ERROR: Traceback (most recent call last):
paramiko.transport: ERROR: File
/usr/local/lib/python2.7/site-packages/paramiko/transport.py, line 1555, in
run
paramiko.transport: ERROR: self._check_banner()
paramiko.transport: ERROR: File
/usr/local/lib/python2.7/site-packages/paramiko/transport.py, line 1681, in
_check_banner
paramiko.transport: ERROR: raise SSHException('Error reading SSH protocol
banner' + str(x))
paramiko.transport: ERROR: SSHException: Error reading SSH protocol banner
paramiko.transport: ERROR:
integration.component.test_routers test cases failed with ssh connection
error
---
Key: CLOUDSTACK-3259
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3259
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.2.0
Environment: Automation : Vmware
Reporter: Rayees Namathponnan
Fix For: 4.2.0
Test cases failed with ssh connection error in vmware
integration.component.test_routers
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3354) [automation] scale up VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701823#comment-13701823
]
ASF subversion and git services commented on CLOUDSTACK-3354:
-
Commit 800c9e4091e72d1e6d02da3b66c9a9c9120357f5 in branch refs/heads/4.2 from
[~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=800c9e4 ]
CLOUDSTACK-3354: The CentOS built-in is dynamically scalable
Marking default CentOS template as dynamically_scalable template. The
PV tools are installed in our CentOS 5.6 template already.
Signed-off-by: Prasanna Santhanam t...@apache.org
(cherry picked from commit d249bc7ce6c35df47705b6cd95eecf8a57de8b49)
[automation] scale up VM is failing
---
Key: CLOUDSTACK-3354
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3354
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
Environment: xenserver 6.1
Reporter: Srikanteswararao Talluri
Assignee: Harikrishna Patnala
Priority: Blocker
Fix For: 4.2.0
Steps to reproduce:
1. create instance with tiny instance.
2. mount xstools iso
3. install xen pv drivers mountpoint/Linux/install.sh
4. Scaleup the vm created in step 1 to a big instance.
2013-07-04 15:52:22,664 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null)
===START=== 10.101.255.52 -- GET
command=scaleVirtualMachineid=adf50367-09ae-447d-9954-44f2e767e3deserviceofferingid=31381d8f-445b-4e89-86d1-0c5903d8e4adresponse=jsonsessionkey=CS5Ro9Vvbhn2TB1iTqjoB1s4lfQ%3D_=1372913891906
2013-07-04 15:52:22,679 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-6:null) ControlledEntity name is:com.cloud.vm.VirtualMachine
2013-07-04 15:52:22,683 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-6:null) ControlledEntity name is:com.cloud.uservm.UserVm
2013-07-04 15:52:22,685 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-6:null) ControlledEntity name
is:com.cloud.network.router.VirtualRouter
2013-07-04 15:52:22,690 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-6:null) InfrastructureEntity name
is:com.cloud.offering.ServiceOffering
2013-07-04 15:52:22,743 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-6:null) submit async job-926, details: AsyncJobVO {id:926,
userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId:
null, cmd: org.apache.cloudstack.api.command.user.vm.ScaleVMCmd,
cmdOriginator: null, cmdInfo:
{id:adf50367-09ae-447d-9954-44f2e767e3de,response:json,sessionkey:CS5Ro9Vvbhn2TB1iTqjoB1s4lfQ\u003d,serviceofferingid:31381d8f-445b-4e89-86d1-0c5903d8e4ad,ctxUserId:2,httpmethod:GET,_:1372913891906,ctxAccountId:2,ctxStartEventId:4321},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7363452993625,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-07-04 15:52:22,747 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null)
===END=== 10.101.255.52 -- GET
command=scaleVirtualMachineid=adf50367-09ae-447d-9954-44f2e767e3deserviceofferingid=31381d8f-445b-4e89-86d1-0c5903d8e4adresponse=jsonsessionkey=CS5Ro9Vvbhn2TB1iTqjoB1s4lfQ%3D_=1372913891906
2013-07-04 15:52:22,771 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-38:job-926) Executing
org.apache.cloudstack.api.command.user.vm.ScaleVMCmd for job-926
2013-07-04 15:52:22,782 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-38:job-926) ControlledEntity name is:com.cloud.vm.VirtualMachine
2013-07-04 15:52:22,785 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-38:job-926) ControlledEntity name is:com.cloud.uservm.UserVm
2013-07-04 15:52:22,787 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-38:job-926) ControlledEntity name
is:com.cloud.network.router.VirtualRouter
2013-07-04 15:52:22,790 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-38:job-926) InfrastructureEntity name
is:com.cloud.offering.ServiceOffering
2013-07-04 15:52:22,859 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-38:job-926) Checking if host: 1 has enough capacity for
requested CPU: 0 and requested RAM: 402653184 , cpuOverprovisioningFactor: 1.0
2013-07-04 15:52:22,864 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-38:job-926) Hosts's actual total CPU: 9576 and CPU after
applying overprovisioning: 9576
2013-07-04 15:52:22,864 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-38:job-926) considerReservedCapacity isfalse , not considering
reserved capacity for calculating free capacity
2013-07-04 15:52:22,864 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-38:job-926) Free CPU: 7576 , Requested CPU: 0
[jira] [Commented] (CLOUDSTACK-3354) [automation] scale up VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701824#comment-13701824
]
ASF subversion and git services commented on CLOUDSTACK-3354:
-
Commit d249bc7ce6c35df47705b6cd95eecf8a57de8b49 in branch refs/heads/master
from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d249bc7 ]
CLOUDSTACK-3354: The CentOS built-in is dynamically scalable
Marking default CentOS template as dynamically_scalable template. The
PV tools are installed in our CentOS 5.6 template already.
Signed-off-by: Prasanna Santhanam t...@apache.org
[automation] scale up VM is failing
---
Key: CLOUDSTACK-3354
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3354
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
Environment: xenserver 6.1
Reporter: Srikanteswararao Talluri
Assignee: Harikrishna Patnala
Priority: Blocker
Fix For: 4.2.0
Steps to reproduce:
1. create instance with tiny instance.
2. mount xstools iso
3. install xen pv drivers mountpoint/Linux/install.sh
4. Scaleup the vm created in step 1 to a big instance.
2013-07-04 15:52:22,664 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null)
===START=== 10.101.255.52 -- GET
command=scaleVirtualMachineid=adf50367-09ae-447d-9954-44f2e767e3deserviceofferingid=31381d8f-445b-4e89-86d1-0c5903d8e4adresponse=jsonsessionkey=CS5Ro9Vvbhn2TB1iTqjoB1s4lfQ%3D_=1372913891906
2013-07-04 15:52:22,679 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-6:null) ControlledEntity name is:com.cloud.vm.VirtualMachine
2013-07-04 15:52:22,683 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-6:null) ControlledEntity name is:com.cloud.uservm.UserVm
2013-07-04 15:52:22,685 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-6:null) ControlledEntity name
is:com.cloud.network.router.VirtualRouter
2013-07-04 15:52:22,690 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-6:null) InfrastructureEntity name
is:com.cloud.offering.ServiceOffering
2013-07-04 15:52:22,743 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-6:null) submit async job-926, details: AsyncJobVO {id:926,
userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId:
null, cmd: org.apache.cloudstack.api.command.user.vm.ScaleVMCmd,
cmdOriginator: null, cmdInfo:
{id:adf50367-09ae-447d-9954-44f2e767e3de,response:json,sessionkey:CS5Ro9Vvbhn2TB1iTqjoB1s4lfQ\u003d,serviceofferingid:31381d8f-445b-4e89-86d1-0c5903d8e4ad,ctxUserId:2,httpmethod:GET,_:1372913891906,ctxAccountId:2,ctxStartEventId:4321},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7363452993625,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-07-04 15:52:22,747 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null)
===END=== 10.101.255.52 -- GET
command=scaleVirtualMachineid=adf50367-09ae-447d-9954-44f2e767e3deserviceofferingid=31381d8f-445b-4e89-86d1-0c5903d8e4adresponse=jsonsessionkey=CS5Ro9Vvbhn2TB1iTqjoB1s4lfQ%3D_=1372913891906
2013-07-04 15:52:22,771 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-38:job-926) Executing
org.apache.cloudstack.api.command.user.vm.ScaleVMCmd for job-926
2013-07-04 15:52:22,782 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-38:job-926) ControlledEntity name is:com.cloud.vm.VirtualMachine
2013-07-04 15:52:22,785 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-38:job-926) ControlledEntity name is:com.cloud.uservm.UserVm
2013-07-04 15:52:22,787 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-38:job-926) ControlledEntity name
is:com.cloud.network.router.VirtualRouter
2013-07-04 15:52:22,790 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-38:job-926) InfrastructureEntity name
is:com.cloud.offering.ServiceOffering
2013-07-04 15:52:22,859 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-38:job-926) Checking if host: 1 has enough capacity for
requested CPU: 0 and requested RAM: 402653184 , cpuOverprovisioningFactor: 1.0
2013-07-04 15:52:22,864 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-38:job-926) Hosts's actual total CPU: 9576 and CPU after
applying overprovisioning: 9576
2013-07-04 15:52:22,864 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-38:job-926) considerReservedCapacity isfalse , not considering
reserved capacity for calculating free capacity
2013-07-04 15:52:22,864 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-38:job-926) Free CPU: 7576 , Requested CPU: 0
2013-07-04 15:52:22,865 DEBUG [cloud.capacity.CapacityManagerImpl]
[jira] [Created] (CLOUDSTACK-3391) [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter
Sailaja Mada created CLOUDSTACK-3391: Summary: [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter Key: CLOUDSTACK-3391 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3391 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sailaja Mada Observation : Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter . Expected behavior : We should have icons to identify these new options separately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-847) [DOC] Document the ability to use multiple IP ranges
[ https://issues.apache.org/jira/browse/CLOUDSTACK-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701826#comment-13701826 ] ASF subversion and git services commented on CLOUDSTACK-847: Commit a9aa659273b152d8ab9b9ad5dbc769ad65495e34 in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a9aa659 ] CLOUDSTACK-847 ui part [DOC] Document the ability to use multiple IP ranges Key: CLOUDSTACK-847 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-847 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: David Nalley Assignee: Radhika Nair Fix For: 4.2.0 Document the ability to make use of multiple IP ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3391) [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3391: - Attachment: dedicatehostUI.png addDc.png [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter -- Key: CLOUDSTACK-3391 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3391 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sailaja Mada Attachments: addDc.png, dedicatehostUI.png Observation : Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter . Expected behavior : We should have icons to identify these new options separately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2547) Should not allow to create VLAN beyond 4095
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam resolved CLOUDSTACK-2547. Resolution: Duplicate Dupes CLOUDSTACK-3384. Closing this since 3384 includes more information and the patch. Should not allow to create VLAN beyond 4095 - Key: CLOUDSTACK-2547 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2547 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Rayees Namathponnan Priority: Minor There are a maximum of 4096 possible values ranging from 0 to 4095 for VLAN, but cloudstack allowing more then this. Steps to reproduce Run below automation test case test/integration/smoke/test_public_ip_range.py -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3384) CloudStack allow VLAN range between 0-4096. Should be 0-'4095'.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701828#comment-13701828 ] Prasanna Santhanam commented on CLOUDSTACK-3384: https://reviews.apache.org/r/12278/ CloudStack allow VLAN range between 0-4096. Should be 0-'4095'. --- Key: CLOUDSTACK-3384 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3384 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: Toshiaki Hatano Assignee: Toshiaki Hatano Priority: Minor Fix For: Future Original Estimate: 2h Remaining Estimate: 2h There're VLAN range check code in com.cloud.network.NetworkServiceImpl. But it allows VLAN range between 0-4096. VLAN ID have 12 bit field and it's between 0-4095 (0x000 - 0xFFF) . CloudStack should return error when someone try to assign VLAN ID 4096 to network. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3352) NTier: Replace Network ACL doesn't remove old ACL rules on the Private Gateway when new empty acl is applied
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy updated CLOUDSTACK-3352: -- Summary: NTier: Replace Network ACL doesn't remove old ACL rules on the Private Gateway when new empty acl is applied (was: NTier: Replace Network ACL doesn't replace the ACL rules on the Private Gateway) NTier: Replace Network ACL doesn't remove old ACL rules on the Private Gateway when new empty acl is applied Key: CLOUDSTACK-3352 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3352 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: Chandan Purushothama Assignee: Jayapal Reddy Priority: Blocker Fix For: 4.2.0 === ACL List: === mysql select * from network_acl where id=3; ++-+--++-+ | id | name| uuid | vpc_id | description | ++-+--++-+ | 3 | Atoms-ACL-1 | 593ef61a-09af-43a4-8bb5-7038d3904377 | 1 | Atoms-ACL-1 | ++-+--++-+ 1 row in set (0.00 sec) = ACL List Items: = mysql select id,start_port,end_port,state,protocol,created,traffic_type,cidr,number,action from network_acl_item where acl_id=3; +++--++--+-+--+---+++ | id | start_port | end_port | state | protocol | created | traffic_type | cidr | number | action | +++--++--+-+--+---+++ | 5 | 18 | 29 | Active | tcp | 2013-07-02 19:06:47 | Ingress | 10.223.131.172/32 | 3 | Allow | | 6 | 17 | 37 | Active | tcp | 2013-07-02 19:08:25 | Ingress | 10.223.195.103/32 | 5 | Deny | | 7 | 16 | 36 | Active | tcp | 2013-07-02 21:27:16 | Egress | 10.223.131.172/32 | 4 | Deny | | 8 | 15 | 35 | Active | tcp | 2013-07-02 21:28:08 | Egress | 10.223.195.103/32 | 6 | Allow | +++--++--+-+--+---+++ 4 rows in set (0.00 sec) == Private Gateway is assigned this ACL: == mysql select * from vpc_gateways \G *** 1. row *** id: 1 uuid: 16300ab6-a039-49f7-a83b-f5eea4c40b20 ip4_address: 10.223.60.30 netmask: 255.255.255.192 gateway: 10.223.60.1 vlan_tag: 600 type: Private network_id: 206 vpc_id: 1 zone_id: 1 created: 2013-07-02 22:17:02 account_id: 3 domain_id: 1 state: Ready removed: NULL source_nat: 1 network_acl_id: 3 1 row in set (0.01 sec) = On the VPC Virtual Router: = root@r-3-NTIERRR:~# ifconfig eth4 eth4 Link encap:Ethernet HWaddr 06:04:5a:00:00:22 inet addr:10.223.60.30 Bcast:10.223.60.63 Mask:255.255.255.192 inet6 addr: fe80::404:5aff:fe00:22/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1748 errors:0 dropped:0 overruns:0 frame:0 TX packets:887 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:80522 (78.6 KiB) TX bytes:37690 (36.8 KiB) Interrupt:27 root@r-3-NTIERRR:~# iptables-save | grep ACL | grep eth4 :ACL_OUTBOUND_eth4 - [0:0] -A PREROUTING -i eth4 -m state --state NEW -j ACL_OUTBOUND_eth4 -A ACL_OUTBOUND_eth4 -d 10.223.195.103/32 -p tcp -m tcp --dport 15:35 -j ACCEPT -A ACL_OUTBOUND_eth4 -d 10.223.131.172/32 -p tcp -m tcp --dport 16:36 -j DROP -A ACL_OUTBOUND_eth4 -j DROP :ACL_INBOUND_eth4 - [0:0] -A FORWARD -o eth4 -j ACL_INBOUND_eth4 -A ACL_INBOUND_eth4 -s 10.223.131.172/32 -p tcp -m tcp --dport 18:29 -j ACCEPT -A ACL_INBOUND_eth4 -s 10.223.195.103/32 -p tcp -m tcp --dport 17:37 -j DROP -A ACL_INBOUND_eth4 -j DROP root@r-3-NTIERRR:~# ** Replace the ACL List to the one mentioned below mysql select * from network_acl where id=4; ++-+--++-+ | id | name| uuid
[jira] [Commented] (CLOUDSTACK-2592) [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701840#comment-13701840 ] ASF subversion and git services commented on CLOUDSTACK-2592: - Commit 5f395e41abd253b65287bdfe601ca3bf6c58604f in branch refs/heads/master from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5f395e4 ] CLOUDSTACK-2592 [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error Now ESXi server license would be fetched to see if HOTPLUG feature is license or not. Throw Exception if the feature is not licensed. Also added FeatureKeyConstants enum type to maintain list of various features to be checked whether licensed or not. [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error --- Key: CLOUDSTACK-2592 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2592 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, VMware Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Assignee: Sateesh Chodapuneedi Stacktrace File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /data/Repo2/qa/incubator-cloudstack/test/integration/smoke/test_scale_vm.py, line 213, in test_01_scale_vm Check service offering of the VM File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual assertion_func(first, second, msg=msg) File /usr/local/lib/python2.7/unittest/case.py, line 902, in assertMultiLineEqual self.fail(self._formatMessage(msg, standardMsg)) File /usr/local/lib/python2.7/unittest/case.py, line 393, in fail raise self.failureException(msg) Check service offering of the VM Upon manual verification :: Setup was unable to scale up the VM. Choosing a larger offering actually doesnt give any errors. But the VM details still reflects old service offering. Digging around reveled from MS log: 2013-05-20 16:13:26,004 ERROR [vmware.resource.VmwareResource] (DirectAgent-1:10.223.250.130) Unexpected exception: java.lang.RuntimeException: License not available to perform the operation. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:291) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:806) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2272) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:500) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) If license is not available then CS should throw appropriate error as Feature not supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2592) [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701841#comment-13701841 ] ASF subversion and git services commented on CLOUDSTACK-2592: - Commit 574f782ab2371828a02e22b3003cd7bbdefc9777 in branch refs/heads/4.2 from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=574f782 ] CLOUDSTACK-2592 [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error Now ESXi server license would be fetched to see if HOTPLUG feature is license or not. Throw Exception if the feature is not licensed. Also added FeatureKeyConstants enum type to maintain list of various features to be checked whether licensed or not. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error --- Key: CLOUDSTACK-2592 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2592 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, VMware Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Assignee: Sateesh Chodapuneedi Stacktrace File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /data/Repo2/qa/incubator-cloudstack/test/integration/smoke/test_scale_vm.py, line 213, in test_01_scale_vm Check service offering of the VM File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual assertion_func(first, second, msg=msg) File /usr/local/lib/python2.7/unittest/case.py, line 902, in assertMultiLineEqual self.fail(self._formatMessage(msg, standardMsg)) File /usr/local/lib/python2.7/unittest/case.py, line 393, in fail raise self.failureException(msg) Check service offering of the VM Upon manual verification :: Setup was unable to scale up the VM. Choosing a larger offering actually doesnt give any errors. But the VM details still reflects old service offering. Digging around reveled from MS log: 2013-05-20 16:13:26,004 ERROR [vmware.resource.VmwareResource] (DirectAgent-1:10.223.250.130) Unexpected exception: java.lang.RuntimeException: License not available to perform the operation. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:291) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:806) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2272) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:500) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) If license is not available then CS should throw appropriate error as Feature not supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2592) [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi resolved CLOUDSTACK-2592. -- Resolution: Fixed Fix Version/s: 4.2.0 [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error --- Key: CLOUDSTACK-2592 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2592 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, VMware Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Stacktrace File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /data/Repo2/qa/incubator-cloudstack/test/integration/smoke/test_scale_vm.py, line 213, in test_01_scale_vm Check service offering of the VM File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual assertion_func(first, second, msg=msg) File /usr/local/lib/python2.7/unittest/case.py, line 902, in assertMultiLineEqual self.fail(self._formatMessage(msg, standardMsg)) File /usr/local/lib/python2.7/unittest/case.py, line 393, in fail raise self.failureException(msg) Check service offering of the VM Upon manual verification :: Setup was unable to scale up the VM. Choosing a larger offering actually doesnt give any errors. But the VM details still reflects old service offering. Digging around reveled from MS log: 2013-05-20 16:13:26,004 ERROR [vmware.resource.VmwareResource] (DirectAgent-1:10.223.250.130) Unexpected exception: java.lang.RuntimeException: License not available to perform the operation. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:291) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:806) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2272) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:500) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) If license is not available then CS should throw appropriate error as Feature not supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3154) [UI] No task notification after successful removal of VMware DC from cloudstack zone.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3154: - Priority: Major (was: Minor) [UI] No task notification after successful removal of VMware DC from cloudstack zone. - Key: CLOUDSTACK-3154 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3154 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Cloudstack deployed over VMware ESXi 5.0 servers Reporter: Sateesh Chodapuneedi Fix For: 4.2.0 Steps to reproduce - 1) Goto Infrastructure - click on zones 2) Click on specific zone which is already added with Vmware DC 3) Click on icon Remove VMware Datacenter 4) Even after successful completion of the command, UI continues to show wait image (circles in middle). Expected - UI should stop wait image display successful or failure notification. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3154) [UI] No task notification after successful removal of VMware DC from cloudstack zone.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701856#comment-13701856 ] Sailaja Mada commented on CLOUDSTACK-3154: -- UI will be in processing state forever . It gives wrong indication that operation still in progress. Hence marking it as major bug as impact is high. [UI] No task notification after successful removal of VMware DC from cloudstack zone. - Key: CLOUDSTACK-3154 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3154 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Cloudstack deployed over VMware ESXi 5.0 servers Reporter: Sateesh Chodapuneedi Fix For: 4.2.0 Steps to reproduce - 1) Goto Infrastructure - click on zones 2) Click on specific zone which is already added with Vmware DC 3) Click on icon Remove VMware Datacenter 4) Even after successful completion of the command, UI continues to show wait image (circles in middle). Expected - UI should stop wait image display successful or failure notification. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3389) Documentation nTier Apps 2.0 : KVM Hypervisor support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701859#comment-13701859 ] Radhika Nair commented on CLOUDSTACK-3389: -- documented in the release notes Documentation nTier Apps 2.0 : KVM Hypervisor support - Key: CLOUDSTACK-3389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3389 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 https://issues.apache.org/jira/browse/CLOUDSTACK-750 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3389) Documentation nTier Apps 2.0 : KVM Hypervisor support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-3389. -- Resolution: Fixed Documentation nTier Apps 2.0 : KVM Hypervisor support - Key: CLOUDSTACK-3389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3389 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 https://issues.apache.org/jira/browse/CLOUDSTACK-750 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3389) Documentation nTier Apps 2.0 : KVM Hypervisor support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701867#comment-13701867 ] ASF subversion and git services commented on CLOUDSTACK-3389: - Commit a711db5a3d3f1689eb2d5a4781390fc82ab69e1f in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a711db5 ] CLOUDSTACK-3389 Documentation nTier Apps 2.0 : KVM Hypervisor support - Key: CLOUDSTACK-3389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3389 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 https://issues.apache.org/jira/browse/CLOUDSTACK-750 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2592) [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701873#comment-13701873 ] ASF subversion and git services commented on CLOUDSTACK-2592: - Commit 30161f8592d9e7d06942c73e131b40d79a90ad54 in branch refs/heads/master-6-17-stable from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=30161f8 ] CLOUDSTACK-2592 [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error Now ESXi server license would be fetched to see if HOTPLUG feature is license or not. Throw Exception if the feature is not licensed. Also added FeatureKeyConstants enum type to maintain list of various features to be checked whether licensed or not. [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate error --- Key: CLOUDSTACK-2592 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2592 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, VMware Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Stacktrace File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /data/Repo2/qa/incubator-cloudstack/test/integration/smoke/test_scale_vm.py, line 213, in test_01_scale_vm Check service offering of the VM File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual assertion_func(first, second, msg=msg) File /usr/local/lib/python2.7/unittest/case.py, line 902, in assertMultiLineEqual self.fail(self._formatMessage(msg, standardMsg)) File /usr/local/lib/python2.7/unittest/case.py, line 393, in fail raise self.failureException(msg) Check service offering of the VM Upon manual verification :: Setup was unable to scale up the VM. Choosing a larger offering actually doesnt give any errors. But the VM details still reflects old service offering. Digging around reveled from MS log: 2013-05-20 16:13:26,004 ERROR [vmware.resource.VmwareResource] (DirectAgent-1:10.223.250.130) Unexpected exception: java.lang.RuntimeException: License not available to perform the operation. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:291) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:806) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2272) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:500) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) If license is not available then CS should throw appropriate error as Feature not supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3389) Documentation nTier Apps 2.0 : KVM Hypervisor support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701872#comment-13701872 ] Radhika Nair commented on CLOUDSTACK-3389: -- Documented in the Inter-VLAN Routing section Documentation nTier Apps 2.0 : KVM Hypervisor support - Key: CLOUDSTACK-3389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3389 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 https://issues.apache.org/jira/browse/CLOUDSTACK-750 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2764) Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-2764. -- Resolution: Fixed Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760) --- Key: CLOUDSTACK-2764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2764 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2764) Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-2764: - Attachment: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf see 15.25.4. Configuring Access Control List Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760) --- Key: CLOUDSTACK-2764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2764 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1297) listVirtualMachines api does not return for the instance name of the Vm created
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701876#comment-13701876 ] Marc Brashear commented on CLOUDSTACK-1297: --- I am seeing this bug in for XenServer in CloudStack 4.1 as well. If listVirtualMachines is run via the API I receive all VM instances. If I specify the name of an instance in the query, I get no results: http://x.x.x.x:8080/client/api?command=listVirtualMachinesname=VLAB02-WOPT-DEMO listvirtualmachinesresponse cloud-stack-version=4.1.0/ List with no filter: http://x.x.x.x:8080/client/api?command=listVirtualMachines listvirtualmachinesresponse cloud-stack-version=4.1.0 count1/count virtualmachine idb92e02b2-f800-46a5-8e62-380b4577d1f9/id nameVLAB02-WOPT-DEMO/name displaynameVLAB02-DEMO-WOPT-1/displayname accountadmin/account domainiddeba188c-e228-11e2-9c07-566ad45d4d5b/domainid domainROOT/domain created2013-07-08T01:41:18+/created stateRunning/state haenablefalse/haenable zoneidf708ed1a-d010-4b97-96e1-6f6d8a36f14e/zoneid zonenameVLAB02-ZONE-1/zonename hostid9f168376-3a5f-426a-850c-9f58831b935e/hostid hostnameVLAB02-HOST-1/hostname templateid9d96af1f-5a1b-4dee-a54b-39a282091731/templateid templatenameVLAB02-WOPT/templatename templatedisplaytextVLAB02-WOPT/templatedisplaytext passwordenabledfalse/passwordenabled serviceofferingida89c0aee-3dd4-4e1d-ad4d-eacf1ca4ccd2/serviceofferingid serviceofferingnameWOPT/serviceofferingname cpunumber1/cpunumber cpuspeed1000/cpuspeed memory2048/memory cpuused2.11%/cpuused networkkbsread201/networkkbsread networkkbswrite191/networkkbswrite guestosiddf812026-e228-11e2-9c07-566ad45d4d5b/guestosid rootdeviceid0/rootdeviceid rootdevicetypeROOT/rootdevicetype nic idafed50ed-4030-4e4f-8cf0-e94d8b8a6498/id networkid35552563-bd95-4c97-a591-d614ce594033/networkid networknameWOPT-WAN-400/networkname netmask255.255.255.248/netmask gateway1.1.1.1/gateway ipaddress1.1.1.2/ipaddress isolationurivlan://400/isolationuri broadcasturivlan://400/broadcasturi traffictypeGuest/traffictype typeShared/type isdefaulttrue/isdefault macaddress06:97:2c:00:00:88/macaddress /nic nic id9dd29926-231a-4c09-8a79-20519ddfb498/id networkided792a27-0bdd-4087-9f93-bf65c13427da/networkid networknameWOPT-LAN-400/networkname netmask255.255.255.248/netmask gateway2.2.2.1/gateway ipaddress2.2.2.2/ipaddress isolationurivlan://400/isolationuri broadcasturivlan://400/broadcasturi traffictypeGuest/traffictype typeShared/type isdefaultfalse/isdefault macaddress06:49:e2:00:00:83/macaddress /nic nic id9cf14057-5b43-4b9c-9ebd-004bce008edf/id networkid5ab86f1b-bceb-4feb-9ca5-b73a5839c617/networkid networknameVM-MGMT-30/networkname netmask255.255.255.0/netmask gateway56.0.4.1/gateway ipaddress56.0.4.21/ipaddress isolationurivlan://30/isolationuri broadcasturivlan://30/broadcasturi traffictypeGuest/traffictype typeShared/type isdefaultfalse/isdefault macaddress06:50:3c:00:00:15/macaddress /nic hypervisorXenServer/hypervisor instancenamei-2-26-VM/instancename tags keyname/key valueVLAB02-DEMO-WOPT-1/value resourcetypeUserVm/resourcetype resourceidb92e02b2-f800-46a5-8e62-380b4577d1f9/resourceid accountadmin/account domainiddeba188c-e228-11e2-9c07-566ad45d4d5b/domainid domainROOT/domain /tags tags keyname/key valueVLAB02-DEMO-WOPT-1/value resourcetypeUserVm/resourcetype resourceidb92e02b2-f800-46a5-8e62-380b4577d1f9/resourceid accountadmin/account domainiddeba188c-e228-11e2-9c07-566ad45d4d5b/domainid domainROOT/domain /tags tags keyname/key valueVLAB02-DEMO-WOPT-1/value resourcetypeUserVm/resourcetype resourceidb92e02b2-f800-46a5-8e62-380b4577d1f9/resourceid accountadmin/account domainiddeba188c-e228-11e2-9c07-566ad45d4d5b/domainid domainROOT/domain /tags /virtualmachine /listvirtualmachinesresponse listVirtualMachines api does not return for the instance name of the Vm created --- Key: CLOUDSTACK-1297 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1297 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: irfan I have deployed CloudStack 3.0.2 on ESXi Vm in vCenter. listVirtualMachines api does not return for the instance name of the Vm created -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2988) UI: checkbox to know whether tools installed on the template during register template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701882#comment-13701882 ] Harikrishna Patnala commented on CLOUDSTACK-2988: - Let me explain the work flow: For dynamic scaling to work virtual machine should have XS tools / VMware tools installed on it. To ensure this Admin/User can do it in two ways :- 1) Admin/User while registering the template provides an input whether tools are installed on the template(or can be done using update template API). 2) If the user deploys a virtual machine with a template that does not have XS tools / VMware tools and later if he/she installs the tools on the VM then he can inform Cloudstack using using updatevirtualmachine API. After installation of tools and updating the virtual machine, user needs to stop and start the vm from cloudstack in order for dynamic scaling of CPU and RAM for that VM. The reason why we need to stop start the VM after updating is we need to set static max memory to some higher value before VM starts so that we can dynamically scale the VM upto static max. UI Changes: During registering/updating template we need to have a checkbox (API boolean parameter isdynamicallyscalable) like we have for public or password enabled. For UpdateVirtualMachine API also we need the same. UI: checkbox to know whether tools installed on the template during register template - Key: CLOUDSTACK-2988 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2988 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Harikrishna Patnala Assignee: Pranav Saxena Fix For: 4.2.0 During template registration/updation there should be a check box to know whether tools are installed on the template or not. Same check box should be there for updateVirtualMachine API. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2816) Documentation for Multiple Private GW Support on VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-2816. -- Resolution: Fixed Documentation for Multiple Private GW Support on VPC Key: CLOUDSTACK-2816 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2816 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 https://issues.apache.org/jira/browse/CLOUDSTACK-767 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2802) Update the Current VPC Documentation for nTier Apps Related Changes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-2802. -- Resolution: Fixed Update the Current VPC Documentation for nTier Apps Related Changes --- Key: CLOUDSTACK-2802 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2802 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 Update the following files: vpc.xml add-vpc.xml add-tier.xml configure-acl.xml add-gateway-vpc.xml add-vm-to-tier.xml acquire-new-ip-for-vpc.xml release-ip-for-vpc.xml enable-disable-static-nat-vpc.xml add-loadbalancer-rule-vpc.xml add-portforward-rule-vpc.xml remove-tier.xml remove-vpc.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2763) Documentation for Supporting Physical Devices to Do LB (CLOUDSTACK-869)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-2763: - Summary: Documentation for Supporting Physical Devices to Do LB (CLOUDSTACK-869) (was: Documentation for Supporting Physical Devices to Do NetworkACL LB (CLOUDSTACK-869)) Documentation for Supporting Physical Devices to Do LB (CLOUDSTACK-869) --- Key: CLOUDSTACK-2763 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2763 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-758) documentation on nTier Apps 2.0: Support upto 8 VPN Gateways
[ https://issues.apache.org/jira/browse/CLOUDSTACK-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-758. - Resolution: Fixed documentation on nTier Apps 2.0: Support upto 8 VPN Gateways Key: CLOUDSTACK-758 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-758 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 Complete documentation on nTier Apps 2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-234) create/delete firewa/lb/pf rule: send ip assoc command only on first rule is created on the IP and last rule is revoked on the IP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701892#comment-13701892 ] ASF subversion and git services commented on CLOUDSTACK-234: Commit ea8b85af2a3052cfb17d7ee6dcf0ee376ecbb177 in branch refs/heads/master from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ea8b85a ] CLOUDSTACK-234: create/delete firewa/lb/pf rule: send ip assoc command only on first rule is created on the IP and last rule is revoked on the IP Current suboptima logic of IP Assoc - On associate IP to GuestNetwork there is an IPAssoc command sent to corresponding network service providers of the network - On every rule apply on IP associated with the network send IP assoc to the network service providers - On every rule deletion on IP associated with a network sernd IP assoc command to the network service providers With this fix logic of IP assoc is changed as below which eliminates executio of unnessary and expensive IpAssocCommand resource command - On associate IP to GuestNetwork, associate IP only to the network, Untill any service is associated with the IP dont send IP Assoc - On creation of first rule on the IP send IPAssoc to corresponding network service provider. Since IP is used for a service, IPAssoc need to be sent to correpondign service provider - On deletion of last rule on the IP send IPAssoc to corresponding network service provider. When last rule is deleted, IP has no service associated with it, so send IP assoc to service provider to remove the IP association create/delete firewa/lb/pf rule: send ip assoc command only on first rule is created on the IP and last rule is revoked on the IP - Key: CLOUDSTACK-234 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-234 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.0.0 Reporter: Alena Prokharchyk Assignee: Murali Reddy Fix For: 4.2.0 We have to improve the logic for creating/deleting any kind of firewall rules. At the moment ipAssoc is being called when: * the first rule for the ip address is being created * the last rule for the IP address is being removed As a part of ipAssoc command, we send all ip addresses assigned to the guest network of the rule. The behavior has to be fixed the way we send ip assoc only for the ip address the rule is being created for. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3392) resizeDataVolume throws an expception when trying to shrink volume on XenServer
Pavan Kumar Bandarupally created CLOUDSTACK-3392:
Summary: resizeDataVolume throws an expception when trying to
shrink volume on XenServer
Key: CLOUDSTACK-3392
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3392
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: Management Server: RHEL 6.3
Xenserver: 6.1
Reporter: Pavan Kumar Bandarupally
Priority: Critical
Fix For: 4.2.0
An exception is thrown when trying to re-size(shrink) a data volume for a guest
VM hosted on Xenserver. The guest VM is shutdown before resizing as resize on
Xenserver is supported on offline VMs
Note: Increasing the volume works fine. The exception is thrown only for
shrink. Attaching MS log.
Stack Trace:
---
2013-07-08 20:18:36,971 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-37:null) Unable to resize volume
SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not allowed]
at com.xensource.xenapi.Types.checkResponse(Types.java:1936)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VDI.resize(VDI.java:1350)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:6155)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:516)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-07-08 20:18:36,972 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-37:null) Seq 1-1025154837: Response Received:
2013-07-08 20:18:36,973 DEBUG [agent.transport.Request] (DirectAgent-37:null)
Seq 1-1025154837: Processing: { Ans: , MgmtId: 7541090156566, via: 1, Ver: v1,
Flags: 10,
[{storage.ResizeVolumeAnswer:{newSize:0,result:false,details:failed to
resize volume:SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not
allowed],wait:0}}] }
2013-07-08 20:18:36,974 DEBUG [agent.transport.Request]
(Job-Executor-36:job-61) Seq 1-1025154837: Received: { Ans: , MgmtId:
7541090156566, via: 1, Ver: v1, Flags: 10, { ResizeVolumeAnswer } }
2013-07-08 20:18:37,029 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-36:job-61) Complete async job-61, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.VolumeResponse@1ff504a5
2013-07-08 20:18:37,044 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-36:job-61) Done executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-61
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3392) resizeDataVolume throws an expception when trying to shrink volume on XenServer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan Kumar Bandarupally updated CLOUDSTACK-3392:
-
Attachment: management-server-log.rar
Attached is the detailed log
resizeDataVolume throws an expception when trying to shrink volume on
XenServer
---
Key: CLOUDSTACK-3392
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3392
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: Management Server: RHEL 6.3
Xenserver: 6.1
Reporter: Pavan Kumar Bandarupally
Priority: Critical
Fix For: 4.2.0
Attachments: management-server-log.rar
An exception is thrown when trying to re-size(shrink) a data volume for a
guest VM hosted on Xenserver. The guest VM is shutdown before resizing as
resize on Xenserver is supported on offline VMs
Note: Increasing the volume works fine. The exception is thrown only for
shrink. Attaching MS log.
Stack Trace:
---
2013-07-08 20:18:36,971 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-37:null) Unable to resize volume
SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not allowed]
at com.xensource.xenapi.Types.checkResponse(Types.java:1936)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VDI.resize(VDI.java:1350)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:6155)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:516)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-07-08 20:18:36,972 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-37:null) Seq 1-1025154837: Response Received:
2013-07-08 20:18:36,973 DEBUG [agent.transport.Request] (DirectAgent-37:null)
Seq 1-1025154837: Processing: { Ans: , MgmtId: 7541090156566, via: 1, Ver:
v1, Flags: 10,
[{storage.ResizeVolumeAnswer:{newSize:0,result:false,details:failed
to resize volume:SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not
allowed],wait:0}}] }
2013-07-08 20:18:36,974 DEBUG [agent.transport.Request]
(Job-Executor-36:job-61) Seq 1-1025154837: Received: { Ans: , MgmtId:
7541090156566, via: 1, Ver: v1, Flags: 10, { ResizeVolumeAnswer } }
2013-07-08 20:18:37,029 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-36:job-61) Complete async job-61, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.VolumeResponse@1ff504a5
2013-07-08 20:18:37,044 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-36:job-61) Done executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-61
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3392) resizeDataVolume throws an expception when trying to shrink volume on XenServer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanna Santhanam updated CLOUDSTACK-3392:
---
Labels: integration-test (was: )
resizeDataVolume throws an expception when trying to shrink volume on
XenServer
---
Key: CLOUDSTACK-3392
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3392
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: Management Server: RHEL 6.3
Xenserver: 6.1
Reporter: Pavan Kumar Bandarupally
Priority: Critical
Labels: integration-test
Fix For: 4.2.0
Attachments: management-server-log.rar
An exception is thrown when trying to re-size(shrink) a data volume for a
guest VM hosted on Xenserver. The guest VM is shutdown before resizing as
resize on Xenserver is supported on offline VMs
Note: Increasing the volume works fine. The exception is thrown only for
shrink. Attaching MS log.
Stack Trace:
---
2013-07-08 20:18:36,971 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-37:null) Unable to resize volume
SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not allowed]
at com.xensource.xenapi.Types.checkResponse(Types.java:1936)
at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
at com.xensource.xenapi.VDI.resize(VDI.java:1350)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:6155)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:516)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-07-08 20:18:36,972 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-37:null) Seq 1-1025154837: Response Received:
2013-07-08 20:18:36,973 DEBUG [agent.transport.Request] (DirectAgent-37:null)
Seq 1-1025154837: Processing: { Ans: , MgmtId: 7541090156566, via: 1, Ver:
v1, Flags: 10,
[{storage.ResizeVolumeAnswer:{newSize:0,result:false,details:failed
to resize volume:SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not
allowed],wait:0}}] }
2013-07-08 20:18:36,974 DEBUG [agent.transport.Request]
(Job-Executor-36:job-61) Seq 1-1025154837: Received: { Ans: , MgmtId:
7541090156566, via: 1, Ver: v1, Flags: 10, { ResizeVolumeAnswer } }
2013-07-08 20:18:37,029 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-36:job-61) Complete async job-61, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.VolumeResponse@1ff504a5
2013-07-08 20:18:37,044 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-36:job-61) Done executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-61
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
Koushik Das created CLOUDSTACK-3393: --- Summary: Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Koushik Das This will result in data loss as a new local volume is created and the old one will be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-3393: Affects Version/s: 4.2.0 Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Koushik Das This will result in data loss as a new local volume is created and the old one will be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-3393: Affects Version/s: 4.1.0 Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Koushik Das Fix For: 4.2.0 This will result in data loss as a new local volume is created and the old one will be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-3393: --- Assignee: Koushik Das Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.2.0 This will result in data loss as a new local volume is created and the old one will be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-3393: Fix Version/s: 4.2.0 Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Koushik Das Fix For: 4.2.0 This will result in data loss as a new local volume is created and the old one will be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3376) NPE: resource count calculation from the account manager on account cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi reassigned CLOUDSTACK-3376: --- Assignee: Sanjay Tripathi NPE: resource count calculation from the account manager on account cleanup --- Key: CLOUDSTACK-3376 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3376 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: Prasanna Santhanam Assignee: Sanjay Tripathi Fix For: 4.2.0 Attachments: 483.tar.bz2 During account cleanup on one of the accounts the following NPE was encountered on a template that had failed to delete. Attaching complete logs. This was an XCP 1.6 setup of cloudstack master Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 06:46:44,066 DEBUG [db.Transaction.Transaction] (AccountChecker-1:null) Rolling back the transaction: Time = 2 Name = -AccountManagerImpl$AccountCleanupTask.run:1481-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679; called by -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-ResourceLimitManagerImpl.recalculateResourceCount:702-HypervisorTemplateAdapter.delete:277-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-TemplateManagerImpl.delete:748-AccountManagerImpl.cleanupAccount:592-AccountManagerImpl$AccountCleanupTask.run:1488-Executors$RunnableAdapter.call:471 Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 06:46:44,066 WARN [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete template while removing account: Public template-5D26S2 due to: Jul 4 23:46:44 java.lang.NullPointerException Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:277) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:748) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at java.lang.Thread.run(Thread.java:679) Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 06:46:44,067 WARN [cloud.user.AccountManagerImpl]
[jira] [Created] (CLOUDSTACK-3394) [portable IP] unable to transfer IP across zones
venkata swamybabu budumuru created CLOUDSTACK-3394: -- Summary: [portable IP] unable to transfer IP across zones Key: CLOUDSTACK-3394 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3394 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 Environment: commit id # 10d9e5965a687c0c2d1d6c3e57f38602420720d6 Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Fix For: 4.2.0 Steps to reproduce: 1. Have latest CloudStack setup 2. create at least 2 advanced zones (zone1, zone2) 3. add a portable ip range : 10.147.49.220-239/24 4. Have at least one non-ROOT domain user. 5. Login as the above user and create at least 1 network in each zone (Network1, Network2) 6. acquire IP (with cross zones : YES) and associate IP to Network1 7. enable staticNat on the IP acquired in Step: 6 with a VM created in zone2 Observations: (i) It failed with the following error in the mgmt server logs 2013-07-08 10:53:34,893 INFO [cloud.api.ApiServer] (catalina-exec-8:null) Unable to create ip forwarding rule, IP address Ip[10.147.49.221-1] is not in the same availability zone as virtual machine VM[User|Zone2VM1] 2013-07-08 10:53:34,896 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null) ===END=== 10.252.192.25 -- GET apiKey=MdUSVCKSP3sL6ptU2mvdqdF4QcRe5vl2gosM74JOZmIVEjzCpVKtABltph2gEC1u1TBadFcjvRaiHGVEhFddNgcommand=enableStaticNatipaddressid=42fa6947-6987-4d88-9d4d-f9c50ea9fe27networkid=2c0e7246-c41a-490b-9852-ee886381659cresponse=jsonvirtualmachineid=a3625eef-6f56-4d71-9d1d-67e9c7418206signature=RDNschQ2tihuCpAItfc1ltzzPcs%3D (ii) At the end I could see that the public ip has been transferred from one network to the other but the datacenter id is not updated. (iii) Here is the snippet from cloud.user_ip_address table. *** 22. row *** id: 22 uuid: 42fa6947-6987-4d88-9d4d-f9c50ea9fe27 account_id: 3 domain_id: 2 public_ip_address: 10.147.49.221 data_center_id: 1 source_nat: 0 allocated: 2013-07-08 14:52:49 vlan_db_id: 4 one_to_one_nat: 0 vm_id: NULL state: Allocated mac_address: 0 source_network_id: 200 network_id: 209 physical_network_id: 200 is_system: 0 vpc_id: NULL dnat_vmip: NULL is_portable: 1 22 rows in set (0.00 sec) Attaching all the required logs along with db dump. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3394) [portable IP] unable to transfer IP across zones
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkata swamybabu budumuru updated CLOUDSTACK-3394: --- Attachment: logs.tgz [portable IP] unable to transfer IP across zones Key: CLOUDSTACK-3394 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3394 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 Environment: commit id # 10d9e5965a687c0c2d1d6c3e57f38602420720d6 Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Fix For: 4.2.0 Attachments: logs.tgz Steps to reproduce: 1. Have latest CloudStack setup 2. create at least 2 advanced zones (zone1, zone2) 3. add a portable ip range : 10.147.49.220-239/24 4. Have at least one non-ROOT domain user. 5. Login as the above user and create at least 1 network in each zone (Network1, Network2) 6. acquire IP (with cross zones : YES) and associate IP to Network1 7. enable staticNat on the IP acquired in Step: 6 with a VM created in zone2 Observations: (i) It failed with the following error in the mgmt server logs 2013-07-08 10:53:34,893 INFO [cloud.api.ApiServer] (catalina-exec-8:null) Unable to create ip forwarding rule, IP address Ip[10.147.49.221-1] is not in the same availability zone as virtual machine VM[User|Zone2VM1] 2013-07-08 10:53:34,896 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null) ===END=== 10.252.192.25 -- GET apiKey=MdUSVCKSP3sL6ptU2mvdqdF4QcRe5vl2gosM74JOZmIVEjzCpVKtABltph2gEC1u1TBadFcjvRaiHGVEhFddNgcommand=enableStaticNatipaddressid=42fa6947-6987-4d88-9d4d-f9c50ea9fe27networkid=2c0e7246-c41a-490b-9852-ee886381659cresponse=jsonvirtualmachineid=a3625eef-6f56-4d71-9d1d-67e9c7418206signature=RDNschQ2tihuCpAItfc1ltzzPcs%3D (ii) At the end I could see that the public ip has been transferred from one network to the other but the datacenter id is not updated. (iii) Here is the snippet from cloud.user_ip_address table. *** 22. row *** id: 22 uuid: 42fa6947-6987-4d88-9d4d-f9c50ea9fe27 account_id: 3 domain_id: 2 public_ip_address: 10.147.49.221 data_center_id: 1 source_nat: 0 allocated: 2013-07-08 14:52:49 vlan_db_id: 4 one_to_one_nat: 0 vm_id: NULL state: Allocated mac_address: 0 source_network_id: 200 network_id: 209 physical_network_id: 200 is_system: 0 vpc_id: NULL dnat_vmip: NULL is_portable: 1 22 rows in set (0.00 sec) Attaching all the required logs along with db dump. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3384) CloudStack allow VLAN range between 0-4096. Should be 0-'4095'.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701908#comment-13701908 ] ASF subversion and git services commented on CLOUDSTACK-3384: - Commit 814630c5428862aa247914e5bc04c3bcbc00c501 in branch refs/heads/master from [~toshiaki.hatano] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=814630c ] CLOUDSTACK-3384: CloudStack allow VLAN range between 0-4096. Should be 0-'4095'. CloudStack allow VLAN range between 0-4096. Should be 0-'4095'. --- Key: CLOUDSTACK-3384 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3384 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: Toshiaki Hatano Assignee: Toshiaki Hatano Priority: Minor Fix For: Future Original Estimate: 2h Remaining Estimate: 2h There're VLAN range check code in com.cloud.network.NetworkServiceImpl. But it allows VLAN range between 0-4096. VLAN ID have 12 bit field and it's between 0-4095 (0x000 - 0xFFF) . CloudStack should return error when someone try to assign VLAN ID 4096 to network. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3384) CloudStack allow VLAN range between 0-4096. Should be 0-'4095'.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701911#comment-13701911 ] ASF subversion and git services commented on CLOUDSTACK-3384: - Commit a93042674134ded31d0dea2d006fac881743ab91 in branch refs/heads/4.2 from [~toshiaki.hatano] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a930426 ] CLOUDSTACK-3384: CloudStack allow VLAN range between 0-4096. Should be 0-'4095'. CloudStack allow VLAN range between 0-4096. Should be 0-'4095'. --- Key: CLOUDSTACK-3384 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3384 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: Toshiaki Hatano Assignee: Toshiaki Hatano Priority: Minor Fix For: Future Original Estimate: 2h Remaining Estimate: 2h There're VLAN range check code in com.cloud.network.NetworkServiceImpl. But it allows VLAN range between 0-4096. VLAN ID have 12 bit field and it's between 0-4095 (0x000 - 0xFFF) . CloudStack should return error when someone try to assign VLAN ID 4096 to network. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3112) [AWSAPI] EC2 SOAP calls fail with an NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701913#comment-13701913 ] ASF subversion and git services commented on CLOUDSTACK-3112: - Commit 24e9797807a1cad684592ce47a75475752f8e2bb in branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=24e9797 ] CLOUDSTACK-3112. UserCredentials that is injected in AuthenticationHandler is not picked up [AWSAPI] EC2 SOAP calls fail with an NPE Key: CLOUDSTACK-3112 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3112 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.2.0 Enable ec2 api flag. Use EC2 API Soap tool to run ec2-describe-availability-zones. Ouput - Server:unknown 2013-06-21 14:51:59,200 DEBUG [auth.ec2.AuthenticationHandler] (catalina-exec-int-1:null) X509 cert's uniqueId: EMAILADDRESS=likithashe...@gmail.com, CN=localhost, OU=cpg, O=citrix, L=bangalore, ST=karnataka, C=in, serial=18442984792527269479 2013-06-21 14:51:59,203 ERROR [auth.ec2.AuthenticationHandler] (catalina-exec-int-1:null) EC2 Authentication Handler: java.lang.NullPointerException at com.cloud.bridge.auth.ec2.AuthenticationHandler.invoke(AuthenticationHandler.java:125) at org.apache.axis2.engine.Phase.invoke(Phase.java:318) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:254) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:114) at com.cloud.bridge.service.EC2MainServlet.doPost(EC2MainServlet.java:89) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3112) [AWSAPI] EC2 SOAP calls fail with an NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701915#comment-13701915 ] ASF subversion and git services commented on CLOUDSTACK-3112: - Commit 2a67e132e96238fc17f42430de4e86dfdcc28221 in branch refs/heads/master-6-17-stable from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2a67e13 ] CLOUDSTACK-3112. UserCredentials that is injected in AuthenticationHandler is not picked up [AWSAPI] EC2 SOAP calls fail with an NPE Key: CLOUDSTACK-3112 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3112 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.2.0 Enable ec2 api flag. Use EC2 API Soap tool to run ec2-describe-availability-zones. Ouput - Server:unknown 2013-06-21 14:51:59,200 DEBUG [auth.ec2.AuthenticationHandler] (catalina-exec-int-1:null) X509 cert's uniqueId: EMAILADDRESS=likithashe...@gmail.com, CN=localhost, OU=cpg, O=citrix, L=bangalore, ST=karnataka, C=in, serial=18442984792527269479 2013-06-21 14:51:59,203 ERROR [auth.ec2.AuthenticationHandler] (catalina-exec-int-1:null) EC2 Authentication Handler: java.lang.NullPointerException at com.cloud.bridge.auth.ec2.AuthenticationHandler.invoke(AuthenticationHandler.java:125) at org.apache.axis2.engine.Phase.invoke(Phase.java:318) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:254) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:114) at com.cloud.bridge.service.EC2MainServlet.doPost(EC2MainServlet.java:89) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3112) [AWSAPI] EC2 SOAP calls fail with an NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701914#comment-13701914 ] ASF subversion and git services commented on CLOUDSTACK-3112: - Commit 2aacc29b4902bbf7d91009ee743a9f0eefb05001 in branch refs/heads/4.2 from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2aacc29 ] CLOUDSTACK-3112. UserCredentials that is injected in AuthenticationHandler is not picked up [AWSAPI] EC2 SOAP calls fail with an NPE Key: CLOUDSTACK-3112 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3112 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: 4.2.0 Enable ec2 api flag. Use EC2 API Soap tool to run ec2-describe-availability-zones. Ouput - Server:unknown 2013-06-21 14:51:59,200 DEBUG [auth.ec2.AuthenticationHandler] (catalina-exec-int-1:null) X509 cert's uniqueId: EMAILADDRESS=likithashe...@gmail.com, CN=localhost, OU=cpg, O=citrix, L=bangalore, ST=karnataka, C=in, serial=18442984792527269479 2013-06-21 14:51:59,203 ERROR [auth.ec2.AuthenticationHandler] (catalina-exec-int-1:null) EC2 Authentication Handler: java.lang.NullPointerException at com.cloud.bridge.auth.ec2.AuthenticationHandler.invoke(AuthenticationHandler.java:125) at org.apache.axis2.engine.Phase.invoke(Phase.java:318) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:254) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:114) at com.cloud.bridge.service.EC2MainServlet.doPost(EC2MainServlet.java:89) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3214) transferring portable IP across zones with enableStatic NAT does not work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701917#comment-13701917 ] ASF subversion and git services commented on CLOUDSTACK-3214: - Commit d01afe0cd94245641a8c6619c4ddf1dc3506a49a in branch refs/heads/master-6-17-stable from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d01afe0 ] CLOUDSTACK-3214: transferring portable IP across zones with enableStatic NAT does not work making an exception for portabe IP, so that if the current datacenter with portable IP is associated is different from destiantion data center also on transfer on to new zone, transfer the portable ip association to new data center, physical network id's transferring portable IP across zones with enableStatic NAT does not work - Key: CLOUDSTACK-3214 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3214 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.2.0 on portable IP association is transfered from a netwok in a zone to another network in zone, using enableStaticNat api, it fails with exception that current network and destination VM's network are different. This needs to be relaxed for portable IP -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3395) [UI][VM_Snapshot] TypeError: json.reverttosnapshotresponse is undefined ........... when we try to revert to a VM snapshot from UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Roy updated CLOUDSTACK-3395: Attachment: revert-snapshot.jpg [UI][VM_Snapshot] TypeError: json.reverttosnapshotresponse is undefined ... when we try to revert to a VM snapshot from UI -- Key: CLOUDSTACK-3395 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3395 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Abhinav Roy Fix For: 4.2.0 Attachments: revert-snapshot.jpg Steps: === 1. Deploy CS advanced zone setup . 2. Deploy a VM 3. Goto the VM and take VM Snapshot 4. Go to that snapshot and Revert to VM Snapshot . Observation : == In the UI we get TypeError: json.reverttosnapshotresponse is undefined ... Attaching screenshot for reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3395) [UI][VM_Snapshot] TypeError: json.reverttosnapshotresponse is undefined ........... when we try to revert to a VM snapshot from UI
Abhinav Roy created CLOUDSTACK-3395: --- Summary: [UI][VM_Snapshot] TypeError: json.reverttosnapshotresponse is undefined ... when we try to revert to a VM snapshot from UI Key: CLOUDSTACK-3395 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3395 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Abhinav Roy Fix For: 4.2.0 Attachments: revert-snapshot.jpg Steps: === 1. Deploy CS advanced zone setup . 2. Deploy a VM 3. Goto the VM and take VM Snapshot 4. Go to that snapshot and Revert to VM Snapshot . Observation : == In the UI we get TypeError: json.reverttosnapshotresponse is undefined ... Attaching screenshot for reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3394) [portable IP] unable to transfer IP across zones
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-3394. -- Resolution: Fixed Fixed this as part of CLOUDSTACK-3214: transferring portable IP across zones with enableStatic NAT does not work. Cherry picked commit to master-6-17-stable with commit d01afe0cd94245641a8c6619c4ddf1dc3506a49a [portable IP] unable to transfer IP across zones Key: CLOUDSTACK-3394 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3394 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 Environment: commit id # 10d9e5965a687c0c2d1d6c3e57f38602420720d6 Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Fix For: 4.2.0 Attachments: logs.tgz Steps to reproduce: 1. Have latest CloudStack setup 2. create at least 2 advanced zones (zone1, zone2) 3. add a portable ip range : 10.147.49.220-239/24 4. Have at least one non-ROOT domain user. 5. Login as the above user and create at least 1 network in each zone (Network1, Network2) 6. acquire IP (with cross zones : YES) and associate IP to Network1 7. enable staticNat on the IP acquired in Step: 6 with a VM created in zone2 Observations: (i) It failed with the following error in the mgmt server logs 2013-07-08 10:53:34,893 INFO [cloud.api.ApiServer] (catalina-exec-8:null) Unable to create ip forwarding rule, IP address Ip[10.147.49.221-1] is not in the same availability zone as virtual machine VM[User|Zone2VM1] 2013-07-08 10:53:34,896 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null) ===END=== 10.252.192.25 -- GET apiKey=MdUSVCKSP3sL6ptU2mvdqdF4QcRe5vl2gosM74JOZmIVEjzCpVKtABltph2gEC1u1TBadFcjvRaiHGVEhFddNgcommand=enableStaticNatipaddressid=42fa6947-6987-4d88-9d4d-f9c50ea9fe27networkid=2c0e7246-c41a-490b-9852-ee886381659cresponse=jsonvirtualmachineid=a3625eef-6f56-4d71-9d1d-67e9c7418206signature=RDNschQ2tihuCpAItfc1ltzzPcs%3D (ii) At the end I could see that the public ip has been transferred from one network to the other but the datacenter id is not updated. (iii) Here is the snippet from cloud.user_ip_address table. *** 22. row *** id: 22 uuid: 42fa6947-6987-4d88-9d4d-f9c50ea9fe27 account_id: 3 domain_id: 2 public_ip_address: 10.147.49.221 data_center_id: 1 source_nat: 0 allocated: 2013-07-08 14:52:49 vlan_db_id: 4 one_to_one_nat: 0 vm_id: NULL state: Allocated mac_address: 0 source_network_id: 200 network_id: 209 physical_network_id: 200 is_system: 0 vpc_id: NULL dnat_vmip: NULL is_portable: 1 22 rows in set (0.00 sec) Attaching all the required logs along with db dump. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3263) [Multiple_IP_Ranges] IP in revoked state should be freed up after VR restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-3263: -- Assignee: Bharat Kumar [Multiple_IP_Ranges] IP in revoked state should be freed up after VR restart Key: CLOUDSTACK-3263 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3263 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 Environment: Latest build from master-6-17-stable branch Reporter: Sanjeev N Assignee: Bharat Kumar Priority: Critical Fix For: 4.2.0 Attachments: management-server.rar IP in revoked state should be freed up after VR restart Steps to Reproduce: 1.Bring up CS in basic zone with xen server 2.Exhaust all the ip addresses from the guest ip range 3.Add another ip range in the new CIDR 4.Deploy guest vm so that IP alias will be created on VR 5.Destroy guest vm and wait for it to expunge 6.Delete the IP range added at step3 and Simulate network connectivity issue while CS trying to delete ip alias from router vm (Before deleting the IP range, bring down link local interface on VR) 7.At this state ip alias created at ste4 will be in revoked state in nic_ip_alias table. 8.Bring up link local interface and reboot VR from CS Expected Behavior: === Rebooting VR from CS should perform following: 1.Delete ip alias from VR 2.Release the ip address and mark the state to NULL in user_ip_address table. 3.Remove the entry from nic_ip_alis table Actual Behavior: = Rebooting VR is only deleting the ip alias from VR and not performing the actions 2,3 mentioned in expected Behavior mysql select * from nic_ip_alias; ++--++---+-+-+---+++--+-+-++---+-+ | id | uuid | nic_id | ip4_address | ip6_address | netmask | gateway | start_ip_of_subnet | network_id | vmId | alias_count | created | account_id | domain_id | state | ++--++---+-+-+---+++--+-+-++---+-+ | 8 | 11d812b4-6cba-4747-b0a2-09c954e4419b | 20 | 10.147.43.132 | NULL | 255.255.255.192 | 10.147.43.129 | 10.147.43.129 |204 | 13 | 72 | 2013-06-28 12:08:55 | 2 | 1 | active | | 7 | db940f92-77fe-4d3b-b75e-34e38c3e3933 | 20 | 10.147.43.130 | NULL | 255.255.255.192 | 10.147.43.129 | 10.147.43.129 |204 | 13 | 70 | 2013-06-28 11:29:01 | 2 | 1 | revoked | ++--++---+-+-+---+++--+-+-++---+-+ 2 rows in set (0.00 sec) mysql select * from user_ip_address where id in(125,127); +-+--++---+---+++-+++---+---+-+---++-+---++---+-+ | id | uuid | account_id | domain_id | public_ip_address | data_center_id | source_nat | allocated | vlan_db_id | one_to_one_nat | vm_id | state | mac_address | source_network_id | network_id | physical_network_id | is_system | vpc_id | dnat_vmip | is_portable | +-+--++---+---+++-+++---+---+-+---++-+---++---+-+ | 125 | 9a331b21-b35a-41a0-883f-9db2ac73a237 | 2 | 1 | 10.147.43.130 | 1 | 0 | 2013-06-28 11:29:01 | 20 | 0 | NULL | Allocated | 70 | 204 | 204 | 200 | 0 | NULL | NULL | 0 | | 127 | 4e80e813-93fc-4f71-8e94-46d41cffbbbe | 2 | 1 | 10.147.43.132 | 1 | 0 | 2013-06-28 12:08:55 |
[jira] [Created] (CLOUDSTACK-3396) Template creation from a snapshot fails
Abhinav Roy created CLOUDSTACK-3396:
---
Summary: Template creation from a snapshot fails
Key: CLOUDSTACK-3396
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3396
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: Abhinav Roy
Fix For: 4.2.0
Steps :
===
1. Deploy CS advanced zone setup .
2. Deploy a VM
3. Goto the root volume of the VM and take Snapshot
4. Go to that snapshot and try to create a template from the snapshot.
Observed behaviour :
===
The template creation fails with
2013-07-08 16:07:07,641 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.144.6.28 -- GET
command=createTemplateresponse=jsonsessionkey=%2Bv%2F%2FZk%2FQzhRmm6AaFNp4DhBDGvE%3Dsnapshotid=16503285-b02b-444c-ba7b-0740c1da1bfename=root-3+tempdisplayText=root-3+temposTypeId=b57bdee6-e544-11e2-a640-fef34996d384isPublic=truepasswordEnabled=false_=1373279981133
2013-07-08 16:07:07,642 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-24:job-67) Executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-67
2013-07-08 16:07:07,707 DEBUG [storage.motion.AncientDataMotionStrategy]
(Job-Executor-24:job-67) copyAsync inspecting src type SNAPSHOT copyAsync
inspecting dest type TEMPLATE
2013-07-08 16:07:07,735 DEBUG [agent.transport.Request]
(Job-Executor-24:job-67) Seq 2-87163067: Sending { Cmd , MgmtId:
280320865129348, via: 2, Ver: v1, Flags: 100111,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{path:snapshots/2/3/afee4b1a-c186-4dad-828c-3dd9e774c480,volume:{uuid:a87d4c2a-dbf1-4f20-b84a-7f2faca0b3a3,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:389dcc10-de2b-334a-b028-704f70580877,id:1,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/abhinav/xen42-pri,port:2049}},name:ROOT-3,size:21474836480,path:953818b2-debe-483a-983c-d8c69dd0950e,volumeId:3,vmName:i-2-3-VM,accountId:2,format:VHD,id:3},dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.102.192.100/cpg_vol/abhinav/xen42-sec,_role:Image}},vmName:i-2-3-VM,name:v1_ROOT-3_20130708064131,hypervisorType:XenServer,id:1}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/2/207,uuid:e5a6fa62-703c-45c4-a165-be48dd578a59,id:207,format:RAW,accountId:2,hvm:true,displayText:root-3
temp,imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.102.192.100/cpg_vol/abhinav/xen42-sec,_role:Image}},name:239eac46b-4690-3f9b-95e9-c0d751a1e29a}},wait:10800}}]
}
2013-07-08 16:07:07,869 DEBUG [agent.transport.Request]
(AgentManager-Handler-8:null) Seq 2-87163067: Processing: { Ans: , MgmtId:
280320865129348, via: 2, Ver: v1, Flags: 110,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:/usr/local/cloud/systemvm/scripts/storage/secondary/create_privatetemplate_from_snapshot_xen.sh:
line 65: /bin/vhd-util: Permission denied30#failed to query
/mnt/SecStorage/ff05d1cd-034d-3032-9adc-3d7451d838fb/snapshots/2/3/afee4b1a-c186-4dad-828c-3dd9e774c480.vhd,wait:0}}]
}
2013-07-08 16:07:07,870 DEBUG [agent.manager.AgentAttache]
(AgentManager-Handler-8:null) Seq 2-87163067: No more commands found
2013-07-08 16:07:07,870 DEBUG [agent.transport.Request]
(Job-Executor-24:job-67) Seq 2-87163067: Received: { Ans: , MgmtId:
280320865129348, via: 2, Ver: v1, Flags: 110, { CopyCmdAnswer } }
2013-07-08 16:07:07,877 DEBUG [cloud.template.TemplateManagerImpl]
(Job-Executor-24:job-67) Failed to create
template/usr/local/cloud/systemvm/scripts/storage/secondary/create_privatetemplate_from_snapshot_xen.sh:
line 65: /bin/vhd-util: Permission denied30#failed to query
/mnt/SecStorage/ff05d1cd-034d-3032-9adc-3d7451d838fb/snapshots/2/3/afee4b1a-c186-4dad-828c-3dd9e774c480.vhd
2013-07-08 16:07:07,913 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-24:job-67) Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to create
template/usr/local/cloud/systemvm/scripts/storage/secondary/create_privatetemplate_from_snapshot_xen.sh:
line 65: /bin/vhd-util: Permission denied30#failed to query
/mnt/SecStorage/ff05d1cd-034d-3032-9adc-3d7451d838fb/snapshots/2/3/afee4b1a-c186-4dad-828c-3dd9e774c480.vhd
at
com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1381)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
[jira] [Created] (CLOUDSTACK-3397) When Template creation from a snapshot fails, the UI pop-up also displays the API resonse
Abhinav Roy created CLOUDSTACK-3397: --- Summary: When Template creation from a snapshot fails, the UI pop-up also displays the API resonse Key: CLOUDSTACK-3397 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3397 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Abhinav Roy Fix For: 4.2.0 Attachments: fail-template.jpg Steps : === 1. Deploy CS advanced zone setup . 2. Deploy a VM 3. Goto the root volume of the VM and take Snapshot 4. Go to that snapshot and try to create a template from the snapshot. Observed behaviour : === The template creation fails and the response displayed in the UI pop-up in same as the API response in the logs. Attaching screenshot for reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3397) When Template creation from a snapshot fails, the UI pop-up also displays the API resonse
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Roy updated CLOUDSTACK-3397: Attachment: fail-template.jpg When Template creation from a snapshot fails, the UI pop-up also displays the API resonse -- Key: CLOUDSTACK-3397 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3397 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Abhinav Roy Fix For: 4.2.0 Attachments: fail-template.jpg Steps : === 1. Deploy CS advanced zone setup . 2. Deploy a VM 3. Goto the root volume of the VM and take Snapshot 4. Go to that snapshot and try to create a template from the snapshot. Observed behaviour : === The template creation fails and the response displayed in the UI pop-up in same as the API response in the logs. Attaching screenshot for reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2884) Test case test_service_offerings.py:test_04_change_offering_small failing automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam resolved CLOUDSTACK-2884. Resolution: Fixed Test case test_service_offerings.py:test_04_change_offering_small failing automation runs Key: CLOUDSTACK-2884 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2884 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Environment: Master - Automation run Reporter: Rayees Namathponnan Assignee: Girish Shilamkar Fix For: 4.2.0 Test case cloudstack/test/integration/smoke/test_service_offerings.py, line 437, in test_04_change_offering_small failing with below error File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /Repo_30X/ipcl/cloudstack/test/integration/smoke/test_service_offerings.py, line 437, in test_04_change_offering_small Check Memory(kb) for small offering File /usr/local/lib/python2.7/unittest/case.py, line 535, in assertAlmostEqual if round(abs(second-first), places) == 0: 'str' object cannot be interpreted as an index -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-3393: Description: If a stopped VM using local storage (already created) is started and for some reasons it fails to start on the last host, the deployment planner picks up another host. In this scenario a new disk is created on the local storage pool associated with the new host and the old disk gets destroyed. This will result in data loss. (was: This will result in data loss as a new local volume is created and the old one will be cleaned up.) Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.2.0 If a stopped VM using local storage (already created) is started and for some reasons it fails to start on the last host, the deployment planner picks up another host. In this scenario a new disk is created on the local storage pool associated with the new host and the old disk gets destroyed. This will result in data loss. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2806) Documentation for ACL on Private Gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701945#comment-13701945 ] ASF subversion and git services commented on CLOUDSTACK-2806: - Commit 03c8f74e982f0e90b05a23088b3f03630fc19b2b in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=03c8f74 ] CLOUDSTACK-2806 Documentation for ACL on Private Gateway Key: CLOUDSTACK-2806 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2806 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 CLOUDSTACK-768 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701946#comment-13701946 ] Koushik Das commented on CLOUDSTACK-3393: - The fix is to prevent recreation of disk. Another option is to migrate the existing disk to the new local storage pool once migration of local disk is supported. Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.2.0 If a stopped VM using local storage (already created) is started and for some reasons it fails to start on the last host, the deployment planner picks up another host. In this scenario a new disk is created on the local storage pool associated with the new host and the old disk gets destroyed. This will result in data loss. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701952#comment-13701952 ] ASF subversion and git services commented on CLOUDSTACK-3393: - Commit 33ed0769691691978999f618cca6a628977db029 in branch refs/heads/master from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=33ed076 ] CLOUDSTACK-3393: Local disk recreated for stopped VM when started Recreating local disk will result in cleanup of the old disk and this will lead to data loss. So preventing this and bailing out with error. Once migration of local disk is supported then another option is to migrate the existing disk to the new local storage pool. Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.2.0 If a stopped VM using local storage (already created) is started and for some reasons it fails to start on the last host, the deployment planner picks up another host. In this scenario a new disk is created on the local storage pool associated with the new host and the old disk gets destroyed. This will result in data loss. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2442) VR:F5:deployVM failed due to multiple generic soure NAT IPs provided for network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701954#comment-13701954 ] sadhu suresh commented on CLOUDSTACK-2442: -- still this issue exits in the latest build: DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-11:job-53) release cpu from host: 4, old used: 2500,reserved: 500, actual total: 9576, total with overprovisioning: 9576; new used: 2000,reserved:500; movedfromreserved: false,moveToReserveredfalse 2013-07-08 13:01:49,539 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-11:job-53) release mem from host: 4, old used: 2550136832,reserved: 134217728, total: 16190156800; new used: 2013265920,reserved:134217728; movedfromreserved: false,moveToReserveredfalse 2013-07-08 13:01:49,569 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-11:job-53) Destroying vm VM[User|vm11] as it failed to create on Host with Id:null 2013-07-08 13:01:49,584 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-11:job-53) VM state transitted from :Stopped to Error with event: OperationFailedToErrorvm's original host id: null new host id: null host id before state transition: null 2013-07-08 13:01:49,601 WARN [apache.cloudstack.alerts] (Job-Executor-11:job-53) alertType:: 8 // dataCenterId:: 2 // podId:: 2 // clusterId:: null // message:: Failed to deploy Vm with Id: 80, on Host with Id: null 2013-07-08 13:01:49,646 WARN [user.vm.DeployVMCmd] (Job-Executor-11:job-53) Exception: com.cloud.exception.AgentUnavailableException: Resource [Host:4] is unreachable: Host 4: Unable to start instance due to Multiple generic soure NAT IPs provided for network at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:943) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:554) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3335) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2873) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2859) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: com.cloud.utils.exception.CloudRuntimeException: Multiple generic soure NAT IPs provided for network at com.cloud.network.NetworkModelImpl.getIpToServices(NetworkModelImpl.java:286) at com.cloud.network.NetworkManagerImpl.applyIpAssociations(NetworkManagerImpl.java:669) at com.cloud.network.NetworkManagerImpl.applyIpAssociations(NetworkManagerImpl.java:639) at com.cloud.network.NetworkManagerImpl.reprogramNetworkRules(NetworkManagerImpl.java:3085) at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:1960) at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1855) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2034) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:847) ... 20 more 2013-07-08 13:01:49,648 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-11:job-53) C VR:F5:deployVM failed due to multiple generic soure NAT IPs provided for network - Key: CLOUDSTACK-2442 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2442 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects
[jira] [Commented] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701955#comment-13701955 ] ASF subversion and git services commented on CLOUDSTACK-3393: - Commit 916a009d5d300d5621970a2ca29bd23e5d29fec3 in branch refs/heads/4.2 from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=916a009 ] CLOUDSTACK-3393: Local disk recreated for stopped VM when started Recreating local disk will result in cleanup of the old disk and this will lead to data loss. So preventing this and bailing out with error. Once migration of local disk is supported then another option is to migrate the existing disk to the new local storage pool. Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.2.0 If a stopped VM using local storage (already created) is started and for some reasons it fails to start on the last host, the deployment planner picks up another host. In this scenario a new disk is created on the local storage pool associated with the new host and the old disk gets destroyed. This will result in data loss. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3393) Local disk recreated for stopped VM when started
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-3393. - Resolution: Fixed Local disk recreated for stopped VM when started Key: CLOUDSTACK-3393 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.2.0 If a stopped VM using local storage (already created) is started and for some reasons it fails to start on the last host, the deployment planner picks up another host. In this scenario a new disk is created on the local storage pool associated with the new host and the old disk gets destroyed. This will result in data loss. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1758) [Automation] SSVM test cases failing in VMware with 4.1 builds
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-1758: - Summary: [Automation] SSVM test cases failing in VMware with 4.1 builds (was: SSVM test cases failing in VMware with 4.1 builds) [Automation] SSVM test cases failing in VMware with 4.1 builds --- Key: CLOUDSTACK-1758 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1758 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.1.0, 4.2.0 Environment: vm ware Reporter: Rayees Namathponnan Assignee: Girish Shilamkar Priority: Blocker Fix For: 4.2.0 SVM test cases failing in VM ware, Traceback (most recent call last): File /data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py, line 804, in test_08_reboot_cpvm self.test_04_cpvm_internals() File /data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py, line 481, in test_04_cpvm_internals Check cloud service is running or not AssertionError: Check cloud service is running or not I checked the ssvm, i can see cloud server is running Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. root@s-3-VM:~# service cloud status cloud.com service (type=secstorage) is running: process id: 2751 root@s-3-VM:~# service cloud status cloud.com service (type=secstorage) is running: process id: 2751 root@s-3-VM:~# followed below steps cp /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud /tmp chmod 600 /tmp/id_rsa.cloud ssh -i /tmp/id_rsa.cloud -p 3922 root@10.223.250.122 (private ip) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3398) [UI] Enhance traffic label configuration in UI to specify switch name, vlan id and switch type with VMWARE hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3398: - Fix Version/s: 4.2.0 [UI] Enhance traffic label configuration in UI to specify switch name, vlan id and switch type with VMWARE hypervisor - Key: CLOUDSTACK-3398 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3398 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sailaja Mada Fix For: 4.2.0 Setup: VMWARE Observation: Usecase : Two physical networks a) Management , Storage traffic with Standard Switch with Physical network 1 b) Public , Guest traffic with DVSwitch - Physical network 2 c) Currently it is text field where Admin has to manually provide the pattern as switch name, vlan id and switch type Ex: dvs3,,vmwaredvs ( If there is no VLAN Id ) This defect is to Enhance traffic label configuration in UI to specify switch name, vlan id and switch type with VMWARE hypervisor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3398) [UI] Enhance traffic label configuration in UI to specify switch name, vlan id and switch type with VMWARE hypervisor
Sailaja Mada created CLOUDSTACK-3398: Summary: [UI] Enhance traffic label configuration in UI to specify switch name, vlan id and switch type with VMWARE hypervisor Key: CLOUDSTACK-3398 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3398 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sailaja Mada Setup: VMWARE Observation: Usecase : Two physical networks a) Management , Storage traffic with Standard Switch with Physical network 1 b) Public , Guest traffic with DVSwitch - Physical network 2 c) Currently it is text field where Admin has to manually provide the pattern as switch name, vlan id and switch type Ex: dvs3,,vmwaredvs ( If there is no VLAN Id ) This defect is to Enhance traffic label configuration in UI to specify switch name, vlan id and switch type with VMWARE hypervisor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3094) [Add network]Adding a shared network to already deployed VM is failing.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saksham Srivastava updated CLOUDSTACK-3094:
---
Status: Ready To Review (was: In Progress)
[Add network]Adding a shared network to already deployed VM is failing.
---
Key: CLOUDSTACK-3094
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3094
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: manasaveloori
Assignee: Saksham Srivastava
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.zip, management-server.zip,
mysqldump1.dmp, mysqldump1.dmp
Steps:
1.Have a CS with advanced zone.
2.Create a VPC and a tier network.
3.Create a VM using the tier network.
4.Create a shared network.
5.Go to the VPC VM -NICs-Add network. Select the shared network from
the dropdown and add the network.
Observation:
Adding the shared network is failing with unexpected exception.
013-06-20 22:37:18,984 DEBUG [network.guru.DirectNetworkGuru]
(Job-Executor-16:job-184) remove nic 80 secondary ip
2013-06-20 22:37:19,000 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-16:job-184) Removed nic id=80
2013-06-20 22:37:19,002 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-16:job-184) Revoving nic secondary ip entry ...
2013-06-20 22:37:19,003 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-16:job-184) Unexpected exception while executing
org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to add NIC to
VM[User|979cbfa9-5e02-4f35-8ac9-fe8c25dac2ae]
at
com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:916)
at
org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:109)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-20 22:37:19,004 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-16:job-184) Complete async job-184, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: Unable to add NIC to
VM[User|979cbfa9-5e02-4f35-8ac9-fe8c25dac2ae]
2013-06-20 22:37:20,113 INFO [vmware.resource.VmwareResource]
(DirectAgent-125:10.147.40.29) vm_data command on domain router 10.147.40.181
completed
2013-06-20 22:37:20,115 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-125:null) Seq 1-563282274: Response Received:
2013-06-20 22:37:20,116 DEBUG [agent.transport.Request]
(DirectAgent-125:null) Seq 1-563282274: Processing: { Ans: , MgmtId:
6805241462820, via: 1, Ver: v1, Flags: 110,
[{Answer:{result:true,wait:0}}] }
UI is listing all the nics even though adding a nic is failing.(Ifconfig –a
in the VM not showing the added shared network)
We are able to add multiple shared networks while deploying the VM(instance
creation), but same is not happening through “ Add network option”
Attaching the MS logs and DB logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3382) Unable to Migrate VM's If the hosts are implicitly or explicitly dedicated.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702035#comment-13702035 ] Saksham Srivastava commented on CLOUDSTACK-3382: The FS is updated. Current behavior is as follows: 1) If VM to be migrated is non-dedicated: if destination host is implicitly or explicitly dedicated, fail migration. if destination host is non-dedicated, migrate it to the destination host. 2) If VM to be migrated is dedicated if destination host is implicitly or explicitly dedicated to the same account, migrate it to that host. if destination host is implicitly or explicitly dedicated to different account, fail migration. if destination host is non-dedicated, fail migration. Unable to Migrate VM's If the hosts are implicitly or explicitly dedicated. --- Key: CLOUDSTACK-3382 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3382 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Saksham Srivastava Priority: Blocker Fix For: 4.2.0 The details of the defect are as follows: 1)I have created a Advanced Zone setup with two hosts. 2)Then created a VM using the Strict Implicit for one account and created another VM with different account without using any dedication. 3)two VM's are created on two hosts available and one is implicitly dedicated host and other one is a shared host. 4)then tried to migrate the VM from one account to another and clicked on the UI option available. Observed that the there is a popup saying no suitable host found. But according to the FS of the Dedicated resources Zone/pod/cluster/host it says as below: Migration of VMs 1.If VM to be migrated is non-dedicated: a.if destination host is implicitly or explicitly dedicated, migrate it to that host, but an alert is generated b.if destination host is non-dedicated, migrate it to the destination host. 2.If VM to be migrated is dedicated a.if destination host is implicitly or explicitly dedicated to the same account, migrate it to that host. b.if destination host is implicitly or explicitly dedicated to different account, migrate it to that host, but an alert is generated c.if destination host is non-dedicated, migrate it to that host but an alert is generated -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3304) [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi updated CLOUDSTACK-3304: - Summary: [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS (was: Vmware - if a VM is initially assigned a RAM of less than 3gb then it cannot be dynamically scaled beyond 3gb. Enforce this check in CS) [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS Key: CLOUDSTACK-3304 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3304 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3304) [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702069#comment-13702069 ] ASF subversion and git services commented on CLOUDSTACK-3304: - Commit 12b39cfd2a6d4fd23a8e2782d46cb54447ba60b5 in branch refs/heads/master-6-17-stable from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=12b39cf ] CLOUDSTACK-3304 [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS Retrieve maximum hotadd memory limit hotadd memory increment size from running VM's configuration to validate dynamic scale memory limit while scaling up a VM. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS Key: CLOUDSTACK-3304 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3304 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3304) [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702078#comment-13702078 ] ASF subversion and git services commented on CLOUDSTACK-3304: - Commit 91d31b29b8157f8934a38bc14b61519937986121 in branch refs/heads/master from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=91d31b2 ] CLOUDSTACK-3304 [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS Retrieve maximum hotadd memory limit hotadd memory increment size from running VM's configuration to validate dynamic scale memory limit while scaling up a VM. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS Key: CLOUDSTACK-3304 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3304 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3304) [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702079#comment-13702079 ] ASF subversion and git services commented on CLOUDSTACK-3304: - Commit 8cab35aa416c9579f449e28cab6247eab13a23f7 in branch refs/heads/4.2 from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8cab35a ] CLOUDSTACK-3304 [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS Retrieve maximum hotadd memory limit hotadd memory increment size from running VM's configuration to validate dynamic scale memory limit while scaling up a VM. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS Key: CLOUDSTACK-3304 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3304 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3304) [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi resolved CLOUDSTACK-3304. -- Resolution: Fixed [Vmware][Dynamic Scaling] - Enforce checks for maximum hotadd memory limit memory increment size in CS Key: CLOUDSTACK-3304 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3304 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-1808) Unexpected behavious when creating template from volume in prject
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-1808. --- Resolution: Duplicate Then its a duplicate of https://issues.apache.org/jira/browse/CLOUDSTACK-3306 Unexpected behavious when creating template from volume in prject - Key: CLOUDSTACK-1808 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1808 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Reporter: Frank Breedijk Assignee: Alena Prokharchyk I have a machine in a project. I then stop the machine, get the volumeId in project context. I then create a template not in project context. Unexpected behaviour, the template is linked to the project, even if the create template was not created in project context. When I make the template public, it is not visible to other cloudstack users outside the project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3028) Object_Store_Refactor - S3 reduced redundancy storage should be an option.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702094#comment-13702094 ] John Burwell commented on CLOUDSTACK-3028: -- Why is reduced redundancy a global setting rather than a setting on the S3 resource? Object_Store_Refactor - S3 reduced redundancy storage should be an option. -- Key: CLOUDSTACK-3028 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3028 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Environment: latest object_store branch on fedora 17 devcloud on same machine Cloudian (for S3 services) on separate machine. (expect similar result with other S3 object stores). Reporter: Thomas O'Dowd Assignee: Min Chen Fix For: 4.2.0 When uploading a template to the S3 object store, I noticed that the request asked to be stored using reduced redundancy. I think this should be an option rather than the default behavior. Steps: 1. setup S3 object storage (can be amazon) 2. Add S3 as secondary storage 3. Upload a new template (I uploaded tinyLinux.vhd.gz by giving a url on my local network where I had it hosted) If you sniff the S3 traffic (assuming you don't use ssl) when you upload the template in step 3, you can see something like this request. === initiate multipart upload request POST /template%2Ftmpl%2F2%2F201%2F201-2-f9a12429-7cf4-3df5-b81c-420f09c1bbcd%2FtinyLinux.vhd.gz?uploads HTTP/1.1. Host: hello.s3.cloudian.com:18080. Authorization: AWS 00d25034c817eeb8c095:5P8Y2VM69TgAbixlZoXhAsNjAzI=. x-amz-storage-class: REDUCED_REDUNDANCY. Date: Fri, 14 Jun 2013 07:05:26 GMT. User-Agent: aws-sdk-java/1.3.21.1 Linux/2.6.32-5-686-bigmem Java_HotSpot(TM)_Client_VM/20.1-b02. Content-Type: application/x-www-form-urlencoded; charset=utf-8. Transfer-Encoding: chunked. Connection: Keep-Alive. . 0. . === initiate multipart upload request Notice that the x-amz-storage-class is set to REDUCED_REDUNDANCY. I cannot see any GUI option to overload this and choose the default storage class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3375) The command listConfigurations with parameter accountid results in error for user/domain-admin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-3375. --- Resolution: Duplicate The command listConfigurations with parameter accountid results in error for user/domain-admin -- Key: CLOUDSTACK-3375 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3375 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Environment: Master Reporter: Isaac Chiang Labels: api Attachments: Screenshot20130705.png Reproduce step: 1. Login with exist user account 2. Navigate to Accounts section and select an account 3. click on Settings tab -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3153) [UI] Network ACL : Incorrect API calls when changing the rule number
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-3153: - Assignee: Brian Federle [UI] Network ACL : Incorrect API calls when changing the rule number Key: CLOUDSTACK-3153 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3153 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Kishan Kavala Assignee: Brian Federle Priority: Critical After creating Network ACL rules, UI for changing the number is not correct. UI should just update the number of rule that is moved. It should be a single updateNetworkACL API call. UI currently fires 2 APIs and both of them fail. UI should not try to swap the numbers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3153) [UI] Network ACL : Incorrect API calls when changing the rule number
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702186#comment-13702186 ] ASF subversion and git services commented on CLOUDSTACK-3153: - Commit c94cb0fc41591a29d178877f34c9139485b67c38 in branch refs/heads/master from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c94cb0f ] CLOUDSTACK-3153: On reorder, only update target ACL item's number [UI] Network ACL : Incorrect API calls when changing the rule number Key: CLOUDSTACK-3153 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3153 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Kishan Kavala Assignee: Brian Federle Priority: Critical After creating Network ACL rules, UI for changing the number is not correct. UI should just update the number of rule that is moved. It should be a single updateNetworkACL API call. UI currently fires 2 APIs and both of them fail. UI should not try to swap the numbers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3153) [UI] Network ACL : Incorrect API calls when changing the rule number
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702188#comment-13702188 ] ASF subversion and git services commented on CLOUDSTACK-3153: - Commit ecd0a1c2425d02e8ba66f9403bf4178ef71c02ea in branch refs/heads/master-6-17-stable from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ecd0a1c ] CLOUDSTACK-3153: On reorder, only update target ACL item's number [UI] Network ACL : Incorrect API calls when changing the rule number Key: CLOUDSTACK-3153 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3153 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Kishan Kavala Assignee: Brian Federle Priority: Critical After creating Network ACL rules, UI for changing the number is not correct. UI should just update the number of rule that is moved. It should be a single updateNetworkACL API call. UI currently fires 2 APIs and both of them fail. UI should not try to swap the numbers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3356) listNetworks API doesn't list the default guest network in case of project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk reassigned CLOUDSTACK-3356:
-
Assignee: Alena Prokharchyk
listNetworks API doesn't list the default guest network in case of project
-
Key: CLOUDSTACK-3356
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3356
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Projects
Affects Versions: 4.2.0
Reporter: shweta agarwal
Assignee: Alena Prokharchyk
Priority: Critical
Fix For: 4.2.0
Repro steps:
1. Have EIP/ELB enabled zone setup
2. Create at least one Project with owner set to any non-ROOT domain account.
3. Login as the above created non-ROOT domain admin account ( whether belongs
to project or not).
4. Try listNetworks with projectid
Observations:
(i) From UI It didn't list any networks
API :
http://10.147.38.141:8080/client/api?command=listNetworksresponse=jsonsessionkey=zoEGBQ8DqrevjfOToRuyBqGzIOA%3Dprojectid=a548b266-18e5-4f36-a3bc-d55c93c3e289listAll=truepage=1pagesize=20_=1372930379531
response:
{ listnetworksresponse : { } }
While when i executed the same API via cloudmonkey , network is listed
API log shows:
2013-07-04 15:11:38,559 INFO [cloud.api.ApiServer] (catalina-exec-15:null)
(userId=6 accountId=7 sessionId=null) 10.147.59.212 -- GET
apiKey=1XeMKeSvcmMN2Isi7COJ1FY2J5g2PR3Gtqy8DH4Ogl4EFf4Y-2DHfiqjxZHHl1z1jX_LCUhbJheeoAlrFKBUzQcommand=listNetworksresponse=jsonsignature=U6JER6eJpY5kqeskbcBYhDl%2Fptc%3D
200 { listnetworksresponse : { count:1 ,network : [
{id:bd683308-2809-42f0-816b-7edbb0ab3eb6,name:defaultGuestNetwork,displaytext:defaultGuestNetwork,broadcastdomaintype:Native,traffictype:Guest,zoneid:bfdf7ac5-16c3-491e-aabd-f7ad696612b8,zonename:BasicwithEIPnELB,networkofferingid:f18269b3-8793-4960-a05c-779ed56752a8,networkofferingname:DefaultSharedNetscalerEIPandELBNetworkOffering,networkofferingdisplaytext:Offering
for Shared networks with Elastic IP and Elastic LB
capabilities,networkofferingavailability:Optional,issystem:false,state:Setup,related:bd683308-2809-42f0-816b-7edbb0ab3eb6,dns1:10.103.128.16,type:Shared,acltype:Domain,subdomainaccess:true,domainid:97e3cec8-e474-11e2-95e7-0682fe17,domain:ROOT,service:[{name:Dhcp},{name:StaticNat,capability:[{name:ElasticIp,value:true,canchooseservicecapability:false}]},{name:SecurityGroup},{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:UserData},{name:Lb,capability:[{name:SupportedLBIsolation,value:dedicated,
shared,canchooseservicecapability:false},{name:SupportedLbAlgorithms,value:roundrobin,leastconn,canchooseservicecapability:false},{name:SupportedStickinessMethods,value:[{\methodname\:\LbCookie\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is cookie based sticky method, can be used only
for
http\},{\methodname\:\AppCookie\,\paramlist\:[{\paramname\:\name\,\required\:true,\isflag\:false,\description\:\
\}],\description\:\This is app session based sticky method, can be used
only for
http\},{\methodname\:\SourceBased\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is source based sticky method, can be used for
any type of
protocol.\}],canchooseservicecapability:false},{name:SupportedProtocols,value:tcp,udp,canchooseservicecapability:false},{name:AutoScaleCounters,value:[{\methodname\:\snmp\,\paramlist\:[{\paramname\:\snmpcommunity\,\required\:true,\isflag\:false,\description\:\the
community string that has to be used to do a SNMP GET on the AutoScaled
Vm\},{\paramname\:\snmpport\,\required\:false,\isflag\:false,\description\:\the
port at which SNMP agent is running on the AutoScaled
Vm\}]},{\methodname\:\netscaler\,\paramlist\:[]}],canchooseservicecapability:false},{name:LbSchemes,value:Public,canchooseservicecapability:false},{name:TrafficStatistics,value:per
public
ip,canchooseservicecapability:false},{name:ElasticLb,value:true,canchooseservicecapability:false},{name:HealthCheckPolicy,value:true,canchooseservicecapability:false},{name:LoadBalancingSupportedIps,value:additional,canchooseservicecapability:false}]}],networkdomain:cs1cloud.internal,physicalnetworkid:a4474756-59bb-4546-b43f-a411cbdf2761,restartrequired:false,specifyipranges:true,canusefordeploy:true,ispersistent:false,tags:[],displaynetwork:true}
] } }
@
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please
[jira] [Commented] (CLOUDSTACK-3153) [UI] Network ACL : Incorrect API calls when changing the rule number
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702206#comment-13702206 ] ASF subversion and git services commented on CLOUDSTACK-3153: - Commit 4cd5dfe2ae784e7634b2c8ec749085ead3c5385d in branch refs/heads/4.2 from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4cd5dfe ] CLOUDSTACK-3153: On reorder, only update target ACL item's number [UI] Network ACL : Incorrect API calls when changing the rule number Key: CLOUDSTACK-3153 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3153 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Kishan Kavala Assignee: Brian Federle Priority: Critical After creating Network ACL rules, UI for changing the number is not correct. UI should just update the number of rule that is moved. It should be a single updateNetworkACL API call. UI currently fires 2 APIs and both of them fail. UI should not try to swap the numbers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3153) [UI] Network ACL : Incorrect API calls when changing the rule number
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-3153: - Assignee: Kishan Kavala (was: Brian Federle) Kishan, though I am now using 1 api call to update the target ACL rule, I'm still getting an error due to overlapping rule numbers: 'ACL item with number 1 already exists in ACL: 43c58857-85b8-4985-987c-2cf587018bea' Since we only want 1 API call per reorder, I'm not sure if I can fix this issue in the UI, since I would need to do an update call for *every* row that is conflicting. Ideally, the backend should handle conflicting row numbers and automatically re-number those rows. [UI] Network ACL : Incorrect API calls when changing the rule number Key: CLOUDSTACK-3153 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3153 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Kishan Kavala Assignee: Kishan Kavala Priority: Critical After creating Network ACL rules, UI for changing the number is not correct. UI should just update the number of rule that is moved. It should be a single updateNetworkACL API call. UI currently fires 2 APIs and both of them fail. UI should not try to swap the numbers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-494) Allow multiple accounts to use the same site-to-site VPN endpoint
[ https://issues.apache.org/jira/browse/CLOUDSTACK-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Noland updated CLOUDSTACK-494: Issue Type: Bug (was: Improvement) Allow multiple accounts to use the same site-to-site VPN endpoint - Key: CLOUDSTACK-494 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-494 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: pre-4.0.0 Reporter: David Noland For example, if an account creates a site-to-site (IPSec) VPN connection to an external endpoint, another account cannot create a site-to-site VPN connection to that same endpoint. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-494) Allow multiple accounts to use the same site-to-site VPN endpoint
[ https://issues.apache.org/jira/browse/CLOUDSTACK-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702214#comment-13702214 ] David Noland commented on CLOUDSTACK-494: - Sheng Yang believe this to be a bug. Allow multiple accounts to use the same site-to-site VPN endpoint - Key: CLOUDSTACK-494 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-494 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: pre-4.0.0 Reporter: David Noland For example, if an account creates a site-to-site (IPSec) VPN connection to an external endpoint, another account cannot create a site-to-site VPN connection to that same endpoint. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2571) [Zone-Wide-PrimaryStorage] NPE while deleting the zone-wide primary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702225#comment-13702225
]
ASF subversion and git services commented on CLOUDSTACK-2571:
-
Commit 7054db44700ba813d513bf8e16b0266d308a8dc6 in branch
refs/heads/master-6-17-stable from [~rajesh_battala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7054db4 ]
CLOUDSTACK-2571 Zone Wide Primary Storage blocker issues while Enabling in
Maintenance State
Conflicts:
engine/api/src/org/apache/cloudstack/storage/datastore/db/PrimaryDataStoreDao.java
engine/api/src/org/apache/cloudstack/storage/datastore/db/PrimaryDataStoreDaoImpl.java
server/src/com/cloud/storage/StorageManagerImpl.java
server/src/com/cloud/storage/StoragePoolAutomationImpl.java
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
CLOUDSTACK-2571
Fixing white spaces.
[Zone-Wide-PrimaryStorage] NPE while deleting the zone-wide primary storage
---
Key: CLOUDSTACK-2571
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2571
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Environment: commit # 85d54cd1c088997dd08f0328984bee1a55703636
Reporter: venkata swamybabu budumuru
Assignee: Rajesh Battala
Labels: automation, integration-test
Fix For: 4.2.0
Attachments: logs.tgz
Steps to reproduce :
1. Have a CloudStack with at least one advanced zone
2. Add a zone-wide primary storage.
3. Try to put the above primary storage into maintenance
Observations:
(i) It throws an NPE while trying to enable the maintenance.
Here is the exception snippet from mgmt server log.
013-05-20 06:14:26,338 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===START=== 10.252.240.57 -- GET
command=createStoragePoolscope=zonezoneid=8adda1e5-ac1c-49b0-bec8-6da98f6ff116name=primaryNewurl=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fswamy%2Fprimary.campo.xen.1response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025128021
2013-05-20 06:14:26,411 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===END=== 10.252.240.57 -- GET
command=createStoragePoolscope=zonezoneid=8adda1e5-ac1c-49b0-bec8-6da98f6ff116name=primaryNewurl=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fswamy%2Fprimary.campo.xen.1response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025128021
2013-05-20 06:14:32,555 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2013-05-20 06:14:32,558 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-05-20 06:14:32,664 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2013-05-20 06:14:32,667 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-05-20 06:14:38,857 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===START=== 10.252.240.57 -- GET
command=listZonesresponse=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3Did=8adda1e5-ac1c-49b0-bec8-6da98f6ff116_=1369025140804
2013-05-20 06:14:38,875 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===END=== 10.252.240.57 -- GET
command=listZonesresponse=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3Did=8adda1e5-ac1c-49b0-bec8-6da98f6ff116_=1369025140804
2013-05-20 06:14:39,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===START=== 10.252.240.57 -- GET
command=listStoragePoolsid=a1a1a150-6709-3d81-a414-4cee93e62168response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025140864
2013-05-20 06:14:39,056 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===END=== 10.252.240.57 -- GET
command=listStoragePoolsid=a1a1a150-6709-3d81-a414-4cee93e62168response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025140864
2013-05-20 06:14:41,077 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===START=== 10.252.240.57 -- GET
command=enableStorageMaintenanceid=a1a1a150-6709-3d81-a414-4cee93e62168response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025142915
2013-05-20 06:14:41,109 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-16:null) submit async job-11, details: AsyncJobVO {id:11,
userId: 2, accountId: 2, sessionKey: null, instanceType: StoragePool,
instanceId: 2, cmd:
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd,
cmdOriginator: null, cmdInfo:
[jira] [Commented] (CLOUDSTACK-2571) [Zone-Wide-PrimaryStorage] NPE while deleting the zone-wide primary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702224#comment-13702224
]
ASF subversion and git services commented on CLOUDSTACK-2571:
-
Commit 7054db44700ba813d513bf8e16b0266d308a8dc6 in branch
refs/heads/master-6-17-stable from [~rajesh_battala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7054db4 ]
CLOUDSTACK-2571 Zone Wide Primary Storage blocker issues while Enabling in
Maintenance State
Conflicts:
engine/api/src/org/apache/cloudstack/storage/datastore/db/PrimaryDataStoreDao.java
engine/api/src/org/apache/cloudstack/storage/datastore/db/PrimaryDataStoreDaoImpl.java
server/src/com/cloud/storage/StorageManagerImpl.java
server/src/com/cloud/storage/StoragePoolAutomationImpl.java
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
CLOUDSTACK-2571
Fixing white spaces.
[Zone-Wide-PrimaryStorage] NPE while deleting the zone-wide primary storage
---
Key: CLOUDSTACK-2571
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2571
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Environment: commit # 85d54cd1c088997dd08f0328984bee1a55703636
Reporter: venkata swamybabu budumuru
Assignee: Rajesh Battala
Labels: automation, integration-test
Fix For: 4.2.0
Attachments: logs.tgz
Steps to reproduce :
1. Have a CloudStack with at least one advanced zone
2. Add a zone-wide primary storage.
3. Try to put the above primary storage into maintenance
Observations:
(i) It throws an NPE while trying to enable the maintenance.
Here is the exception snippet from mgmt server log.
013-05-20 06:14:26,338 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===START=== 10.252.240.57 -- GET
command=createStoragePoolscope=zonezoneid=8adda1e5-ac1c-49b0-bec8-6da98f6ff116name=primaryNewurl=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fswamy%2Fprimary.campo.xen.1response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025128021
2013-05-20 06:14:26,411 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===END=== 10.252.240.57 -- GET
command=createStoragePoolscope=zonezoneid=8adda1e5-ac1c-49b0-bec8-6da98f6ff116name=primaryNewurl=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fswamy%2Fprimary.campo.xen.1response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025128021
2013-05-20 06:14:32,555 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2013-05-20 06:14:32,558 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-05-20 06:14:32,664 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2013-05-20 06:14:32,667 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-05-20 06:14:38,857 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===START=== 10.252.240.57 -- GET
command=listZonesresponse=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3Did=8adda1e5-ac1c-49b0-bec8-6da98f6ff116_=1369025140804
2013-05-20 06:14:38,875 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===END=== 10.252.240.57 -- GET
command=listZonesresponse=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3Did=8adda1e5-ac1c-49b0-bec8-6da98f6ff116_=1369025140804
2013-05-20 06:14:39,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===START=== 10.252.240.57 -- GET
command=listStoragePoolsid=a1a1a150-6709-3d81-a414-4cee93e62168response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025140864
2013-05-20 06:14:39,056 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===END=== 10.252.240.57 -- GET
command=listStoragePoolsid=a1a1a150-6709-3d81-a414-4cee93e62168response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025140864
2013-05-20 06:14:41,077 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===START=== 10.252.240.57 -- GET
command=enableStorageMaintenanceid=a1a1a150-6709-3d81-a414-4cee93e62168response=jsonsessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D_=1369025142915
2013-05-20 06:14:41,109 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-16:null) submit async job-11, details: AsyncJobVO {id:11,
userId: 2, accountId: 2, sessionKey: null, instanceType: StoragePool,
instanceId: 2, cmd:
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd,
cmdOriginator: null, cmdInfo:
[jira] [Commented] (CLOUDSTACK-3329) [Automation] Failed to deploy VM with NullPointer Exception” , and observed LibvirtException: name in virStorageVolLookupByName must not be NULL in agent log
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702229#comment-13702229
]
ASF subversion and git services commented on CLOUDSTACK-3329:
-
Commit e3e16ba0fab68a102deaec32be097868eb53209a in branch
refs/heads/master-6-17-stable from [~edison]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e3e16ba ]
CLOUDSTACK-3329: it's the same bug that storage pool is randomly missing
[Automation] Failed to deploy VM with NullPointer Exception” , and observed
LibvirtException: name in virStorageVolLookupByName must not be NULL in agent
log
-
Key: CLOUDSTACK-3329
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3329
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Volumes
Affects Versions: 4.2.0
Environment: KVM
master-6-17-stable
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
Fix For: 4.2.0
Attachments: CLOUDSTACK-3329.rar
This issue observed during automation run in KVM
Here taking Job : 151 for reference
1) VR created successfully
2013-07-02 04:54:18,306 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-4:job-151) Start completed for VM VM[DomainRouter|r-37-QA]
2013-07-02 04:54:18,308 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-4:job-151) Reprogramming network Ntwk[222|Guest|8] as a part of
network implement
2013-07-02 04:54:18,317 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-4:job-151)
Applying ip association in network Ntwk[222|Guest|8]
2) Create volume completed successfully
2013-07-02 04:55:48,634 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-4:job-151) Checking if we need to prepare 1 volumes for
VM[User|2c6aada6-d82e-4edc-bed1-01f21726e43f]
2013-07-02 04:55:48,639 DEBUG [storage.image.ImageDataFactoryImpl]
(Job-Executor-4:job-151) template 4 is not in store:1, type:Image
2013-07-02 04:55:48,655 DEBUG [agent.transport.Request]
(Job-Executor-4:job-151) Seq 5-1791689215: Waiting for Seq 1791689211
Scheduling: { Cmd , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:41,pool:{id:1,uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049,type:NetworkFilesystem},diskCharacteristics:{size:8589934592,tags:[],type:ROOT,name:ROOT-36,useLocalStorage:false,recreatable:true,diskOfferingId:39,volumeId:41},templateUrl:3fd1c1cd-6583-46eb-b2e6-e7ac7e933ecc,wait:0}}]
}
2013-07-02 04:55:48,766 DEBUG [agent.transport.Request]
(AgentManager-Handler-7:null) Seq 5-1791689211: Processing: { Ans: , MgmtId:
29066118877352, via: 5, Ver: v1, Flags: 110,
[{storage.CreateAnswer:{volume:{id:45,name:/export/home/rayees/SC_QA_AUTO4/primary2,mountPoint:5a1b1c5a-5d60-451e-b74b-aea295be9ba6,path:5a1b1c5a-5d60-451e-b74b-aea295be9ba6,size:276572672,type:ROOT,storagePoolType:NetworkFilesystem,storagePoolUuid:41b632b5-40b3-3024-a38b-ea259c72579f,deviceId:0},requestTemplateReload:false,result:true,wait:0}}]
}
3) Observed below error in MS log
2013-07-02 04:55:49,255 DEBUG [agent.transport.Request]
(AgentManager-Handler-10:null) Seq 4-829227230: Processing: { Ans: , MgmtId:
29066118877352, via: 4, Ver: v1, Flags: 110,
[{Answer:{result:false,details:com.cloud.utils.exception.CloudRuntimeException:
org.libvirt.LibvirtException: name in virStorageVolLookupByName must not be
NULL\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getVolume(LibvirtStorageAdaptor.java:106)\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getPhysicalDisk(LibvirtStorageAdaptor.java:401)\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDisk(LibvirtStoragePool.java:123)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVbd(LibvirtComputingResource.java:3455)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3346)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1211)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
[jira] [Closed] (CLOUDSTACK-3329) [Automation] Failed to deploy VM with NullPointer Exception” , and observed LibvirtException: name in virStorageVolLookupByName must not be NULL in agent log
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su closed CLOUDSTACK-3329.
-
Resolution: Fixed
It's the same bug, as reported long time ago, that the storage pool is missing
on kvm host, then createcommand failed, but mgt server didn't catch this error,
sending out startcommand to kvm host regardless the failure of createcommand.
Add a fix, mgt server needs to honor the result of createcommand.
[Automation] Failed to deploy VM with NullPointer Exception” , and observed
LibvirtException: name in virStorageVolLookupByName must not be NULL in agent
log
-
Key: CLOUDSTACK-3329
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3329
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Volumes
Affects Versions: 4.2.0
Environment: KVM
master-6-17-stable
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
Fix For: 4.2.0
Attachments: CLOUDSTACK-3329.rar
This issue observed during automation run in KVM
Here taking Job : 151 for reference
1) VR created successfully
2013-07-02 04:54:18,306 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-4:job-151) Start completed for VM VM[DomainRouter|r-37-QA]
2013-07-02 04:54:18,308 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-4:job-151) Reprogramming network Ntwk[222|Guest|8] as a part of
network implement
2013-07-02 04:54:18,317 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-4:job-151)
Applying ip association in network Ntwk[222|Guest|8]
2) Create volume completed successfully
2013-07-02 04:55:48,634 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-4:job-151) Checking if we need to prepare 1 volumes for
VM[User|2c6aada6-d82e-4edc-bed1-01f21726e43f]
2013-07-02 04:55:48,639 DEBUG [storage.image.ImageDataFactoryImpl]
(Job-Executor-4:job-151) template 4 is not in store:1, type:Image
2013-07-02 04:55:48,655 DEBUG [agent.transport.Request]
(Job-Executor-4:job-151) Seq 5-1791689215: Waiting for Seq 1791689211
Scheduling: { Cmd , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:41,pool:{id:1,uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049,type:NetworkFilesystem},diskCharacteristics:{size:8589934592,tags:[],type:ROOT,name:ROOT-36,useLocalStorage:false,recreatable:true,diskOfferingId:39,volumeId:41},templateUrl:3fd1c1cd-6583-46eb-b2e6-e7ac7e933ecc,wait:0}}]
}
2013-07-02 04:55:48,766 DEBUG [agent.transport.Request]
(AgentManager-Handler-7:null) Seq 5-1791689211: Processing: { Ans: , MgmtId:
29066118877352, via: 5, Ver: v1, Flags: 110,
[{storage.CreateAnswer:{volume:{id:45,name:/export/home/rayees/SC_QA_AUTO4/primary2,mountPoint:5a1b1c5a-5d60-451e-b74b-aea295be9ba6,path:5a1b1c5a-5d60-451e-b74b-aea295be9ba6,size:276572672,type:ROOT,storagePoolType:NetworkFilesystem,storagePoolUuid:41b632b5-40b3-3024-a38b-ea259c72579f,deviceId:0},requestTemplateReload:false,result:true,wait:0}}]
}
3) Observed below error in MS log
2013-07-02 04:55:49,255 DEBUG [agent.transport.Request]
(AgentManager-Handler-10:null) Seq 4-829227230: Processing: { Ans: , MgmtId:
29066118877352, via: 4, Ver: v1, Flags: 110,
[{Answer:{result:false,details:com.cloud.utils.exception.CloudRuntimeException:
org.libvirt.LibvirtException: name in virStorageVolLookupByName must not be
NULL\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getVolume(LibvirtStorageAdaptor.java:106)\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getPhysicalDisk(LibvirtStorageAdaptor.java:401)\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDisk(LibvirtStoragePool.java:123)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVbd(LibvirtComputingResource.java:3455)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3346)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1211)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
[jira] [Assigned] (CLOUDSTACK-494) Allow multiple accounts to use the same site-to-site VPN endpoint
[ https://issues.apache.org/jira/browse/CLOUDSTACK-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang reassigned CLOUDSTACK-494: - Assignee: Sheng Yang Allow multiple accounts to use the same site-to-site VPN endpoint - Key: CLOUDSTACK-494 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-494 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: pre-4.0.0 Reporter: David Noland Assignee: Sheng Yang For example, if an account creates a site-to-site (IPSec) VPN connection to an external endpoint, another account cannot create a site-to-site VPN connection to that same endpoint. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3356) listNetworks API doesn't list the default guest network in case of project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702240#comment-13702240
]
ASF subversion and git services commented on CLOUDSTACK-3356:
-
Commit f68a74eadab2394427b7355bfa39568982aa5933 in branch refs/heads/master
from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f68a74e ]
CLOUDSTACK-3356: list shared networks available for projects when call is
executed by the admin who is not a part of the project
listNetworks API doesn't list the default guest network in case of project
-
Key: CLOUDSTACK-3356
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3356
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Projects
Affects Versions: 4.2.0
Reporter: shweta agarwal
Assignee: Alena Prokharchyk
Priority: Critical
Fix For: 4.2.0
Repro steps:
1. Have EIP/ELB enabled zone setup
2. Create at least one Project with owner set to any non-ROOT domain account.
3. Login as the above created non-ROOT domain admin account ( whether belongs
to project or not).
4. Try listNetworks with projectid
Observations:
(i) From UI It didn't list any networks
API :
http://10.147.38.141:8080/client/api?command=listNetworksresponse=jsonsessionkey=zoEGBQ8DqrevjfOToRuyBqGzIOA%3Dprojectid=a548b266-18e5-4f36-a3bc-d55c93c3e289listAll=truepage=1pagesize=20_=1372930379531
response:
{ listnetworksresponse : { } }
While when i executed the same API via cloudmonkey , network is listed
API log shows:
2013-07-04 15:11:38,559 INFO [cloud.api.ApiServer] (catalina-exec-15:null)
(userId=6 accountId=7 sessionId=null) 10.147.59.212 -- GET
apiKey=1XeMKeSvcmMN2Isi7COJ1FY2J5g2PR3Gtqy8DH4Ogl4EFf4Y-2DHfiqjxZHHl1z1jX_LCUhbJheeoAlrFKBUzQcommand=listNetworksresponse=jsonsignature=U6JER6eJpY5kqeskbcBYhDl%2Fptc%3D
200 { listnetworksresponse : { count:1 ,network : [
{id:bd683308-2809-42f0-816b-7edbb0ab3eb6,name:defaultGuestNetwork,displaytext:defaultGuestNetwork,broadcastdomaintype:Native,traffictype:Guest,zoneid:bfdf7ac5-16c3-491e-aabd-f7ad696612b8,zonename:BasicwithEIPnELB,networkofferingid:f18269b3-8793-4960-a05c-779ed56752a8,networkofferingname:DefaultSharedNetscalerEIPandELBNetworkOffering,networkofferingdisplaytext:Offering
for Shared networks with Elastic IP and Elastic LB
capabilities,networkofferingavailability:Optional,issystem:false,state:Setup,related:bd683308-2809-42f0-816b-7edbb0ab3eb6,dns1:10.103.128.16,type:Shared,acltype:Domain,subdomainaccess:true,domainid:97e3cec8-e474-11e2-95e7-0682fe17,domain:ROOT,service:[{name:Dhcp},{name:StaticNat,capability:[{name:ElasticIp,value:true,canchooseservicecapability:false}]},{name:SecurityGroup},{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:UserData},{name:Lb,capability:[{name:SupportedLBIsolation,value:dedicated,
shared,canchooseservicecapability:false},{name:SupportedLbAlgorithms,value:roundrobin,leastconn,canchooseservicecapability:false},{name:SupportedStickinessMethods,value:[{\methodname\:\LbCookie\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is cookie based sticky method, can be used only
for
http\},{\methodname\:\AppCookie\,\paramlist\:[{\paramname\:\name\,\required\:true,\isflag\:false,\description\:\
\}],\description\:\This is app session based sticky method, can be used
only for
http\},{\methodname\:\SourceBased\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is source based sticky method, can be used for
any type of
protocol.\}],canchooseservicecapability:false},{name:SupportedProtocols,value:tcp,udp,canchooseservicecapability:false},{name:AutoScaleCounters,value:[{\methodname\:\snmp\,\paramlist\:[{\paramname\:\snmpcommunity\,\required\:true,\isflag\:false,\description\:\the
community string that has to be used to do a SNMP GET on the AutoScaled
Vm\},{\paramname\:\snmpport\,\required\:false,\isflag\:false,\description\:\the
port at which SNMP agent is running on the AutoScaled
Vm\}]},{\methodname\:\netscaler\,\paramlist\:[]}],canchooseservicecapability:false},{name:LbSchemes,value:Public,canchooseservicecapability:false},{name:TrafficStatistics,value:per
public
[jira] [Resolved] (CLOUDSTACK-3356) listNetworks API doesn't list the default guest network in case of project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-3356.
---
Resolution: Fixed
listNetworks API doesn't list the default guest network in case of project
-
Key: CLOUDSTACK-3356
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3356
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Projects
Affects Versions: 4.2.0
Reporter: shweta agarwal
Assignee: Alena Prokharchyk
Priority: Critical
Fix For: 4.2.0
Repro steps:
1. Have EIP/ELB enabled zone setup
2. Create at least one Project with owner set to any non-ROOT domain account.
3. Login as the above created non-ROOT domain admin account ( whether belongs
to project or not).
4. Try listNetworks with projectid
Observations:
(i) From UI It didn't list any networks
API :
http://10.147.38.141:8080/client/api?command=listNetworksresponse=jsonsessionkey=zoEGBQ8DqrevjfOToRuyBqGzIOA%3Dprojectid=a548b266-18e5-4f36-a3bc-d55c93c3e289listAll=truepage=1pagesize=20_=1372930379531
response:
{ listnetworksresponse : { } }
While when i executed the same API via cloudmonkey , network is listed
API log shows:
2013-07-04 15:11:38,559 INFO [cloud.api.ApiServer] (catalina-exec-15:null)
(userId=6 accountId=7 sessionId=null) 10.147.59.212 -- GET
apiKey=1XeMKeSvcmMN2Isi7COJ1FY2J5g2PR3Gtqy8DH4Ogl4EFf4Y-2DHfiqjxZHHl1z1jX_LCUhbJheeoAlrFKBUzQcommand=listNetworksresponse=jsonsignature=U6JER6eJpY5kqeskbcBYhDl%2Fptc%3D
200 { listnetworksresponse : { count:1 ,network : [
{id:bd683308-2809-42f0-816b-7edbb0ab3eb6,name:defaultGuestNetwork,displaytext:defaultGuestNetwork,broadcastdomaintype:Native,traffictype:Guest,zoneid:bfdf7ac5-16c3-491e-aabd-f7ad696612b8,zonename:BasicwithEIPnELB,networkofferingid:f18269b3-8793-4960-a05c-779ed56752a8,networkofferingname:DefaultSharedNetscalerEIPandELBNetworkOffering,networkofferingdisplaytext:Offering
for Shared networks with Elastic IP and Elastic LB
capabilities,networkofferingavailability:Optional,issystem:false,state:Setup,related:bd683308-2809-42f0-816b-7edbb0ab3eb6,dns1:10.103.128.16,type:Shared,acltype:Domain,subdomainaccess:true,domainid:97e3cec8-e474-11e2-95e7-0682fe17,domain:ROOT,service:[{name:Dhcp},{name:StaticNat,capability:[{name:ElasticIp,value:true,canchooseservicecapability:false}]},{name:SecurityGroup},{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:UserData},{name:Lb,capability:[{name:SupportedLBIsolation,value:dedicated,
shared,canchooseservicecapability:false},{name:SupportedLbAlgorithms,value:roundrobin,leastconn,canchooseservicecapability:false},{name:SupportedStickinessMethods,value:[{\methodname\:\LbCookie\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is cookie based sticky method, can be used only
for
http\},{\methodname\:\AppCookie\,\paramlist\:[{\paramname\:\name\,\required\:true,\isflag\:false,\description\:\
\}],\description\:\This is app session based sticky method, can be used
only for
http\},{\methodname\:\SourceBased\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is source based sticky method, can be used for
any type of
protocol.\}],canchooseservicecapability:false},{name:SupportedProtocols,value:tcp,udp,canchooseservicecapability:false},{name:AutoScaleCounters,value:[{\methodname\:\snmp\,\paramlist\:[{\paramname\:\snmpcommunity\,\required\:true,\isflag\:false,\description\:\the
community string that has to be used to do a SNMP GET on the AutoScaled
Vm\},{\paramname\:\snmpport\,\required\:false,\isflag\:false,\description\:\the
port at which SNMP agent is running on the AutoScaled
Vm\}]},{\methodname\:\netscaler\,\paramlist\:[]}],canchooseservicecapability:false},{name:LbSchemes,value:Public,canchooseservicecapability:false},{name:TrafficStatistics,value:per
public
ip,canchooseservicecapability:false},{name:ElasticLb,value:true,canchooseservicecapability:false},{name:HealthCheckPolicy,value:true,canchooseservicecapability:false},{name:LoadBalancingSupportedIps,value:additional,canchooseservicecapability:false}]}],networkdomain:cs1cloud.internal,physicalnetworkid:a4474756-59bb-4546-b43f-a411cbdf2761,restartrequired:false,specifyipranges:true,canusefordeploy:true,ispersistent:false,tags:[],displaynetwork:true}
] } }
@
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your
[jira] [Commented] (CLOUDSTACK-3356) listNetworks API doesn't list the default guest network in case of project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702242#comment-13702242
]
ASF subversion and git services commented on CLOUDSTACK-3356:
-
Commit 8c34f35a3ffb636d45dba8a36348dc7cde245cde in branch refs/heads/4.2 from
[~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8c34f35 ]
CLOUDSTACK-3356: list shared networks available for projects when call is
executed by the admin who is not a part of the project
listNetworks API doesn't list the default guest network in case of project
-
Key: CLOUDSTACK-3356
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3356
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Projects
Affects Versions: 4.2.0
Reporter: shweta agarwal
Assignee: Alena Prokharchyk
Priority: Critical
Fix For: 4.2.0
Repro steps:
1. Have EIP/ELB enabled zone setup
2. Create at least one Project with owner set to any non-ROOT domain account.
3. Login as the above created non-ROOT domain admin account ( whether belongs
to project or not).
4. Try listNetworks with projectid
Observations:
(i) From UI It didn't list any networks
API :
http://10.147.38.141:8080/client/api?command=listNetworksresponse=jsonsessionkey=zoEGBQ8DqrevjfOToRuyBqGzIOA%3Dprojectid=a548b266-18e5-4f36-a3bc-d55c93c3e289listAll=truepage=1pagesize=20_=1372930379531
response:
{ listnetworksresponse : { } }
While when i executed the same API via cloudmonkey , network is listed
API log shows:
2013-07-04 15:11:38,559 INFO [cloud.api.ApiServer] (catalina-exec-15:null)
(userId=6 accountId=7 sessionId=null) 10.147.59.212 -- GET
apiKey=1XeMKeSvcmMN2Isi7COJ1FY2J5g2PR3Gtqy8DH4Ogl4EFf4Y-2DHfiqjxZHHl1z1jX_LCUhbJheeoAlrFKBUzQcommand=listNetworksresponse=jsonsignature=U6JER6eJpY5kqeskbcBYhDl%2Fptc%3D
200 { listnetworksresponse : { count:1 ,network : [
{id:bd683308-2809-42f0-816b-7edbb0ab3eb6,name:defaultGuestNetwork,displaytext:defaultGuestNetwork,broadcastdomaintype:Native,traffictype:Guest,zoneid:bfdf7ac5-16c3-491e-aabd-f7ad696612b8,zonename:BasicwithEIPnELB,networkofferingid:f18269b3-8793-4960-a05c-779ed56752a8,networkofferingname:DefaultSharedNetscalerEIPandELBNetworkOffering,networkofferingdisplaytext:Offering
for Shared networks with Elastic IP and Elastic LB
capabilities,networkofferingavailability:Optional,issystem:false,state:Setup,related:bd683308-2809-42f0-816b-7edbb0ab3eb6,dns1:10.103.128.16,type:Shared,acltype:Domain,subdomainaccess:true,domainid:97e3cec8-e474-11e2-95e7-0682fe17,domain:ROOT,service:[{name:Dhcp},{name:StaticNat,capability:[{name:ElasticIp,value:true,canchooseservicecapability:false}]},{name:SecurityGroup},{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:UserData},{name:Lb,capability:[{name:SupportedLBIsolation,value:dedicated,
shared,canchooseservicecapability:false},{name:SupportedLbAlgorithms,value:roundrobin,leastconn,canchooseservicecapability:false},{name:SupportedStickinessMethods,value:[{\methodname\:\LbCookie\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is cookie based sticky method, can be used only
for
http\},{\methodname\:\AppCookie\,\paramlist\:[{\paramname\:\name\,\required\:true,\isflag\:false,\description\:\
\}],\description\:\This is app session based sticky method, can be used
only for
http\},{\methodname\:\SourceBased\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is source based sticky method, can be used for
any type of
protocol.\}],canchooseservicecapability:false},{name:SupportedProtocols,value:tcp,udp,canchooseservicecapability:false},{name:AutoScaleCounters,value:[{\methodname\:\snmp\,\paramlist\:[{\paramname\:\snmpcommunity\,\required\:true,\isflag\:false,\description\:\the
community string that has to be used to do a SNMP GET on the AutoScaled
Vm\},{\paramname\:\snmpport\,\required\:false,\isflag\:false,\description\:\the
port at which SNMP agent is running on the AutoScaled
Vm\}]},{\methodname\:\netscaler\,\paramlist\:[]}],canchooseservicecapability:false},{name:LbSchemes,value:Public,canchooseservicecapability:false},{name:TrafficStatistics,value:per
public
[jira] [Commented] (CLOUDSTACK-3356) listNetworks API doesn't list the default guest network in case of project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702238#comment-13702238
]
ASF subversion and git services commented on CLOUDSTACK-3356:
-
Commit 7eff343e4948468e94377a0e86658e9fe1e36c1e in branch
refs/heads/master-6-17-stable from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7eff343 ]
CLOUDSTACK-3356: list shared networks available for projects when call is
executed by the admin who is not a part of the project
listNetworks API doesn't list the default guest network in case of project
-
Key: CLOUDSTACK-3356
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3356
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Projects
Affects Versions: 4.2.0
Reporter: shweta agarwal
Assignee: Alena Prokharchyk
Priority: Critical
Fix For: 4.2.0
Repro steps:
1. Have EIP/ELB enabled zone setup
2. Create at least one Project with owner set to any non-ROOT domain account.
3. Login as the above created non-ROOT domain admin account ( whether belongs
to project or not).
4. Try listNetworks with projectid
Observations:
(i) From UI It didn't list any networks
API :
http://10.147.38.141:8080/client/api?command=listNetworksresponse=jsonsessionkey=zoEGBQ8DqrevjfOToRuyBqGzIOA%3Dprojectid=a548b266-18e5-4f36-a3bc-d55c93c3e289listAll=truepage=1pagesize=20_=1372930379531
response:
{ listnetworksresponse : { } }
While when i executed the same API via cloudmonkey , network is listed
API log shows:
2013-07-04 15:11:38,559 INFO [cloud.api.ApiServer] (catalina-exec-15:null)
(userId=6 accountId=7 sessionId=null) 10.147.59.212 -- GET
apiKey=1XeMKeSvcmMN2Isi7COJ1FY2J5g2PR3Gtqy8DH4Ogl4EFf4Y-2DHfiqjxZHHl1z1jX_LCUhbJheeoAlrFKBUzQcommand=listNetworksresponse=jsonsignature=U6JER6eJpY5kqeskbcBYhDl%2Fptc%3D
200 { listnetworksresponse : { count:1 ,network : [
{id:bd683308-2809-42f0-816b-7edbb0ab3eb6,name:defaultGuestNetwork,displaytext:defaultGuestNetwork,broadcastdomaintype:Native,traffictype:Guest,zoneid:bfdf7ac5-16c3-491e-aabd-f7ad696612b8,zonename:BasicwithEIPnELB,networkofferingid:f18269b3-8793-4960-a05c-779ed56752a8,networkofferingname:DefaultSharedNetscalerEIPandELBNetworkOffering,networkofferingdisplaytext:Offering
for Shared networks with Elastic IP and Elastic LB
capabilities,networkofferingavailability:Optional,issystem:false,state:Setup,related:bd683308-2809-42f0-816b-7edbb0ab3eb6,dns1:10.103.128.16,type:Shared,acltype:Domain,subdomainaccess:true,domainid:97e3cec8-e474-11e2-95e7-0682fe17,domain:ROOT,service:[{name:Dhcp},{name:StaticNat,capability:[{name:ElasticIp,value:true,canchooseservicecapability:false}]},{name:SecurityGroup},{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:UserData},{name:Lb,capability:[{name:SupportedLBIsolation,value:dedicated,
shared,canchooseservicecapability:false},{name:SupportedLbAlgorithms,value:roundrobin,leastconn,canchooseservicecapability:false},{name:SupportedStickinessMethods,value:[{\methodname\:\LbCookie\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is cookie based sticky method, can be used only
for
http\},{\methodname\:\AppCookie\,\paramlist\:[{\paramname\:\name\,\required\:true,\isflag\:false,\description\:\
\}],\description\:\This is app session based sticky method, can be used
only for
http\},{\methodname\:\SourceBased\,\paramlist\:[{\paramname\:\holdtime\,\required\:false,\isflag\:false,\description\:\
\}],\description\:\This is source based sticky method, can be used for
any type of
protocol.\}],canchooseservicecapability:false},{name:SupportedProtocols,value:tcp,udp,canchooseservicecapability:false},{name:AutoScaleCounters,value:[{\methodname\:\snmp\,\paramlist\:[{\paramname\:\snmpcommunity\,\required\:true,\isflag\:false,\description\:\the
community string that has to be used to do a SNMP GET on the AutoScaled
Vm\},{\paramname\:\snmpport\,\required\:false,\isflag\:false,\description\:\the
port at which SNMP agent is running on the AutoScaled
Vm\}]},{\methodname\:\netscaler\,\paramlist\:[]}],canchooseservicecapability:false},{name:LbSchemes,value:Public,canchooseservicecapability:false},{name:TrafficStatistics,value:per
public
[jira] [Commented] (CLOUDSTACK-3170) UI: NTier: There is no option/ button made available to update different parameters of a Network ACL Item
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702251#comment-13702251 ] ASF subversion and git services commented on CLOUDSTACK-3170: - Commit b48d99b51821d8cbcb0a4e45ae7e3e42341ab775 in branch refs/heads/4.2 from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b48d99b ] CLOUDSTACK-3170: Support editing ACL rule items Conflicts: ui/scripts/vpc.js UI: NTier: There is no option/ button made available to update different parameters of a Network ACL Item - Key: CLOUDSTACK-3170 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3170 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Chandan Purushothama Assignee: Brian Federle Priority: Blocker Fix For: 4.2.0 Attachments: edit-button.png, edit-dialog.png Currently there is only provision to update the rule priority number on the UI by moving the rules up and down. There is no provision/button made available to update other parameters using the updateNetworkACL API. = As per FS at https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+ACL+deny+rules: = updateNetworkACLItem (aliased to updateNetworkACL) - async Updates an existing NetworkACLItem Parameters: id (required) - Id of the network ACL Item trafficType (optional) - can be ingress/egress (defaulted to ingress if not specified) cidrlist (optional) - List of the coma separated CIDRs for the rule. If not specified, defaulted to 0.0.0.0/0 startPort (optional) endPort (optional) protocol (optional). TCP/UDP/ICMP protocol types are supported icmpType (optional) - type of the icmp message being sent icmpCode (optional) - error code for this icmp message action (optional) - allow/deny number (optional) - rule number -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-494) Allow multiple accounts to use the same site-to-site VPN endpoint
[ https://issues.apache.org/jira/browse/CLOUDSTACK-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang updated CLOUDSTACK-494: -- Fix Version/s: 4.2.0 Allow multiple accounts to use the same site-to-site VPN endpoint - Key: CLOUDSTACK-494 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-494 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: pre-4.0.0 Reporter: David Noland Assignee: Sheng Yang Fix For: 4.2.0 For example, if an account creates a site-to-site (IPSec) VPN connection to an external endpoint, another account cannot create a site-to-site VPN connection to that same endpoint. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1676) basic zone security groups enabled with 'DefaultSharedNetworkOffering'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702267#comment-13702267 ] ASF subversion and git services commented on CLOUDSTACK-1676: - Commit 608f1a6869d2ad2fc8cd2e0f0a139f65cbdbe507 in branch refs/heads/master-6-17-stable from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=608f1a6 ] CLOUDSTACK-1676: UI zone wizard basic zone pass securitygroupenabled=true if selected network offering includes security group service; pass securitygroupenabled=false if selected network offering does not include security group service. basic zone security groups enabled with 'DefaultSharedNetworkOffering' -- Key: CLOUDSTACK-1676 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1676 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.1.0, 4.2.0 Environment: KVM Hosts Reporter: Marcus Sorensen Assignee: Jessica Wang Fix For: 4.2.0 I deployed a basic zone with a management bridge and a guest bridge, selecting 'DefaultSharedNetworkOffering' as the network offering. I launched an instance I could not ssh into instance, but instance could ping gateway, google, etc. I ran 'ebtables -t nat -L' and saw that there were rules for this instance. I ran 'ebtables -t nat -F i-2-3-VM-in', and could now SSH into server. It was as though firewall/security groups were enabled, but without any way to edit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
