[jira] [Reopened] (CLOUDSTACK-1758) 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 ] Rayees Namathponnan reopened CLOUDSTACK-1758: - As per https://issues.apache.org/jira/browse/CLOUDSTACK-2534, need to fix in test case 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 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] [Commented] (CLOUDSTACK-3000) [Automation] Router not stopped based on network.gc.interval property
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687649#comment-13687649
]
Ram Ganesh commented on CLOUDSTACK-3000:
Should we not resolve this bug and re-open when the issue occurs again?
[Automation] Router not stopped based on network.gc.interval property
Key: CLOUDSTACK-3000
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3000
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: Automation Env
Master build
Reporter: Rayees Namathponnan
Assignee: Rajesh Battala
Fix For: 4.2.0
Step 1 : Create advanced zone
Step 2: set network.gc.interval = 60, in global properties
Step 3 : Create an account, deploy and deploy vm with new network
Step 4 : Stop VM
Expected Result
Router should be stopped after one minute vm stops, but router taking more
than 2 minute to stop
Please see the below log
a) VM i-141-163-QA stop command send at 14 01:35:03,
b) i-141-163-QA stopped at 01:35:32
c ) Router r-164-QA should be stopped at 1:36:32 but, router stop command
issues at 01:37:47
2013-06-14 01:35:03,634 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-28:job-624) ControlledEntity name
is:com.cloud.network.router.VirtualRouter
2013-06-14 01:35:03,663 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-28:job-624) VM state transitted from :Running to Stopping with
event: StopRequestedvm's origin
al host id: 4 new host id: 4 host id before state transition: 4
2013-06-14 01:35:03,666 DEBUG [agent.transport.Request]
(Job-Executor-28:job-624) Seq 4-524091527: Sending { Cmd , MgmtId:
29066118877352, via: 4, Ver: v1, Flags: 100111, [{
StopCommand:{isProxy:false,vmName:i-141-163-QA,wait:0}}] }
2013-06-14 01:35:04,908 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
===START=== 10.216.51.168 -- GET
command=listVirtualMachinesresponse=jsonsessionkey=dQ8vH3fJP0
MSmEE61n6FIRSKDOA%3DlistAll=truepage=1pagesize=20_=1371188260986
2013-06-14 01:35:04,922 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:nu
2013-06-14 01:35:32,311 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-624) Complete async job-624, jobStatus: 1, resultCode:
0, result: org.apache.cloudstack.api.response.UserVmResponse@30c871f
2013-06-14 01:35:32,336 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-624) Done executing
org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-624
2013-06-14 01:35:33,674 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.216.51.168 -- GET
command=queryAsyncJobResultjobId=63e1a985-93f5-4f1b-9763-6f147cdd34e8response=jsonsessionkey=dQ8vH3fJP0MSmEE61n6FIRSKDOA%3D_=1371188289775
2013-06-14 01:35:33,683 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-25:null) Async job-624 completed
2013-06-14 01:35:33,689 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.216.51.168 -- GET
command=queryAsyncJobResultjobId=63e1a985-93f5-4f1b-9763-6f147cdd34e8response=jsonsessionkey=dQ8vH3fJP0MSmEE61n6FIRSKDOA%3D_=1371188289775
2013-06-14 01:37:47,793 DEBUG [cloud.network.NetworkManagerImpl]
(Network-Scavenger-1:null) Sending network shutdown to VirtualRouter
2013-06-14 01:37:47,795 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(Network-Scavenger-1:null) Stopping router VM[DomainRouter|r-164-QA]
2013-06-14 01:37:47,801 DEBUG [cloud.capacity.CapacityManagerImpl]
(Network-Scavenger-1:null) VM state transitted from :Running to Stopping with
event: StopRequestedvm's origi
nal host id: 4 new host id: 4 host id before state transition: 4
--
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-3060) BVT test_routers.py test case failing in Vmware with connection error
Rayees Namathponnan created CLOUDSTACK-3060: --- Summary: BVT test_routers.py test case failing in Vmware with connection error Key: CLOUDSTACK-3060 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3060 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 integration.smoke.test_routers.TestRouterServices.test_01_router_internal_basic integration.smoke.test_routers.TestRouterServices.test_02_router_internal_adv integration.smoke.test_routers.TestRouterServices.test_04_restart_network_wo_cleanup integration.smoke.test_routers.TestRouterServices.test_10_network_gc Test cases failed with error File /usr/local/lib/python2.7/unittest/case.py, line 318, in run testMethod() File /data/Repo2/qa/cloudstack/test/integration/smoke/test_routers.py, line 839, in test_10_network_gc Check state of the router after stopping all VMs associated 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 487, in _baseAssertEqual raise self.failureException(msg) Check state of the router after stopping all VMs associated -- 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) 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 ] Rayees Namathponnan updated CLOUDSTACK-1758: Priority: Blocker (was: Major) 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] [Commented] (CLOUDSTACK-3000) [Automation] Router not stopped based on network.gc.interval property
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687662#comment-13687662
]
Rajesh Battala commented on CLOUDSTACK-3000:
Resolving the issue as the issue is not reproducible in the latest run.
please feel free to open if the issue is reproducible.
[Automation] Router not stopped based on network.gc.interval property
Key: CLOUDSTACK-3000
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3000
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: Automation Env
Master build
Reporter: Rayees Namathponnan
Assignee: Rajesh Battala
Fix For: 4.2.0
Step 1 : Create advanced zone
Step 2: set network.gc.interval = 60, in global properties
Step 3 : Create an account, deploy and deploy vm with new network
Step 4 : Stop VM
Expected Result
Router should be stopped after one minute vm stops, but router taking more
than 2 minute to stop
Please see the below log
a) VM i-141-163-QA stop command send at 14 01:35:03,
b) i-141-163-QA stopped at 01:35:32
c ) Router r-164-QA should be stopped at 1:36:32 but, router stop command
issues at 01:37:47
2013-06-14 01:35:03,634 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-28:job-624) ControlledEntity name
is:com.cloud.network.router.VirtualRouter
2013-06-14 01:35:03,663 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-28:job-624) VM state transitted from :Running to Stopping with
event: StopRequestedvm's origin
al host id: 4 new host id: 4 host id before state transition: 4
2013-06-14 01:35:03,666 DEBUG [agent.transport.Request]
(Job-Executor-28:job-624) Seq 4-524091527: Sending { Cmd , MgmtId:
29066118877352, via: 4, Ver: v1, Flags: 100111, [{
StopCommand:{isProxy:false,vmName:i-141-163-QA,wait:0}}] }
2013-06-14 01:35:04,908 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
===START=== 10.216.51.168 -- GET
command=listVirtualMachinesresponse=jsonsessionkey=dQ8vH3fJP0
MSmEE61n6FIRSKDOA%3DlistAll=truepage=1pagesize=20_=1371188260986
2013-06-14 01:35:04,922 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:nu
2013-06-14 01:35:32,311 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-624) Complete async job-624, jobStatus: 1, resultCode:
0, result: org.apache.cloudstack.api.response.UserVmResponse@30c871f
2013-06-14 01:35:32,336 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-624) Done executing
org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-624
2013-06-14 01:35:33,674 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.216.51.168 -- GET
command=queryAsyncJobResultjobId=63e1a985-93f5-4f1b-9763-6f147cdd34e8response=jsonsessionkey=dQ8vH3fJP0MSmEE61n6FIRSKDOA%3D_=1371188289775
2013-06-14 01:35:33,683 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-25:null) Async job-624 completed
2013-06-14 01:35:33,689 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.216.51.168 -- GET
command=queryAsyncJobResultjobId=63e1a985-93f5-4f1b-9763-6f147cdd34e8response=jsonsessionkey=dQ8vH3fJP0MSmEE61n6FIRSKDOA%3D_=1371188289775
2013-06-14 01:37:47,793 DEBUG [cloud.network.NetworkManagerImpl]
(Network-Scavenger-1:null) Sending network shutdown to VirtualRouter
2013-06-14 01:37:47,795 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(Network-Scavenger-1:null) Stopping router VM[DomainRouter|r-164-QA]
2013-06-14 01:37:47,801 DEBUG [cloud.capacity.CapacityManagerImpl]
(Network-Scavenger-1:null) VM state transitted from :Running to Stopping with
event: StopRequestedvm's origi
nal host id: 4 new host id: 4 host id before state transition: 4
--
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-3000) [Automation] Router not stopped based on network.gc.interval property
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Battala resolved CLOUDSTACK-3000.
Resolution: Cannot Reproduce
[Automation] Router not stopped based on network.gc.interval property
Key: CLOUDSTACK-3000
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3000
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: Automation Env
Master build
Reporter: Rayees Namathponnan
Assignee: Rajesh Battala
Fix For: 4.2.0
Step 1 : Create advanced zone
Step 2: set network.gc.interval = 60, in global properties
Step 3 : Create an account, deploy and deploy vm with new network
Step 4 : Stop VM
Expected Result
Router should be stopped after one minute vm stops, but router taking more
than 2 minute to stop
Please see the below log
a) VM i-141-163-QA stop command send at 14 01:35:03,
b) i-141-163-QA stopped at 01:35:32
c ) Router r-164-QA should be stopped at 1:36:32 but, router stop command
issues at 01:37:47
2013-06-14 01:35:03,634 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-28:job-624) ControlledEntity name
is:com.cloud.network.router.VirtualRouter
2013-06-14 01:35:03,663 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-28:job-624) VM state transitted from :Running to Stopping with
event: StopRequestedvm's origin
al host id: 4 new host id: 4 host id before state transition: 4
2013-06-14 01:35:03,666 DEBUG [agent.transport.Request]
(Job-Executor-28:job-624) Seq 4-524091527: Sending { Cmd , MgmtId:
29066118877352, via: 4, Ver: v1, Flags: 100111, [{
StopCommand:{isProxy:false,vmName:i-141-163-QA,wait:0}}] }
2013-06-14 01:35:04,908 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
===START=== 10.216.51.168 -- GET
command=listVirtualMachinesresponse=jsonsessionkey=dQ8vH3fJP0
MSmEE61n6FIRSKDOA%3DlistAll=truepage=1pagesize=20_=1371188260986
2013-06-14 01:35:04,922 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:nu
2013-06-14 01:35:32,311 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-624) Complete async job-624, jobStatus: 1, resultCode:
0, result: org.apache.cloudstack.api.response.UserVmResponse@30c871f
2013-06-14 01:35:32,336 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-624) Done executing
org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-624
2013-06-14 01:35:33,674 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.216.51.168 -- GET
command=queryAsyncJobResultjobId=63e1a985-93f5-4f1b-9763-6f147cdd34e8response=jsonsessionkey=dQ8vH3fJP0MSmEE61n6FIRSKDOA%3D_=1371188289775
2013-06-14 01:35:33,683 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-25:null) Async job-624 completed
2013-06-14 01:35:33,689 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.216.51.168 -- GET
command=queryAsyncJobResultjobId=63e1a985-93f5-4f1b-9763-6f147cdd34e8response=jsonsessionkey=dQ8vH3fJP0MSmEE61n6FIRSKDOA%3D_=1371188289775
2013-06-14 01:37:47,793 DEBUG [cloud.network.NetworkManagerImpl]
(Network-Scavenger-1:null) Sending network shutdown to VirtualRouter
2013-06-14 01:37:47,795 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(Network-Scavenger-1:null) Stopping router VM[DomainRouter|r-164-QA]
2013-06-14 01:37:47,801 DEBUG [cloud.capacity.CapacityManagerImpl]
(Network-Scavenger-1:null) VM state transitted from :Running to Stopping with
event: StopRequestedvm's origi
nal host id: 4 new host id: 4 host id before state transition: 4
--
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] [Reopened] (CLOUDSTACK-2534) Packaging puts SSH private keys as public readable on management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam reopened CLOUDSTACK-2534: Reopening to fix the issue with packaging: The private key under /usr should not be public readable Packaging puts SSH private keys as public readable on management server --- Key: CLOUDSTACK-2534 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2534 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Reporter: Girish Shilamkar Priority: Blocker Fix For: 4.2.0 SSH public key is group readable which is security threat. ls -la /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud -rw-r--r--. 1 root root 1670 May 15 22:54 /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud -- 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-2534) Packaging puts SSH private keys as public readable on management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687668#comment-13687668 ] Prasanna Santhanam commented on CLOUDSTACK-2534: Both the keys are the same private key. However one of them is public readable. While the one in /var will allow you to login to vmware hosts because of ssh security, the one under /usr still needs to be made secure enough. It shouldn't be world readable. Packaging puts SSH private keys as public readable on management server --- Key: CLOUDSTACK-2534 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2534 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Reporter: Girish Shilamkar Priority: Blocker Fix For: 4.2.0 SSH public key is group readable which is security threat. ls -la /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud -rw-r--r--. 1 root root 1670 May 15 22:54 /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud -- 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-2534) Packaging puts SSH private keys as public readable on management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-2534: --- Labels: security (was: ) Packaging puts SSH private keys as public readable on management server --- Key: CLOUDSTACK-2534 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2534 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Packaging Reporter: Girish Shilamkar Priority: Critical Labels: security Fix For: 4.2.0 SSH public key is group readable which is security threat. ls -la /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud -rw-r--r--. 1 root root 1670 May 15 22:54 /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud -- 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-2534) Packaging puts SSH private keys as public readable on management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-2534: --- Component/s: (was: VMware) Packaging Packaging puts SSH private keys as public readable on management server --- Key: CLOUDSTACK-2534 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2534 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Packaging Reporter: Girish Shilamkar Priority: Critical Fix For: 4.2.0 SSH public key is group readable which is security threat. ls -la /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud -rw-r--r--. 1 root root 1670 May 15 22:54 /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud -- 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-1758) 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:comment-tabpanelfocusedCommentId=13687674#comment-13687674 ] ASF subversion and git services commented on CLOUDSTACK-1758: - Commit 6e63bb78220a057bca329ee6a8779f0e4c476586 in branch refs/heads/master from [~gpshilamkar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6e63bb7 ] CLOUDSTACK-1758: Update ssh key location for vmware Signed-off-by: Prasanna Santhanam t...@apache.org 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] [Resolved] (CLOUDSTACK-1758) 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 ] Prasanna Santhanam resolved CLOUDSTACK-1758. Resolution: Fixed 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] [Created] (CLOUDSTACK-3063) [UI]Dedicating a host to non-root domain which has instances of other domain(root/nonroot) should throw appropriate message to the user.
manasaveloori created CLOUDSTACK-3063: - Summary: [UI]Dedicating a host to non-root domain which has instances of other domain(root/nonroot) should throw appropriate message to the user. Key: CLOUDSTACK-3063 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3063 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: manasaveloori Priority: Minor Steps: 1. Have CS with advanced zone. 2. Create a non-root domain say “Test”. 3. Create instances in root and non-root domains. 4. Now go to host and try to dedicate it to non-root domain. Observation: User is given a message “Host dedicated”, but actually host will not get dedicated . MS logs are giving an exception while dedicating a host which has instances in other domain which is correct ,but UI is not throwing any message. -- 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-3063) [UI]Dedicating a host to non-root domain which has instances of other domain(root/nonroot) should throw appropriate message to the user.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori updated CLOUDSTACK-3063: -- Attachment: HostDedicated.jpg [UI]Dedicating a host to non-root domain which has instances of other domain(root/nonroot) should throw appropriate message to the user. - Key: CLOUDSTACK-3063 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3063 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: manasaveloori Priority: Minor Attachments: HostDedicated.jpg Steps: 1.Have CS with advanced zone. 2.Create a non-root domain say “Test”. 3.Create instances in root and non-root domains. 4.Now go to host and try to dedicate it to non-root domain. Observation: User is given a message “Host dedicated”, but actually host will not get dedicated . MS logs are giving an exception while dedicating a host which has instances in other domain which is correct ,but UI is not throwing any message. -- 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-3059) Testcase test_redundant_router not creating network offering with capabilitytype=RedundantRouter
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanna Santhanam resolved CLOUDSTACK-3059.
Resolution: Fixed
serviceCapabilityList needs to be case sensitive. Fixed with
b0d186ce5bd42a9120243d1f32adabc6851865a5
Testcase test_redundant_router not creating network offering with
capabilitytype=RedundantRouter
Key: CLOUDSTACK-3059
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3059
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
Reporter: Rayees Namathponnan
Assignee: Prasanna Santhanam
Priority: Blocker
Fix For: 4.2.0
test_redundant_router.py failed completed, test cases not creating network
offering with RR,
Test cases failed with below error
File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
testMethod()
File
/Repo_30X/ipcl/cloudstack/test/integration/component/test_redundant_router.py,
line 399, in test_createRvRNetwork
Length of the list router should be 2 (Backup master)
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 487, in
_baseAssertEqual
raise self.failureException(msg)
Length of the list router should be 2 (Backup master)
Below API log generated during automation run, here you can see RR is
False
2013-06-18 19:46:09,024 INFO [cloud.api.ApiServer] (catalina-exec-22:null)
(userId=2 accountId=2 sessionId=null) 10.223.240.194 -- GET
apiKey=Zzxy3ps4AUUdnMT3EadmeO8zROnnKN0bqKmh56llSxmiI2BbqsqJgnF1lLPSsLJUd4WVptxoyXadJ3Yc149OAwserviceproviderlist%5B2%5D.provider=VirtualRouterserviceproviderlist%5B5%5D.service=Dhcpdisplaytext=Network+off-RVR+services-7968S7serviceproviderlist%5B0%5D.service=UserDataserviceproviderlist%5B4%5D.provider=VirtualRouterserviceproviderlist%5B1%5D.provider=VirtualRouteravailability=Optionalconservemode=Trueserviceproviderlist%5B3%5D.service=Dnsserviceproviderlist%5B5%5D.provider=VirtualRouterresponse=jsonserviceproviderlist%5B0%5D.provider=VirtualRouterserviceproviderlist%5B8%5D.provider=VirtualRouterserviceproviderlist%5B1%5D.service=Lbserviceproviderlist%5B4%5D.service=Firewallsupportedservices=Vpn%2CDhcp%2CDns%2CSourceNat%2CPortForwarding%2CFirewall%2CLb%2CUserData%2CStaticNattraffictype=GUESTserviceproviderlist%5B6%5D.provider=VirtualRouterserviceproviderlist%5B8%5D.service=StaticNatserviceproviderlist%5B3%5D.provider=VirtualRoutername=Network+offering-RVR+services-QLUAERguestiptype=Isolatedserviceproviderlist%5B7%5D.provider=VirtualRouterserviceproviderlist%5B7%5D.service=SourceNatserviceproviderlist%5B2%5D.service=PortForwardingserviceproviderlist%5B6%5D.service=Vpncommand=createNetworkOfferingsignature=VOzYZ36FtZXJy97lCfmQftsyKiM%3D
200 { createnetworkofferingresponse : { networkoffering :
{id:3864b774-4439-4cad-bffb-89a0516b4f6f,name:Network offering-RVR
services-QLUAER,displaytext:Network off-RVR
services-7968S7,traffictype:Guest,isdefault:false,specifyvlan:false,conservemode:true,specifyipranges:false,availability:Optional,networkrate:200,state:Disabled,guestiptype:Isolated,serviceofferingid:12a3fa54-e945-48dd-8da3-826c7b7646e4,service:[{name:PortForwarding,provider:[{name:VirtualRouter}]},{name:Vpn,provider:[{name:VirtualRouter}]},{name:StaticNat,provider:[{name:VirtualRouter}],capability:[{name:ElasticIp,value:false,canchooseservicecapability:false},{name:AssociatePublicIP,value:false,canchooseservicecapability:false}]},{name:Firewall,provider:[{name:VirtualRouter}]},{name:Dns,provider:[{name:VirtualRouter}]},{name:Dhcp,provider:[{name:VirtualRouter}]},{name:Lb,provider:[{name:VirtualRouter}],capability:[{name:SupportedLBIsolation,value:shared,canchooseservicecapability:false},{name:ElasticLb,value:false,canchooseservicecapability:false},{name:InlineMode,value:false,canchooseservicecapability:false}]},{name:UserData,provider:[{name:VirtualRouter}]},{name:SourceNat,provider:[{name:VirtualRouter}],capability:[{name:SupportedSourceNatTypes,value:peraccount,canchooseservicecapability:false},{name:RedundantRouter,value:false,canchooseservicecapability:false}]}],forvpc:false,ispersistent:false}
} }
--
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-2882) Test case test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso failing due to wrong mount point
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687726#comment-13687726
]
Sateesh Chodapuneedi commented on CLOUDSTACK-2882:
--
I don't have a vmware environment handy, can you tell us the mount pattern for
devices on vmware?
Prasanna,
I think you can use /dev/cdrom as mount point for iso device in case of VMware.
Test case test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso
failing due to wrong mount point
Key: CLOUDSTACK-2882
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2882
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 - BVT
Reporter: Rayees Namathponnan
Assignee: Prasanna Santhanam
Fix For: 4.2.0
Test case test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso
failing due to wrong mount point in KVM
Test case failing with below error
paramiko.transport: INFO: Secsh channel 3 opened.
paramiko.transport: DEBUG: [chan 3] Sesch channel 3 request ok
sshClient: DEBUG: {Cmd: mount -rt iso9660 /dev/xvdd /mnt/tmp via Host:
10.208.10.22} {returns: ['mount: special device /dev/xvdd does not exist']}
http://jenkins.cloudstack.org/view/cloudstack-qa/job/test-smoke-matrix/389/suite=test_vm_life_cycle/testReport/integration.smoke.test_vm_life_cycle/TestVMLifeCycle/test_10_attachAndDetach_iso/
--
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-2882) Test case test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso failing due to wrong mount point
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687762#comment-13687762
]
Prasanna Santhanam commented on CLOUDSTACK-2882:
[~sateeshc] /dev/cdrom is for ISOs. I'm looking for the pattern for attached
disks/volumes. On xen it goes like /dev/xvda,b,c and on KVM /dev/vda,b,c etc
Test case test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso
failing due to wrong mount point
Key: CLOUDSTACK-2882
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2882
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 - BVT
Reporter: Rayees Namathponnan
Assignee: Prasanna Santhanam
Fix For: 4.2.0
Test case test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso
failing due to wrong mount point in KVM
Test case failing with below error
paramiko.transport: INFO: Secsh channel 3 opened.
paramiko.transport: DEBUG: [chan 3] Sesch channel 3 request ok
sshClient: DEBUG: {Cmd: mount -rt iso9660 /dev/xvdd /mnt/tmp via Host:
10.208.10.22} {returns: ['mount: special device /dev/xvdd does not exist']}
http://jenkins.cloudstack.org/view/cloudstack-qa/job/test-smoke-matrix/389/suite=test_vm_life_cycle/testReport/integration.smoke.test_vm_life_cycle/TestVMLifeCycle/test_10_attachAndDetach_iso/
--
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-3065) test_network_acl fails with service/provider combination failure
Prasanna Santhanam created CLOUDSTACK-3065: -- Summary: test_network_acl fails with service/provider combination failure Key: CLOUDSTACK-3065 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3065 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Prasanna Santhanam Priority: Critical The NetworkACL tests have been failing for the past two builds with Service/provider combination Lb/VpcVirtualRouter is not supported by VPC [VPC [1-vpc-networkacl-RMTQBE] http://jenkins.buildacloud.org/job/test-smoke-matrix/suite=test_network_acl/lastCompletedBuild/testReport/integration.smoke.test_network_acl/TestNetworkACL/test_network_acl/ -- 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-3065) test_network_acl fails with service/provider combination failure
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3065: --- Attachment: 408.tar.bz2 management server logs (failures were found on XCP and KVM) test_network_acl fails with service/provider combination failure Key: CLOUDSTACK-3065 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3065 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Prasanna Santhanam Priority: Critical Attachments: 408.tar.bz2 The NetworkACL tests have been failing for the past two builds with Service/provider combination Lb/VpcVirtualRouter is not supported by VPC [VPC [1-vpc-networkacl-RMTQBE] http://jenkins.buildacloud.org/job/test-smoke-matrix/suite=test_network_acl/lastCompletedBuild/testReport/integration.smoke.test_network_acl/TestNetworkACL/test_network_acl/ -- 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-3066) No Error message is popped up on UI when a dedicated resource is dedicated to another Account.
Kiran Koneti created CLOUDSTACK-3066: Summary: No Error message is popped up on UI when a dedicated resource is dedicated to another Account. Key: CLOUDSTACK-3066 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3066 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 Fix For: 4.2.0 Below are the steps followed. 1)Dedicated a Zone to account1 from domain1 2)Then tried to dedicate the pod in that zone to another Account from different domain 3)Then the UI Shows a message the POD is dedicated but there is a error message logged in the management server log as below: 2013-06-19 20:24:07,842 ERROR [cloudstack.dedicated.DedicatedResourceManagerImpl] (Job-Executor-26:job-26) Cannot dedicate Pod. Its zone is already dedicated 2013-06-19 20:24:07,847 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-26:job-26) Unexpected exception while executing org.apache.cloudstack.api.commands.DedicatePodCmd com.cloud.utils.exception.CloudRuntimeException: Pod's Zone Z1 is already dedicated at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.dedicatePod(DedicatedResourceManagerImpl.java:266) at org.apache.cloudstack.api.commands.DedicatePodCmd.execute(DedicatePodCmd.java:95) 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) The expected result is the UI should also pop up a message saying the pod is dedicated to another Account instead of saying the dedication as successful. -- 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-2990) After scaling up ,increased memory and cpu is not getting registered in guest OS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687865#comment-13687865 ] Nitin Mehta commented on CLOUDSTACK-2990: - Pranav - If its vmware HV then you need to show helper text to the user when he is trying to scale the vm. You should say Please read the dynamic scaling section in the admin guide before scaling the vm. This is needed because after the user scales his vm he needs to run a couple of commands in http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=1012764 After scaling up ,increased memory and cpu is not getting registered in guest OS --- Key: CLOUDSTACK-2990 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2990 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, VMware Affects Versions: 4.2.0 Environment: Hypervisor Esxi 5.1 Reporter: prashant kumar mishra Assignee: Nitin Mehta Priority: Critical Fix For: 4.2.0 Guest OS :CentOS 5.3(64-bit) no GUI (vSphere) Default template. Steps to reproduce - 1-Deploy a vm with SO small ( RAM :512 MB,CPU 500MHz) 2-Scale up to SO medium (RAM:1024MB,CPU 1000MHz) Expected -- Guest OS should be able to use increased memory and cpu Actual --- Guest OS still shows old( before scale up) memory and cpu values My observation --- -On xen server increased memory and cpu is getting registered in Guest OS after scale 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] [Commented] (CLOUDSTACK-3056) Add Intelligence mechanism in the UI to restore back to the step where the zone wizard failed because of addVmWareDc API call failure
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687870#comment-13687870 ] ASF subversion and git services commented on CLOUDSTACK-3056: - Commit 8ff565860942d9caeec574fda352b0ab6b67c5bb in branch refs/heads/master-6-17-stable from [~pranav.sax...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8ff5658 ] CLOUDSTACK-3056:Intelligence mechanism on the UI in case of addVmwareDC API call failure Add Intelligence mechanism in the UI to restore back to the step where the zone wizard failed because of addVmWareDc API call failure - Key: CLOUDSTACK-3056 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3056 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: Pranav Saxena Assignee: Pranav Saxena Currently the UI will be stuck because the zone wizard hangs if the addVmWareDC api call isn't successful .The only possible workaround is to refresh the browser and enter the details from the beginning . Requirement - Add some intelligence mechanism in the UI to restore it to the step which led to the zone wizard failure . -- 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-2444) Not able to deploy Vms with service offering that has 128 MB memory requirement on Xenserver hosts.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Tripathi reassigned CLOUDSTACK-2444:
---
Assignee: Sanjay Tripathi
Not able to deploy Vms with service offering that has 128 MB memory
requirement on Xenserver hosts.
---
Key: CLOUDSTACK-2444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2444
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: Build from pvlan branch ( same behavior seen with builds
form master)
Reporter: Sangeetha Hariharan
Assignee: Sanjay Tripathi
Fix For: 4.2.0
Not able to deploy Vms with service offering that has 128 MB memory
requirement.
Set up:
Create service offering that has 128 MB memory requirement.
Deploy a Vm using this service offerings.
User Vm starts successfully but it gets to stopped state after few seconds.
deployVM reports success . But later on cluster sync sees this Vm in stopped
state and sends a StopCommand for this VM.
management server logs:
2013-05-10 16:49:42,506 DEBUG [agent.transport.Request]
(Job-Executor-96:job-161) Seq 5-1363347283: Executing: { Cmd , MgmtId:
7647994577963, via: 5, Ver: v1, Fl
ags: 100111,
[{StartCommand:{vm:{id:58,name:i-2-58-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:100,maxSpeed:100,minRam:136314880,max
Ram:136314880,arch:x86_64,os:CentOS 5.3
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,vncPassword:8df034e62ede1e55
,params:{},uuid:7d37fc57-465d-4d62-9e4b-956b07af45c7,disks:[{id:57,name:ROOT-58,mountPoint:/export/home/sangeetha/campo-systemp/primary,path:
69d5b936-5dd9-4988-86d0-178ac6bea9de,size:21474836480,type:ROOT,storagePoolType:NetworkFilesystem,storagePoolUuid:aaaeab15-72db-3ed6-8f46-c83495269
4d6,deviceId:0},{id:58,name:CentOS 5.6(64-bit) no GUI
(XenServer),size:0,type:ISO,storagePoolType:ISO,deviceId:3}],nics:[{deviceId:0,net
workRateMbps:200,defaultNic:true,uuid:e2d6e8aa-620a-4a54-89fd-b2d04107df58,ip:10.1.1.64,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:1f:
31:00:0e,dns1:72.52.126.11,dns2:72.52.126.12,broadcastType:Vlan,type:Guest,broadcastUri:vlan://2021,isolationUri:vlan://2021,isSecurityG
roupEnabled:false}]},hostIp:10.223.81.61,wait:0}}] }
2013-05-10 16:49:42,506 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-52:null) Seq 5-1363347283: Executing request
2013-05-10 16:49:42,592 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-52:null) 1. The VM i-2-58-VM is in Starting state.
2013-05-10 16:49:42,652 DEBUG [xen.resource.XenServer56FP1Resource]
(DirectAgent-52:null) Created VM e13cd8ae-2406-e01d-2364-c540418d642a for
i-2-58-VM
2013-05-10 16:49:42,706 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-52:null) VBD ec4df891-7dcb-a292-53f2-5da1093423ab created for
Vol[57|ROOT|69d5b936-5d
d9-4988-86d0-178ac6bea9de|21474836480]
2013-05-10 16:49:42,744 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-52:null) VBD b96694b0-2645-2820-8e68-97dc972e7c1d created for
Vol[58|ISO|null|0]
2013-05-10 16:49:42,744 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-52:null) Creating VIF for i-2-58-VM on nic
[Nic:Guest-10.1.1.64-vlan://2021]
2013-05-10 16:49:42,799 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-52:null) Found a network called
VLAN-1ae20f16-2367-e10e-b79d-8c27642cdae0-2021 on hos
t=10.223.81.61; Network=7627057c-1db5-26ec-fc0e-b2b3ecce177a;
pif=b8922d23-102a-1c02-4093-ee491e70f820
2013-05-10 16:49:42,829 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-52:null) Created a vif 062aa30d-a65f-5419-dc33-99203758ebbf on 0
2013-05-10 16:49:43,206 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===START=== 10.217.252.128 -- GET
command=queryAsyncJobResultjobId=3f2b44ae-2b94-4
f93-bc48-c316fb7a71a8response=jsonsessionkey=oh7DW9oqg1QskMNcZZBe3a5JRH0%3D_=1368229787809
2013-05-10 16:49:43,220 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===END=== 10.217.252.128 -- GET
command=queryAsyncJobResultjobId=3f2b44ae-2b94-4f9
3-bc48-c316fb7a71a8response=jsonsessionkey=oh7DW9oqg1QskMNcZZBe3a5JRH0%3D_=1368229787809
2013-05-10 16:49:43,324 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 2 routers to update status.
2013-05-10 16:49:43,325 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-05-10 16:49:43,644 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 2 routers to update status.
2013-05-10 16:49:43,645 DEBUG
[jira] [Commented] (CLOUDSTACK-3066) No Error message is popped up on UI when a dedicated resource is dedicated to another Account.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687871#comment-13687871
]
Kiran Koneti commented on CLOUDSTACK-3066:
--
The Firefox api response is as below:
{ listdomainsresponse : { count:3 ,domain : [
{id:d8ec3a84-d8d2-11e2-a40e-0618b087,name:ROOT,level:0,haschild:true,path:ROOT},
{id:7a6b12ae-6a8e-4f02-a6a0-5f8be82c20c9,name:Kiran,level:1,parentdomainid:d8ec3a84-d8d2-11e2-a40e-0618b087,parentdomainname:ROOT,haschild:false,path:ROOT/Kiran},
{id:1352d92d-50ca-4583-b152-19c7eff8739f,name:Swathi,level:1,parentdomainid:d8ec3a84-d8d2-11e2-a40e-0618b087,parentdomainname:ROOT,haschild:false,path:ROOT/Swathi}
] } }
{ dedicatepodresponse : {jobid:0173a2ba-2f4a-40ea-ba2e-ad7c896930c6} }
{ listzonesresponse : { count:1 ,zone : [
{id:93cab9dd-0aa8-4f48-a81b-1244a5d2ad3d,name:Z1,dns1:10.103.128.16,internaldns1:10.103.128.16,guestcidraddress:10.1.1.0/24,networktype:Advanced,securitygroupsenabled:false,allocationstate:Enabled,zonetoken:bc982533-bbe0-36e6-b07d-c7529c5e6cc7,dhcpprovider:VirtualRouter,localstorageenabled:false}
] } }
{ listzonesresponse : { count:1 ,zone : [
{id:93cab9dd-0aa8-4f48-a81b-1244a5d2ad3d,name:Z1,dns1:10.103.128.16,internaldns1:10.103.128.16,guestcidraddress:10.1.1.0/24,networktype:Advanced,securitygroupsenabled:false,allocationstate:Enabled,zonetoken:bc982533-bbe0-36e6-b07d-c7529c5e6cc7,dhcpprovider:VirtualRouter,localstorageenabled:false}
] } }
{ listdedicatedpodsresponse : { } }
No Error message is popped up on UI when a dedicated resource is dedicated to
another Account.
--
Key: CLOUDSTACK-3066
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3066
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
Fix For: 4.2.0
Below are the steps followed.
1)Dedicated a Zone to account1 from domain1
2)Then tried to dedicate the pod in that zone to another Account from
different domain
3)Then the UI Shows a message the POD is dedicated but there is a error
message logged in the management server log as below:
2013-06-19 20:24:07,842 ERROR
[cloudstack.dedicated.DedicatedResourceManagerImpl] (Job-Executor-26:job-26)
Cannot dedicate Pod. Its zone is already dedicated
2013-06-19 20:24:07,847 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-26) Unexpected exception while executing
org.apache.cloudstack.api.commands.DedicatePodCmd
com.cloud.utils.exception.CloudRuntimeException: Pod's Zone Z1 is already
dedicated
at
org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.dedicatePod(DedicatedResourceManagerImpl.java:266)
at
org.apache.cloudstack.api.commands.DedicatePodCmd.execute(DedicatePodCmd.java:95)
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)
The expected result is the UI should also pop up a message saying the pod is
dedicated to another Account instead of saying the dedication as successful.
--
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-3069) [UI]Quickview of POD is not displaying any info in UI.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Chiang reassigned CLOUDSTACK-3069: Assignee: Isaac Chiang [UI]Quickview of POD is not displaying any info in UI. -- Key: CLOUDSTACK-3069 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3069 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: CloudPlatform-4.0-91-rhel6.3. Reporter: manasaveloori Assignee: Isaac Chiang Priority: Minor Fix For: 4.2.0 Attachments: pod.jpg 1.Have a CS with any zone. 2.Go to Infrastructure-Pods-Quickview Observation: Quickview option of the POD not displaying any information. API is working fine. Attached is the SC 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] [Commented] (CLOUDSTACK-1758) 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:comment-tabpanelfocusedCommentId=13688056#comment-13688056 ] ASF subversion and git services commented on CLOUDSTACK-1758: - Commit 5140473f2b754c1f178aae7946798d95027ec69a in branch refs/heads/master from [~gpshilamkar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5140473 ] CLOUDSTACK-1758: Fix ssvm test failures, where ssh to ssvm failed. Signed-off-by: Prasanna Santhanam t...@apache.org 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] [Created] (CLOUDSTACK-3075) Account created during automation run should append test case name in account
Rayees Namathponnan created CLOUDSTACK-3075: --- Summary: Account created during automation run should append test case name in account Key: CLOUDSTACK-3075 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3075 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Reporter: Rayees Namathponnan Assignee: Rayees Namathponnan Fix For: 4.2.0 Account created during automation run should append test case name in account. It will help during test case analysis -- 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-3076) Delete snapshot test case should have use case for CLOUDSTACK-3046
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-3076: Summary: Delete snapshot test case should have use case for CLOUDSTACK-3046 (was: Delete snap shot test case should have use case for CLOUDSTACK-3046 ) Delete snapshot test case should have use case for CLOUDSTACK-3046 --- Key: CLOUDSTACK-3076 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3076 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Reporter: Rayees Namathponnan Assignee: Rayees Namathponnan Fix For: 4.2.0 Delete snap shot test case should have use case for CLOUDSTACK-3046 -- 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-3076) Delete snap shot test case should have use case for CLOUDSTACK-3046
Rayees Namathponnan created CLOUDSTACK-3076: --- Summary: Delete snap shot test case should have use case for CLOUDSTACK-3046 Key: CLOUDSTACK-3076 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3076 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Reporter: Rayees Namathponnan Assignee: Rayees Namathponnan Fix For: 4.2.0 Delete snap shot test case should have use case for CLOUDSTACK-3046 -- 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-3076) Delete snapshot test case should have use case for CLOUDSTACK-3046
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-3076: Description: Delete snap shot test case should have use case for CLOUDSTACK-3046 Test case snapshot.py in regression suite was:Delete snap shot test case should have use case for CLOUDSTACK-3046 Delete snapshot test case should have use case for CLOUDSTACK-3046 --- Key: CLOUDSTACK-3076 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3076 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Reporter: Rayees Namathponnan Assignee: Rayees Namathponnan Fix For: 4.2.0 Delete snap shot test case should have use case for CLOUDSTACK-3046 Test case snapshot.py in regression suite -- 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-2073) java.lang.NullPointerException when trying to put a Zone wide primary storage in maintenance mode.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Battala reassigned CLOUDSTACK-2073:
--
Assignee: Rajesh Battala
java.lang.NullPointerException when trying to put a Zone wide primary storage
in maintenance mode.
--
Key: CLOUDSTACK-2073
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2073
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: Build from master
Reporter: Sangeetha Hariharan
Assignee: Rajesh Battala
Priority: Critical
Fix For: 4.2.0
java.lang.NullPointerException when trying to put a Zone wide primary storage
in maintenance mode.
Steps to reproduce the problem:
Configured a NFS primary storage zone wide.
Tried to put the primary storage in maintenance mode.
It fails with Command failed due to Internal Server Error.
2013-04-17 13:39:08,259 INFO [cloud.api.ApiServer] (catalina-exec-1:null)
(userId=2 accountId=2 sessionId=A716D4755FFE21C87D8EA5E2E459AD8C)
10.217.252.128 -- GET
command=enableStorageMaintenanceid=27f5ddfc-f967-3e4e-91f1-ee19890c9577response=jsonsessionkey=tit%2Bdz%2Fux9eXh3FHUDUxlY6x8vo%3D_=1366231160791
200 { prepareprimarystorageformaintenanceresponse :
{jobid:ff569d61-2474-4fe1-8eec-2701b26dd2ea} }
2013-04-17 13:39:11,306 INFO [cloud.api.ApiServer] (catalina-exec-17:null)
(userId=2 accountId=2 sessionId=A716D4755FFE21C87D8EA5E2E459AD8C)
10.217.252.128 -- GET
command=queryAsyncJobResultjobId=ff569d61-2474-4fe1-8eec-2701b26dd2earesponse=jsonsessionkey=tit%2Bdz%2Fux9eXh3FHUDUxlY6x8vo%3D_=1366231163927
200 { queryasyncjobresultresponse :
{accountid:cd06b3dc-a625-11e2-8627-06d4460004b1,userid:cd07b7e6-a625-11e2-8627-06d4460004b1,cmd:org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:Command
failed due to Internal Server
Error},created:2013-04-17T13:39:08-0700,jobid:ff569d61-2474-4fe1-8eec-2701b26dd2ea}
}
management server logs:
2013-04-17 13:39:08,260 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-15:job-64) Executing org.apache.cloudstack.api.command.admin.
storage.PreparePrimaryStorageForMaintenanceCmd for job-64
2013-04-17 13:39:08,268 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-15:job-64) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd
java.lang.NullPointerException
at
com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:1417)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:189)
at
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd.execute(PreparePrimaryStorageForMaintenanceCmd.java:102)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164)
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-04-17 13:39:08,269 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-15:job-64) Complete async job-64, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: null
2013-04-17 13:39:11,295 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===START=== 10.217.252.128 -- GET
command=queryAsyncJobResultjobId=ff569d61-2474-4fe1-8eec-2701b26dd2earesponse=jsonsessionkey=tit%2Bdz%2Fux9eXh3FHUDUxlY6x8vo%3D_=1366231163927
2013-04-17 13:39:11,303 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-17:null) Async job-64 completed
2013-04-17 13:39:11,307 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===END=== 10.217.252.128 -- GET
command=queryAsyncJobResultjobId=ff569d61-2474-4fe1-8eec-2701b26dd2earesponse=jsonsessionkey=tit%2Bdz%2Fux9eXh3FHUDUxlY6x8vo%3D_=1366231163927
2013-04-17 13:39:20,127 DEBUG [cloud.server.StatsCollector]
[jira] [Resolved] (CLOUDSTACK-2843) Support parallel VM deployment with CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-2843. --- Resolution: Fixed For QA to test DeployVm cases * deploy multiple vms for the new network * deploy multiple vms for the existing network in Implemented state * deploy multiple vms from password enabled template * deploy multiple vms with huge userData. Make sure user data was set for all of them * deploy multiple vms from password enabled template. Make sure that the password works for all of them Start Vm cases = * start multiple vms that are in Stopped state * start multiple vms having more than 1 disk attached * start multiple vms with huge user data Stop vm cases * stop multiple vms * execute stop commnad right after start command was sent for the vm StartCommand StopCommand CreateCommand CopyVolumeCommand DhcpEntryCommand PasswordResetCommand UserDataCommand VmDataCommand * Test on different hypervisors * Check that you can turn synchornization back on by changing following parameters values to true (false by default): execute.in.sequence.hypervisor.commands execute.in.sequence.network.element.commands Support parallel VM deployment with CloudStack -- Key: CLOUDSTACK-2843 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2843 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: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.0 When a user deploys multiple instances concurrently, the deployment of these VMs are in fact queued up, so although CloudStack reports that all deployments have started to be created, it would appear in reality that until the 1st instance is deployed, the second, third, etc are queued and waiting to be executed. CS should be able to support parallel VM deployment assuming the cluster resources can handle it. As a part of it, we have to: 1) Set executeInSequence=false for Start/Stop commands (also might make it false for PrimaryStorageDownload command as well) 2) Identify possible implication of turning off the synchronization for those commands, and fix the problematic places in the code. -- 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-2843) Support parallel VM deployment with CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688170#comment-13688170 ] ASF subversion and git services commented on CLOUDSTACK-2843: - Commit d66e9c7b518895c28461118523698b6a7f0fd830 in branch refs/heads/master from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d66e9c7 ] CLOUDSTACK-2843: Provideded an ability to turn off the synchronization being done on the CS agent side, for number of commands participating in Vm deployment process, as parallel deployment is supported on the hypervisor side. The behavior is controlled by global config varirables: execute.in.sequence.hypervisor.commands (false by default) sets/resets the synchronization for commands: = StartCommand StopCommand CreateCommand CopyVolumeCommand execute.in.sequence.network.element.commands (false by default) sets/resets the synchronization for commands: == DhcpEntryCommand SavePasswordCommand UserDataCommand VmDataCommand As a part of the fix, increased the global lock timeout to 30 mins in several VR scripts: === edithosts.sh savepassword.sh userdata.sh to support situations when multiple concurrent calls to the script are being made. Support parallel VM deployment with CloudStack -- Key: CLOUDSTACK-2843 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2843 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: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.0 When a user deploys multiple instances concurrently, the deployment of these VMs are in fact queued up, so although CloudStack reports that all deployments have started to be created, it would appear in reality that until the 1st instance is deployed, the second, third, etc are queued and waiting to be executed. CS should be able to support parallel VM deployment assuming the cluster resources can handle it. As a part of it, we have to: 1) Set executeInSequence=false for Start/Stop commands (also might make it false for PrimaryStorageDownload command as well) 2) Identify possible implication of turning off the synchronization for those commands, and fix the problematic places in the code. -- 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-3016) remove zonetype parameter from list API commands
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688176#comment-13688176 ] ASF subversion and git services commented on CLOUDSTACK-3016: - Commit d5d0142ed4c14e5d4d8fe255486c1437730425a5 in branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d5d0142 ] CLOUDSTACK-3016: listZones API - take in networktype instead of zonetype parameter to be consistent with networktype property in ZoneResponse. remove zonetype parameter from list API commands Key: CLOUDSTACK-3016 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Reporter: Jessica Wang Assignee: Jessica Wang -- 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-2843) Support parallel VM deployment with CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688181#comment-13688181 ] ASF subversion and git services commented on CLOUDSTACK-2843: - Commit 0fe7c5c9353eb1970238015cf48668d196adf82d in branch refs/heads/master-6-17-stable from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0fe7c5c ] CLOUDSTACK-2843: Provideded an ability to turn off the synchronization being done on the CS agent side, for number of commands participating in Vm deployment process, as parallel deployment is supported on the hypervisor side. The behavior is controlled by global config varirables: execute.in.sequence.hypervisor.commands (false by default) sets/resets the synchronization for commands: = StartCommand StopCommand CreateCommand CopyVolumeCommand execute.in.sequence.network.element.commands (false by default) sets/resets the synchronization for commands: == DhcpEntryCommand SavePasswordCommand UserDataCommand VmDataCommand As a part of the fix, increased the global lock timeout to 30 mins in several VR scripts: === edithosts.sh savepassword.sh userdata.sh to support situations when multiple concurrent calls to the script are being made. Support parallel VM deployment with CloudStack -- Key: CLOUDSTACK-2843 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2843 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: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.0 When a user deploys multiple instances concurrently, the deployment of these VMs are in fact queued up, so although CloudStack reports that all deployments have started to be created, it would appear in reality that until the 1st instance is deployed, the second, third, etc are queued and waiting to be executed. CS should be able to support parallel VM deployment assuming the cluster resources can handle it. As a part of it, we have to: 1) Set executeInSequence=false for Start/Stop commands (also might make it false for PrimaryStorageDownload command as well) 2) Identify possible implication of turning off the synchronization for those commands, and fix the problematic places in the code. -- 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] [Closed] (CLOUDSTACK-1866) NPE while getting VPC Netusage statistics @ KVM cloud agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-1866. NPE while getting VPC Netusage statistics @ KVM cloud agent Key: CLOUDSTACK-1866 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1866 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Network Controller Affects Versions: 4.1.0, 4.2.0 Reporter: Sailaja Mada Assignee: Wei Zhou Priority: Blocker Fix For: 4.2.0 Attachments: agent.log, apilog.log, management-server.log Setup: MS : Rhel 6.3 with KVM 6.3 host , Advanced Networking Steps: 1. Stop Management Server and Agent 2. Upgrade the packages of MS and Agent from 4.0 to 4.1 3. Create VPC with no tiers in it. Observation @ Cloud agent log: NPE while getting VPC Netusage statistics @ KVM cloud agent 2013-04-01 12:25:52,938 INFO [cloud.agent.Agent] (agentRequest-Handler-2:null) Ready command is processed: agent id = 1 2013-04-01 12:59:21,517 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-3:null) Using old style bridge name for vlan 814 because existing bridge cloudVirBr814 was found 2013-04-01 12:59:21,599 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-3:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found 2013-04-01 13:00:58,653 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-4:null) Using old style bridge name for vlan 811 because existing bridge cloudVirBr811 was found 2013-04-01 13:00:58,729 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-4:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found 2013-04-01 13:17:05,849 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-2:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found 2013-04-01 13:26:53,202 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-2:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found 2013-04-01 13:40:51,665 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-1:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found 2013-04-01 13:48:39,861 WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:null) Exception: /usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vpc_netusage.sh 169.254.1.225 -l null -c -v null java.lang.NullPointerException at java.lang.ProcessBuilder.start(ProcessBuilder.java:457) at com.cloud.utils.script.Script.execute(Script.java:183) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.VPCNetworkUsage(LibvirtComputingResource.java:2741) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1123) at com.cloud.agent.Agent.processRequest(Agent.java:525) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) at com.cloud.utils.nio.Task.run(Task.java:83) 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-04-01 13:48:39,904 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-5:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found -- 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-3016) remove zonetype parameter from list API commands
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688196#comment-13688196 ] ASF subversion and git services commented on CLOUDSTACK-3016: - Commit 751bf4c54980746df7eebcedae6c1747bbde7aad in branch refs/heads/master-6-17-stable from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=751bf4c ] CLOUDSTACK-3016: listZones API - take in networktype instead of zonetype parameter to be consistent with networktype property in ZoneResponse. remove zonetype parameter from list API commands Key: CLOUDSTACK-3016 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Reporter: Jessica Wang Assignee: Jessica Wang -- 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-1618) Baremetal - Stop VM fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sheng Yang reassigned CLOUDSTACK-1618:
--
Assignee: Sheng Yang (was: frank zhang)
Baremetal - Stop VM fail
Key: CLOUDSTACK-1618
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1618
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Baremetal, Management Server
Affects Versions: 4.2.0
Environment: MS ASF 4.1 build 70
host baremetal guest OS centos 6.3
Reporter: angeline shen
Assignee: Sheng Yang
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.log.gz
1. create basic zone baremetal network type. Add DHCP PXE server. Add
baremetal host, template centos 6.3. Deploy VM with baremetal template
centos 6.3
2.Stop VM . VM was not stopped. After 30 minutes, Timed out . Unable to
stop vm VM[User|z1centos63V1]
2013-03-08 20:21:00,814 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-28) Executing
org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-28
2013-03-08 20:21:00,815 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null)
===END=== 10.216.133.70 -- GET
command=stopVirtualMachineid=562e36e8-36ec-4d0b-8341-ff869bb0483dforced=trueresponse=jsonsessionkey=kQqK9pFlb8STco
ZbZ%2BOqzBtxXng%3D_=1362792722106
2013-03-08 20:51:00,847 DEBUG [agent.manager.AgentAttache]
(Job-Executor-28:job-28) Seq 1-51445943: Waited too long.
2013-03-08 20:51:00,847 INFO [utils.exception.CSExceptionErrorCode]
(Job-Executor-28:job-28) Could not find exception:
com.cloud.exception.OperationTimedoutException in error code list for
exceptions
2013-03-08 20:51:00,847 WARN [agent.manager.AgentAttache]
(Job-Executor-28:job-28) Seq 1-51445943: Timed out on Seq 1-51445943: { Cmd
, MgmtId: 206915885079873, via: 1, Ver: v1, Flags: 100111,
[{StopCommand:{isProxy:false
,vmName:i-2-1-VM,wait:0}}] }
2013-03-08 20:51:00,847 DEBUG [agent.manager.AgentAttache]
(Job-Executor-28:job-28) Seq 1-51445943: Cancelling.
2013-03-08 20:51:00,847 WARN [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-28:job-28) Unable to stop vm VM[User|z1centos63V1]
2013-03-08 20:51:00,902 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-28:job-28) VM state transitted from :Stopping to Running with
event: OperationFailedvm's original host id: 1 new host id: 1 host id before
state t
ransition: 1
2013-03-08 20:51:00,909 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-28) Complete async job-28, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.UserVmResponse@b95ab39
2013-03-08 20:51:00,930 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-28) Done executing
org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-28
2013-03-08 20:51:01,742 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.216.133.70 -- GET
command=queryAsyncJobResultjobId=1043a559-426d-4471-942d-59a56ce40793response=jsonsessionkey=kQqK9pFlb8STcoZbZ%2B
OqzBtxXng%3D_=1362794523111
2013-03-08 20:51:01,751 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-5:null) Async job-28 completed
--
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-1614) Baremetal - Reboot VM fail
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang reassigned CLOUDSTACK-1614: -- Assignee: Sheng Yang (was: frank zhang) Baremetal - Reboot VM fail --- Key: CLOUDSTACK-1614 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1614 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Baremetal Affects Versions: 4.2.0 Environment: MS ASF 4.1 build 70 host baremetal gueest OS centos 6.3 Reporter: angeline shen Assignee: Sheng Yang Priority: Critical Fix For: 4.2.0 Attachments: management-server.log.gz 1. create basic zone baremetal type. Add DHCP PXE server. Add baremetal host, template centos 6.3 Deploy VM with baremetal template centos 6.3 2. reboot VM . No reboot occurred. After 30 minutes, Unable to send the reboot command to host Host [-1-Routing] for the vm VM[User|z1centos63V1] due to operation timeout resultCode: 530, result: Error Code: 530 Error text: Failed to reboot the vm on host Host[-1-Routing] 2013-03-08 19:47:50,254 DEBUG [agent.manager.AgentAttache] (Job-Executor-27:job-27) Seq 1-51445814: Cancelling. 2013-03-08 19:47:50,255 WARN [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-27:job-27) Unable to send the reboot command to host Host[-1-Routing] for the vm VM[User|z1centos63V1] due to operation timeout com.cloud.exception.OperationTimedoutException: Commands 51445814 to Host 1 timed out after 1800 at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:421) at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:511) at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:1036) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:37) at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) at $Proxy109.send(Unknown Source) at com.cloud.vm.VirtualMachineManagerImpl.advanceReboot(VirtualMachineManagerImpl.java:1584) at com.cloud.vm.VirtualMachineManagerImpl.reboot(VirtualMachineManagerImpl.java:1560) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at
[jira] [Assigned] (CLOUDSTACK-1610) Baremetal API addBaremetalPxeKickStartServer fail to prepare PXE server causing create instance with Kickstart style image to fail
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang reassigned CLOUDSTACK-1610: -- Assignee: Sheng Yang (was: frank zhang) Baremetal API addBaremetalPxeKickStartServer fail to prepare PXE server causing create instance with Kickstart style image to fail --- Key: CLOUDSTACK-1610 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1610 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Baremetal, Management Server Affects Versions: 4.2.0 Reporter: angeline shen Assignee: Sheng Yang Priority: Blocker Fix For: 4.2.0 Attachments: management-server.log.2013-03-07.gz, management-server.log.gz, Screenshot-CloudStack - Mozilla Firefox.png, Screenshot-CloudStack - Mozilla Firefox.png 1. Install MS . setup host IPMI. Enable PXE on baremetal host 2. Create baremetal image on NFS server 3. Deploy basic zone with baremetal. 4. curl http://localhost:8096/?command=addBaremetalHostzoneid=403d8b3d-fe32-4fbb-b6dd-4592a21f503epodid=4881c4b1-fb33-42b0-87ba-b900721d2871clusterid=319febb1-2d9d-425e-87a6-d017df85a575hypervisor=BareMetalclustertype=CloudManagedhosttags=largeusername=rootpassword=calvinurl=http%3A%2F%2F10.223.103.48cpunumber=1cpuspeed=2600memory=16384hostmac=bc:30:5b:d4:60:af; curl http://localhost:8096/?command=addBaremetalPxeKickStartServerphysicalnetworkid=f5dbcd99-5656-4b82-b5d5-b1e2f91eec62podid=4881c4b1-fb33-42b0-87ba-b900721d2871url=http://10.223.51.11username=rootpassword=passwordpxeservertype=KICK_STARTtftpdir=/var/lib/tftpboot; curl http://localhost:8096/?command=addBaremetalDhcpphysicalnetworkid=f5dbcd99-5656-4b82-b5d5-b1e2f91eec62podid=4881c4b1-fb33-42b0-87ba-b900721d2871url=http://10.223.51.11dhcpservertype=DHCPDurl=http://10.223.51.11username=rootpassword=password; 5. Deploy Baremetal instance fail with error: Resource [Host:3] is unreachable: Host 3: Unable to start instance due to Cannot prepare pxe server -- 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-3077) Re-enabling Baremetal for MASTER
Sheng Yang created CLOUDSTACK-3077: -- Summary: Re-enabling Baremetal for MASTER Key: CLOUDSTACK-3077 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3077 Project: CloudStack Issue Type: Task Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Sheng Yang Assignee: Sheng Yang Priority: Blocker Fix For: 4.2.0 Due to the stability issue, we've disabled baremetal feature for 4.1 release. But we need to enable it for 4.2 release. This would make https://issues.apache.org/jira/browse/CLOUDSTACK-1773 obsolete. And after enabling, the following bugs would have been fixed as well. https://issues.apache.org/jira/browse/CLOUDSTACK-1610 https://issues.apache.org/jira/browse/CLOUDSTACK-1618 https://issues.apache.org/jira/browse/CLOUDSTACK-1614 https://issues.apache.org/jira/browse/CLOUDSTACK-1440 -- 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-558) Duplicate routerVM entry on network create!
[ https://issues.apache.org/jira/browse/CLOUDSTACK-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-558: Assignee: Alena Prokharchyk Duplicate routerVM entry on network create! --- Key: CLOUDSTACK-558 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-558 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Environment: 3.0.2-4.0 upgrade, CentOS, VMware Reporter: Tamas Monos Assignee: Alena Prokharchyk Priority: Blocker Hi, In 4.0 when trying to create a new network the cloud.vm.VirtualMachineManagerImpl calls the Allocating entries for VM: VM[DomainRouter|r-x-VM twice and this causes mysql exception due to the duplicate entry! 2012-11-29 13:29:27,511 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Creating the router 40 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$88af38d9@1 2012-11-29 13:29:27,517 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Allocating the domR with the hypervisor type VMware 2012-11-29 13:29:27,519 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating entries for VM: VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,523 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating nics for VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,524 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[211|Guest|7] with requested profile NicProfile[0-0-null-10.1.1.1-vlan://937 2012-11-29 13:29:27,537 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Service SecurityGroup is not supported in the network id=211 2012-11-29 13:29:27,539 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[202|Control|3] with requested profile null 2012-11-29 13:29:27,547 WARN [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Can't get the physical network 2012-11-29 13:29:27,548 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[200|Public|1] with requested profile NicProfile[0-0-null-217.27.254.119-vlan://100 2012-11-29 13:29:27,556 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocaing disks for VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,560 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocation completed for VM: VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,560 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Allocating the domR with the hypervisor type VMware 2012-11-29 13:29:27,562 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating entries for VM: VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,565 DEBUG [db.Transaction.Transaction] (Job-Executor-18:job-49) Rolling back the transaction: Time = 3 Name = -AsyncJobManagerImpl$1.run:398-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; called by -Transaction.rollback:887-Transaction.removeUpTo:830-Transaction.close:649-DatabaseCallback.interceptComplete:71-DatabaseCallback.intercept:36-VirtualNetworkApplianceManagerImpl.persist:2476-VirtualNetworkApplianceManagerImpl.persist:235-VirtualMachineManagerImpl.allocate:284-DatabaseCallback.intercept:34-VirtualMachineManagerImpl.allocate:337-VirtualNetworkApplianceManagerImpl.deployRouter:1409-VirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInGuestNetwork:1350 2012-11-29 13:29:27,567 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Lock is released for network id 211 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(2)-Storage(Volume(47|ROOT--Pool(201))] 2012-11-29 13:29:27,567 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Cleaning up because we're unable to implement the network Ntwk[211|Guest|7] -- 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-558) Duplicate routerVM entry on network create!
[ https://issues.apache.org/jira/browse/CLOUDSTACK-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688230#comment-13688230 ] Alena Prokharchyk commented on CLOUDSTACK-558: -- The problem is fixed in 4.1/4.2 with commit c36744a18c9a9e64a8b4c92d2ba43f0f644b5f63 Duplicate routerVM entry on network create! --- Key: CLOUDSTACK-558 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-558 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Environment: 3.0.2-4.0 upgrade, CentOS, VMware Reporter: Tamas Monos Assignee: Alena Prokharchyk Priority: Blocker Hi, In 4.0 when trying to create a new network the cloud.vm.VirtualMachineManagerImpl calls the Allocating entries for VM: VM[DomainRouter|r-x-VM twice and this causes mysql exception due to the duplicate entry! 2012-11-29 13:29:27,511 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Creating the router 40 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$88af38d9@1 2012-11-29 13:29:27,517 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Allocating the domR with the hypervisor type VMware 2012-11-29 13:29:27,519 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating entries for VM: VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,523 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating nics for VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,524 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[211|Guest|7] with requested profile NicProfile[0-0-null-10.1.1.1-vlan://937 2012-11-29 13:29:27,537 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Service SecurityGroup is not supported in the network id=211 2012-11-29 13:29:27,539 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[202|Control|3] with requested profile null 2012-11-29 13:29:27,547 WARN [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Can't get the physical network 2012-11-29 13:29:27,548 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[200|Public|1] with requested profile NicProfile[0-0-null-217.27.254.119-vlan://100 2012-11-29 13:29:27,556 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocaing disks for VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,560 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocation completed for VM: VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,560 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Allocating the domR with the hypervisor type VMware 2012-11-29 13:29:27,562 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating entries for VM: VM[DomainRouter|r-40-VM] 2012-11-29 13:29:27,565 DEBUG [db.Transaction.Transaction] (Job-Executor-18:job-49) Rolling back the transaction: Time = 3 Name = -AsyncJobManagerImpl$1.run:398-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; called by -Transaction.rollback:887-Transaction.removeUpTo:830-Transaction.close:649-DatabaseCallback.interceptComplete:71-DatabaseCallback.intercept:36-VirtualNetworkApplianceManagerImpl.persist:2476-VirtualNetworkApplianceManagerImpl.persist:235-VirtualMachineManagerImpl.allocate:284-DatabaseCallback.intercept:34-VirtualMachineManagerImpl.allocate:337-VirtualNetworkApplianceManagerImpl.deployRouter:1409-VirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInGuestNetwork:1350 2012-11-29 13:29:27,567 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Lock is released for network id 211 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(2)-Storage(Volume(47|ROOT--Pool(201))] 2012-11-29 13:29:27,567 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Cleaning up because we're unable to implement the network Ntwk[211|Guest|7] -- 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-2371) NTier: Deletion of Private Gateway failed due to Null Pointer Exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-2371.
---
Resolution: Fixed
NTier: Deletion of Private Gateway failed due to Null Pointer Exception
---
Key: CLOUDSTACK-2371
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2371
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
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.zip
===
Observations:
===
2013-05-07 18:31:57,693 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null)
===END=== 10.216.132.104 -- GET
command=deletePrivateGatewayid=59ec16d4-a076-4692-9abe-b986cf81cda4response=jsonsessionkey=xMoElKyZsirl3kELteeIURhHbIU%3D_=1367976753038
2013-05-07 18:31:57,695 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) Executing
org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for job-41
2013-05-07 18:31:57,700 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) Sync job-41 execution on object vpc.1
2013-05-07 18:31:57,706 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) job
org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for
job-41 was queued, processing the queue.
2013-05-07 18:31:57,711 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) Executing sync queue item: SyncQueueItemVO {id:21,
queueId: 1, contentType: AsyncJob, contentId: 41, lastProcessMsid:
7508777239729, lastprocessNumber: 21, lastProcessTime: Tue May 07 18:31:57
PDT 2013, created: Tue May 07 18:31:57 PDT 2013}
2013-05-07 18:31:57,712 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) Schedule queued job-41
2013-05-07 18:31:57,718 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-50:job-41) There is a pending process in sync queue(id: 1)
2013-05-07 18:31:57,719 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-51:job-41) Executing
org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for job-41
2013-05-07 18:31:57,727 DEBUG [network.vpc.VpcManagerImpl]
(Job-Executor-51:job-41) Marked gateway VpcGateway[10|10.223.60.32|1] with
state Deleting
2013-05-07 18:31:57,736 DEBUG
[network.router.VpcVirtualNetworkApplianceManagerImpl]
(Job-Executor-51:job-41) Releasing private ip for gateway
com.cloud.network.vpc.PrivateGatewayProfile@eed2c67 from
VM[DomainRouter|r-5-NATONPRVGW]
2013-05-07 18:31:57,743 DEBUG [cloud.network.NetworkModelImpl]
(Job-Executor-51:job-41) Service SecurityGroup is not supported in the
network id=209
2013-05-07 18:31:57,753 DEBUG [agent.transport.Request]
(Job-Executor-51:job-41) Seq 1-275054878: Sending { Cmd , MgmtId:
7508777239729, via: 1, Ver: v1, Flags: 100011,
[{routing.IpAssocVpcCommand:{ipAddresses:[{accountId:1,publicIp:10.223.60.33,sourceNat:true,add:false,oneToOneNat:false,firstIP:false,vlanId:600,vlanGateway:10.223.60.1,vlanNetmask:255.255.255.192,vifMacAddress:06:11:c0:00:00:2b,trafficType:Guest}],accessDetails:{router.guest.ip:10.223.60.33,zone.network.type:Advanced,router.ip:169.254.3.235,router.name:r-5-NATONPRVGW},wait:0}}]
}
2013-05-07 18:31:58,544 DEBUG [agent.transport.Request]
(AgentManager-Handler-5:null) Seq 1-275054878: Processing: { Ans: , MgmtId:
7508777239729, via: 1, Ver: v1, Flags: 10,
[{routing.IpAssocAnswer:{results:[10.223.60.33 -
success],result:true,wait:0}}] }
2013-05-07 18:31:58,544 DEBUG [agent.transport.Request]
(Job-Executor-51:job-41) Seq 1-275054878: Received: { Ans: , MgmtId:
7508777239729, via: 1, Ver: v1, Flags: 10, { IpAssocAnswer } }
2013-05-07 18:31:58,544 DEBUG
[network.router.VpcVirtualNetworkApplianceManagerImpl]
(Job-Executor-51:job-41) Successfully applied ip association for ip
com.cloud.network.vpc.PrivateIpAddress@32595f0d in vpc network
Ntwk[209|Guest|5]
2013-05-07 18:31:58,544 DEBUG
[network.router.VpcVirtualNetworkApplianceManagerImpl]
(Job-Executor-51:job-41) Removing router VM[DomainRouter|r-5-NATONPRVGW] from
private network Ntwk[209|Guest|5] as a part of delete private gateway
2013-05-07 18:31:58,557 DEBUG [cloud.network.NetworkModelImpl]
(Job-Executor-51:job-41) Service SecurityGroup is not supported in the
network id=209
2013-05-07 18:31:58,598 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-51:job-41) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd
java.lang.NullPointerException
at
com.cloud.hypervisor.HypervisorGuruBase.toNicTO(HypervisorGuruBase.java:72)
[jira] [Commented] (CLOUDSTACK-2371) NTier: Deletion of Private Gateway failed due to Null Pointer Exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688245#comment-13688245
]
Alena Prokharchyk commented on CLOUDSTACK-2371:
---
Should be fixed with c1ad3b7974449f457a1cc4e50fe7af260d1c5bf6
NTier: Deletion of Private Gateway failed due to Null Pointer Exception
---
Key: CLOUDSTACK-2371
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2371
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
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.zip
===
Observations:
===
2013-05-07 18:31:57,693 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null)
===END=== 10.216.132.104 -- GET
command=deletePrivateGatewayid=59ec16d4-a076-4692-9abe-b986cf81cda4response=jsonsessionkey=xMoElKyZsirl3kELteeIURhHbIU%3D_=1367976753038
2013-05-07 18:31:57,695 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) Executing
org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for job-41
2013-05-07 18:31:57,700 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) Sync job-41 execution on object vpc.1
2013-05-07 18:31:57,706 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) job
org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for
job-41 was queued, processing the queue.
2013-05-07 18:31:57,711 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) Executing sync queue item: SyncQueueItemVO {id:21,
queueId: 1, contentType: AsyncJob, contentId: 41, lastProcessMsid:
7508777239729, lastprocessNumber: 21, lastProcessTime: Tue May 07 18:31:57
PDT 2013, created: Tue May 07 18:31:57 PDT 2013}
2013-05-07 18:31:57,712 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-50:job-41) Schedule queued job-41
2013-05-07 18:31:57,718 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-50:job-41) There is a pending process in sync queue(id: 1)
2013-05-07 18:31:57,719 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-51:job-41) Executing
org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for job-41
2013-05-07 18:31:57,727 DEBUG [network.vpc.VpcManagerImpl]
(Job-Executor-51:job-41) Marked gateway VpcGateway[10|10.223.60.32|1] with
state Deleting
2013-05-07 18:31:57,736 DEBUG
[network.router.VpcVirtualNetworkApplianceManagerImpl]
(Job-Executor-51:job-41) Releasing private ip for gateway
com.cloud.network.vpc.PrivateGatewayProfile@eed2c67 from
VM[DomainRouter|r-5-NATONPRVGW]
2013-05-07 18:31:57,743 DEBUG [cloud.network.NetworkModelImpl]
(Job-Executor-51:job-41) Service SecurityGroup is not supported in the
network id=209
2013-05-07 18:31:57,753 DEBUG [agent.transport.Request]
(Job-Executor-51:job-41) Seq 1-275054878: Sending { Cmd , MgmtId:
7508777239729, via: 1, Ver: v1, Flags: 100011,
[{routing.IpAssocVpcCommand:{ipAddresses:[{accountId:1,publicIp:10.223.60.33,sourceNat:true,add:false,oneToOneNat:false,firstIP:false,vlanId:600,vlanGateway:10.223.60.1,vlanNetmask:255.255.255.192,vifMacAddress:06:11:c0:00:00:2b,trafficType:Guest}],accessDetails:{router.guest.ip:10.223.60.33,zone.network.type:Advanced,router.ip:169.254.3.235,router.name:r-5-NATONPRVGW},wait:0}}]
}
2013-05-07 18:31:58,544 DEBUG [agent.transport.Request]
(AgentManager-Handler-5:null) Seq 1-275054878: Processing: { Ans: , MgmtId:
7508777239729, via: 1, Ver: v1, Flags: 10,
[{routing.IpAssocAnswer:{results:[10.223.60.33 -
success],result:true,wait:0}}] }
2013-05-07 18:31:58,544 DEBUG [agent.transport.Request]
(Job-Executor-51:job-41) Seq 1-275054878: Received: { Ans: , MgmtId:
7508777239729, via: 1, Ver: v1, Flags: 10, { IpAssocAnswer } }
2013-05-07 18:31:58,544 DEBUG
[network.router.VpcVirtualNetworkApplianceManagerImpl]
(Job-Executor-51:job-41) Successfully applied ip association for ip
com.cloud.network.vpc.PrivateIpAddress@32595f0d in vpc network
Ntwk[209|Guest|5]
2013-05-07 18:31:58,544 DEBUG
[network.router.VpcVirtualNetworkApplianceManagerImpl]
(Job-Executor-51:job-41) Removing router VM[DomainRouter|r-5-NATONPRVGW] from
private network Ntwk[209|Guest|5] as a part of delete private gateway
2013-05-07 18:31:58,557 DEBUG [cloud.network.NetworkModelImpl]
(Job-Executor-51:job-41) Service SecurityGroup is not supported in the
network id=209
2013-05-07 18:31:58,598 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-51:job-41) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd
[jira] [Commented] (CLOUDSTACK-2304) [ZWPS]NPE while migrating volume from one zone wide primary to another
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688258#comment-13688258
]
Rajesh Battala commented on CLOUDSTACK-2304:
issue is reproducible on latest master.
[ZWPS]NPE while migrating volume from one zone wide primary to another
--
Key: CLOUDSTACK-2304
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2304
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: KVM/VMware deployment with Zone wide primary storage
Reporter: Srikanteswararao Talluri
Assignee: Rajesh Battala
Priority: Critical
Fix For: 4.2.0
Attachments: Archive.zip
Try to migrate a volume from one zone wide primary storage to another.
===START=== 10.252.241.40 -- GET
command=migrateVolumestorageid=230ae4af-0446-3929-a8cd-63ab88f31ab1volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173response=jsonsessionkey=yMNGYR64PRQhdJaPj99Bvs2KDDE%3D_=1367485037836
2013-05-02 20:06:59,384 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-3:null) submit async job-97, details: AsyncJobVO {id:97,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId:
null, cmd: org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,sessionkey:yMNGYR64PRQhdJaPj99Bvs2KDDE\u003d,ctxUserId:2,storageid:230ae4af-0446-3929-a8cd-63ab88f31ab1,_:1367485037836,volumeid:d9efc3d8-1612-4998-95d7-c713e90b7173,ctxAccountId:2,ctxStartEventId:310},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-02 20:06:59,388 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.252.241.40 -- GET
command=migrateVolumestorageid=230ae4af-0446-3929-a8cd-63ab88f31ab1volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173response=jsonsessionkey=yMNGYR64PRQhdJaPj99Bvs2KDDE%3D_=1367485037836
2013-05-02 20:06:59,391 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-97
2013-05-02 20:06:59,423 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-66:job-97) migrate volume failed:java.lang.NullPointerException
2013-05-02 20:06:59,424 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Complete async job-97, jobStatus: 1, resultCode: 0,
result: null
2013-05-02 20:06:59,434 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Done executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-97
--
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-2073) java.lang.NullPointerException when trying to put a Zone wide primary storage in maintenance mode.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688255#comment-13688255
]
Rajesh Battala commented on CLOUDSTACK-2073:
issue is reproducible on latest master.
java.lang.NullPointerException when trying to put a Zone wide primary storage
in maintenance mode.
--
Key: CLOUDSTACK-2073
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2073
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: Build from master
Reporter: Sangeetha Hariharan
Assignee: Rajesh Battala
Priority: Critical
Fix For: 4.2.0
java.lang.NullPointerException when trying to put a Zone wide primary storage
in maintenance mode.
Steps to reproduce the problem:
Configured a NFS primary storage zone wide.
Tried to put the primary storage in maintenance mode.
It fails with Command failed due to Internal Server Error.
2013-04-17 13:39:08,259 INFO [cloud.api.ApiServer] (catalina-exec-1:null)
(userId=2 accountId=2 sessionId=A716D4755FFE21C87D8EA5E2E459AD8C)
10.217.252.128 -- GET
command=enableStorageMaintenanceid=27f5ddfc-f967-3e4e-91f1-ee19890c9577response=jsonsessionkey=tit%2Bdz%2Fux9eXh3FHUDUxlY6x8vo%3D_=1366231160791
200 { prepareprimarystorageformaintenanceresponse :
{jobid:ff569d61-2474-4fe1-8eec-2701b26dd2ea} }
2013-04-17 13:39:11,306 INFO [cloud.api.ApiServer] (catalina-exec-17:null)
(userId=2 accountId=2 sessionId=A716D4755FFE21C87D8EA5E2E459AD8C)
10.217.252.128 -- GET
command=queryAsyncJobResultjobId=ff569d61-2474-4fe1-8eec-2701b26dd2earesponse=jsonsessionkey=tit%2Bdz%2Fux9eXh3FHUDUxlY6x8vo%3D_=1366231163927
200 { queryasyncjobresultresponse :
{accountid:cd06b3dc-a625-11e2-8627-06d4460004b1,userid:cd07b7e6-a625-11e2-8627-06d4460004b1,cmd:org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:Command
failed due to Internal Server
Error},created:2013-04-17T13:39:08-0700,jobid:ff569d61-2474-4fe1-8eec-2701b26dd2ea}
}
management server logs:
2013-04-17 13:39:08,260 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-15:job-64) Executing org.apache.cloudstack.api.command.admin.
storage.PreparePrimaryStorageForMaintenanceCmd for job-64
2013-04-17 13:39:08,268 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-15:job-64) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd
java.lang.NullPointerException
at
com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:1417)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:189)
at
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd.execute(PreparePrimaryStorageForMaintenanceCmd.java:102)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164)
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-04-17 13:39:08,269 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-15:job-64) Complete async job-64, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: null
2013-04-17 13:39:11,295 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===START=== 10.217.252.128 -- GET
command=queryAsyncJobResultjobId=ff569d61-2474-4fe1-8eec-2701b26dd2earesponse=jsonsessionkey=tit%2Bdz%2Fux9eXh3FHUDUxlY6x8vo%3D_=1366231163927
2013-04-17 13:39:11,303 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-17:null) Async job-64 completed
2013-04-17 13:39:11,307 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===END=== 10.217.252.128 -- GET
command=queryAsyncJobResultjobId=ff569d61-2474-4fe1-8eec-2701b26dd2earesponse=jsonsessionkey=tit%2Bdz%2Fux9eXh3FHUDUxlY6x8vo%3D_=1366231163927
[jira] [Resolved] (CLOUDSTACK-1352) KVM 6.3 snapshot - when snapshot of ROOT volume is being created, snapshot of data volume remains in Creating state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-1352. - Resolution: Invalid KVM 6.3 snapshot - when snapshot of ROOT volume is being created, snapshot of data volume remains in Creating state --- Key: CLOUDSTACK-1352 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1352 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Storage Controller Affects Versions: 4.1.0, 4.2.0 Environment: MS rhel 6.3 latest build 2/20/2013 host rhel 6.3 KVM Reporter: angeline shen Assignee: Venkata Siva Vijayendra Bhamidipati Fix For: 4.2.0 MS rhel 6.3 latest build 2/20/2013 host rhel 6.3 KVM latest build 2/20/2013 1. advance zone. VPC : VPC network: create VMs 2. while snapshot of ROOT volume is being taken, take snapshot of DATA volume Result: Error dialog: There is other active snapshot tasks on the instance to which the volume is attached, please try again later snapshot of data volume remains in Creating state but is deletable. This behavior is different than Cloudplatform where snapshot of ROOT volume and DATA volume can be taken simultaneously. -- 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-2397) Not able to deploy a Vm with userdata in Shared network.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-2397:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
Not able to deploy a Vm with userdata in Shared network.
Key: CLOUDSTACK-2397
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2397
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: Build from pvlan
Reporter: Sangeetha Hariharan
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
Attachments: logs.rar
Steps to reproduce the problem:
Advanced zone with Xen 6.1 hosts.
Create a Shared network by passing private Vlan.
Deploy a Vm in this network by passing userdata.
Vm deployment errors out.
GET
command=deployVirtualMachinezoneId=b5b71f7b-19a4-4f32-9512-d9b0eac382f3templateId=b79f666e-b760-11e2-a38a-06f4b42bhypervisor=XenServerserviceOfferingId=4480e764-0d39-4950-86a9-a422e7ae3b7dnetworkIds=a2fb9fda-f6a1-4348-beb1-4e29367b3dbddisplayname=yo-userdataname=yo-userdataresponse=jsonsessionkey=LqAvWj%2BQ0xeg3eqoKXMhOoA%2B53E%3Duserdata=Y2F0Y2ggbWUgaWYgeW91IGNhbg==
200 { deployvirtualmachineresponse :
{id:05f1426d-6650-470f-8f6e-36b18b3bcd8c,jobid:e3bd77a2-aca2-4c39-b85f-9f928c7af000}
}
Following exception seen in management server log:
2013-05-08 13:47:27,815 DEBUG [agent.transport.Request]
(Job-Executor-18:job-39) Seq 1-1674709490: Executing: { Cmd , MgmtId:
7647994577963, via: 1, Ver: v1, Flags: 100111,
[{routing.SavePasswordCommand:{password:fnirq_cnffjbeq,vmIpAddress:10.223.161.116,vmName:yo-userdata,accessDetails:{router.guest.ip:10.223.161.110,zone.network.type:Advanced,router.ip:169.254.0.235,router.name:r-13-VM},wait:0}},{routing.VmDataCommand:{vmIpAddress:10.223.161.116,vmName:yo-userdata,accessDetails:{router.guest.ip:10.223.161.110,zone.network.type:Advanced,router.ip:169.254.0.235,router.name:r-13-VM},wait:0}}]
}
2013-05-08 13:47:27,815 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-164:null) Seq 1-1674709490: Executing request
2013-05-08 13:47:29,899 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-05-08 13:47:30,039 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-05-08 13:47:33,199 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2013-05-08 13:47:33,200 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-05-08 13:47:33,280 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2013-05-08 13:47:33,281 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-05-08 13:47:37,894 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-164:null) Seq 1-1674709490: Response Received:
2013-05-08 13:47:37,895 DEBUG [agent.transport.Request]
(DirectAgent-164:null) Seq 1-1674709490: Processing: { Ans: , MgmtId:
7647994577963, via: 1, Ver: v1, Flags: 110,
[{Answer:{result:true,wait:0}},{Answer:{result:false,details:vm_data
failed,wait:0}}] }
2013-05-08 13:47:37,895 DEBUG [agent.manager.AgentAttache]
(DirectAgent-164:null) Seq 1-1674709490: No more commands found
2013-05-08 13:47:37,895 DEBUG [agent.transport.Request]
(Job-Executor-18:job-39) Seq 1-1674709490: Received: { Ans: , MgmtId:
7647994577963, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
2013-05-08 13:47:37,895 INFO [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-18:job-39) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
unreachable: Unable to apply userdata and password entry on router
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3496)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2790)
at
com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:861)
at
com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:1611)
at
com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:1716)
at
[jira] [Commented] (CLOUDSTACK-3016) remove zonetype parameter from list API commands
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688310#comment-13688310 ] ASF subversion and git services commented on CLOUDSTACK-3016: - Commit 2d10ae7580018611919be070bc51818f476bc1e4 in branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2d10ae7 ] CLOUDSTACK-3016: UI - (1) remove obsolete code that pass zonetype to API calls. (2) network menu: use listZonesnetworktype=Advanced to determine which section to show. remove zonetype parameter from list API commands Key: CLOUDSTACK-3016 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Reporter: Jessica Wang Assignee: Jessica Wang -- 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-3016) remove zonetype parameter from list API commands
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688311#comment-13688311 ] ASF subversion and git services commented on CLOUDSTACK-3016: - Commit afd8645f917ed1726929825c176da60690aa7915 in branch refs/heads/master-6-17-stable from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=afd8645 ] CLOUDSTACK-3016: UI - (1) remove obsolete code that pass zonetype to API calls. (2) network menu: use listZonesnetworktype=Advanced to determine which section to show. remove zonetype parameter from list API commands Key: CLOUDSTACK-3016 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Reporter: Jessica Wang Assignee: Jessica Wang -- 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-2770) UI to add Baremetal DHCP server, Baremetal PXE server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688377#comment-13688377 ] ASF subversion and git services commented on CLOUDSTACK-2770: - Commit d51e552ed9782ac4dba90c6a92a625d66a076118 in branch refs/heads/baremetal-4.2 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d51e552 ] CLOUDSTACK-2770: UI - Infrastructure menu - physical netework - network service providers - add Baremetal DHCP, Baremetal PXE. UI to add Baremetal DHCP server, Baremetal PXE server - Key: CLOUDSTACK-2770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2770 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jessica Wang Assignee: Jessica Wang http://support.citrix.com/article/CTX135163 Cannot Add PXE/DHCP Server to Setup BareMetal Provisioning -- 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-3078) [Automation] Unable to create dedicated VLAN in Guest Network
Rayees Namathponnan created CLOUDSTACK-3078: --- Summary: [Automation] Unable to create dedicated VLAN in Guest Network Key: CLOUDSTACK-3078 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3078 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: Master Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.2.0 Test case “test_guest_vlan_range.py” failing in BVT environment; while debugging this test noticed below error “2013-06-18 14:41:42,780 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) ===START=== 10.216.133.100 -- GET command=dedicateGuestVlanRangeresponse=jsonsessionkey=B0tIw0cl1VktTB0Tkm4AoxlMtKo%3Dphysicalnetworkid=261047ea-c3e7-4fb8-8a25-5a90d79dc943vlanrange=2354-2356domainid=5c80ab3b-71cb-4819-8b0f-6140145263a7account=a_=1371580887060 2013-06-18 14:41:42,794 INFO [cloud.api.ApiServer] (catalina-exec-6:null) Cannot dedicate guest vlan range. Physical isolation type of network 200 is not VLAN” Here the guest VLAN range information mysql select * from physical_network; +-+--+--++-+---+---++-+-+-+ | id | uuid | name | data_center_id | vnet| speed | domain_id | broadcast_domain_range | state | created | removed | +-+--+--++-+---+---++-+-+-+ | 200 | 261047ea-c3e7-4fb8-8a25-5a90d79dc943 | Sandbox-pnet | 1 | 2301-2352;2354-2356 | NULL | NULL | ZONE | Enabled | 2013-06-17 21:21:55 | NULL| | 201 | afe4ec42-f7ac-4b70-8e2a-f77782fe458f | Sandbox-pnet | 2 | 2181-2210 | NULL | NULL | ZONE | Enabled | 2013-06-17 21:24:41 | NULL| +-+--+--++-+---+---++-+-+-+ 2 rows in set (0.00 sec) mysql select * from physical_network_isolation_methods; Empty set (0.00 sec) I am trying to create dedicated VLAN range for “2354-2356”, but it failed with above error During create a guest network with the vlan, we are not checking isolation method, we shouldn't add the same check during guest network creation -- 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-2770) UI to add Baremetal DHCP server, Baremetal PXE server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688376#comment-13688376 ] ASF subversion and git services commented on CLOUDSTACK-2770: - Commit 0293875e01a8c1937e0f9d2ae49edbea23d9bc4e in branch refs/heads/baremetal-4.2 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0293875 ] CLOUDSTACK-2770: UI - Infrastructure menu - physical netework - network service providers - Baremetal PXE - Add Baremetal PXE Device dialog - add Tftp Root Diectory field. UI to add Baremetal DHCP server, Baremetal PXE server - Key: CLOUDSTACK-2770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2770 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jessica Wang Assignee: Jessica Wang http://support.citrix.com/article/CTX135163 Cannot Add PXE/DHCP Server to Setup BareMetal Provisioning -- 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-1737) Unable to create advance security group zone
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Xu resolved CLOUDSTACK-1737.
Resolution: Fixed
fixed by branch merge
Unable to create advance security group zone
-
Key: CLOUDSTACK-1737
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1737
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: Jayapal Reddy
Assignee: Anthony Xu
Priority: Critical
Fix For: 4.2.0
Attachments: AdvancedSg.jpeg
Creating advanced security zone on master branch failed with below error:
network must have SecurityGroup provider in security group enabled zone
Logs:
2013-03-20 10:53:58,265 DEBUG [cloud.network.NetworkServiceImpl]
(Job-Executor-6:job-6) updating state of the service provider id=2 on
physical network: 200 to state: Enabled
2013-03-20 10:53:58,363 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-6:job-6) Complete async job-6, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.ProviderResponse@8daa3e
2013-03-20 10:53:58,384 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-6:job-6) Done executing
org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd
for job-6
2013-03-20 10:54:01,263 DEBUG [cloud.api.ApiServlet]
(19080391@qtp-20859304-2:null) ===START=== 10.146.0.132 -- GET
command=queryAsyncJobResultjobId=8348379f-4144-4671-ab01-7de61c6b63d6response=jsonsessionkey=kZtTOwwZtEAbomInGNk7imMpG1Q%3D_=1363757041216
2013-03-20 10:54:01,266 DEBUG [cloud.api.ApiServlet]
(23128481@qtp-20859304-3:null) ===START=== 10.146.0.132 -- GET
command=queryAsyncJobResultjobId=84bbc9c0-bd9f-4bd6-b8ac-7e84379ff7caresponse=jsonsessionkey=kZtTOwwZtEAbomInGNk7imMpG1Q%3D_=1363757041239
2013-03-20 10:54:01,388 DEBUG [cloud.async.AsyncJobManagerImpl]
(23128481@qtp-20859304-3:null) Async job-6 completed
2013-03-20 10:54:01,396 DEBUG [cloud.async.AsyncJobManagerImpl]
(19080391@qtp-20859304-2:null) Async job-5 completed
2013-03-20 10:54:01,459 DEBUG [cloud.api.ApiServlet]
(23128481@qtp-20859304-3:null) ===END=== 10.146.0.132 -- GET
command=queryAsyncJobResultjobId=84bbc9c0-bd9f-4bd6-b8ac-7e84379ff7caresponse=jsonsessionkey=kZtTOwwZtEAbomInGNk7imMpG1Q%3D_=1363757041239
2013-03-20 10:54:01,463 DEBUG [cloud.api.ApiServlet]
(19080391@qtp-20859304-2:null) ===END=== 10.146.0.132 -- GET
command=queryAsyncJobResultjobId=8348379f-4144-4671-ab01-7de61c6b63d6response=jsonsessionkey=kZtTOwwZtEAbomInGNk7imMpG1Q%3D_=1363757041216
2013-03-20 10:54:01,541 DEBUG [cloud.api.ApiServlet]
(19080391@qtp-20859304-2:null) ===START=== 10.146.0.132 -- GET
command=updateNetworkServiceProviderstate=Enabledid=902f12b6-ec80-4f32-bb78-3359b2b65b06response=jsonsessionkey=kZtTOwwZtEAbomInGNk7imMpG1Q%3D_=1363757041503
2013-03-20 10:54:01,614 DEBUG [cloud.async.AsyncJobManagerImpl]
(19080391@qtp-20859304-2:null) submit async job-7, details: AsyncJobVO {id:7,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId:
null, cmd:
org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd,
cmdOriginator: null, cmdInfo:
{id:902f12b6-ec80-4f32-bb78-3359b2b65b06,response:json,sessionkey:kZtTOwwZtEAbomInGNk7imMpG1Q\u003d,ctxUserId:2,state:Enabled,_:1363757041503,ctxAccountId:2,ctxStartEventId:22},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 8796763348531,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-03-20 10:54:01,629 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-7:job-7) Executing
org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd
for job-7
2013-03-20 10:54:01,669 DEBUG [cloud.api.ApiServlet]
(19080391@qtp-20859304-2:null) ===END=== 10.146.0.132 -- GET
command=updateNetworkServiceProviderstate=Enabledid=902f12b6-ec80-4f32-bb78-3359b2b65b06response=jsonsessionkey=kZtTOwwZtEAbomInGNk7imMpG1Q%3D_=1363757041503
2013-03-20 10:54:01,730 DEBUG [cloud.network.NetworkServiceImpl]
(Job-Executor-7:job-7) updating state of the service provider id=1 on
physical network: 200 to state: Enabled
2013-03-20 10:54:01,783 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-7:job-7) Complete async job-7, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.ProviderResponse@1eabdef
2013-03-20 10:54:01,818 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-7:job-7) Done executing
org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd
for job-7
2013-03-20
[jira] [Commented] (CLOUDSTACK-1405) ZWPS: listStoragePool API doesn't accept scope parameter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688460#comment-13688460 ] ASF subversion and git services commented on CLOUDSTACK-1405: - Commit 2abca44da62af45b0071420903dc7b6bd467c0d8 in branch refs/heads/master-6-17-stable from [~edison] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2abca44 ] CLOUDSTACK-1405: add scope type in liststoragepoolcmd ZWPS: listStoragePool API doesn't accept scope parameter Key: CLOUDSTACK-1405 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1405 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: advanced zone Reporter: Srikanteswararao Talluri Assignee: edison su Priority: Critical Fix For: 4.2.0 listStoragePool API doesn't accept scope parameter -- 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-1405) ZWPS: listStoragePool API doesn't accept scope parameter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] edison su resolved CLOUDSTACK-1405. --- Resolution: Fixed ZWPS: listStoragePool API doesn't accept scope parameter Key: CLOUDSTACK-1405 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1405 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: advanced zone Reporter: Srikanteswararao Talluri Assignee: edison su Priority: Critical Fix For: 4.2.0 listStoragePool API doesn't accept scope parameter -- 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-3015) VPC virtual router lists deleted nics
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen resolved CLOUDSTACK-3015. -- Resolution: Fixed VPC virtual router lists deleted nics - Key: CLOUDSTACK-3015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3015 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0, 4.2.0 Reporter: Marcus Sorensen Assignee: Min Chen Priority: Blocker Labels: integration-test Fix For: 4.1.1, 4.2.0 Create a VPC Create a network in VPC Create a VM in network in VPC Shut down VM Wait awhile Observed: Something cleans up the unused network in the VPC, removing the guest network nic from the VPC router. Start VM Observed: New nic is allocated for VPC router List routers Observed: Router shows both old and new nics. We need to either avoid cleaning up these nics when the aren't used, or avoid showing them whenever a VPC/router is queried for nics. As a bonus, I've occasionally seen vpcs fail to be deletable. It seemed to be because some of its nics had no broadcast URI (the removed ones), and a NULL pointer was thrown. -- 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-1639) Failed to enable primary storage to maintenance mode [Primary storage added at the cluster level]
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-1639.
---
Resolution: Fixed
should be fixed in f18a1d6f140608ba77b54fec9976ed5318495ec4, which is committed
into master at April, could your try to test it again?
Failed to enable primary storage to maintenance mode [Primary storage added
at the cluster level]
-
Key: CLOUDSTACK-1639
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1639
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
Reporter: Sailaja Mada
Assignee: edison su
Priority: Critical
Fix For: 4.2.0
Setup: Advanced networking zone with Xen 6.1
Steps:
1. Tried to enable primary storage to maintenance mode which is in up state,
Observation : It failed with below exception.
2013-03-12 12:28:40,965 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.144.7.13 -- GET
command=listStoragePoolsid=ef996b6b-80d7-3c64-b83a-7017cd620c28response=jsonsessionkey=hDfOx9R3UY3sQnY4xMSW8G%2BINEE%3D_=1363071600847
2013-03-12 12:28:41,404 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-14:null) Ping from 4
2013-03-12 12:28:41,447 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-15:null) Ping from 3
2013-03-12 12:28:43,011 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 10.144.7.13 -- GET
command=enableStorageMaintenanceid=ef996b6b-80d7-3c64-b83a-7017cd620c28response=jsonsessionkey=hDfOx9R3UY3sQnY4xMSW8G%2BINEE%3D_=1363071602844
2013-03-12 12:28:43,034 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-1:null) submit async job-74, details: AsyncJobVO {id:74,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId:
202, cmd:
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:ef996b6b-80d7-3c64-b83a-7017cd620c28,sessionkey:hDfOx9R3UY3sQnY4xMSW8G+INEE\u003d,ctxUserId:2,_:1363071602844,ctxAccountId:2,ctxStartEventId:101},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 73143235720,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-03-12 12:28:43,036 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.144.7.13 -- GET
command=enableStorageMaintenanceid=ef996b6b-80d7-3c64-b83a-7017cd620c28response=jsonsessionkey=hDfOx9R3UY3sQnY4xMSW8G%2BINEE%3D_=1363071602844
2013-03-12 12:28:43,038 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-51:job-74) Executing
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd
for job-74
2013-03-12 12:28:43,046 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-51:job-74) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd
com.cloud.exception.InvalidParameterValueException: Primary storage with id
202 is not ready for migration, as the status is:Up
at
com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:1411)
at
com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:190)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
at
com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:40)
at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
[jira] [Assigned] (CLOUDSTACK-1510) NPE when primary storage is added with wrong path
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-1510:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
NPE when primary storage is added with wrong path
--
Key: CLOUDSTACK-1510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Minor
Fix For: 4.2.0
Steps :
1. Configure Advanced zone
2. Tried to add second nfs primary storage with wrong path.
Observation: It failed with NPE
2013-03-05 15:02:16,535 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:203,uuid:40e80e79-ac1b-31d1-a067-1ec03e7bc67b,host:10.102.192.100,path:/cpg_vol/sailaja/priamry,port:2049,type:NetworkFilesystem},localPath:/mnt//40e80e79-ac1b-31d1-a067-1ec03e7bc67b,wait:0}}]
}
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 1-16676: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)\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:1110)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
java.lang.Thread.run(Thread.java:679)\n,wait:0}}] }
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Received: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-03-05 15:02:16,702 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-25:null) Details from executing class
com.cloud.agent.api.ModifyStoragePoolCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
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-03-05 15:02:16,708 WARN [cloud.storage.StorageManagerImpl]
(catalina-exec-25:null) Unable to establish a connection between
Host[-1-Routing] and Pool[203|NetworkFilesystem]
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203]
is unreachable: Unable establish connection from storage head to storage pool
203 due to java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
[jira] [Commented] (CLOUDSTACK-3027) Object_Store_Refactor - Uploaded template S3 content-type is not appropriate.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688501#comment-13688501 ] Min Chen commented on CLOUDSTACK-3027: -- We can use content-type header returned from HttpClient.GetMethod to set the content type when we upload the object to S3. I tried curl HEAD command for a .vhd file, got this: Mins-MacBook-Pro:cloud-asf minc$ curl -i -X HEAD http://people.apache.org/~bhaisaab/vms/ttylinux_pv.vhd HTTP/1.1 200 OK Date: Wed, 19 Jun 2013 21:38:53 GMT Server: Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.1e DAV/2 Last-Modified: Tue, 11 Sep 2012 05:03:57 GMT ETag: 1b89568-3018200-4c96600604940 Accept-Ranges: bytes Content-Length: 50430464 Content-Type: text/plain Connection: Keep-Alive It seems that curl will treat a .vhd file as text/plain. If I issued the HEAD command for a compressed /vhd: Mins-MacBook-Pro:cloud-asf minc$ curl -i -X HEAD http://nfs1.lab.vmops.com/templates/campo_qa/systemvmtemplate-2013-06-12-master-xen.vhd.bz2 HTTP/1.1 200 OK Date: Wed, 19 Jun 2013 21:39:24 GMT Server: Apache/2.2.3 (CentOS) Last-Modified: Thu, 13 Jun 2013 18:13:30 GMT ETag: 11210005-d32a50f-4df0d16630680 Accept-Ranges: bytes Content-Length: 221422863 Connection: close Content-Type: application/x-bzip2 application/x-bzip2 makes sense. Object_Store_Refactor - Uploaded template S3 content-type is not appropriate. - Key: CLOUDSTACK-3027 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3027 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 This bug is related to the object_store branch. 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. 4. The template will be uploaded to S3. Next using s3cmd or other tool, have a look at the Content-Type of the object that is stored by issuing either a HEAD or a GET request on that object. Here is what I got when i captured the HEAD request using ngrep. === HEAD request and response === HEAD /template/tmpl/2/201/201-2-f9a12429-7cf4-3df5-b81c-420f09c1bbcd/tinyLinux.vhd.gz HTTP/1.1. Host: hello.s3.cloudian.com:18080. Accept-Encoding: identity. Date: Mon, 17 Jun 2013 05:06:19 GMT. Content-Length: 0. Authorization: AWS 00d25034c817eeb8c095:g/S63k9LHeZfz73l+moWm7MJ7z0=. User-Agent: Boto/2.9.4 (linux2). . ## T 10.181.164.132:18080 - 10.181.164.198:50450 [AP] HTTP/1.1 200 OK. Date: Mon, 17 Jun 2013 05:06:19 GMT. x-amz-request-id: A55A3220D70B11E2. Last-Modified: Fri, 14 Jun 2013 07:05:27 GMT. ETag: 5b5c3506aef231519d0434f9749c951d-5. Content-Type: application/x-www-form-urlencoded; charset=utf-8. Content-Length: 25712307. === end of HEAD request and response = Notice in the HTTP response that the Content-Type header is set to application/x-www-form-urlencoded; charset=utf-8. This does not correctly describe the template content type. The Content-Type was set by the client (Cloudstack) in the Multipart Upload Initiate request at the beginning of the upload and should be fixed at that point. I haven't looked at the code but perhaps we need to set a header or add another parameter when initiating the multipart upload. Of course, this begs the question... well what is the correct content type? I looked around to see if I could find one for .vhd files but with no luck. Perhaps application/octet-stream or even application/x-gzip (as this particular object is compressed). -- 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-1389) Interactive Password Prompts during Management Server Startup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688505#comment-13688505 ] Ian Duffy commented on CLOUDSTACK-1389: --- Any progress or workaround for this? Interactive Password Prompts during Management Server Startup - Key: CLOUDSTACK-1389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1389 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0, 4.2.0 Environment: devcloud Reporter: John Burwell Assignee: Abhinandan Prateek Labels: security Fix For: 4.2.0 When starting the management with no SSL certificate present, the system attempts to run a shell script that requires interactive password entry. Executing the following steps with a user that is either non-sudoer or a sudoer that requires a password authentication to perform sudo actions (and who has not already authenticated to sudo), execute the following commands from root directory of a cloudstack/4.1 checkout: 1. mvn -P developer clean install 2. mvn -pl :cloud-client-ui jetty:run During the startup process, the management server will not find the cloud.keystore in the the client/target/cloud-client-ui-4.1-SNAPSHOT/WEB-INF/classes directory, and attempt to generate an SSL certificate using the following shell scripts: sudo keytool -genkey -keystore /Users/jburwell/Documents/projects/cloudstack/src/cloudstack-basho/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/cloud.keystore -store pass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn=Cloudstack User,ou=0.8.31,o=0.8.31,c=Unknown The following is a capture of the script timeout error from the vmops.log: 2013-02-27 09:52:17,157 INFO [cloud.server.ConfigurationServerImpl] (Timer-2:null) SSL keystore located at /Users/jburwell/Docum ents/projects/cloudstack/src/cloudstack-basho/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/cloud.keystore 2013-02-27 09:52:17,176 DEBUG [utils.script.Script] (Timer-2:null) Executing: sudo keytool -genkey -keystore /Users/jburwell/Docu ments/projects/cloudstack/src/cloudstack-basho/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/cloud.keystore -store pass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn=Cloudstack User,ou=0.8.31,o=0.8.31,c=Unknown 2013-02-27 09:52:22,188 WARN [utils.script.Script] (Script-1:null) Interrupting script. 2013-02-27 09:52:22,190 WARN [utils.script.Script] (Timer-2:null) Timed out: sudo keytool -genkey -keystore /Users/jburwell/Docu ments/projects/cloudstack/src/cloudstack-basho/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/cloud.keystore -store pass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn=Cloudstack User,ou=0.8.31,o=0.8.31,c=Unknown . Ou tput is: dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid 2013-02-27 09:52:22,191 WARN [cloud.server.ConfigurationServerImpl] (Timer-2:null) Would use fail-safe keystore to continue. java.io.IOException: Fail to generate certificate!: timeout at com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:490) at com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:511) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:272) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:144) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:8 0) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:37) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at
[jira] [Created] (CLOUDSTACK-3079) Unable to change interval of host PingCommand as global parameter ping.timeout is not used in calculating interval
Alena Prokharchyk created CLOUDSTACK-3079: - Summary: Unable to change interval of host PingCommand as global parameter ping.timeout is not used in calculating interval Key: CLOUDSTACK-3079 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3079 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0, 4.0.0, 4.2.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.0 ping.timeout is not being counted when calculating the interval. We always multiply ping.interval by 3 (hardcoded in ClusteredAgentManagerImpl) -- 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-3079) Unable to change interval of host PingCommand as global parameter ping.timeout is not used in calculating interval
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688536#comment-13688536 ] ASF subversion and git services commented on CLOUDSTACK-3079: - Commit 0a4e65126fd297a7e04ee746b51ebd0cd8137998 in branch refs/heads/master from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0a4e651 ] CLOUDSTACK-3079: Use global var ping.timeout as a multiplier to ping.interval before announcing an agent has timed out. The multiplier used to be hardcoded to 3 Unable to change interval of host PingCommand as global parameter ping.timeout is not used in calculating interval -- Key: CLOUDSTACK-3079 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3079 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, 4.1.0, 4.2.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.0 ping.timeout is not being counted when calculating the interval. We always multiply ping.interval by 3 (hardcoded in ClusteredAgentManagerImpl) -- 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-3079) Unable to change interval of host PingCommand as global parameter ping.timeout is not used in calculating interval
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-3079. --- Resolution: Fixed Unable to change interval of host PingCommand as global parameter ping.timeout is not used in calculating interval -- Key: CLOUDSTACK-3079 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3079 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, 4.1.0, 4.2.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.0 ping.timeout is not being counted when calculating the interval. We always multiply ping.interval by 3 (hardcoded in ClusteredAgentManagerImpl) -- 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-3007) cloudstack-specific tomcat servlet engine is getting stopped in around 2 mins after restart it.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-3007. --- Resolution: Duplicate cloudstack-specific tomcat servlet engine is getting stopped in around 2 mins after restart it. --- Key: CLOUDSTACK-3007 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3007 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Reporter: Yugandhar Yetham Hi Team, Please help me on the below issue. CloudStack-management Tomcat Servelet is getting stopped in around 2 mins after restart. and the UI page also will be active as tomcat servelet is running. We won't get the UI page as soon as Tomcat Servelet getting stops. We have checked for the all logs. But i couldn't understand anything here and also it is not much clear to understand that. Kindly let me know the what might be the problem -- 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-2920) VPC network from shared network offering for VPC does not work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688543#comment-13688543 ] Alena Prokharchyk commented on CLOUDSTACK-2920: --- Prasanna: 1) You can't create Shared network for VPC 2) But the vm that belongs to Isolated VPC network, can also belong to the Shared network outside of VPC. VPC network from shared network offering for VPC does not work -- Key: CLOUDSTACK-2920 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2920 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: Prasanna Santhanam Fix For: 4.2.0 Can we create shared networks inside a VPC? If yes - why does the UI filter out the network offerings in the VPC dialog on listing networks using forvpc=true guestiptype=Isolated? If no - we can get rid of a test suite - TestVMLifeCycleSharedNwVPC. But was it supported before and dropped recently? I was able to create a networkoffering with vpc=true and guestIpType=Shared, but the VPC network creation fails with Network offering can't be used for VPC networks -- 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-2565) ExternalLoadBalancerDeviceVO's gslbProvider setter is a nop
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-2565.
---
Resolution: Fixed
Fixed with 45d2e60656a7c9b2b4171bc63450afa229ca4e75
ExternalLoadBalancerDeviceVO's gslbProvider setter is a nop
---
Key: CLOUDSTACK-2565
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2565
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API
Affects Versions: 4.0.2
Reporter: Dave Brosius
Assignee: Dave Brosius
Priority: Trivial
Attachments: 2565.txt
public void setGslbProvider(boolean gslbProvider) {
gslbProvider = gslbProvider;
}
is missing a this.
added in patch
--
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-2531) when comparing scopes, compare scope ids by value, not reference.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-2531. --- Resolution: Fixed Fix Version/s: 4.2.0 Fixed with 49faa002e220311f10a5f3fad66a22836dad when comparing scopes, compare scope ids by value, not reference. - Key: CLOUDSTACK-2531 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2531 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.0.2 Reporter: Dave Brosius Assignee: Dave Brosius Priority: Trivial Fix For: 4.2.0 Attachments: 2531.txt code compares Long values with == which will work for Long cached values, but not others switched to use .equals -- 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-2954) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does n
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk updated CLOUDSTACK-2954:
--
Component/s: (was: API)
UI
Unable to execute API command queryasyncjobresult due to invalid value.
Invalid parameter jobid value=undefined due to incorrect long value format,
or entity does not exist or due to incorrect parameter annotation for the
field in api cmd class
-
Key: CLOUDSTACK-2954
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2954
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: prashant kumar mishra
Priority: Minor
Fix For: 4.2.0
Attachments: DB_Logs.rar
MS log is full of this message
API
--
--
http://10.147.*.*:8080/client/api?command=queryAsyncJobResultjobId=undefinedresponse=json
sessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031697935
response
{ queryasyncjobresultresponse :
{uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to
execute API command queryasyncjobresult due to invalid value. Invalid
parameter jobid value=undefined due to incorrect long value format, or entity
does not exist or due to incorrect parameter annotation for the field in api
cmd class.} }
Log
-
2013-06-12 11:28:24,137 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-18:null) Async job-161 completed
2013-06-12 11:28:24,145 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031453325
2013-06-12 11:28:25,881 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===START=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963
2013-06-12 11:28:25,892 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-23:null) Object entity uuid = undefined does not exist in the
database.
2013-06-12 11:28:25,892 INFO [cloud.api.ApiServer] (catalina-exec-23:null)
Unable to execute API command queryasyncjobresult due to invalid value.
Invalid parameter jobid value=undefined due to incorrect long value format,
or entity does not exist or due to incorrect parameter annotation for the
field in api cmd class.
2013-06-12 11:28:25,894 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963
2013-06-12 11:28:26,107 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315
2013-06-12 11:28:26,126 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-25:null) Async job-159 completed
2013-06-12 11:28:26,134 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315
2013-06-12 11:28:27,076 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
===START=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198
2013-06-12 11:28:27,086 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-10:null) Object entity uuid = undefined does not exist in the
database.
2013-06-12 11:28:27,086 INFO [cloud.api.ApiServer] (catalina-exec-10:null)
Unable to execute API command queryasyncjobresult due to invalid value.
Invalid parameter jobid value=undefined due to incorrect long value format,
or entity does not exist or due to incorrect parameter annotation for the
field in api cmd class.
2013-06-12 11:28:27,088 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198
2013-06-12 11:28:27,118 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
===START=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031456327
2013-06-12 11:28:27,138 DEBUG
[jira] [Commented] (CLOUDSTACK-2954) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688570#comment-13688570
]
Alena Prokharchyk commented on CLOUDSTACK-2954:
---
UI bug. Looks like UI passes undefined value to the jobId parameter, and this
value is invalid.
Unable to execute API command queryasyncjobresult due to invalid value.
Invalid parameter jobid value=undefined due to incorrect long value format,
or entity does not exist or due to incorrect parameter annotation for the
field in api cmd class
-
Key: CLOUDSTACK-2954
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2954
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: prashant kumar mishra
Priority: Minor
Fix For: 4.2.0
Attachments: DB_Logs.rar
MS log is full of this message
API
--
--
http://10.147.*.*:8080/client/api?command=queryAsyncJobResultjobId=undefinedresponse=json
sessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031697935
response
{ queryasyncjobresultresponse :
{uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to
execute API command queryasyncjobresult due to invalid value. Invalid
parameter jobid value=undefined due to incorrect long value format, or entity
does not exist or due to incorrect parameter annotation for the field in api
cmd class.} }
Log
-
2013-06-12 11:28:24,137 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-18:null) Async job-161 completed
2013-06-12 11:28:24,145 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031453325
2013-06-12 11:28:25,881 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===START=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963
2013-06-12 11:28:25,892 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-23:null) Object entity uuid = undefined does not exist in the
database.
2013-06-12 11:28:25,892 INFO [cloud.api.ApiServer] (catalina-exec-23:null)
Unable to execute API command queryasyncjobresult due to invalid value.
Invalid parameter jobid value=undefined due to incorrect long value format,
or entity does not exist or due to incorrect parameter annotation for the
field in api cmd class.
2013-06-12 11:28:25,894 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963
2013-06-12 11:28:26,107 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315
2013-06-12 11:28:26,126 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-25:null) Async job-159 completed
2013-06-12 11:28:26,134 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315
2013-06-12 11:28:27,076 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
===START=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198
2013-06-12 11:28:27,086 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-10:null) Object entity uuid = undefined does not exist in the
database.
2013-06-12 11:28:27,086 INFO [cloud.api.ApiServer] (catalina-exec-10:null)
Unable to execute API command queryasyncjobresult due to invalid value.
Invalid parameter jobid value=undefined due to incorrect long value format,
or entity does not exist or due to incorrect parameter annotation for the
field in api cmd class.
2013-06-12 11:28:27,088 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198
2013-06-12 11:28:27,118 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
===START=== 10.252.192.7 -- GET
[jira] [Commented] (CLOUDSTACK-2917) Router vm failed to start after setting up network.throttling.rate to 0.1 (100Kbit/sec)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688594#comment-13688594 ] Alena Prokharchyk commented on CLOUDSTACK-2917: --- Networking code expects the network throttling to be Integer (no floating point number), while global config is allowed to be set to float. Router vm failed to start after setting up network.throttling.rate to 0.1 (100Kbit/sec) - Key: CLOUDSTACK-2917 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2917 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: prashant kumar mishra Fix For: 4.2.0 Attachments: Logs.rar Tried to set Network throttling rate to 100Kb/sec, VR failed to start. Steps to Repro -- 1-Stop VR 2-set GP network.throttling.rate to 0.1(100Kbit/sec) 3-Restart MS 4-Start router Expected -- VR should come up Actual -- VR failed to start Log - 2013-06-10 08:59:12,777 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-2:job-45) Failed to start instance VM[DomainRouter|r-12-VM] java.lang.NumberFormatException: For input string: 0.1 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:481) at java.lang.Integer.parseInt(Integer.java:514) at com.cloud.configuration.ConfigurationManagerImpl.getServiceOfferingNetworkRate(ConfigurationManagerImpl.java:4633) at com.cloud.network.NetworkModelImpl.getNetworkRate(NetworkModelImpl.java:945) at com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2032) at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2021) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:842) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2720) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1861) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3118) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3068) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110) 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-10 08:59:12,796 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-2:job-45) Cleaning up resources for the vm VM[DomainRouter|r-12-VM] in Starting state -- 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-1940) Job-Executor and StartCommand in sequence
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-1940.
---
Resolution: Fixed
Fixed with d66e9c7b518895c28461118523698b6a7f0fd830
Job-Executor and StartCommand in sequence
-
Key: CLOUDSTACK-1940
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1940
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API
Affects Versions: 4.0.0, 4.0.1, 4.1.0, 4.2.0
Reporter: Jeronimo
Assignee: Alena Prokharchyk
Labels: patch
Hi List.
I'm having issues when deploying a big number of virtual machines across a
number of nodes.
the imporession that i get ( from the logs) is that the AsyncJobExecutor is
pulling jobs from the queue and do them one by one (which when you are
deploying a big number of virtual machines could take a long while)
After sending emails to the dev group they've asked me to open a BUG.
Here more data:
I can see the override on agent/api/StartCommand.java
@Override
public boolean executeInSequence() {
return true;
}
--
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-1939) Job-Executor and StartCommand in sequence
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-1939.
---
Resolution: Fixed
Fixed with d66e9c7b518895c28461118523698b6a7f0fd830
Job-Executor and StartCommand in sequence
-
Key: CLOUDSTACK-1939
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1939
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API
Affects Versions: 4.0.0, 4.0.1
Reporter: Jeronimo
Assignee: Alena Prokharchyk
Priority: Minor
Hi List.
I'm having issues when deploying a big number of virtual machines across a
number of nodes.
the imporession that i get ( from the logs) is that the AsyncJobExecutor is
pulling jobs from the queue and do them one by one (which when you are
deploying a big number of virtual machines could take a long while)
After sending emails to the dev group they've asked me to open a BUG.
Here more data:
I can see the override on agent/api/StartCommand.java
@Override
public boolean executeInSequence() {
return true;
}
--
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-1939) Job-Executor and StartCommand in sequence
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk reassigned CLOUDSTACK-1939:
-
Assignee: Alena Prokharchyk
Job-Executor and StartCommand in sequence
-
Key: CLOUDSTACK-1939
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1939
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API
Affects Versions: 4.0.0, 4.0.1
Reporter: Jeronimo
Assignee: Alena Prokharchyk
Priority: Minor
Hi List.
I'm having issues when deploying a big number of virtual machines across a
number of nodes.
the imporession that i get ( from the logs) is that the AsyncJobExecutor is
pulling jobs from the queue and do them one by one (which when you are
deploying a big number of virtual machines could take a long while)
After sending emails to the dev group they've asked me to open a BUG.
Here more data:
I can see the override on agent/api/StartCommand.java
@Override
public boolean executeInSequence() {
return true;
}
--
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-1938) Add the ability to limit number of networks for a given Accounts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688615#comment-13688615 ] Alena Prokharchyk commented on CLOUDSTACK-1938: --- We do limit it. There is a global config parameter max.account.networks for that matter. Add the ability to limit number of networks for a given Accounts Key: CLOUDSTACK-1938 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1938 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Francois Gaudreault Assignee: Alena Prokharchyk Priority: Minor We can limit the number of networks per project, but not by domain or accounts... We can do it globally, but It would be great to add this per account/domain limits. -- 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-1938) Add the ability to limit number of networks for a given Accounts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-1938: - Assignee: Alena Prokharchyk Add the ability to limit number of networks for a given Accounts Key: CLOUDSTACK-1938 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1938 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Francois Gaudreault Assignee: Alena Prokharchyk Priority: Minor We can limit the number of networks per project, but not by domain or accounts... We can do it globally, but It would be great to add this per account/domain limits. -- 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-1938) Add the ability to limit number of networks for a given Accounts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-1938. --- Resolution: Not A Problem Add the ability to limit number of networks for a given Accounts Key: CLOUDSTACK-1938 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1938 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Francois Gaudreault Assignee: Alena Prokharchyk Priority: Minor We can limit the number of networks per project, but not by domain or accounts... We can do it globally, but It would be great to add this per account/domain limits. -- 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-1869) listVolumes with listall=true API call as ROOT admin not returning all volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-1869: - Assignee: Alena Prokharchyk listVolumes with listall=true API call as ROOT admin not returning all volumes --- Key: CLOUDSTACK-1869 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1869 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Volumes Affects Versions: 4.0.1 Environment: CentOS 6.3 + KVM + NFS Reporter: Nick Wales Assignee: Alena Prokharchyk Priority: Minor Labels: api, volumes Calling the listVolumes method with listall = true as root admin doesn't return volumes in subdomain projects owned by other accounts. -- 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-1869) listVolumes with listall=true API call as ROOT admin not returning all volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-1869. --- Resolution: Won't Fix This is by design: * when no projectId is passed in, and listAll=true, we list all the resources in the system except for project resources. * when projectId=valid project id is passed in, we list only resources of this project * when projectId=-1 is passed in, we return all project based resources for all the projects in the system. listVolumes with listall=true API call as ROOT admin not returning all volumes --- Key: CLOUDSTACK-1869 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1869 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Volumes Affects Versions: 4.0.1 Environment: CentOS 6.3 + KVM + NFS Reporter: Nick Wales Assignee: Alena Prokharchyk Priority: Minor Labels: api, volumes Calling the listVolumes method with listall = true as root admin doesn't return volumes in subdomain projects owned by other accounts. -- 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-1678) Destroying errored out VM deployment fails with NPE
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-1678.
---
Resolution: Fixed
Fixed with 6e55776795d2bf3c71f02ee8a38ad29e5d303f9d
Destroying errored out VM deployment fails with NPE
---
Key: CLOUDSTACK-1678
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1678
Project: CloudStack
Issue Type: Bug
Components: Management Server
Affects Versions: 4.0.1
Environment: EL6.3 - KVM 4.0.1
Reporter: David Nalley
Assignee: Alena Prokharchyk
Steps to reproduce:
* Attempt to deploy an instance that will fail (in this case deploying with a
service offering with a storage tag that doesn't exist)
* Watch deployment error out (VM shows up as error in list of instances)
* Attempt to destroy the instance.
* See the following exception.
2013-03-14 02:27:32,374 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 70.194.132.238 -- GET
command=destroyVirtualMachineid=d65e6997-f26a-499f-ba38-f2b8908d0200response=jsonsessionkey=YZBscdunOv2wR%2FOHDtAS8LpkylM%3D_=1363242452991
2013-03-14 02:27:32,531 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-1:null) submit async job-238, details: AsyncJobVO {id:238,
userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
instanceId: 89, cmd: com.cloud.api.commands.DestroyVMCmd, cmdOriginator:
null, cmdInfo:
{response:json,id:d65e6997-f26a-499f-ba38-f2b8908d0200,sessionkey:YZBscdunOv2wR/OHDtAS8LpkylM\u003d,ctxUserId:2,_:1363242452991,ctxAccountId:2,ctxStartEventId:1062},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 206915886132947,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-03-14 02:27:32,534 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-142:job-238) Executing com.cloud.api.commands.DestroyVMCmd for
job-238
2013-03-14 02:27:32,535 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 70.194.132.238 -- GET
command=destroyVirtualMachineid=d65e6997-f26a-499f-ba38-f2b8908d0200response=jsonsessionkey=YZBscdunOv2wR%2FOHDtAS8LpkylM%3D_=1363242452991
2013-03-14 02:27:32,593 ERROR [cloud.api.ApiDispatcher]
(Job-Executor-142:job-238) Exception while executing DestroyVMCmd:
java.lang.NullPointerException
at
com.cloud.utils.AnnotationHelper.getTableName(AnnotationHelper.java:34)
at
com.cloud.utils.exception.RuntimeCloudException.addProxyObject(RuntimeCloudException.java:53)
at
com.cloud.vm.UserVmManagerImpl.getHypervisorTypeOfUserVM(UserVmManagerImpl.java:3260)
at com.cloud.api.commands.DestroyVMCmd.execute(DestroyVMCmd.java:101)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
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:722)
2013-03-14 02:27:32,597 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-142:job-238) Complete async job-238, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: null
--
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] [Closed] (CLOUDSTACK-2170) NPE while updating the updatePhysicalNetwork to enable state with invalid ID
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk closed CLOUDSTACK-2170. - The issue is fixed with 6e55776795d2bf3c71f02ee8a38ad29e5d303f9d NPE while updating the updatePhysicalNetwork to enable state with invalid ID - Key: CLOUDSTACK-2170 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2170 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Reporter: Sailaja Mada Assignee: Likitha Shetty Fix For: 4.2.0 Setup: Advanced Networking Zone with Nexus, MS : RHEL 6.3 Steps: 1. Add VNMC provider to cloudstack: http://localhost/client/api?command=addNetworkServiceProviderphysicalnetworkid=200name=CiscoVnmc 2) Tried to update the above provider state as enabled: (http://10.102.192.194:8096/client/api?command=updatePhysicalNetworkid=4state=Enabled) Observation: NPE while updating the updatePhysicalNetwork to enable state with invalid ID 2013-04-24 16:41:19,108 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-12:job-12) Executing org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd for job-12 2013-04-24 16:41:19,147 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-12:job-12) Unexpected exception while executing org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd java.lang.NullPointerException at com.cloud.utils.AnnotationHelper.getTableName(AnnotationHelper.java:34) at com.cloud.utils.exception.CloudRuntimeException.addProxyObject(CloudRuntimeException.java:59) at com.cloud.network.NetworkServiceImpl.updatePhysicalNetwork(NetworkServiceImpl.java:2301) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd.execute(UpdatePhysicalNetworkCmd.java:104) 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-04-24 16:41:19,148 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-12:job-12) Complete async job-12, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null 2013-04-24 16:41:23,502 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) VmStatsCollector is running... This XML file does not appear to have any style information associated with it. The document tree is shown below. queryasyncjobresultresponse cloud-stack-version=4.2.0-SNAPSHOTaccountid1daa4ce0-acca-11e2-8b37-c2ae49691a00/accountiduserid1dac1908-acca-11e2-8b37-c2ae49691a00/useridcmdorg.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd/cmdjobstatus2/jobstatusjobprocstatus0/jobprocstatusjobresultcode530/jobresultcodejobresulttypeobject/jobresulttypejobresulterrorcode530/errorcodeerrortextCommand failed due to Internal Server Error/errortext/jobresultcreated2013-04-24T16:41:19+0530/createdjobid6e7887c1-83da-4d02-98e7-2cc36949364b/jobid/queryasyncjobresultresponse -- 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-1510) NPE when primary storage is added with wrong path
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688642#comment-13688642
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-1510:
-
Three issues were seen when fixing this issue:
a) Invalid path of primary storage is resulting in NPE
b) No error dialog is showing up in GUI because the storage management layer
isn't propagating the exception upward.
c) If the KVM cloud agent on the KVM host is down, and an attempt is made to
add primary storage, the primary storage is failing to be added as expected,
but is getting entered into the database in the storage_pool table, so it shows
up in the GUI as well.
Working on the fixes for these. Will update bug with review board link once the
fixes are ready.
NPE when primary storage is added with wrong path
--
Key: CLOUDSTACK-1510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Minor
Fix For: 4.2.0
Steps :
1. Configure Advanced zone
2. Tried to add second nfs primary storage with wrong path.
Observation: It failed with NPE
2013-03-05 15:02:16,535 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:203,uuid:40e80e79-ac1b-31d1-a067-1ec03e7bc67b,host:10.102.192.100,path:/cpg_vol/sailaja/priamry,port:2049,type:NetworkFilesystem},localPath:/mnt//40e80e79-ac1b-31d1-a067-1ec03e7bc67b,wait:0}}]
}
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 1-16676: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)\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:1110)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
java.lang.Thread.run(Thread.java:679)\n,wait:0}}] }
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Received: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-03-05 15:02:16,702 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-25:null) Details from executing class
com.cloud.agent.api.ModifyStoragePoolCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
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-03-05 15:02:16,708 WARN [cloud.storage.StorageManagerImpl]
(catalina-exec-25:null) Unable to establish a connection between
Host[-1-Routing] and Pool[203|NetworkFilesystem]
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203]
is unreachable: Unable establish connection from storage head to storage pool
203 due to java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
[jira] [Comment Edited] (CLOUDSTACK-1510) NPE when primary storage is added with wrong path
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688642#comment-13688642
]
Venkata Siva Vijayendra Bhamidipati edited comment on CLOUDSTACK-1510 at
6/19/13 11:47 PM:
---
Three issues were seen when fixing this issue:
a) Invalid path of primary storage is resulting in NPE
b) No error dialog is showing up in GUI because the storage management layer
isn't propagating the exception upward.
c) If the KVM cloud agent on the KVM host is down, and an attempt is made to
add primary storage, whether the storage path is valid or not, the primary
storage is failing to be added as expected, but is getting entered into the
database in the storage_pool table, so it shows up in the GUI as well.
Working on the fixes for these. Will update bug with review board link once the
fixes are ready.
was (Author: vijayendrabvs):
Three issues were seen when fixing this issue:
a) Invalid path of primary storage is resulting in NPE
b) No error dialog is showing up in GUI because the storage management layer
isn't propagating the exception upward.
c) If the KVM cloud agent on the KVM host is down, and an attempt is made to
add primary storage, the primary storage is failing to be added as expected,
but is getting entered into the database in the storage_pool table, so it shows
up in the GUI as well.
Working on the fixes for these. Will update bug with review board link once the
fixes are ready.
NPE when primary storage is added with wrong path
--
Key: CLOUDSTACK-1510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Minor
Fix For: 4.2.0
Steps :
1. Configure Advanced zone
2. Tried to add second nfs primary storage with wrong path.
Observation: It failed with NPE
2013-03-05 15:02:16,535 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:203,uuid:40e80e79-ac1b-31d1-a067-1ec03e7bc67b,host:10.102.192.100,path:/cpg_vol/sailaja/priamry,port:2049,type:NetworkFilesystem},localPath:/mnt//40e80e79-ac1b-31d1-a067-1ec03e7bc67b,wait:0}}]
}
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 1-16676: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)\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:1110)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
java.lang.Thread.run(Thread.java:679)\n,wait:0}}] }
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Received: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-03-05 15:02:16,702 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-25:null) Details from executing class
com.cloud.agent.api.ModifyStoragePoolCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
[jira] [Commented] (CLOUDSTACK-3027) Object_Store_Refactor - Uploaded template S3 content-type is not appropriate.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688667#comment-13688667 ] ASF subversion and git services commented on CLOUDSTACK-3027: - Commit f0ebb0596dd26c7156e96ce2fedb25bca2af75f1 in branch refs/heads/object_store from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0ebb05 ] CLOUDSTACK-3027:Object_Store_Refactor - Uploaded template S3 content-type is not appropriate Object_Store_Refactor - Uploaded template S3 content-type is not appropriate. - Key: CLOUDSTACK-3027 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3027 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 This bug is related to the object_store branch. 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. 4. The template will be uploaded to S3. Next using s3cmd or other tool, have a look at the Content-Type of the object that is stored by issuing either a HEAD or a GET request on that object. Here is what I got when i captured the HEAD request using ngrep. === HEAD request and response === HEAD /template/tmpl/2/201/201-2-f9a12429-7cf4-3df5-b81c-420f09c1bbcd/tinyLinux.vhd.gz HTTP/1.1. Host: hello.s3.cloudian.com:18080. Accept-Encoding: identity. Date: Mon, 17 Jun 2013 05:06:19 GMT. Content-Length: 0. Authorization: AWS 00d25034c817eeb8c095:g/S63k9LHeZfz73l+moWm7MJ7z0=. User-Agent: Boto/2.9.4 (linux2). . ## T 10.181.164.132:18080 - 10.181.164.198:50450 [AP] HTTP/1.1 200 OK. Date: Mon, 17 Jun 2013 05:06:19 GMT. x-amz-request-id: A55A3220D70B11E2. Last-Modified: Fri, 14 Jun 2013 07:05:27 GMT. ETag: 5b5c3506aef231519d0434f9749c951d-5. Content-Type: application/x-www-form-urlencoded; charset=utf-8. Content-Length: 25712307. === end of HEAD request and response = Notice in the HTTP response that the Content-Type header is set to application/x-www-form-urlencoded; charset=utf-8. This does not correctly describe the template content type. The Content-Type was set by the client (Cloudstack) in the Multipart Upload Initiate request at the beginning of the upload and should be fixed at that point. I haven't looked at the code but perhaps we need to set a header or add another parameter when initiating the multipart upload. Of course, this begs the question... well what is the correct content type? I looked around to see if I could find one for .vhd files but with no luck. Perhaps application/octet-stream or even application/x-gzip (as this particular object is compressed). -- 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-702) Multiple IP Ranges
[ https://issues.apache.org/jira/browse/CLOUDSTACK-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688696#comment-13688696 ] ASF subversion and git services commented on CLOUDSTACK-702: Commit b3fb4851ee204b1be514e389c66fd6e08d4b7fa4 in branch refs/heads/master from [~yasker] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b3fb485 ] Fix regression of return Userdata provider when caller asked for DHCP It's introduced by: commit 052c24c4d1c881f791b804dbb9c2fc083af7da36 Author: Bharat Kumar bharat.ku...@citrix.com Date: Mon May 13 17:02:27 2013 +0530 CLOUDSTACK-702: Multiple ip ranges in different subnets. This commit get userdata provider when caller asked for dhcp provider, thus result in trouble e.g. ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-11:job-10) Unexpected exception while executing org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd java.lang.ClassCastException: com.cloud.baremetal.networkservice.BaremetalUserdataElement_EnhancerByCloudStack_5dee69d2 cannot be cast to com.cloud.network.element.DhcpServiceProvider at com.cloud.network.NetworkManagerImpl.getDhcpServiceProvider(NetworkManagerImpl.java:3309) ... Multiple IP Ranges -- Key: CLOUDSTACK-702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-702 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: Manan Shah Assignee: Bharat Kumar Fix For: 4.2.0 Requirements described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Multiple+IP+Ranges Requirements discussion email thread link: http://markmail.org/search/?q=[ASFCS41]+Multiple+IP+Ranges+list%3Aorg.apache.incubator.cloudstack-dev -- 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-3079) Unable to change interval of host PingCommand as global parameter ping.timeout is not used in calculating interval
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688733#comment-13688733 ] ASF subversion and git services commented on CLOUDSTACK-3079: - Commit 0a4e65126fd297a7e04ee746b51ebd0cd8137998 in branch refs/heads/object_store from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0a4e651 ] CLOUDSTACK-3079: Use global var ping.timeout as a multiplier to ping.interval before announcing an agent has timed out. The multiplier used to be hardcoded to 3 Unable to change interval of host PingCommand as global parameter ping.timeout is not used in calculating interval -- Key: CLOUDSTACK-3079 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3079 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, 4.1.0, 4.2.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.0 ping.timeout is not being counted when calculating the interval. We always multiply ping.interval by 3 (hardcoded in ClusteredAgentManagerImpl) -- 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-1405) ZWPS: listStoragePool API doesn't accept scope parameter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688735#comment-13688735 ] ASF subversion and git services commented on CLOUDSTACK-1405: - Commit 11b9d5ff6442aafede62502a59b035f52b28c633 in branch refs/heads/object_store from [~edison] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=11b9d5f ] CLOUDSTACK-1405: add scope type in liststoragepoolcmd ZWPS: listStoragePool API doesn't accept scope parameter Key: CLOUDSTACK-1405 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1405 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: advanced zone Reporter: Srikanteswararao Talluri Assignee: edison su Priority: Critical Fix For: 4.2.0 listStoragePool API doesn't accept scope parameter -- 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-3015) VPC virtual router lists deleted nics
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688734#comment-13688734 ] ASF subversion and git services commented on CLOUDSTACK-3015: - Commit 5cd6d6944a5b80aa401587c90fb0f69863ec4a96 in branch refs/heads/object_store from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5cd6d69 ] CLOUDSTACK-3015: VPC virtual router lists deleted nics VPC virtual router lists deleted nics - Key: CLOUDSTACK-3015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3015 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0, 4.2.0 Reporter: Marcus Sorensen Assignee: Min Chen Priority: Blocker Labels: integration-test Fix For: 4.1.1, 4.2.0 Create a VPC Create a network in VPC Create a VM in network in VPC Shut down VM Wait awhile Observed: Something cleans up the unused network in the VPC, removing the guest network nic from the VPC router. Start VM Observed: New nic is allocated for VPC router List routers Observed: Router shows both old and new nics. We need to either avoid cleaning up these nics when the aren't used, or avoid showing them whenever a VPC/router is queried for nics. As a bonus, I've occasionally seen vpcs fail to be deletable. It seemed to be because some of its nics had no broadcast URI (the removed ones), and a NULL pointer was thrown. -- 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-1869) listVolumes with listall=true API call as ROOT admin not returning all volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688746#comment-13688746 ] Nick Wales commented on CLOUDSTACK-1869: Using -1 makes it easier however none of these options allow me to see every project based and non project based instance at once which is what I really want. It would also be useful in the UI to see all the instances of a host in the infrastructure tab rather than just the non project based instances as in my mind this should be the place I go to shuffle my resources around. listVolumes with listall=true API call as ROOT admin not returning all volumes --- Key: CLOUDSTACK-1869 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1869 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Volumes Affects Versions: 4.0.1 Environment: CentOS 6.3 + KVM + NFS Reporter: Nick Wales Assignee: Alena Prokharchyk Priority: Minor Labels: api, volumes Calling the listVolumes method with listall = true as root admin doesn't return volumes in subdomain projects owned by other accounts. -- 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-3080) listVirtualMachines tag search refinement no longer working
Nick Wales created CLOUDSTACK-3080:
--
Summary: listVirtualMachines tag search refinement no longer
working
Key: CLOUDSTACK-3080
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3080
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API
Affects Versions: 4.1.0
Reporter: Nick Wales
Priority: Critical
In 4.0.1 I was able to make a call to the API similar to the below which would
return only the instances tagged as eg (app=my_app_name).
{ :command=listVirtualMachines,
tags[0].value=my_app_name,
tags[0].key=app}
(I'm using the cloudstack_helper ruby gem which explains the formatting)
However since I have upgraded to 4.1 I now get returned every instance for the
same query.
--
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-3069) [UI]Quickview of POD is not displaying any info in UI.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688804#comment-13688804 ] ASF subversion and git services commented on CLOUDSTACK-3069: - Commit 791eb601b75456d111324e5b9b21a4a4b1edef43 in branch refs/heads/master from [~isaacchi...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=791eb60 ] CLOUDSTACK-3069: [UI]Quickview of POD is not displaying any info in UI [UI]Quickview of POD is not displaying any info in UI. -- Key: CLOUDSTACK-3069 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3069 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: CloudPlatform-4.0-91-rhel6.3. Reporter: manasaveloori Assignee: Isaac Chiang Priority: Minor Fix For: 4.2.0 Attachments: pod.jpg 1.Have a CS with any zone. 2.Go to Infrastructure-Pods-Quickview Observation: Quickview option of the POD not displaying any information. API is working fine. Attached is the SC 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] [Closed] (CLOUDSTACK-3069) [UI]Quickview of POD is not displaying any info in UI.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Chiang closed CLOUDSTACK-3069. Resolution: Fixed Please refer to commit: 791eb6 [UI]Quickview of POD is not displaying any info in UI. -- Key: CLOUDSTACK-3069 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3069 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: CloudPlatform-4.0-91-rhel6.3. Reporter: manasaveloori Assignee: Isaac Chiang Priority: Minor Fix For: 4.2.0 Attachments: pod.jpg 1.Have a CS with any zone. 2.Go to Infrastructure-Pods-Quickview Observation: Quickview option of the POD not displaying any information. API is working fine. Attached is the SC 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] [Commented] (CLOUDSTACK-1510) NPE when primary storage is added with wrong path
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688810#comment-13688810
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-1510:
-
Patch posted to https://reviews.apache.org/r/11984/
NPE when primary storage is added with wrong path
--
Key: CLOUDSTACK-1510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Minor
Fix For: 4.2.0
Steps :
1. Configure Advanced zone
2. Tried to add second nfs primary storage with wrong path.
Observation: It failed with NPE
2013-03-05 15:02:16,535 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:203,uuid:40e80e79-ac1b-31d1-a067-1ec03e7bc67b,host:10.102.192.100,path:/cpg_vol/sailaja/priamry,port:2049,type:NetworkFilesystem},localPath:/mnt//40e80e79-ac1b-31d1-a067-1ec03e7bc67b,wait:0}}]
}
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 1-16676: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)\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:1110)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
java.lang.Thread.run(Thread.java:679)\n,wait:0}}] }
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Received: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-03-05 15:02:16,702 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-25:null) Details from executing class
com.cloud.agent.api.ModifyStoragePoolCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
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-03-05 15:02:16,708 WARN [cloud.storage.StorageManagerImpl]
(catalina-exec-25:null) Unable to establish a connection between
Host[-1-Routing] and Pool[203|NetworkFilesystem]
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203]
is unreachable: Unable establish connection from storage head to storage pool
203 due to java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at
[jira] [Updated] (CLOUDSTACK-1510) NPE when primary storage is added with wrong path
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-1510:
Status: Ready To Review (was: In Progress)
NPE when primary storage is added with wrong path
--
Key: CLOUDSTACK-1510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1510
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.1.0, 4.2.0
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Minor
Fix For: 4.2.0
Steps :
1. Configure Advanced zone
2. Tried to add second nfs primary storage with wrong path.
Observation: It failed with NPE
2013-03-05 15:02:16,535 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:203,uuid:40e80e79-ac1b-31d1-a067-1ec03e7bc67b,host:10.102.192.100,path:/cpg_vol/sailaja/priamry,port:2049,type:NetworkFilesystem},localPath:/mnt//40e80e79-ac1b-31d1-a067-1ec03e7bc67b,wait:0}}]
}
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 1-16676: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:java.lang.NullPointerException\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)\n\tat
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)\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:1110)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
java.lang.Thread.run(Thread.java:679)\n,wait:0}}] }
2013-03-05 15:02:16,701 DEBUG [agent.transport.Request]
(catalina-exec-25:null) Seq 1-16676: Received: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-03-05 15:02:16,702 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-25:null) Details from executing class
com.cloud.agent.api.ModifyStoragePoolCommand: java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
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-03-05 15:02:16,708 WARN [cloud.storage.StorageManagerImpl]
(catalina-exec-25:null) Unable to establish a connection between
Host[-1-Routing] and Pool[203|NetworkFilesystem]
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203]
is unreachable: Unable establish connection from storage head to storage pool
203 due to java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2336)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
[jira] [Commented] (CLOUDSTACK-2888) PVLAN - Ubuntu 13.04 vmware - should not allow networks with different primary VLAN with same Secondary VLAN, same primary VLAN with different Secondary VLAN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688811#comment-13688811 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2888: - Closing this bug with comments above - Angie/others, please reopen this bug if you have any questions or feel the need for changes to the current approach. PVLAN - Ubuntu 13.04 vmware - should not allow networks with different primary VLAN with same Secondary VLAN, same primary VLAN with different Secondary VLAN -- Key: CLOUDSTACK-2888 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2888 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: MS ASF 4.2 build CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz vmware ESXi 5.0 hosts ubuntu 13.04 hosts Reporter: angeline shen Assignee: Venkata Siva Vijayendra Bhamidipati Fix For: 4.2.0 Attachments: management-server.log.gz Given: pvlan1 = 1611svlan1 = 998 pvlan2 = 1612svlan2 = 997 nonexistent svlan3 = 999 Following PVLAN networks SHOULD NOT HAVE BEEN ALLOWED to be created : pvlan1 , svlan2 pvlan1 , svlan3 pvlan2 , svlan1 pvlan2 , svlan3 Result: Above PVLAN networks were allowed to be 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] [Resolved] (CLOUDSTACK-2888) PVLAN - Ubuntu 13.04 vmware - should not allow networks with different primary VLAN with same Secondary VLAN, same primary VLAN with different Secondary VLAN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-2888. - Resolution: Not A Problem PVLAN - Ubuntu 13.04 vmware - should not allow networks with different primary VLAN with same Secondary VLAN, same primary VLAN with different Secondary VLAN -- Key: CLOUDSTACK-2888 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2888 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: MS ASF 4.2 build CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz vmware ESXi 5.0 hosts ubuntu 13.04 hosts Reporter: angeline shen Assignee: Venkata Siva Vijayendra Bhamidipati Fix For: 4.2.0 Attachments: management-server.log.gz Given: pvlan1 = 1611svlan1 = 998 pvlan2 = 1612svlan2 = 997 nonexistent svlan3 = 999 Following PVLAN networks SHOULD NOT HAVE BEEN ALLOWED to be created : pvlan1 , svlan2 pvlan1 , svlan3 pvlan2 , svlan1 pvlan2 , svlan3 Result: Above PVLAN networks were allowed to be 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-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=13688820#comment-13688820 ] Rajesh Battala commented on CLOUDSTACK-2571: New Exception log : 2787 2013-06-19 23:45:17,697 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-52:job-136) Unexpected exception while executing org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd 2788 java.lang.NullPointerException 2789 at com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:1421) 2790 at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) 2791 at com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:190) 2792 at org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd.execute(PreparePrimaryStorageForMaintenanceCmd.java:102) 2793 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) 2794 at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) 2795 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 2796 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 2797 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 2798 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 2799 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 2800 at java.lang.Thread.run(Thread.java:722) [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
[jira] [Created] (CLOUDSTACK-3081) Even a dedicate pod operation fails, the system shows Task Complete
Isaac Chiang created CLOUDSTACK-3081: Summary: Even a dedicate pod operation fails, the system shows Task Complete Key: CLOUDSTACK-3081 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3081 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Environment: Master Reporter: Isaac Chiang The DedicatePodCmd is an async command. The UI should keep querying the asynchronous job result, not pop up a notice with Task Complete immediately. -- 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-3081) Even a dedicate pod operation fails, the system shows Task Complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-3081: --- Assignee: Pranav Saxena Even a dedicate pod operation fails, the system shows Task Complete - Key: CLOUDSTACK-3081 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3081 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Environment: Master Reporter: Isaac Chiang Assignee: Pranav Saxena Labels: ui Attachments: Screenshot-1.png, Screenshot-3.png The DedicatePodCmd is an async command. The UI should keep querying the asynchronous job result, not pop up a notice with Task Complete immediately. -- 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
