[jira] [Commented] (CLOUDSTACK-2546) [Automation] Failed to add second NIC to vm in KVM environment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660412#comment-13660412 ] Mice Xia commented on CLOUDSTACK-2546: -- /test/integration/smoke/test_nic.py still uses same network to test add_nic, i'd change it if nobody shows concern > [Automation] Failed to add second NIC to vm in KVM environment > --- > > Key: CLOUDSTACK-2546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2546 > 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: KVM > Build : Latest master build >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > > Automation test case /test/integration/smoke/test_nic.py failed > Steps to reproduce > 1) Create and account, service offering > 2) Create Network offering (isolated) and Create network > 3) Create VM with the network > 4) After VM is up, add another network to VM > Expected result > Second nic should be added > Actual result > Failed to add second nic > 2013-05-16 10:49:07,804 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-68:job-292) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd > com.cloud.utils.exception.CloudRuntimeException: A NIC already exists for > VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030 > at > com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:844) > at > org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:109) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-05-16 10:49:07,809 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-68:job-292) Complete async job-292, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: A NIC already exists for > VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030 > 2013-05-16 10:49:09,334 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready -- 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-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-tabpanel&focusedCommentId=13660399#comment-13660399
]
Jayapal Reddy commented on CLOUDSTACK-2371:
---
I think it is regression with Niciri integration.
> 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
>Assignee: Jayapal Reddy
>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=deletePrivateGateway&id=59ec16d4-a076-4692-9abe-b986cf81cda4&response=json&sessionkey=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
[jira] [Assigned] (CLOUDSTACK-2548) [Automation] Failed to delete public IP range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reassigned CLOUDSTACK-2548: Assignee: Bharat Kumar > [Automation] Failed to delete public IP range > -- > > Key: CLOUDSTACK-2548 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2548 > 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 build : Latest > Issue found : During BVT automation run on KVM >Reporter: Rayees Namathponnan >Assignee: Bharat Kumar >Priority: Blocker > Fix For: 4.2.0 > > > Test case : test/integration/smoke/test_public_ip_range.py > Steps to reproduce > Step 1 : Create advance zone, and add IP range [In my case added > 10.223.122.124 to 10.223.122.126] > Step 2 : Delete this IP range > Actual Result > Release IP range operation failed with below error > "One of the ips in the range is used to provide Dhcp service to this subnet. > cannot delete this range as" > If you look the DB, ip range 10.223.122.124 to 10.223.122.126 is not > allocated > mysql> select * from user_ip_address where state!="Free"; > ++--++---+---+++-+++---+---+-+---++-+---++---+ > | id | uuid | account_id | domain_id | > public_ip_address | data_center_id | source_nat | allocated | > vlan_db_id | one_to_one_nat | vm_id | state | mac_address | > source_network_id | network_id | physical_network_id | is_system | vpc_id | > dnat_vmip | > ++--++---+---+++-+++---+---+-+---++-+---++---+ > | 2 | ddd29f48-54ba-4b76-b493-c62948f1 | 38 | 1 | > 10.223.122.67 | 1 | 1 | 2013-05-16 18:01:34 | >1 | 0 | NULL | Allocated | 60 | 200 | >241 | 200 | 0 | NULL | NULL | > | 3 | e4f7899b-1d5b-4c7c-91bd-38af7db1945a | 4 | 1 | > 10.223.122.68 | 1 | 1 | 2013-05-16 03:54:34 | >1 | 0 | NULL | Releasing | 61 | 200 | >209 | 200 | 0 | NULL | NULL | > | 4 | ab3b333a-bad2-427f-ad7d-6d9f3cac5336 | 1 | 1 | > 10.223.122.69 | 1 | 0 | 2013-05-16 04:56:39 | >1 | 0 | NULL | Allocated | 62 | 200 | > NULL | 200 | 0 | NULL | NULL | > | 6 | 73fe34aa-bdce-4f58-bc54-40fe6584a2da | 2 | 1 | > 10.223.122.71 | 1 | 1 | 2013-05-16 05:43:59 | >1 | 0 | NULL | Allocated | 64 | 200 | >230 | 200 | 0 | NULL | NULL | > | 23 | b97b3062-a82d-487a-8d56-4355ce72d3c7 | 2 | 1 | > 10.223.122.88 | 1 | 1 | 2013-05-16 05:23:12 | >1 | 0 | NULL | Allocated | 81 | 200 | >227 | 200 | 0 | NULL | NULL | > | 32 | 3d1f0625-90a0-4632-9cfb-aed018efa51c | 2 | 1 | > 10.223.122.97 | 1 | 1 | 2013-05-16 05:52:11 | >1 | 0 | NULL | Allocated | 90 | 200 | >232 | 200 | 0 | NULL | NULL | > | 52 | 851757d9-92f2-493c-98f6-3bd01b0c2d3b | 1 | 1 | > 10.223.122.117| 1 | 0 | 2013-05-16 04:54:09 | >1 | 0 | NULL | Allocated | 110 | 200 | > NULL | 200 | 0 | NULL | NULL | > | 60 | eede24f6-6587-4f75-8e2a-7063ffd2c833 | 1 | 1 | > 10.223.121.132| 2 | 0 | 2013-05-16 03:39:09 | >2 | 0 | NULL | Allocated | 61 | 204 | > NULL | 201 | 0 | NULL | NULL | > | 63 | a720338f-15f8-4d47-acc0-da6a2917406d | 1 | 1 | > 10.223.121.135| 2 | 0 | 2013-05-16 03:39:17 | >2 | 0 |
[jira] [Commented] (CLOUDSTACK-2546) [Automation] Failed to add second NIC to vm in KVM environment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660344#comment-13660344 ] Mice Xia commented on CLOUDSTACK-2546: -- i added this check for https://issues.apache.org/jira/browse/CLOUDSTACK-2341 > [Automation] Failed to add second NIC to vm in KVM environment > --- > > Key: CLOUDSTACK-2546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2546 > 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: KVM > Build : Latest master build >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > > Automation test case /test/integration/smoke/test_nic.py failed > Steps to reproduce > 1) Create and account, service offering > 2) Create Network offering (isolated) and Create network > 3) Create VM with the network > 4) After VM is up, add another network to VM > Expected result > Second nic should be added > Actual result > Failed to add second nic > 2013-05-16 10:49:07,804 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-68:job-292) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd > com.cloud.utils.exception.CloudRuntimeException: A NIC already exists for > VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030 > at > com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:844) > at > org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:109) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-05-16 10:49:07,809 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-68:job-292) Complete async job-292, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: A NIC already exists for > VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030 > 2013-05-16 10:49:09,334 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready -- 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-2549) createipAlias.sh/deleteipAlias.sh won't be copied to XenServer host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N resolved CLOUDSTACK-2549. --- Resolution: Duplicate This is a duplicate of bug https://issues.apache.org/jira/browse/CLOUDSTACK-2543 > createipAlias.sh/deleteipAlias.sh won't be copied to XenServer host > --- > > Key: CLOUDSTACK-2549 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2549 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Sheng Yang >Assignee: Bharat Kumar >Priority: Blocker > Fix For: 4.2.0 > > > Found this in my mgmt server log: > WARN [xen.resource.CitrixResourceBase] (DirectAgent-1:) We cannot locate > /home/yasker/develop/cloudstack-oss.asf/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/hypervisor/xenserver/xenserver60/../../../deleteipAlias.sh > WARN [xen.resource.CitrixResourceBase] (DirectAgent-1:) We cannot locate > /home/yasker/develop/cloudstack-oss.asf/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/hypervisor/xenserver/xenserver60/../../../createipAlias.sh > Then saw this: > diff --git a/scripts/vm/hypervisor/xenserver/xcpserver/patch > b/scripts/vm/hypervisor/xenserver/xcpserver/patch > index b7961bb..bfecd0c 100644 > --- a/scripts/vm/hypervisor/xenserver/xcpserver/patch > +++ b/scripts/vm/hypervisor/xenserver/xcpserver/patch > @@ -40,6 +40,8 @@ make_migratable.sh=..,0755,/opt/xensource/bin > setup_iscsi.sh=..,0755,/opt/xensource/bin > pingtest.sh=../../..,0755,/opt/xensource/bin > dhcp_entry.sh=../../../../network/domr/,0755,/opt/xensource/bin > +createipAlias.sh=../../..,0755,/opt/xensource/bin > +deleteipAlias.sh=../../..,0755,/opt/xensource/bin > router_proxy.sh=../../../../network/domr/,0755,/opt/xensource/bin > vm_data.sh=../../../../network/domr/,0755,/opt/xensource/bin > save_password_to_domr.sh=../../../../network/domr/,0755,/opt/xensource/bin > diff --git a/scripts/vm/hypervisor/xenserver/xenserver56/patch > b/scripts/vm/hypervisor/xenserver/xenserver56/patch > index 36dba3d..1be14ea 100644 > --- a/scripts/vm/hypervisor/xenserver/xenserver56/patch > +++ b/scripts/vm/hypervisor/xenserver/xenserver56/patch > @@ -38,6 +38,8 @@ make_migratable.sh=..,0755,/opt/xensource/bin > setup_iscsi.sh=..,0755,/opt/xensource/bin > cloud-setup-bonding.sh=..,0755,/opt/xensource/bin > pingtest.sh=../../..,0755,/opt/xensource/bin > +createipAlias.sh=../../..,0755,/opt/xensource/bin > +deleteipAlias.sh=../../..,0755,/opt/xensource/bin > dhcp_entry.sh=../../../../network/domr/,0755,/opt/xensource/bin > vm_data.sh=../../../../network/domr/,0755,/opt/xensource/bin > save_password_to_domr.sh=../../../../network/domr/,0755,/opt/xensource/bin > diff --git a/scripts/vm/hypervisor/xenserver/xenserver56fp1/patch > b/scripts/vm/hypervisor/xenserver/xenserver56fp1/patch > index d20e60f..dd31e44 100644 > --- a/scripts/vm/hypervisor/xenserver/xenserver56fp1/patch > +++ b/scripts/vm/hypervisor/xenserver/xenserver56fp1/patch > @@ -37,6 +37,8 @@ setupxenserver.sh=..,0755,/opt/xensource/bin > make_migratable.sh=..,0755,/opt/xensource/bin > setup_iscsi.sh=..,0755,/opt/xensource/bin > pingtest.sh=../../..,0755,/opt/xensource/bin > +createipAlias.sh=../../..,0755,/opt/xensource/bin > +deleteipAlias.sh=../../..,0755,/opt/xensource/bin > dhcp_entry.sh=../../../../network/domr/,0755,/opt/xensource/bin > vm_data.sh=../../../../network/domr/,0755,/opt/xensource/bin > save_password_to_domr.sh=../../../../network/domr/,0755,/opt/xensource/bin > diff --git a/scripts/vm/hypervisor/xenserver/xenserver60/patch > b/scripts/vm/hypervisor/xenserver/xenserver60/patch > index c9125f4..787f474 100644 > --- a/scripts/vm/hypervisor/xenserver/xenserver60/patch > +++ b/scripts/vm/hypervisor/xenserver/xenserver60/patch > @@ -40,6 +40,8 @@ id_rsa.cloud=../../../systemvm,0600,/root/.ssh > network_info.sh=..,0755,/opt/xensource/bin > setupxenserver.sh=..,0755,/opt/xensource/bin > make_migratable.sh=..,0755,/opt/xensource/bin > +createipAlias.sh=../../..,0755,/opt/xensource/bin > +deleteipAlias.sh=../../..,0755,/opt/xensource/bin > setup_iscsi.sh=..,0755,/opt/xensource/bin > pingtest.sh=../../..,0755,/opt/xensource/bin > dhcp_entry.sh=../../../../network/domr/,0755,/opt/xensource/bin > The feature is added by: > commit 052c24c4d1c881f791b804dbb9c2fc083af7da36 > Author: Bharat Kumar > Date: Mon May 13 17:02:27 2013 +0530 > CLOUDSTACK-702: Multiple ip ranges in different subnets. > > This feature enables adding of guest ip ranges (public ips) form > different subnets. > > In order to provide the dhcp service to a different subnet we create an > ipalias on
[jira] [Assigned] (CLOUDSTACK-2457) No check for input values,special character,-ive values can be assigne to GLobal parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala reassigned CLOUDSTACK-2457: --- Assignee: Harikrishna Patnala > No check for input values,special character,-ive values can be assigne to > GLobal parameter "cluster.cpu.allocated.capacity.disablethreshold" > > > Key: CLOUDSTACK-2457 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2457 > 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 >Assignee: Harikrishna Patnala >Priority: Minor > Fix For: 4.2.0 > > Attachments: screenshot-1.jpg > > > check screenshot for more details -- 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-2437) special character can be set to Global/Zone level parameter "guest.domain.sufix" ;there is no API level check .
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala reassigned CLOUDSTACK-2437: --- Assignee: Harikrishna Patnala > special character can be set to Global/Zone level parameter > "guest.domain.sufix" ;there is no API level check . > > > Key: CLOUDSTACK-2437 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2437 > 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 >Assignee: Harikrishna Patnala >Priority: Minor > Fix For: 4.2.0 > > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > For parameter "guest.domain.suffix" special character(like <>&^%#$) should > not be allowed ,please check screenshot for better understanding -- 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-2551) Update Quick Install Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660279#comment-13660279 ] Jessica Tomechak commented on CLOUDSTACK-2551: -- Published at http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.2/html/Quick_Install_Guide/index.html. Not sure where the source files are. > Update Quick Install Guide > -- > > Key: CLOUDSTACK-2551 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2551 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 >Reporter: Jessica Tomechak > Fix For: 4.2.0 > > > The Quick Install Guide has not been updated since v4.0. There is sure to be > new information to add and out-of-date information to remove. -- 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-2551) Update Quick Install Guide
Jessica Tomechak created CLOUDSTACK-2551: Summary: Update Quick Install Guide Key: CLOUDSTACK-2551 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2551 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Jessica Tomechak Fix For: 4.2.0 The Quick Install Guide has not been updated since v4.0. There is sure to be new information to add and out-of-date information to remove. -- 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-2530) fix npe if no network isolation methods
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660272#comment-13660272 ] ASF subversion and git services commented on CLOUDSTACK-2530: - Commit 973c43a152d39b85f53428b00f451fba9cb82003 in branch refs/heads/master from [~dbrosius] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=973c43a ] CLOUDSTACK-2530: fix npe if no network isolation methods Signed-off-by: Mice Xia > fix npe if no network isolation methods > --- > > Key: CLOUDSTACK-2530 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2530 > 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: 2530.txt > > > ListNetworkIsolationMethodsCmd checks to see if isolation methods are null, > If it is, NPE, fixed. -- 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-2056) DeploymentPlanner choice via ServiceOffering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle resolved CLOUDSTACK-2056. -- Resolution: Fixed > DeploymentPlanner choice via ServiceOffering > - > > Key: CLOUDSTACK-2056 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2056 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Prachi Damle >Assignee: Prachi Damle > Fix For: 4.2.0 > > > Currently in a CloudStack deployment, only one of these planners can be used > for all VM deployments. The global parameter 'vm.allocation.algorithm' > decides which planner will be used. > However there could be a need to be able to choose different planning > strategies within a single CS deployment. So letting Admin choose a > deployment planner for a set of VMs will be helpful. > To enable this, proposal is: >1) Expose deployment planner as part of a ServiceOffering API. By > default, the value can be set to the default CS FirstFitPlanner, but admin > can override it and set some other strategy as per needs. >2) Add a resource reservation mechanism to let deployment planners co-exist -- 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-2550) OVS: Fix add host for KVM OVS enabled host
Sheng Yang created CLOUDSTACK-2550: -- Summary: OVS: Fix add host for KVM OVS enabled host Key: CLOUDSTACK-2550 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2550 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sheng Yang Fix For: 4.2.0 Current adding host for KVM OVS enabled host is unsupported. We need to support that, rather than ask user to configure the host manually everytime. Basically cloudstack-setup-agent doesn't work well because brctl won't show the bridges.(BRCOMPAT disabled). -- 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-2546) [Automation] Failed to add second NIC to vm in KVM environment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660180#comment-13660180 ] Fang Wang commented on CLOUDSTACK-2546: --- in UserVmManagerImpl.java, in method addNicToVirtualMachine( ), it rejected the existing network ID. any one familiar with the code? > [Automation] Failed to add second NIC to vm in KVM environment > --- > > Key: CLOUDSTACK-2546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2546 > 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: KVM > Build : Latest master build >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > > Automation test case /test/integration/smoke/test_nic.py failed > Steps to reproduce > 1) Create and account, service offering > 2) Create Network offering (isolated) and Create network > 3) Create VM with the network > 4) After VM is up, add another network to VM > Expected result > Second nic should be added > Actual result > Failed to add second nic > 2013-05-16 10:49:07,804 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-68:job-292) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd > com.cloud.utils.exception.CloudRuntimeException: A NIC already exists for > VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030 > at > com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:844) > at > org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:109) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-05-16 10:49:07,809 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-68:job-292) Complete async job-292, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: A NIC already exists for > VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030 > 2013-05-16 10:49:09,334 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready -- 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-2548) [Automation] Failed to delete public IP range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660155#comment-13660155 ] Fang Wang commented on CLOUDSTACK-2548: --- This is not a KVM issue. More of a IP range handling in ConfigurationManagerImpl.java. > [Automation] Failed to delete public IP range > -- > > Key: CLOUDSTACK-2548 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2548 > 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 build : Latest > Issue found : During BVT automation run on KVM >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > > Test case : test/integration/smoke/test_public_ip_range.py > Steps to reproduce > Step 1 : Create advance zone, and add IP range [In my case added > 10.223.122.124 to 10.223.122.126] > Step 2 : Delete this IP range > Actual Result > Release IP range operation failed with below error > "One of the ips in the range is used to provide Dhcp service to this subnet. > cannot delete this range as" > If you look the DB, ip range 10.223.122.124 to 10.223.122.126 is not > allocated > mysql> select * from user_ip_address where state!="Free"; > ++--++---+---+++-+++---+---+-+---++-+---++---+ > | id | uuid | account_id | domain_id | > public_ip_address | data_center_id | source_nat | allocated | > vlan_db_id | one_to_one_nat | vm_id | state | mac_address | > source_network_id | network_id | physical_network_id | is_system | vpc_id | > dnat_vmip | > ++--++---+---+++-+++---+---+-+---++-+---++---+ > | 2 | ddd29f48-54ba-4b76-b493-c62948f1 | 38 | 1 | > 10.223.122.67 | 1 | 1 | 2013-05-16 18:01:34 | >1 | 0 | NULL | Allocated | 60 | 200 | >241 | 200 | 0 | NULL | NULL | > | 3 | e4f7899b-1d5b-4c7c-91bd-38af7db1945a | 4 | 1 | > 10.223.122.68 | 1 | 1 | 2013-05-16 03:54:34 | >1 | 0 | NULL | Releasing | 61 | 200 | >209 | 200 | 0 | NULL | NULL | > | 4 | ab3b333a-bad2-427f-ad7d-6d9f3cac5336 | 1 | 1 | > 10.223.122.69 | 1 | 0 | 2013-05-16 04:56:39 | >1 | 0 | NULL | Allocated | 62 | 200 | > NULL | 200 | 0 | NULL | NULL | > | 6 | 73fe34aa-bdce-4f58-bc54-40fe6584a2da | 2 | 1 | > 10.223.122.71 | 1 | 1 | 2013-05-16 05:43:59 | >1 | 0 | NULL | Allocated | 64 | 200 | >230 | 200 | 0 | NULL | NULL | > | 23 | b97b3062-a82d-487a-8d56-4355ce72d3c7 | 2 | 1 | > 10.223.122.88 | 1 | 1 | 2013-05-16 05:23:12 | >1 | 0 | NULL | Allocated | 81 | 200 | >227 | 200 | 0 | NULL | NULL | > | 32 | 3d1f0625-90a0-4632-9cfb-aed018efa51c | 2 | 1 | > 10.223.122.97 | 1 | 1 | 2013-05-16 05:52:11 | >1 | 0 | NULL | Allocated | 90 | 200 | >232 | 200 | 0 | NULL | NULL | > | 52 | 851757d9-92f2-493c-98f6-3bd01b0c2d3b | 1 | 1 | > 10.223.122.117| 1 | 0 | 2013-05-16 04:54:09 | >1 | 0 | NULL | Allocated | 110 | 200 | > NULL | 200 | 0 | NULL | NULL | > | 60 | eede24f6-6587-4f75-8e2a-7063ffd2c833 | 1 | 1 | > 10.223.121.132| 2 | 0 | 2013-05-16 03:39:09 | >2 | 0 | NULL | Allocated | 61 | 204 | > NULL | 201 | 0 | NULL | NULL | > | 63 | a720338f-15f8-4d47-acc0-da6a2917406d | 1 | 1 | > 10.223.121.135|
[jira] [Commented] (CLOUDSTACK-2056) DeploymentPlanner choice via ServiceOffering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660066#comment-13660066 ] ASF subversion and git services commented on CLOUDSTACK-2056: - Commit a2eb7bab1ef67de6589053ccd45515cf410d187c in branch refs/heads/master from Prachi Damle [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a2eb7ba ] CLOUDSTACK-2056: DeploymentPlanner choice via ServiceOffering - Changes merged from planner_reserve branch - Exposing deploymentplanner as an optional parameter while creating a service offering - changes to DeploymentPlanningManagerImpl to make sure host reserve-release happens between conflicting planner usages. > DeploymentPlanner choice via ServiceOffering > - > > Key: CLOUDSTACK-2056 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2056 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Prachi Damle >Assignee: Prachi Damle > Fix For: 4.2.0 > > > Currently in a CloudStack deployment, only one of these planners can be used > for all VM deployments. The global parameter 'vm.allocation.algorithm' > decides which planner will be used. > However there could be a need to be able to choose different planning > strategies within a single CS deployment. So letting Admin choose a > deployment planner for a set of VMs will be helpful. > To enable this, proposal is: >1) Expose deployment planner as part of a ServiceOffering API. By > default, the value can be set to the default CS FirstFitPlanner, but admin > can override it and set some other strategy as per needs. >2) Add a resource reservation mechanism to let deployment planners co-exist -- 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-2544) System VM's are failed to start with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660013#comment-13660013 ] Animesh Chaturvedi commented on CLOUDSTACK-2544: does my account work? > System VM's are failed to start with NPE > > > Key: CLOUDSTACK-2544 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2544 > 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: Sailaja Mada >Assignee: Kishan Kavala >Priority: Blocker > > Steps: > 1. Create Adv networking setup. > Observation: > System VM's are failed to start with NPE > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release cpu from host: 1, old used: 0,reserved: 0, actual > total: 9572, total with overprovisioning: 9572; new used: 0,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release mem from host: 1, old used: 0,reserved: 0, total: > 17166258176; new used: 0,reserved:0; movedfromreserved: > false,moveToReserveredfalse > 2013-05-16 17:12:20,524 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > java.lang.NullPointerException > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:684) > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:90) > at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117) > at > com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1251) > at > com.cloud.vm.VirtualMachineManagerImpl.changeState(VirtualMachineManagerImpl.java:660) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:817) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:540) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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-05-16 17:12:20,526 INFO [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Unable to start secondary storage vm for standby > capacity, secStorageVm vm Id : 4, will recycle it and start a new one > 2013-05-16 17:12:20,529 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) VM is already stopped: VM[SecondaryStorageVm|s-4-VM] > 2013-05-16 17:12:20,537 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Stopped to Expunging with > event: ExpungeOperationvm's original host id: null new host id: null host id > before state transition: null > 2013-05-16 17:12:20,540 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) Destroying vm VM[SecondaryStorageVm|s-4-VM] -- This message is automatically generated
[jira] [Issue Comment Deleted] (CLOUDSTACK-2544) System VM's are failed to start with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-2544: --- Comment: was deleted (was: does my account work?) > System VM's are failed to start with NPE > > > Key: CLOUDSTACK-2544 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2544 > 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: Sailaja Mada >Assignee: Kishan Kavala >Priority: Blocker > > Steps: > 1. Create Adv networking setup. > Observation: > System VM's are failed to start with NPE > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release cpu from host: 1, old used: 0,reserved: 0, actual > total: 9572, total with overprovisioning: 9572; new used: 0,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release mem from host: 1, old used: 0,reserved: 0, total: > 17166258176; new used: 0,reserved:0; movedfromreserved: > false,moveToReserveredfalse > 2013-05-16 17:12:20,524 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > java.lang.NullPointerException > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:684) > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:90) > at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117) > at > com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1251) > at > com.cloud.vm.VirtualMachineManagerImpl.changeState(VirtualMachineManagerImpl.java:660) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:817) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:540) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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-05-16 17:12:20,526 INFO [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Unable to start secondary storage vm for standby > capacity, secStorageVm vm Id : 4, will recycle it and start a new one > 2013-05-16 17:12:20,529 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) VM is already stopped: VM[SecondaryStorageVm|s-4-VM] > 2013-05-16 17:12:20,537 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Stopped to Expunging with > event: ExpungeOperationvm's original host id: null new host id: null host id > before state transition: null > 2013-05-16 17:12:20,540 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) Destroying vm VM[SecondaryStorageVm|s-4-VM] -- This message is automatically generated by JIRA. If you think it was sent in
[jira] [Commented] (CLOUDSTACK-2545) Inconsistent unit of network statistics between js and kvm plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660007#comment-13660007 ] ASF subversion and git services commented on CLOUDSTACK-2545: - Commit 1a83bf4b447ab058ccf37b4103f8a1c4c44e594b in branch refs/heads/4.1 from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1a83bf4 ] CLOUDSTACK-2545: Change unit of network statistics from 1000 to 1024 for KVM Signed-off-by: Chip Childers > Inconsistent unit of network statistics between js and kvm plugin > - > > Key: CLOUDSTACK-2545 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2545 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 >Reporter: Wei Zhou >Assignee: Wei Zhou >Priority: Minor > Fix For: 4.1.0 > > > when convert bytes to KBs in kvm plugin (LibvirtComputingResource.java) > stats.setNetworkReadKBs(deltarx / 1000); > stats.setNetworkWriteKBs(deltatx / 1000); > But on cloudstack ui (ui/scripts/instances.js) > networkkbsread: (jsonObj.networkkbsread == null)? "N/A": > cloudStack.converters.convertBytes(jsonObj.networkkbsread * 1024), > networkkbswrite: (jsonObj.networkkbswrite == null)? "N/A": > cloudStack.converters.convertBytes(jsonObj.networkkbswrite * 1024) > It means, if the real value is 1000, the display on cloudstack ui will be > 1024. -- 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-2549) createipAlias.sh/deleteipAlias.sh won't be copied to XenServer host
Sheng Yang created CLOUDSTACK-2549: -- Summary: createipAlias.sh/deleteipAlias.sh won't be copied to XenServer host Key: CLOUDSTACK-2549 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2549 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sheng Yang Assignee: Bharat Kumar Priority: Blocker Fix For: 4.2.0 Found this in my mgmt server log: WARN [xen.resource.CitrixResourceBase] (DirectAgent-1:) We cannot locate /home/yasker/develop/cloudstack-oss.asf/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/hypervisor/xenserver/xenserver60/../../../deleteipAlias.sh WARN [xen.resource.CitrixResourceBase] (DirectAgent-1:) We cannot locate /home/yasker/develop/cloudstack-oss.asf/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/hypervisor/xenserver/xenserver60/../../../createipAlias.sh Then saw this: diff --git a/scripts/vm/hypervisor/xenserver/xcpserver/patch b/scripts/vm/hypervisor/xenserver/xcpserver/patch index b7961bb..bfecd0c 100644 --- a/scripts/vm/hypervisor/xenserver/xcpserver/patch +++ b/scripts/vm/hypervisor/xenserver/xcpserver/patch @@ -40,6 +40,8 @@ make_migratable.sh=..,0755,/opt/xensource/bin setup_iscsi.sh=..,0755,/opt/xensource/bin pingtest.sh=../../..,0755,/opt/xensource/bin dhcp_entry.sh=../../../../network/domr/,0755,/opt/xensource/bin +createipAlias.sh=../../..,0755,/opt/xensource/bin +deleteipAlias.sh=../../..,0755,/opt/xensource/bin router_proxy.sh=../../../../network/domr/,0755,/opt/xensource/bin vm_data.sh=../../../../network/domr/,0755,/opt/xensource/bin save_password_to_domr.sh=../../../../network/domr/,0755,/opt/xensource/bin diff --git a/scripts/vm/hypervisor/xenserver/xenserver56/patch b/scripts/vm/hypervisor/xenserver/xenserver56/patch index 36dba3d..1be14ea 100644 --- a/scripts/vm/hypervisor/xenserver/xenserver56/patch +++ b/scripts/vm/hypervisor/xenserver/xenserver56/patch @@ -38,6 +38,8 @@ make_migratable.sh=..,0755,/opt/xensource/bin setup_iscsi.sh=..,0755,/opt/xensource/bin cloud-setup-bonding.sh=..,0755,/opt/xensource/bin pingtest.sh=../../..,0755,/opt/xensource/bin +createipAlias.sh=../../..,0755,/opt/xensource/bin +deleteipAlias.sh=../../..,0755,/opt/xensource/bin dhcp_entry.sh=../../../../network/domr/,0755,/opt/xensource/bin vm_data.sh=../../../../network/domr/,0755,/opt/xensource/bin save_password_to_domr.sh=../../../../network/domr/,0755,/opt/xensource/bin diff --git a/scripts/vm/hypervisor/xenserver/xenserver56fp1/patch b/scripts/vm/hypervisor/xenserver/xenserver56fp1/patch index d20e60f..dd31e44 100644 --- a/scripts/vm/hypervisor/xenserver/xenserver56fp1/patch +++ b/scripts/vm/hypervisor/xenserver/xenserver56fp1/patch @@ -37,6 +37,8 @@ setupxenserver.sh=..,0755,/opt/xensource/bin make_migratable.sh=..,0755,/opt/xensource/bin setup_iscsi.sh=..,0755,/opt/xensource/bin pingtest.sh=../../..,0755,/opt/xensource/bin +createipAlias.sh=../../..,0755,/opt/xensource/bin +deleteipAlias.sh=../../..,0755,/opt/xensource/bin dhcp_entry.sh=../../../../network/domr/,0755,/opt/xensource/bin vm_data.sh=../../../../network/domr/,0755,/opt/xensource/bin save_password_to_domr.sh=../../../../network/domr/,0755,/opt/xensource/bin diff --git a/scripts/vm/hypervisor/xenserver/xenserver60/patch b/scripts/vm/hypervisor/xenserver/xenserver60/patch index c9125f4..787f474 100644 --- a/scripts/vm/hypervisor/xenserver/xenserver60/patch +++ b/scripts/vm/hypervisor/xenserver/xenserver60/patch @@ -40,6 +40,8 @@ id_rsa.cloud=../../../systemvm,0600,/root/.ssh network_info.sh=..,0755,/opt/xensource/bin setupxenserver.sh=..,0755,/opt/xensource/bin make_migratable.sh=..,0755,/opt/xensource/bin +createipAlias.sh=../../..,0755,/opt/xensource/bin +deleteipAlias.sh=../../..,0755,/opt/xensource/bin setup_iscsi.sh=..,0755,/opt/xensource/bin pingtest.sh=../../..,0755,/opt/xensource/bin dhcp_entry.sh=../../../../network/domr/,0755,/opt/xensource/bin The feature is added by: commit 052c24c4d1c881f791b804dbb9c2fc083af7da36 Author: Bharat Kumar Date: Mon May 13 17:02:27 2013 +0530 CLOUDSTACK-702: Multiple ip ranges in different subnets. This feature enables adding of guest ip ranges (public ips) form different subnets. In order to provide the dhcp service to a different subnet we create an ipalias on the router. This allows the router to listen to the dhcp request from the guest vms and respond accordingly. Every time a vm is deployed in the new subnet w The details of the alias ips are stored in db in the nic_ip_alias table. Every time a new subnet is added one of the ip from the subnet is used to configure the ip alias. I have pushed the code to https://github.com/bvbharatk/cloud-stack/tree/Cloudstack-702 , also rebased the c
[jira] [Commented] (CLOUDSTACK-2545) Inconsistent unit of network statistics between js and kvm plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660008#comment-13660008 ] ASF subversion and git services commented on CLOUDSTACK-2545: - Commit a29e39365aab0ff4024ff5ff4b04fccb7abc2885 in branch refs/heads/master from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a29e393 ] CLOUDSTACK-2545: Change unit of network statistics from 1000 to 1024 for KVM Signed-off-by: Chip Childers > Inconsistent unit of network statistics between js and kvm plugin > - > > Key: CLOUDSTACK-2545 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2545 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 >Reporter: Wei Zhou >Assignee: Wei Zhou >Priority: Minor > Fix For: 4.1.0 > > > when convert bytes to KBs in kvm plugin (LibvirtComputingResource.java) > stats.setNetworkReadKBs(deltarx / 1000); > stats.setNetworkWriteKBs(deltatx / 1000); > But on cloudstack ui (ui/scripts/instances.js) > networkkbsread: (jsonObj.networkkbsread == null)? "N/A": > cloudStack.converters.convertBytes(jsonObj.networkkbsread * 1024), > networkkbswrite: (jsonObj.networkkbswrite == null)? "N/A": > cloudStack.converters.convertBytes(jsonObj.networkkbswrite * 1024) > It means, if the real value is 1000, the display on cloudstack ui will be > 1024. -- 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-2545) Inconsistent unit of network statistics between js and kvm plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-2545. --- Resolution: Fixed committed from reviewboard > Inconsistent unit of network statistics between js and kvm plugin > - > > Key: CLOUDSTACK-2545 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2545 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 >Reporter: Wei Zhou >Assignee: Wei Zhou >Priority: Minor > Fix For: 4.1.0 > > > when convert bytes to KBs in kvm plugin (LibvirtComputingResource.java) > stats.setNetworkReadKBs(deltarx / 1000); > stats.setNetworkWriteKBs(deltatx / 1000); > But on cloudstack ui (ui/scripts/instances.js) > networkkbsread: (jsonObj.networkkbsread == null)? "N/A": > cloudStack.converters.convertBytes(jsonObj.networkkbsread * 1024), > networkkbswrite: (jsonObj.networkkbswrite == null)? "N/A": > cloudStack.converters.convertBytes(jsonObj.networkkbswrite * 1024) > It means, if the real value is 1000, the display on cloudstack ui will be > 1024. -- 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-2516) Create User API compability broken now
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659991#comment-13659991
]
Chip Childers commented on CLOUDSTACK-2516:
---
We need to document the upgrade scenario.
Also, does this need to be cherry-picked into master?
> Create User API compability broken now
> --
>
> Key: CLOUDSTACK-2516
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2516
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Chip Childers
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
>
> From email thread:
> On Wed, May 15, 2013 at 04:22:14PM +0200, Ove Ewerlid wrote:
> > NB; The 402/410 deployments are on RHES64(OEL64) via RPMs built from
> > latest git repos.
> > /Ove
> >
> > On 05/15/2013 03:02 PM, Ove Ewerlid wrote:
> > >Hi!
> > >
> > >When testing a deploy script, that works as expected with 4.0.2, on 4.1
> > >I noticed that there was a need to pass plaintext passwords to
> > >createUser, rather then the documented MD5 hash. When passing MD5 hash,
> > >the password gets double MD5:hashed in 41.
> > >
> > >There is new code in 4.1 that encodes password using the authenticator
> > >plugins (encode method);
> > >
> > >cloudstack.4.1/server/src/com/cloud/user/AccountManagerImpl.java
> > >
> > >...
> > >String encodedPassword = null;
> > > for (UserAuthenticator authenticator : _userAuthenticators) {
> > > encodedPassword = authenticator.encode(password);
> > > if (encodedPassword != null) {
> > > break;
> > > }
> > > }
> > >...
> > >
> > >The 41 API docs still notes that an MD5 hash shall be passed in.
> > >What am I missing here?
> > >
> > >/Ove
--
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-2505) Object_Store_Refactor- Adding s3 image store fails if optional parameters are not passed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-2505. -- Resolution: Fixed > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > - > > Key: CLOUDSTACK-2505 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2505 > 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 object_store feature branch >Reporter: Sanjeev N >Assignee: Jessica Wang > Fix For: 4.2.0 > > > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > Steps to Reproduce: > = > 1.While adding s3 as secondary storage don't pass optional arguments > Expected Result: > == > Adding image store should succeed > Actual Result: > === > Failed to add image store with following error: > Something went wrong; please correct the following: > For input string: "" > API being fired: > 2013-05-15 08:08:26,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===START=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > 2013-05-15 08:08:26,100 INFO > [datastore.lifecycle.CloudStackImageStoreLifeCycleImpl] > (catalina-exec-12:null) Trying to add a new host at > nfs://10.147.28.7/export/home/sanjeev/sec_xen_os in data center 1 > 2013-05-15 08:08:26,107 INFO [datastore.lifecycle.S3ImageStoreLifeCycleImpl] > (catalina-exec-10:null) Trying to add a S3 store in data center null > 2013-05-15 08:08:26,237 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) > ===END=== 10.146.0.15 -- GET > command=createCacheStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=NFS&zoneid=3ae5c4e1-9605-45a6-b797-6a3f28c113c1&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fsanjeev%2Fsec_xen_os&_=136854478 > 2013-05-15 08:08:26,458 INFO [cloud.api.ApiServer] (catalina-exec-10:null) > For input string: "" > 2013-05-15 08:08:26,460 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===END=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > If the optional parameter value is not specified blank values are being > passed to api. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2516) Create User API compability broken now
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659986#comment-13659986
]
ASF subversion and git services commented on CLOUDSTACK-2516:
-
Commit 3dc916a32875fa26c1d1fae2cb4fd2ac49659707 in branch refs/heads/4.1 from
[~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3dc916a ]
CLOUDSTACK-2516: Added PlainText to Authenticator list for backward
compatibility
> Create User API compability broken now
> --
>
> Key: CLOUDSTACK-2516
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2516
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Chip Childers
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
>
> From email thread:
> On Wed, May 15, 2013 at 04:22:14PM +0200, Ove Ewerlid wrote:
> > NB; The 402/410 deployments are on RHES64(OEL64) via RPMs built from
> > latest git repos.
> > /Ove
> >
> > On 05/15/2013 03:02 PM, Ove Ewerlid wrote:
> > >Hi!
> > >
> > >When testing a deploy script, that works as expected with 4.0.2, on 4.1
> > >I noticed that there was a need to pass plaintext passwords to
> > >createUser, rather then the documented MD5 hash. When passing MD5 hash,
> > >the password gets double MD5:hashed in 41.
> > >
> > >There is new code in 4.1 that encodes password using the authenticator
> > >plugins (encode method);
> > >
> > >cloudstack.4.1/server/src/com/cloud/user/AccountManagerImpl.java
> > >
> > >...
> > >String encodedPassword = null;
> > > for (UserAuthenticator authenticator : _userAuthenticators) {
> > > encodedPassword = authenticator.encode(password);
> > > if (encodedPassword != null) {
> > > break;
> > > }
> > > }
> > >...
> > >
> > >The 41 API docs still notes that an MD5 hash shall be passed in.
> > >What am I missing here?
> > >
> > >/Ove
--
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-2505) Object_Store_Refactor- Adding s3 image store fails if optional parameters are not passed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-2505: Assignee: Jessica Wang > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > - > > Key: CLOUDSTACK-2505 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2505 > 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 object_store feature branch >Reporter: Sanjeev N >Assignee: Jessica Wang > Fix For: 4.2.0 > > > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > Steps to Reproduce: > = > 1.While adding s3 as secondary storage don't pass optional arguments > Expected Result: > == > Adding image store should succeed > Actual Result: > === > Failed to add image store with following error: > Something went wrong; please correct the following: > For input string: "" > API being fired: > 2013-05-15 08:08:26,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===START=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > 2013-05-15 08:08:26,100 INFO > [datastore.lifecycle.CloudStackImageStoreLifeCycleImpl] > (catalina-exec-12:null) Trying to add a new host at > nfs://10.147.28.7/export/home/sanjeev/sec_xen_os in data center 1 > 2013-05-15 08:08:26,107 INFO [datastore.lifecycle.S3ImageStoreLifeCycleImpl] > (catalina-exec-10:null) Trying to add a S3 store in data center null > 2013-05-15 08:08:26,237 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) > ===END=== 10.146.0.15 -- GET > command=createCacheStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=NFS&zoneid=3ae5c4e1-9605-45a6-b797-6a3f28c113c1&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fsanjeev%2Fsec_xen_os&_=136854478 > 2013-05-15 08:08:26,458 INFO [cloud.api.ApiServer] (catalina-exec-10:null) > For input string: "" > 2013-05-15 08:08:26,460 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===END=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > If the optional parameter value is not specified blank values are being > passed to api. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2505) Object_Store_Refactor- Adding s3 image store fails if optional parameters are not passed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659982#comment-13659982 ] ASF subversion and git services commented on CLOUDSTACK-2505: - Commit cd318661d2f60ed218f5c1fa7b316b9228148216 in branch refs/heads/object_store from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cd31866 ] CLOUDSTACK-2505: object_store - UI - infrastructure menu - secondary storages - add URL, Provider, Scope, Details to detailView. > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > - > > Key: CLOUDSTACK-2505 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2505 > 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 object_store feature branch >Reporter: Sanjeev N > Fix For: 4.2.0 > > > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > Steps to Reproduce: > = > 1.While adding s3 as secondary storage don't pass optional arguments > Expected Result: > == > Adding image store should succeed > Actual Result: > === > Failed to add image store with following error: > Something went wrong; please correct the following: > For input string: "" > API being fired: > 2013-05-15 08:08:26,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===START=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > 2013-05-15 08:08:26,100 INFO > [datastore.lifecycle.CloudStackImageStoreLifeCycleImpl] > (catalina-exec-12:null) Trying to add a new host at > nfs://10.147.28.7/export/home/sanjeev/sec_xen_os in data center 1 > 2013-05-15 08:08:26,107 INFO [datastore.lifecycle.S3ImageStoreLifeCycleImpl] > (catalina-exec-10:null) Trying to add a S3 store in data center null > 2013-05-15 08:08:26,237 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) > ===END=== 10.146.0.15 -- GET > command=createCacheStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=NFS&zoneid=3ae5c4e1-9605-45a6-b797-6a3f28c113c1&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fsanjeev%2Fsec_xen_os&_=136854478 > 2013-05-15 08:08:26,458 INFO [cloud.api.ApiServer] (catalina-exec-10:null) > For input string: "" > 2013-05-15 08:08:26,460 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===END=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > If the optional parameter value is not specified blank values are being > passed to api. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2505) Object_Store_Refactor- Adding s3 image store fails if optional parameters are not passed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659983#comment-13659983 ] ASF subversion and git services commented on CLOUDSTACK-2505: - Commit 44adba06f490e6a76a643a22ca9739b4e38d5925 in branch refs/heads/object_store from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=44adba0 ] CLOUDSTACK-2505: object_store - UI - zone wizard - add secondary storage- S3, Swift - not pass details[i] info when corresponding field is empty. > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > - > > Key: CLOUDSTACK-2505 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2505 > 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 object_store feature branch >Reporter: Sanjeev N > Fix For: 4.2.0 > > > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > Steps to Reproduce: > = > 1.While adding s3 as secondary storage don't pass optional arguments > Expected Result: > == > Adding image store should succeed > Actual Result: > === > Failed to add image store with following error: > Something went wrong; please correct the following: > For input string: "" > API being fired: > 2013-05-15 08:08:26,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===START=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > 2013-05-15 08:08:26,100 INFO > [datastore.lifecycle.CloudStackImageStoreLifeCycleImpl] > (catalina-exec-12:null) Trying to add a new host at > nfs://10.147.28.7/export/home/sanjeev/sec_xen_os in data center 1 > 2013-05-15 08:08:26,107 INFO [datastore.lifecycle.S3ImageStoreLifeCycleImpl] > (catalina-exec-10:null) Trying to add a S3 store in data center null > 2013-05-15 08:08:26,237 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) > ===END=== 10.146.0.15 -- GET > command=createCacheStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=NFS&zoneid=3ae5c4e1-9605-45a6-b797-6a3f28c113c1&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fsanjeev%2Fsec_xen_os&_=136854478 > 2013-05-15 08:08:26,458 INFO [cloud.api.ApiServer] (catalina-exec-10:null) > For input string: "" > 2013-05-15 08:08:26,460 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===END=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > If the optional parameter value is not specified blank values are being > passed to api. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2548) [Automation] Failed to delete public IP range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659966#comment-13659966 ] Fang Wang commented on CLOUDSTACK-2548: --- Can you show the DB results for the ip in the range 124-126? (the 10.223.122.124 , 10.223.122.125 and 10.223.122.126) are they all have state "free"? > [Automation] Failed to delete public IP range > -- > > Key: CLOUDSTACK-2548 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2548 > 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 build : Latest > Issue found : During BVT automation run on KVM >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > > Test case : test/integration/smoke/test_public_ip_range.py > Steps to reproduce > Step 1 : Create advance zone, and add IP range [In my case added > 10.223.122.124 to 10.223.122.126] > Step 2 : Delete this IP range > Actual Result > Release IP range operation failed with below error > "One of the ips in the range is used to provide Dhcp service to this subnet. > cannot delete this range as" > If you look the DB, ip range 10.223.122.124 to 10.223.122.126 is not > allocated > mysql> select * from user_ip_address where state!="Free"; > ++--++---+---+++-+++---+---+-+---++-+---++---+ > | id | uuid | account_id | domain_id | > public_ip_address | data_center_id | source_nat | allocated | > vlan_db_id | one_to_one_nat | vm_id | state | mac_address | > source_network_id | network_id | physical_network_id | is_system | vpc_id | > dnat_vmip | > ++--++---+---+++-+++---+---+-+---++-+---++---+ > | 2 | ddd29f48-54ba-4b76-b493-c62948f1 | 38 | 1 | > 10.223.122.67 | 1 | 1 | 2013-05-16 18:01:34 | >1 | 0 | NULL | Allocated | 60 | 200 | >241 | 200 | 0 | NULL | NULL | > | 3 | e4f7899b-1d5b-4c7c-91bd-38af7db1945a | 4 | 1 | > 10.223.122.68 | 1 | 1 | 2013-05-16 03:54:34 | >1 | 0 | NULL | Releasing | 61 | 200 | >209 | 200 | 0 | NULL | NULL | > | 4 | ab3b333a-bad2-427f-ad7d-6d9f3cac5336 | 1 | 1 | > 10.223.122.69 | 1 | 0 | 2013-05-16 04:56:39 | >1 | 0 | NULL | Allocated | 62 | 200 | > NULL | 200 | 0 | NULL | NULL | > | 6 | 73fe34aa-bdce-4f58-bc54-40fe6584a2da | 2 | 1 | > 10.223.122.71 | 1 | 1 | 2013-05-16 05:43:59 | >1 | 0 | NULL | Allocated | 64 | 200 | >230 | 200 | 0 | NULL | NULL | > | 23 | b97b3062-a82d-487a-8d56-4355ce72d3c7 | 2 | 1 | > 10.223.122.88 | 1 | 1 | 2013-05-16 05:23:12 | >1 | 0 | NULL | Allocated | 81 | 200 | >227 | 200 | 0 | NULL | NULL | > | 32 | 3d1f0625-90a0-4632-9cfb-aed018efa51c | 2 | 1 | > 10.223.122.97 | 1 | 1 | 2013-05-16 05:52:11 | >1 | 0 | NULL | Allocated | 90 | 200 | >232 | 200 | 0 | NULL | NULL | > | 52 | 851757d9-92f2-493c-98f6-3bd01b0c2d3b | 1 | 1 | > 10.223.122.117| 1 | 0 | 2013-05-16 04:54:09 | >1 | 0 | NULL | Allocated | 110 | 200 | > NULL | 200 | 0 | NULL | NULL | > | 60 | eede24f6-6587-4f75-8e2a-7063ffd2c833 | 1 | 1 | > 10.223.121.132| 2 | 0 | 2013-05-16 03:39:09 | >2 | 0 | NULL | Allocated | 61 | 204 | > NULL | 201 | 0 | NULL | NULL | > | 63 | a720338f-15f8-4d47-acc0
[jira] [Commented] (CLOUDSTACK-2505) Object_Store_Refactor- Adding s3 image store fails if optional parameters are not passed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659920#comment-13659920 ] ASF subversion and git services commented on CLOUDSTACK-2505: - Commit 47aeda9893ff218fe6f52467d3eb762d9417f445 in branch refs/heads/object_store from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=47aeda9 ] CLOUDSTACK-2505: object_store - UI - infrastructure menu - add secondary storage- Swift - not pass details[i] info when corresponding field is empty. > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > - > > Key: CLOUDSTACK-2505 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2505 > 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 object_store feature branch >Reporter: Sanjeev N > Fix For: 4.2.0 > > > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > Steps to Reproduce: > = > 1.While adding s3 as secondary storage don't pass optional arguments > Expected Result: > == > Adding image store should succeed > Actual Result: > === > Failed to add image store with following error: > Something went wrong; please correct the following: > For input string: "" > API being fired: > 2013-05-15 08:08:26,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===START=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > 2013-05-15 08:08:26,100 INFO > [datastore.lifecycle.CloudStackImageStoreLifeCycleImpl] > (catalina-exec-12:null) Trying to add a new host at > nfs://10.147.28.7/export/home/sanjeev/sec_xen_os in data center 1 > 2013-05-15 08:08:26,107 INFO [datastore.lifecycle.S3ImageStoreLifeCycleImpl] > (catalina-exec-10:null) Trying to add a S3 store in data center null > 2013-05-15 08:08:26,237 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) > ===END=== 10.146.0.15 -- GET > command=createCacheStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=NFS&zoneid=3ae5c4e1-9605-45a6-b797-6a3f28c113c1&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fsanjeev%2Fsec_xen_os&_=136854478 > 2013-05-15 08:08:26,458 INFO [cloud.api.ApiServer] (catalina-exec-10:null) > For input string: "" > 2013-05-15 08:08:26,460 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===END=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > If the optional parameter value is not specified blank values are being > passed to api. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2505) Object_Store_Refactor- Adding s3 image store fails if optional parameters are not passed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659905#comment-13659905 ] ASF subversion and git services commented on CLOUDSTACK-2505: - Commit d5ab59614af70be8cb89d3d0400521f9f2a3ee19 in branch refs/heads/object_store from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d5ab596 ] CLOUDSTACK-2505: object_store - UI - infrastructure menu - add secondary storage- S3 - not pass details[i] info when corresponding field is empty. > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > - > > Key: CLOUDSTACK-2505 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2505 > 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 object_store feature branch >Reporter: Sanjeev N > Fix For: 4.2.0 > > > Object_Store_Refactor- Adding s3 image store fails if optional parameters are > not passed > Steps to Reproduce: > = > 1.While adding s3 as secondary storage don't pass optional arguments > Expected Result: > == > Adding image store should succeed > Actual Result: > === > Failed to add image store with following error: > Something went wrong; please correct the following: > For input string: "" > API being fired: > 2013-05-15 08:08:26,058 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===START=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > 2013-05-15 08:08:26,100 INFO > [datastore.lifecycle.CloudStackImageStoreLifeCycleImpl] > (catalina-exec-12:null) Trying to add a new host at > nfs://10.147.28.7/export/home/sanjeev/sec_xen_os in data center 1 > 2013-05-15 08:08:26,107 INFO [datastore.lifecycle.S3ImageStoreLifeCycleImpl] > (catalina-exec-10:null) Trying to add a S3 store in data center null > 2013-05-15 08:08:26,237 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) > ===END=== 10.146.0.15 -- GET > command=createCacheStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=NFS&zoneid=3ae5c4e1-9605-45a6-b797-6a3f28c113c1&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fsanjeev%2Fsec_xen_os&_=136854478 > 2013-05-15 08:08:26,458 INFO [cloud.api.ApiServer] (catalina-exec-10:null) > For input string: "" > 2013-05-15 08:08:26,460 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) > ===END=== 10.146.0.15 -- GET > command=addImageStore&response=json&sessionkey=NWajIbj6m6eR9RDr5919OL3dqGA%3D&provider=S3&details%5B0%5D.key=accesskey&details%5B0%5D.value=GLSDOYWL06R-NTXGU_VM&details%5B1%5D.key=secretkey&details%5B1%5D.value=c9eS5SzPLfYkd-BetHKWhd-eSoYPWHjF6-xo4Q%3D%3D&details%5B2%5D.key=bucket&details%5B2%5D.value=s3%3A%2F%2Ftemplates&details%5B3%5D.key=endpoint&details%5B3%5D.value=&details%5B4%5D.key=usehttps&details%5B4%5D.value=false&details%5B5%5D.key=connectiontimeout&details%5B5%5D.value=&details%5B6%5D.key=maxerrorretry&details%5B6%5D.value=&details%5B7%5D.key=sockettimeout&details%5B7%5D.value=&_=136854473 > If the optional parameter value is not specified blank values are being > passed to api. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2529) [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the full GSLB domain name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659865#comment-13659865 ] ASF subversion and git services commented on CLOUDSTACK-2529: - Commit d2d0398e3321b819756a537c0b1fab0491e5a3e6 in branch refs/heads/planner_reserve from Murali Reddy [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d2d0398 ] CLOUDSTACK-2529: GlobalLoadBalancerResponse should have the full FQDN for the global load balanced service > [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the > full GSLB domain name > --- > > Key: CLOUDSTACK-2529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy > Fix For: 4.2.0 > > > Steps to reproduce : > 1. Have at least one GSLB enabled zone > 2. Have at least one non-ROOT domain user > 3. Login as the above user and create a GSLB rule and assign LB rules to GSLB > Observations: > (i) Everything goes fine but, there is no way currently to inform the user > what will be the full domain name. > (ii) It will be good if we can prompt a message and show the complete domain > name > Complete domain name will be "GSLB domain name specified by user + value of > the global setting cloud.dns.name" -- 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-2462) [GSLB] Failed to create GSLB rule with "proximity" algorithm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659864#comment-13659864
]
ASF subversion and git services commented on CLOUDSTACK-2462:
-
Commit 33e683915c3083ac60a578fc90a7d90a64cb028e in branch
refs/heads/planner_reserve from Murali Reddy
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=33e6839 ]
CLOUDSTACK-2462: Failed to create GSLB rule with "proximity" algorithm
add RTT as load balancing method for GSLB vserver
> [GSLB] Failed to create GSLB rule with "proximity" algorithm
>
>
> Key: CLOUDSTACK-2462
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2462
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have CloudStack setup with at least 1 adv zone
> 2. Try to create a GSLB rule by setting "gslblbmethod" to "proximity"
> Observations :
> (i) It fails with the following error in the mgmt server logs
> 2013-05-13 16:20:35,421 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-22:job-327) Access to Rule[7-LoadBalancing-Active] granted to
> Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4
> 2013-05-13 16:20:35,467 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Sending { Cmd , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 100011,
> [{"routing.GlobalLoadBalancerConfigCommand":{"domainName":"proximity.cloud.xyztelcom.com","serviceType":"tcp","lbMethod":"proximity","persistenceType":"sourceip","gslbId":26,"revoked":false,"siteLoadBalancers":[{"local":true,"revoked":false,"serviceType":"tcp","servicePublicIp":"10.147.44.61","servicePort":"22","gslbProviderPrivateIp":"10.147.44.20","dataCenterId":1}],"wait":0}}]
> }
> 2013-05-13 16:20:35,467 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Executing: { Cmd , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 100011,
> [{"routing.GlobalLoadBalancerConfigCommand":{"domainName":"proximity.cloud.xyztelcom.com","serviceType":"tcp","lbMethod":"proximity","persistenceType":"sourceip","gslbId":26,"revoked":false,"siteLoadBalancers":[{"local":true,"revoked":false,"serviceType":"tcp","servicePublicIp":"10.147.44.61","servicePort":"22","gslbProviderPrivateIp":"10.147.44.20","dataCenterId":1}],"wait":0}}]
> }
> 2013-05-13 16:20:35,468 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-492:null) Seq 26-754647047: Executing request
> 2013-05-13 16:20:35,540 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,582 WARN [network.resource.NetscalerResource]
> (DirectAgent-492:null) Retrying GlobalLoadBalancerConfigCommand. Number of
> retries remaining: 1
> 2013-05-13 16:20:35,651 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,704 WARN [network.resource.NetscalerResource]
> (DirectAgent-492:null) Retrying GlobalLoadBalancerConfigCommand. Number of
> retries remaining: 0
> 2013-05-13 16:20:35,772 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,773 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-492:null) Seq 26-754647047: Response Received:
> 2013-05-13 16:20:35,773 DEBUG [agent.transport.Request]
> (DirectAgent-492:null) Seq 26-754647047: Processing: { Ans: , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 10,
> [{"routing.GlobalLoadBalancerConfigAnswer":{"result":false,"details":"Failed
> to apply GSLB configuration due to Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]","wait":0}}] }
> 2013-05-13 16:20:35,773 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Received: { Ans: , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 10, { GlobalLoadBalancerConfigAnswer
> } }
> 2013-05-13 16:20:35,773 DEBUG [agent.manager.AgentManagerImpl]
> (Job-Executor-22:job-327) Details from executing class
> com.cloud.agent.api.routing.Globa
[jira] [Commented] (CLOUDSTACK-2378) [GSLB] assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing when there are multiple physical network in a zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659863#comment-13659863 ] ASF subversion and git services commented on CLOUDSTACK-2378: - Commit f441582e1b7747bba1385ecb48a7b7b34a9dded1 in branch refs/heads/planner_reserve from Murali Reddy [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f441582 ] CLOUDSTACK-2378: assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing when there are multiple physical network in a zone adding support for deployments where multiple physical networks are configured for guest traffic in a zone > [GSLB] assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing > when there are multiple physical network in a zone > --- > > Key: CLOUDSTACK-2378 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2378 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have CloudStack with at least one zone with multiple physical networks > 2. Have GSLB device configured in each physical network of the zone > 3. create GSLB rule > 4. Try to assign at least one LB rule from any of the above physical networks > Observations : > (i) It fails with the following error > 2013-05-08 08:14:59,990 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-79:job-238) Schedule queued job-238 > 2013-05-08 08:14:59,997 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-79:job-238) There is a pending process in sync queue(id: 67) > 2013-05-08 08:15:00,000 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > for job-238 > 2013-05-08 08:15:00,023 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-80:job-238) Access to > org.apache.cloudstack.region.gslb.GlobalLoadBalancerRuleVO$$EnhancerByCGLIB$$75a5db02@5b35b0ae > granted to Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-08 08:15:00,030 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-80:job-238) Access to Rule[7-LoadBalancing-Active] granted to > Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-08 08:15:00,039 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Unexpected exception while executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > com.cloud.exception.InvalidParameterValueException: Unable to get physical > network in zone id = 1 > at > com.cloud.network.element.NetscalerElement.findGslbProvider(NetscalerElement.java:861) > at > com.cloud.network.element.NetscalerElement.isServiceEnabledInZone(NetscalerElement.java:872) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.checkGslbServiceEnabledInZone(GlobalLoadBalancingRulesServiceImpl.java:608) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:224) > at > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:106) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-05-08 08:15:00,041 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Complete async job-238, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Unable to get physical network in > zone id = 1 > 2013-05-08 08:15:00,058 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-80:job-238) Sync queue (67) is currently empty > (ii) if we are going to support multiple physical networks with GSLB
[jira] [Commented] (CLOUDSTACK-2544) System VM's are failed to start with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659862#comment-13659862 ] ASF subversion and git services commented on CLOUDSTACK-2544: - Commit d078f921671d0f28d9291fa2bffa8a7eab53cda7 in branch refs/heads/planner_reserve from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d078f92 ] CLOUDSTACK-2544: Fix NPE while comparing lastHostId during capacity calculation > System VM's are failed to start with NPE > > > Key: CLOUDSTACK-2544 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2544 > 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: Sailaja Mada >Assignee: Kishan Kavala >Priority: Blocker > > Steps: > 1. Create Adv networking setup. > Observation: > System VM's are failed to start with NPE > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release cpu from host: 1, old used: 0,reserved: 0, actual > total: 9572, total with overprovisioning: 9572; new used: 0,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release mem from host: 1, old used: 0,reserved: 0, total: > 17166258176; new used: 0,reserved:0; movedfromreserved: > false,moveToReserveredfalse > 2013-05-16 17:12:20,524 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > java.lang.NullPointerException > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:684) > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:90) > at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117) > at > com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1251) > at > com.cloud.vm.VirtualMachineManagerImpl.changeState(VirtualMachineManagerImpl.java:660) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:817) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:540) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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-05-16 17:12:20,526 INFO [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Unable to start secondary storage vm for standby > capacity, secStorageVm vm Id : 4, will recycle it and start a new one > 2013-05-16 17:12:20,529 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) VM is already stopped: VM[SecondaryStorageVm|s-4-VM] > 2013-05-16 17:12:20,537 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Stopped to Expunging with > event: ExpungeOperationvm's orig
[jira] [Created] (CLOUDSTACK-2548) [Automation] Failed to delete public IP range
Rayees Namathponnan created CLOUDSTACK-2548: --- Summary: [Automation] Failed to delete public IP range Key: CLOUDSTACK-2548 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2548 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 build : Latest Issue found : During BVT automation run on KVM Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.2.0 Test case : test/integration/smoke/test_public_ip_range.py Steps to reproduce Step 1 : Create advance zone, and add IP range [In my case added 10.223.122.124 to 10.223.122.126] Step 2 : Delete this IP range Actual Result Release IP range operation failed with below error "One of the ips in the range is used to provide Dhcp service to this subnet. cannot delete this range as" If you look the DB, ip range 10.223.122.124 to 10.223.122.126 is not allocated mysql> select * from user_ip_address where state!="Free"; ++--++---+---+++-+++---+---+-+---++-+---++---+ | id | uuid | account_id | domain_id | public_ip_address | data_center_id | source_nat | allocated | vlan_db_id | one_to_one_nat | vm_id | state | mac_address | source_network_id | network_id | physical_network_id | is_system | vpc_id | dnat_vmip | ++--++---+---+++-+++---+---+-+---++-+---++---+ | 2 | ddd29f48-54ba-4b76-b493-c62948f1 | 38 | 1 | 10.223.122.67 | 1 | 1 | 2013-05-16 18:01:34 | 1 | 0 | NULL | Allocated | 60 | 200 | 241 | 200 | 0 | NULL | NULL | | 3 | e4f7899b-1d5b-4c7c-91bd-38af7db1945a | 4 | 1 | 10.223.122.68 | 1 | 1 | 2013-05-16 03:54:34 | 1 | 0 | NULL | Releasing | 61 | 200 | 209 | 200 | 0 | NULL | NULL | | 4 | ab3b333a-bad2-427f-ad7d-6d9f3cac5336 | 1 | 1 | 10.223.122.69 | 1 | 0 | 2013-05-16 04:56:39 | 1 | 0 | NULL | Allocated | 62 | 200 | NULL | 200 | 0 | NULL | NULL | | 6 | 73fe34aa-bdce-4f58-bc54-40fe6584a2da | 2 | 1 | 10.223.122.71 | 1 | 1 | 2013-05-16 05:43:59 | 1 | 0 | NULL | Allocated | 64 | 200 | 230 | 200 | 0 | NULL | NULL | | 23 | b97b3062-a82d-487a-8d56-4355ce72d3c7 | 2 | 1 | 10.223.122.88 | 1 | 1 | 2013-05-16 05:23:12 | 1 | 0 | NULL | Allocated | 81 | 200 | 227 | 200 | 0 | NULL | NULL | | 32 | 3d1f0625-90a0-4632-9cfb-aed018efa51c | 2 | 1 | 10.223.122.97 | 1 | 1 | 2013-05-16 05:52:11 | 1 | 0 | NULL | Allocated | 90 | 200 | 232 | 200 | 0 | NULL | NULL | | 52 | 851757d9-92f2-493c-98f6-3bd01b0c2d3b | 1 | 1 | 10.223.122.117| 1 | 0 | 2013-05-16 04:54:09 | 1 | 0 | NULL | Allocated | 110 | 200 | NULL | 200 | 0 | NULL | NULL | | 60 | eede24f6-6587-4f75-8e2a-7063ffd2c833 | 1 | 1 | 10.223.121.132| 2 | 0 | 2013-05-16 03:39:09 | 2 | 0 | NULL | Allocated | 61 | 204 | NULL | 201 | 0 | NULL | NULL | | 63 | a720338f-15f8-4d47-acc0-da6a2917406d | 1 | 1 | 10.223.121.135| 2 | 0 | 2013-05-16 03:39:17 | 2 | 0 | NULL | Allocated | 64 | 204 | NULL | 201 | 0 | NULL | NULL | ++--++---+---+++-+++---+---+-+--
[jira] [Created] (CLOUDSTACK-2547) [Automation] Should not allow to create VLAN beyond 4095
Rayees Namathponnan created CLOUDSTACK-2547: --- Summary: [Automation] Should not allow to create VLAN beyond 4095 Key: CLOUDSTACK-2547 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2547 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Rayees Namathponnan Priority: Minor There are a maximum of 4096 possible values ranging from 0 to 4095 for VLAN, but cloudstack allowing more then this. Steps to reproduce Run below automation test case test/integration/smoke/test_public_ip_range.py -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-747) nTier Apps 2.0 : Internal Load Balancing between the VPC tiers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659811#comment-13659811 ] ASF subversion and git services commented on CLOUDSTACK-747: Commit b5acb9034f2463c891fa424cd9deaae17501eebc in branch refs/heads/ui-vpc-redesign from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b5acb90 ] CLOUDSTACK-747: UI - Internal LB - implement Add Internal LB action. > nTier Apps 2.0 : Internal Load Balancing between the VPC tiers > --- > > Key: CLOUDSTACK-747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-747 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Kishan Kavala >Assignee: Brian Federle > Fix For: 4.2.0 > > > This item is sub task (2.2) of > https://issues.apache.org/jira/browse/CLOUDSTACK-621 > Currently, Load Balancing VPC VR is only supported on one of the Tiers of an > nTier Application. With this release, CloudStack should support load > balancing on all tiers of an nTier application. > Use Case: Users would like to deploy a multi-tier application with the VR > load balancing each of the tiers. As a result, users would be able to provide > flexibility and elasticity at each tier of their application -- 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-2215) ACS41 SSVM does not use allocated storage ip range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ilya musayev updated CLOUDSTACK-2215: - Affects Version/s: 4.0.1 4.0.2 > ACS41 SSVM does not use allocated storage ip range > -- > > Key: CLOUDSTACK-2215 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2215 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, Storage Controller >Affects Versions: 4.0.1, 4.0.2, 4.1.0 > Environment: ACS4.1 as of 04/15/13 - i know its 10 days old, but i've > not seen fixes for this yet. > VMWare vSphere 5.0 with Advanced Network >Reporter: ilya musayev >Priority: Blocker > Labels: Network, SSVM > > Create Advanced Network Zone, assign a range of IPs to storage network, also > predefine public range. > The Secondary Storage VM gets the IPs of Public Networks and not whats its > been given. In my example, i've defined two public networks - with very small > ip range (4 on each). I noticed that SSVM took 2 IPs from Public Network A, > and 1 IP from Public Network B. > If you have stringent setup and you need to allocate IPs as designed and > setup firewall rules, one would expect to setup firewall rules on storage ip > range, thinking that SSVM is going to use the IP from that range, however, > instead - it uses public ip range. -- 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-2522) While processing agents behind on ping, we may fail to process a host that is already in 'Down' state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659794#comment-13659794 ] ASF subversion and git services commented on CLOUDSTACK-2522: - Commit c8af438e64abea2c4138fab13c1d4d5ab669ada0 in branch refs/heads/planner_reserve from Prachi Damle [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c8af438 ] CLOUDSTACK-2522: While processing agents behind on ping, we may fail to process a host that is already in 'Down' state Changes: - Added a transition for DOWN -> DOWN state on PING TIMEOUT so that transition will set mgmt_server_id in the host table to null. > While processing agents behind on ping, we may fail to process a host that is > already in 'Down' state > - > > Key: CLOUDSTACK-2522 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2522 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Prachi Damle >Assignee: Prachi Damle > Fix For: 4.2.0 > > > From the code I see that there is no transition for hosts from DOWN state > with event PING > timeout. This causes an error when AgentMonitor does a delayed processing of > the ping, for a host that has gone to DOWN state. As a result the host state > never gets updated in our DB. > Only when host state transition happens then is the mgmt_server_id made null > by > HostDaoImpl:: Update code. > Since state transition never happens, mgmt_server_id remains non-null causing > reconnect of this host not to trigger. > I think this can be fixed by introducing state transition for DOWN state on > ping timeout. -- 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-2519) VMs on local storage incorrectly destroyed when removing another host using deleteHost API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659795#comment-13659795 ] ASF subversion and git services commented on CLOUDSTACK-2519: - Commit ddd7cfd71c45c708012d30a0b7858db9d74c90f4 in branch refs/heads/planner_reserve from Prachi Damle [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ddd7cfd ] CLOUDSTACK-2519: VMs on local storage incorrectly destroyed when removing another host using deleteHost API - For DeleteHost API: Search for Volumes in READY state on the local storage of the host to find VM's in 'Running' State - For PrepareForMaintenance API: Search for Volumes not in Destroy or Expunging state to check if the Local Storage on the host is being used. > VMs on local storage incorrectly destroyed when removing another host using > deleteHost API > -- > > Key: CLOUDSTACK-2519 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2519 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Prachi Damle >Assignee: Prachi Damle > Fix For: 4.2.0 > > > Steps to reproduce: > Using local storage following erroneous situation is observed while using > deleteHost API: > - Use local storage. Suppose Zone has 2 clusters, say Cluster1 has 2 hosts > (host A and host B). Cluster 2 has 1 host (host C) > During deployVM following needs to happen: > 1) host A is selected and VM's root disk is created on its local storage. > Then mgt server sends start command to the host A to start this vm, but > somehow, start vm failed. > 2) Then we will retry another host in the same cluster, but no other host in > that cluster can be used since the root Disk on local storage is not > accessible to hostB. > 3) Then planner will find host C in other cluster and a new local storage pool > 4) Mgmt server will mark the previous root disk as destroyed, and create new > root disk on local stoarge of host C > 5) Vm starts successfully on host C > 6) At this point, VM instance is on host C. In volumes table, 2 records point > to this VM instance - one record is the root disk in READY state on host C > LVM. Another entry is root disk in Destroy state (that was created in step 1 > ) on host A LVM. This is fine. > 7) Now using deleteHostAPI, try to delete Host A. When host A is deleted, the > VM running on host C gets destroyed. Use command: > command=deleteHost&id=&forced=true&forcedestroylocalstorage=true > This is a bug that is picking the VM on host C wrongly because we find a > volume record on host A LVM pointing to this VM. Mgmt Server should not > destroy this VM. To fix this it should search the volumes records that are in > READY state only. > To reproduce this, simulator might be needed since we need to somehow return > error to the startCommand from hostA in step 1 above. But host C should > return success. -- 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-2517) [nTier:PrivateGateway] network create issues with private gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659796#comment-13659796 ] ASF subversion and git services commented on CLOUDSTACK-2517: - Commit 9f59c618e277f4b9ce7e3cdd4156012b1d538471 in branch refs/heads/planner_reserve from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9f59c61 ] CLOUDSTACK-2517: fixed private gateway creation. Following fixes went in: 1) Only PrivateNetworkGuru handles network creation for the private gateway. Exluded Guest Network Guru from this list (was mistakenly included as a part of merge for Nicira integration) 2) Pass vpc_id to createNetwork call when the network is created as a part of private gateway creation 3) Fixed VPC restart when there are multiple private gateways present (have to grab all the private gateways when creating nic profiles for the VPC router that is being re-created) 4) 41-42 db upgarde: set vpc_id for the private networks of the existing VPCs > [nTier:PrivateGateway] network create issues with private gateway > - > > Key: CLOUDSTACK-2517 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2517 > 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: Alena Prokharchyk >Priority: Critical > Fix For: 4.2.0 > > > 1. creating private gateway create two network entries (ExternalNetworkGuru, > privateNetworkGuru) into networks table. > 2. When creating same private gateway in different vpc cloudstack is not > created two different networks into networks table. > 3. private networks in networks table did not have VPC id. So not able to > distinguish networks for the two vacs. > 4. Creating two network entries causing issues while adding and deleting > private gateway > a.CLOUDSTACK-2426 because the network (ExternalNetworkGuru is not cleanup) -- 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-2486) Deleting the host_details and inserting them back can lead to mysql deadlock
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659797#comment-13659797 ] ASF subversion and git services commented on CLOUDSTACK-2486: - Commit 73030f43729f408acd8c6325541db2f184757e80 in branch refs/heads/planner_reserve from Prachi Damle [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=73030f4 ] CLOUDSTACK-2486: Deleting the host_details and inserting them back can lead to mysql deadlock - Changing the correct details dao. Instead of using separate delete and insert, we will use ON DUPLICATE KEY UPDATE to avoid the MySQL deadlock > Deleting the host_details and inserting them back can lead to mysql deadlock > > > Key: CLOUDSTACK-2486 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2486 > 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: Prachi Damle >Assignee: Prachi Damle > > When host tries to connect to management server, the old host_details are > deleted and new records are inserted. MySQL deadlock is seen sometimes during > this delete and insert on the same table. If this error happens, host > connection fails. > a) This issue is intermittent issue seen with MySQL. It seems to happen when > we are deleting and inserting records in the same table in one transaction. > b)CS auto-corrects this error state: > CloudStack has host connection 'retry' mechanism where we try to connect back > to the host. This retry mechanism corrects this issue because the DB issue is > intermittent and eventually the hosts connect back. > Hence this does not affect the CS functionality. -- 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-2492) System VM Clock Drift
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659731#comment-13659731 ] ASF subversion and git services commented on CLOUDSTACK-2492: - Commit 2fdeee4de7aaca336d68010de9baa731e440cadb in branch refs/heads/4.1 from Chip Childers [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2fdeee4 ] CLOUDSTACK-2492: enable time sync on vmware if ntp is not installed > System VM Clock Drift > - > > Key: CLOUDSTACK-2492 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2492 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: ISO >Affects Versions: 4.1.0 > Environment: devcloud/Xen >Reporter: John Burwell >Priority: Blocker > Labels: documentaion > > Testing of S3-backed Secondary Storage has revealed that the SSVM (and likely > all other system VMs) have no provision for clock synchronization (e.g. NTP > to dom0 for Xen, vmware-tools for VMWare, etc). In particular, the S3 > protocol is sensitive to drift between clients and S3. As an example, the > following is the stack trace caused by clock drift S3: > 2013-05-14 06:51:55,400 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) > Putting directory > /mnt/SecStorage/93fd0cb0-033b-3248-bcd0-ef6d460635ef/template/tmpl/1/5 in S3 > bucket jsb-cloudstack-templates. > 2013-05-14 06:51:55,401 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) > Creating S3 client with configuration: [protocol: https, connectionTimeOut: > 5, maxErrorRetry: 3, socketTimeout: 5] > 2013-05-14 06:51:55,403 DEBUG [storage.resource.NfsSecondaryStorageResource] > (agentRequest-Handler-3:) Determining key using account id 1 and template id 5 > 2013-05-14 06:51:55,403 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) > Putting file > /mnt/SecStorage/93fd0cb0-033b-3248-bcd0-ef6d460635ef/template/tmpl/1/5/template.properties > into bucket jsb-cloudstack-templates with key > template/tmpl/1/5/template.properties. > 2013-05-14 06:51:55,578 ERROR [storage.resource.NfsSecondaryStorageResource] > (agentRequest-Handler-3:) Failed to upload template id 5 > Status Code: 403, AWS Service: Amazon S3, AWS Request ID: 970A274E132A9ACB, > AWS Error Code: RequestTimeTooSkewed, AWS Error Message: The difference > between the request time and the current time is too large., S3 Extended > Request ID: 9w8a6YBxTn+WlBg96s9stxWuuP8oQ7ksZtg6++wVRHJfE2qmucrilhoEJVetJui4 > at > com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:609) > at > com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:309) > at > com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:164) > at > com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:2863) > at > com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1100) > at > com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:963) > at com.cloud.utils.S3Utils.putDirectory(S3Utils.java:282) > at > com.cloud.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:414) > at > com.cloud.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:212) > 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$Worker.runTask(ThreadPoolExecutor.java:886) > In addition to impacting S3, this clock drift also makes log correlation > between the management server and system VMs very difficult, if not, > impossible. Finally, there are suspicions that the clock drift could also > impact operation of console proxy and virtual router VMs. -- 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-2215) ACS41 SSVM does not use allocated storage ip range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reassigned CLOUDSTACK-2215: - Assignee: (was: Chip Childers) > ACS41 SSVM does not use allocated storage ip range > -- > > Key: CLOUDSTACK-2215 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2215 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, Storage Controller >Affects Versions: 4.1.0 > Environment: ACS4.1 as of 04/15/13 - i know its 10 days old, but i've > not seen fixes for this yet. > VMWare vSphere 5.0 with Advanced Network >Reporter: ilya musayev >Priority: Blocker > Labels: Network, SSVM > > Create Advanced Network Zone, assign a range of IPs to storage network, also > predefine public range. > The Secondary Storage VM gets the IPs of Public Networks and not whats its > been given. In my example, i've defined two public networks - with very small > ip range (4 on each). I noticed that SSVM took 2 IPs from Public Network A, > and 1 IP from Public Network B. > If you have stringent setup and you need to allocate IPs as designed and > setup firewall rules, one would expect to setup firewall rules on storage ip > range, thinking that SSVM is going to use the IP from that range, however, > instead - it uses public ip range. -- 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-2544) System VM's are failed to start with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659720#comment-13659720 ] ASF subversion and git services commented on CLOUDSTACK-2544: - Commit d078f921671d0f28d9291fa2bffa8a7eab53cda7 in branch refs/heads/ui-vpc-redesign from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d078f92 ] CLOUDSTACK-2544: Fix NPE while comparing lastHostId during capacity calculation > System VM's are failed to start with NPE > > > Key: CLOUDSTACK-2544 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2544 > 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: Sailaja Mada >Assignee: Kishan Kavala >Priority: Blocker > > Steps: > 1. Create Adv networking setup. > Observation: > System VM's are failed to start with NPE > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release cpu from host: 1, old used: 0,reserved: 0, actual > total: 9572, total with overprovisioning: 9572; new used: 0,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release mem from host: 1, old used: 0,reserved: 0, total: > 17166258176; new used: 0,reserved:0; movedfromreserved: > false,moveToReserveredfalse > 2013-05-16 17:12:20,524 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > java.lang.NullPointerException > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:684) > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:90) > at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117) > at > com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1251) > at > com.cloud.vm.VirtualMachineManagerImpl.changeState(VirtualMachineManagerImpl.java:660) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:817) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:540) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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-05-16 17:12:20,526 INFO [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Unable to start secondary storage vm for standby > capacity, secStorageVm vm Id : 4, will recycle it and start a new one > 2013-05-16 17:12:20,529 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) VM is already stopped: VM[SecondaryStorageVm|s-4-VM] > 2013-05-16 17:12:20,537 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Stopped to Expunging with > event: ExpungeOperationvm's orig
[jira] [Commented] (CLOUDSTACK-2378) [GSLB] assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing when there are multiple physical network in a zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659721#comment-13659721 ] ASF subversion and git services commented on CLOUDSTACK-2378: - Commit f441582e1b7747bba1385ecb48a7b7b34a9dded1 in branch refs/heads/ui-vpc-redesign from Murali Reddy [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f441582 ] CLOUDSTACK-2378: assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing when there are multiple physical network in a zone adding support for deployments where multiple physical networks are configured for guest traffic in a zone > [GSLB] assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing > when there are multiple physical network in a zone > --- > > Key: CLOUDSTACK-2378 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2378 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have CloudStack with at least one zone with multiple physical networks > 2. Have GSLB device configured in each physical network of the zone > 3. create GSLB rule > 4. Try to assign at least one LB rule from any of the above physical networks > Observations : > (i) It fails with the following error > 2013-05-08 08:14:59,990 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-79:job-238) Schedule queued job-238 > 2013-05-08 08:14:59,997 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-79:job-238) There is a pending process in sync queue(id: 67) > 2013-05-08 08:15:00,000 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > for job-238 > 2013-05-08 08:15:00,023 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-80:job-238) Access to > org.apache.cloudstack.region.gslb.GlobalLoadBalancerRuleVO$$EnhancerByCGLIB$$75a5db02@5b35b0ae > granted to Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-08 08:15:00,030 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-80:job-238) Access to Rule[7-LoadBalancing-Active] granted to > Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-08 08:15:00,039 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Unexpected exception while executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > com.cloud.exception.InvalidParameterValueException: Unable to get physical > network in zone id = 1 > at > com.cloud.network.element.NetscalerElement.findGslbProvider(NetscalerElement.java:861) > at > com.cloud.network.element.NetscalerElement.isServiceEnabledInZone(NetscalerElement.java:872) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.checkGslbServiceEnabledInZone(GlobalLoadBalancingRulesServiceImpl.java:608) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:224) > at > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:106) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-05-08 08:15:00,041 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Complete async job-238, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Unable to get physical network in > zone id = 1 > 2013-05-08 08:15:00,058 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-80:job-238) Sync queue (67) is currently empty > (ii) if we are going to support multiple physical networks with GSLB
[jira] [Commented] (CLOUDSTACK-2462) [GSLB] Failed to create GSLB rule with "proximity" algorithm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659722#comment-13659722
]
ASF subversion and git services commented on CLOUDSTACK-2462:
-
Commit 33e683915c3083ac60a578fc90a7d90a64cb028e in branch
refs/heads/ui-vpc-redesign from Murali Reddy
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=33e6839 ]
CLOUDSTACK-2462: Failed to create GSLB rule with "proximity" algorithm
add RTT as load balancing method for GSLB vserver
> [GSLB] Failed to create GSLB rule with "proximity" algorithm
>
>
> Key: CLOUDSTACK-2462
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2462
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have CloudStack setup with at least 1 adv zone
> 2. Try to create a GSLB rule by setting "gslblbmethod" to "proximity"
> Observations :
> (i) It fails with the following error in the mgmt server logs
> 2013-05-13 16:20:35,421 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-22:job-327) Access to Rule[7-LoadBalancing-Active] granted to
> Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4
> 2013-05-13 16:20:35,467 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Sending { Cmd , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 100011,
> [{"routing.GlobalLoadBalancerConfigCommand":{"domainName":"proximity.cloud.xyztelcom.com","serviceType":"tcp","lbMethod":"proximity","persistenceType":"sourceip","gslbId":26,"revoked":false,"siteLoadBalancers":[{"local":true,"revoked":false,"serviceType":"tcp","servicePublicIp":"10.147.44.61","servicePort":"22","gslbProviderPrivateIp":"10.147.44.20","dataCenterId":1}],"wait":0}}]
> }
> 2013-05-13 16:20:35,467 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Executing: { Cmd , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 100011,
> [{"routing.GlobalLoadBalancerConfigCommand":{"domainName":"proximity.cloud.xyztelcom.com","serviceType":"tcp","lbMethod":"proximity","persistenceType":"sourceip","gslbId":26,"revoked":false,"siteLoadBalancers":[{"local":true,"revoked":false,"serviceType":"tcp","servicePublicIp":"10.147.44.61","servicePort":"22","gslbProviderPrivateIp":"10.147.44.20","dataCenterId":1}],"wait":0}}]
> }
> 2013-05-13 16:20:35,468 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-492:null) Seq 26-754647047: Executing request
> 2013-05-13 16:20:35,540 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,582 WARN [network.resource.NetscalerResource]
> (DirectAgent-492:null) Retrying GlobalLoadBalancerConfigCommand. Number of
> retries remaining: 1
> 2013-05-13 16:20:35,651 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,704 WARN [network.resource.NetscalerResource]
> (DirectAgent-492:null) Retrying GlobalLoadBalancerConfigCommand. Number of
> retries remaining: 0
> 2013-05-13 16:20:35,772 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,773 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-492:null) Seq 26-754647047: Response Received:
> 2013-05-13 16:20:35,773 DEBUG [agent.transport.Request]
> (DirectAgent-492:null) Seq 26-754647047: Processing: { Ans: , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 10,
> [{"routing.GlobalLoadBalancerConfigAnswer":{"result":false,"details":"Failed
> to apply GSLB configuration due to Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]","wait":0}}] }
> 2013-05-13 16:20:35,773 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Received: { Ans: , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 10, { GlobalLoadBalancerConfigAnswer
> } }
> 2013-05-13 16:20:35,773 DEBUG [agent.manager.AgentManagerImpl]
> (Job-Executor-22:job-327) Details from executing class
> com.cloud.agent.api.routing.Globa
[jira] [Commented] (CLOUDSTACK-2529) [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the full GSLB domain name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659723#comment-13659723 ] ASF subversion and git services commented on CLOUDSTACK-2529: - Commit d2d0398e3321b819756a537c0b1fab0491e5a3e6 in branch refs/heads/ui-vpc-redesign from Murali Reddy [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d2d0398 ] CLOUDSTACK-2529: GlobalLoadBalancerResponse should have the full FQDN for the global load balanced service > [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the > full GSLB domain name > --- > > Key: CLOUDSTACK-2529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy > Fix For: 4.2.0 > > > Steps to reproduce : > 1. Have at least one GSLB enabled zone > 2. Have at least one non-ROOT domain user > 3. Login as the above user and create a GSLB rule and assign LB rules to GSLB > Observations: > (i) Everything goes fine but, there is no way currently to inform the user > what will be the full domain name. > (ii) It will be good if we can prompt a message and show the complete domain > name > Complete domain name will be "GSLB domain name specified by user + value of > the global setting cloud.dns.name" -- 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-2215) ACS41 SSVM does not use allocated storage ip range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659675#comment-13659675 ] Noel D. Kendall commented on CLOUDSTACK-2215: - It appears to me that there are some defects in this area. In my 4.0.1 environment, I see that the SSVM has an incorrect routing table set up. I have a simple setup with one host. Advanced networking, two physical networks, one for mgmt and storage, traffic segregated with VLANs, and a bridge on host for management, and one for storage. The host quite happily is able to mount NFS secondary storage. The SSVM's routing table starts life with an entry routing the public network out through my configured pod gateway. However, the gateway for the storage subnet is also incorrectly set to the Pod gateway. The routing table should simply point to the interface which is bridged over to the storage on the host. The result is that NFS mounts in the SSVM hang (the NFS packets are forwarded to the pod gateway, which has no path to the storage network at all). In my view, from what I have read in the documentation, and numerous online examples, the plumbing to interconnect the storage subnet in the SSVM is dead simple, and should not be touched or affected by the need for a route to either an external DNS or a public network. As a workaround, I have added a couple of lines in rc.local that delete the incorrect route and add back the correct route, and this has been effective. Seems like a straightforward defect to me. In reading the original description, it seems to cloud (pardon the pun) the real issue. > ACS41 SSVM does not use allocated storage ip range > -- > > Key: CLOUDSTACK-2215 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2215 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, Storage Controller >Affects Versions: 4.1.0 > Environment: ACS4.1 as of 04/15/13 - i know its 10 days old, but i've > not seen fixes for this yet. > VMWare vSphere 5.0 with Advanced Network >Reporter: ilya musayev >Assignee: Chip Childers >Priority: Blocker > Labels: Network, SSVM > > Create Advanced Network Zone, assign a range of IPs to storage network, also > predefine public range. > The Secondary Storage VM gets the IPs of Public Networks and not whats its > been given. In my example, i've defined two public networks - with very small > ip range (4 on each). I noticed that SSVM took 2 IPs from Public Network A, > and 1 IP from Public Network B. > If you have stringent setup and you need to allocate IPs as designed and > setup firewall rules, one would expect to setup firewall rules on storage ip > range, thinking that SSVM is going to use the IP from that range, however, > instead - it uses public ip range. -- 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-2215) ACS41 SSVM does not use allocated storage ip range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ilya musayev reopened CLOUDSTACK-2215: -- Chip, As per IRC communication with several users, we believe this is a valid issue and it was reported by 2 people on IRC in 2 days. Below is excerpt from the doc: Storage. Traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network. My understanding of this - SSVM should get an IP and network configs from the network range defined by on storage network. Where as now, it does not. I've asked another user on IRC, NDK to update this issue as he has the same problem on KVM setup. Thanks ilya > ACS41 SSVM does not use allocated storage ip range > -- > > Key: CLOUDSTACK-2215 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2215 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, Storage Controller >Affects Versions: 4.1.0 > Environment: ACS4.1 as of 04/15/13 - i know its 10 days old, but i've > not seen fixes for this yet. > VMWare vSphere 5.0 with Advanced Network >Reporter: ilya musayev >Assignee: Chip Childers >Priority: Blocker > Labels: Network, SSVM > > Create Advanced Network Zone, assign a range of IPs to storage network, also > predefine public range. > The Secondary Storage VM gets the IPs of Public Networks and not whats its > been given. In my example, i've defined two public networks - with very small > ip range (4 on each). I noticed that SSVM took 2 IPs from Public Network A, > and 1 IP from Public Network B. > If you have stringent setup and you need to allocate IPs as designed and > setup firewall rules, one would expect to setup firewall rules on storage ip > range, thinking that SSVM is going to use the IP from that range, however, > instead - it uses public ip range. -- 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-2546) [Automation] Failed to add second NIC to vm in KVM environment
Rayees Namathponnan created CLOUDSTACK-2546: --- Summary: [Automation] Failed to add second NIC to vm in KVM environment Key: CLOUDSTACK-2546 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2546 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: KVM Build : Latest master build Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.2.0 Automation test case /test/integration/smoke/test_nic.py failed Steps to reproduce 1) Create and account, service offering 2) Create Network offering (isolated) and Create network 3) Create VM with the network 4) After VM is up, add another network to VM Expected result Second nic should be added Actual result Failed to add second nic 2013-05-16 10:49:07,804 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-68:job-292) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd com.cloud.utils.exception.CloudRuntimeException: A NIC already exists for VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030 at com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:844) at org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:109) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-05-16 10:49:07,809 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-68:job-292) Complete async job-292, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: A NIC already exists for VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030 2013-05-16 10:49:09,334 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready -- 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-2545) Inconsistent unit of network statistics between js and kvm plugin
Wei Zhou created CLOUDSTACK-2545: Summary: Inconsistent unit of network statistics between js and kvm plugin Key: CLOUDSTACK-2545 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2545 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Wei Zhou Assignee: Wei Zhou Priority: Minor Fix For: 4.1.0 when convert bytes to KBs in kvm plugin (LibvirtComputingResource.java) stats.setNetworkReadKBs(deltarx / 1000); stats.setNetworkWriteKBs(deltatx / 1000); But on cloudstack ui (ui/scripts/instances.js) networkkbsread: (jsonObj.networkkbsread == null)? "N/A": cloudStack.converters.convertBytes(jsonObj.networkkbsread * 1024), networkkbswrite: (jsonObj.networkkbswrite == null)? "N/A": cloudStack.converters.convertBytes(jsonObj.networkkbswrite * 1024) It means, if the real value is 1000, the display on cloudstack ui will be 1024. -- 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-2544) System VM's are failed to start with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala resolved CLOUDSTACK-2544. --- Resolution: Fixed > System VM's are failed to start with NPE > > > Key: CLOUDSTACK-2544 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2544 > 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: Sailaja Mada >Assignee: Kishan Kavala >Priority: Blocker > > Steps: > 1. Create Adv networking setup. > Observation: > System VM's are failed to start with NPE > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release cpu from host: 1, old used: 0,reserved: 0, actual > total: 9572, total with overprovisioning: 9572; new used: 0,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release mem from host: 1, old used: 0,reserved: 0, total: > 17166258176; new used: 0,reserved:0; movedfromreserved: > false,moveToReserveredfalse > 2013-05-16 17:12:20,524 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > java.lang.NullPointerException > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:684) > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:90) > at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117) > at > com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1251) > at > com.cloud.vm.VirtualMachineManagerImpl.changeState(VirtualMachineManagerImpl.java:660) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:817) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:540) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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-05-16 17:12:20,526 INFO [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Unable to start secondary storage vm for standby > capacity, secStorageVm vm Id : 4, will recycle it and start a new one > 2013-05-16 17:12:20,529 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) VM is already stopped: VM[SecondaryStorageVm|s-4-VM] > 2013-05-16 17:12:20,537 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Stopped to Expunging with > event: ExpungeOperationvm's original host id: null new host id: null host id > before state transition: null > 2013-05-16 17:12:20,540 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) Destroying vm VM[SecondaryStorageVm|s-4-VM] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA admin
[jira] [Assigned] (CLOUDSTACK-2544) System VM's are failed to start with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala reassigned CLOUDSTACK-2544: - Assignee: Kishan Kavala > System VM's are failed to start with NPE > > > Key: CLOUDSTACK-2544 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2544 > 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: Sailaja Mada >Assignee: Kishan Kavala >Priority: Blocker > > Steps: > 1. Create Adv networking setup. > Observation: > System VM's are failed to start with NPE > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release cpu from host: 1, old used: 0,reserved: 0, actual > total: 9572, total with overprovisioning: 9572; new used: 0,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release mem from host: 1, old used: 0,reserved: 0, total: > 17166258176; new used: 0,reserved:0; movedfromreserved: > false,moveToReserveredfalse > 2013-05-16 17:12:20,524 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > java.lang.NullPointerException > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:684) > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:90) > at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117) > at > com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1251) > at > com.cloud.vm.VirtualMachineManagerImpl.changeState(VirtualMachineManagerImpl.java:660) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:817) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:540) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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-05-16 17:12:20,526 INFO [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Unable to start secondary storage vm for standby > capacity, secStorageVm vm Id : 4, will recycle it and start a new one > 2013-05-16 17:12:20,529 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) VM is already stopped: VM[SecondaryStorageVm|s-4-VM] > 2013-05-16 17:12:20,537 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Stopped to Expunging with > event: ExpungeOperationvm's original host id: null new host id: null host id > before state transition: null > 2013-05-16 17:12:20,540 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) Destroying vm VM[SecondaryStorageVm|s-4-VM] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your
[jira] [Commented] (CLOUDSTACK-2544) System VM's are failed to start with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659527#comment-13659527 ] ASF subversion and git services commented on CLOUDSTACK-2544: - Commit d078f921671d0f28d9291fa2bffa8a7eab53cda7 in branch refs/heads/master from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d078f92 ] CLOUDSTACK-2544: Fix NPE while comparing lastHostId during capacity calculation > System VM's are failed to start with NPE > > > Key: CLOUDSTACK-2544 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2544 > 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: Sailaja Mada >Assignee: Kishan Kavala >Priority: Blocker > > Steps: > 1. Create Adv networking setup. > Observation: > System VM's are failed to start with NPE > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release cpu from host: 1, old used: 0,reserved: 0, actual > total: 9572, total with overprovisioning: 9572; new used: 0,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) release mem from host: 1, old used: 0,reserved: 0, total: > 17166258176; new used: 0,reserved:0; movedfromreserved: > false,moveToReserveredfalse > 2013-05-16 17:12:20,524 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > java.lang.NullPointerException > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:684) > at > com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:90) > at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117) > at > com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1251) > at > com.cloud.vm.VirtualMachineManagerImpl.changeState(VirtualMachineManagerImpl.java:660) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:817) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:540) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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-05-16 17:12:20,526 INFO [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Unable to start secondary storage vm for standby > capacity, secStorageVm vm Id : 4, will recycle it and start a new one > 2013-05-16 17:12:20,529 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (secstorage-1:null) VM is already stopped: VM[SecondaryStorageVm|s-4-VM] > 2013-05-16 17:12:20,537 DEBUG [cloud.capacity.CapacityManagerImpl] > (secstorage-1:null) VM state transitted from :Stopped to Expunging with > event: ExpungeOperationvm's original host
[jira] [Assigned] (CLOUDSTACK-2532) remove bogus self assign to parent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Brosius reassigned CLOUDSTACK-2532: Assignee: Dave Brosius > remove bogus self assign to parent > -- > > Key: CLOUDSTACK-2532 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2532 > 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: 2532.txt > > > code assigns > this.parent = parent; > even tho there isn't any non-field parent in the constructor... > removed. -- 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-2530) fix npe if no network isolation methods
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Brosius reassigned CLOUDSTACK-2530: Assignee: Dave Brosius > fix npe if no network isolation methods > --- > > Key: CLOUDSTACK-2530 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2530 > 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: 2530.txt > > > ListNetworkIsolationMethodsCmd checks to see if isolation methods are null, > If it is, NPE, fixed. -- 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-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 ] Dave Brosius reassigned CLOUDSTACK-2531: Assignee: Dave Brosius > 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 > 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] [Created] (CLOUDSTACK-2544) System VM's are failed to start with NPE
Sailaja Mada created CLOUDSTACK-2544: Summary: System VM's are failed to start with NPE Key: CLOUDSTACK-2544 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2544 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: Sailaja Mada Priority: Blocker Steps: 1. Create Adv networking setup. Observation: System VM's are failed to start with NPE 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) release cpu from host: 1, old used: 0,reserved: 0, actual total: 9572, total with overprovisioning: 9572; new used: 0,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-05-16 17:12:20,523 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) release mem from host: 1, old used: 0,reserved: 0, total: 17166258176; new used: 0,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-05-16 17:12:20,524 WARN [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Exception while trying to start secondary storage vm java.lang.NullPointerException at com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:684) at com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:90) at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117) at com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1251) at com.cloud.vm.VirtualMachineManagerImpl.changeState(VirtualMachineManagerImpl.java:660) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:817) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:540) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:262) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:687) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1303) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) 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-05-16 17:12:20,526 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 4, will recycle it and start a new one 2013-05-16 17:12:20,529 DEBUG [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) VM is already stopped: VM[SecondaryStorageVm|s-4-VM] 2013-05-16 17:12:20,537 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) VM state transitted from :Stopped to Expunging with event: ExpungeOperationvm's original host id: null new host id: null host id before state transition: null 2013-05-16 17:12:20,540 DEBUG [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Destroying vm VM[SecondaryStorageVm|s-4-VM] -- 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-2308) [VPC] [VMware] Failed to bring up VPC router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659521#comment-13659521 ] Jayapal Reddy commented on CLOUDSTACK-2308: --- patch is in review board https://reviews.apache.org/r/11201/ > [VPC] [VMware] Failed to bring up VPC router > > > Key: CLOUDSTACK-2308 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2308 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Jayapal Reddy >Priority: Blocker > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have an advanced zone with VMware > 2. Try to create a VPC > Observations : > (i) Have seen errors like "Could not connect to 10.147.40.76 due to > java.net.ConnectException: Connection timed out" > (ii) When i checked "route -n" on the VPC router, couldn't find any route > that makes the communication between mgmt server and router. > (iii) found the following error during the cloud-early-config > + '[' -n 10.147.59.0/24 -a -n 10.147.40.1 ']' > + ip route add 10.147.59.0/24 via 10.147.40.1 dev eth1 > Cannot find device "eth1" > + ip route delete default" > (iv) attaching the log for cloud-early-config which was run using "set -x". > (v) here is the route -n output at the time of issue > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse Iface > 10.147.40.0 0.0.0.0 255.255.254.0 U 0 00 eth0 > (vi) ifconfig output at the time of issueroot@r-20-VM:~# ifconfig -a > eth0 Link encap:Ethernet HWaddr 02:00:53:64:00:0c > inet addr:10.147.40.76 Bcast:10.147.41.255 Mask:255.255.254.0 > inet6 addr: fe80::53ff:fe64:c/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3919 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1010 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:301242 (294.1 KiB) TX bytes:163172 (159.3 KiB) > loLink encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:10 errors:0 dropped:0 overruns:0 frame:0 > TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1318 (1.2 KiB) TX bytes:1318 (1.2 KiB) > Attaching all the required logs along with db dump to the bug. > Here is brief about my network info : > Mgmt sever : 10.147.59.194/24 > mgmt network : 10.147.40.x/24 > public network : 10.147.44.x/24 -- 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-2039) Improve console access security with 128-bit AES encryption and securely-randomized key generation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-2039. --- Resolution: Fixed Wido: The issue you describe is covered in the upgrade instructions (Release Notes): "Once you've upgraded the packages on your management servers, you'll need to restart the system VMs." It's a required step for not just this issue, but other updates that the system VMs need after the upgrade. Resolving based on the info you provided. Re-open if you disagree! > Improve console access security with 128-bit AES encryption and > securely-randomized key generation > -- > > Key: CLOUDSTACK-2039 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2039 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 >Reporter: Kelven Yang >Assignee: Kelven Yang >Priority: Blocker > Fix For: 4.1.0, 4.2.0 > > > Improve console access security with 128-bit AES encryption and > securely-randomized key generation -- 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-2543) [Multiple_IP_Ranges] Failed to create IP alias on router vm
Sanjeev N created CLOUDSTACK-2543: - Summary: [Multiple_IP_Ranges] Failed to create IP alias on router vm Key: CLOUDSTACK-2543 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2543 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Latest master build: CloudStack-non-OSS-MASTER-340-rhel6.3.tar.gz Reporter: Sanjeev N Priority: Critical Fix For: 4.2.0 Failed to create IP alias on router vm Repro steps: === 1.Bring up CS in basic zone with xen6.1 cluster 2.Add another guest ip range in new cidr 3.Exhaust all guest IP addresses from the primary IP range 4.Try to deploy guest vm (CS will try to assing ip address from new cidr added at step2) Expected Result: == Since vm gets IP address from new cidr ip alias should be created on router vm to server dhcp requests Actual Result: vm deployment failed since ip alias creation failed. Observations: 1.Observed following error in SMlog on xenserver: [13543] 2013-05-16 12:23:13.043525 ['bin/bash', '/opt/xensource/bin/createipAlias.sh', '169.254.2.157', '465:10.147.42.204:255.255.254.0-'] [13543] 2013-05-16 12:23:13.052127 FAILED in util.pread: (rc 127) stdout: '', stderr: 'bin/bash: /opt/xensource/bin/createipAlias.sh: No such file or directory 2.createipAlias.sh script was not copied when host got added to CS. 3.Looked at management server log and found that createipAlias.sh path is wrong in patch file. log snippet from mgmt server log while adding host to CS: 2013-05-15 11:10:19,443 WARN [xen.resource.CitrixResourceBase] (DirectAgent-1:null) We cannot locate /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/../../../createipAlias.sh Script path mentioned in xenserver60 patch file is as follows: createipAlias.sh=../../..,0755,/opt/xensource/bin deleteipAlias.sh=../../..,0755,/opt/xensource/bin But it should be "..,0755,/opt/xensource/bin" for both the above scripts since both of them are present in following location in CS: /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/ -- 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-2378) [GSLB] assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing when there are multiple physical network in a zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-2378. -- Resolution: Fixed > [GSLB] assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing > when there are multiple physical network in a zone > --- > > Key: CLOUDSTACK-2378 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2378 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have CloudStack with at least one zone with multiple physical networks > 2. Have GSLB device configured in each physical network of the zone > 3. create GSLB rule > 4. Try to assign at least one LB rule from any of the above physical networks > Observations : > (i) It fails with the following error > 2013-05-08 08:14:59,990 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-79:job-238) Schedule queued job-238 > 2013-05-08 08:14:59,997 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-79:job-238) There is a pending process in sync queue(id: 67) > 2013-05-08 08:15:00,000 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > for job-238 > 2013-05-08 08:15:00,023 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-80:job-238) Access to > org.apache.cloudstack.region.gslb.GlobalLoadBalancerRuleVO$$EnhancerByCGLIB$$75a5db02@5b35b0ae > granted to Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-08 08:15:00,030 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-80:job-238) Access to Rule[7-LoadBalancing-Active] granted to > Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-08 08:15:00,039 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Unexpected exception while executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > com.cloud.exception.InvalidParameterValueException: Unable to get physical > network in zone id = 1 > at > com.cloud.network.element.NetscalerElement.findGslbProvider(NetscalerElement.java:861) > at > com.cloud.network.element.NetscalerElement.isServiceEnabledInZone(NetscalerElement.java:872) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.checkGslbServiceEnabledInZone(GlobalLoadBalancingRulesServiceImpl.java:608) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:224) > at > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:106) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-05-08 08:15:00,041 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Complete async job-238, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Unable to get physical network in > zone id = 1 > 2013-05-08 08:15:00,058 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-80:job-238) Sync queue (67) is currently empty > (ii) if we are going to support multiple physical networks with GSLB enabled > then we need to change our code to allow the above otherwise we should > restrict adding GSLB provider in more than one physical network of the same > zone. > Attaching all the required logs along with the db dump. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2378) [GSLB] assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing when there are multiple physical network in a zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659492#comment-13659492 ] ASF subversion and git services commented on CLOUDSTACK-2378: - Commit f441582e1b7747bba1385ecb48a7b7b34a9dded1 in branch refs/heads/master from Murali Reddy [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f441582 ] CLOUDSTACK-2378: assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing when there are multiple physical network in a zone adding support for deployments where multiple physical networks are configured for guest traffic in a zone > [GSLB] assignToGSLBRule or removeFromGlobalLoadBalancerRule APIs are failing > when there are multiple physical network in a zone > --- > > Key: CLOUDSTACK-2378 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2378 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have CloudStack with at least one zone with multiple physical networks > 2. Have GSLB device configured in each physical network of the zone > 3. create GSLB rule > 4. Try to assign at least one LB rule from any of the above physical networks > Observations : > (i) It fails with the following error > 2013-05-08 08:14:59,990 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-79:job-238) Schedule queued job-238 > 2013-05-08 08:14:59,997 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-79:job-238) There is a pending process in sync queue(id: 67) > 2013-05-08 08:15:00,000 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > for job-238 > 2013-05-08 08:15:00,023 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-80:job-238) Access to > org.apache.cloudstack.region.gslb.GlobalLoadBalancerRuleVO$$EnhancerByCGLIB$$75a5db02@5b35b0ae > granted to Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-08 08:15:00,030 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-80:job-238) Access to Rule[7-LoadBalancing-Active] granted to > Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-08 08:15:00,039 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Unexpected exception while executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > com.cloud.exception.InvalidParameterValueException: Unable to get physical > network in zone id = 1 > at > com.cloud.network.element.NetscalerElement.findGslbProvider(NetscalerElement.java:861) > at > com.cloud.network.element.NetscalerElement.isServiceEnabledInZone(NetscalerElement.java:872) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.checkGslbServiceEnabledInZone(GlobalLoadBalancingRulesServiceImpl.java:608) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:224) > at > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:106) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-05-08 08:15:00,041 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-80:job-238) Complete async job-238, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Unable to get physical network in > zone id = 1 > 2013-05-08 08:15:00,058 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-80:job-238) Sync queue (67) is currently empty > (ii) if we are going to support multiple physical networks with GSLB enabled
[jira] [Commented] (CLOUDSTACK-867) Document Scaling up CPU and RAM for running VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659465#comment-13659465 ] Nitin Mehta commented on CLOUDSTACK-867: Please definitely take in the hypervisor related changes in the FS for documentation. > Document Scaling up CPU and RAM for running VMs > > > Key: CLOUDSTACK-867 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-867 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > > Document Scaling up CPU and RAM for running VMs -- 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-2542) Modify routers test to run for basic zone
Srikanteswararao Talluri created CLOUDSTACK-2542: Summary: Modify routers test to run for basic zone Key: CLOUDSTACK-2542 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2542 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.2.0 Reporter: Srikanteswararao Talluri Fix For: 4.2.0 Don't pass account info while calling list routers for basic zone -- 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] [Comment Edited] (CLOUDSTACK-2354) Unable to create Windows VMs using ISO
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659446#comment-13659446 ] Nitin Mehta edited comment on CLOUDSTACK-2354 at 5/16/13 11:40 AM: --- The observation is correct. The right design will remove the hard coding. It will set all the values as following static min = service_offering / memory_overprovisioning_of_cluster. dynamic min = service_offering / memory_overprovisioning_of_cluster. dynamic max = service_offering static max = (4 * service_offering) / memory_overprovisioning_of_cluster While scaling "up" the vm say from service offering "x" to "y" we will change dynamic min = new service_offering / memory_overprovisioning_of_cluster. dynamic max = new service_offering and ensure that new dynamic max (y) <= static max and new dynamic min (y / memory_overprovisioning_of_cluster) >= static min. Note : From XS following are the constraints 0 ≤ memory-static-min ≤ memory-dynamic-min ≤ memory-dynamic-max ≤ memory-static-max Dynamic Minimum ≥ 1⁄4 Static Maximum for all supported operating systems was (Author: nitinme): The observation is correct. The right design will remove the hard coding. It will set all the values as following static min = service_offering / memory_overprovisioning_of_cluster. dynamic min = service_offering / memory_overprovisioning_of_cluster. dynamic max = service_offering static max = (4 * service_offering) / memory_overprovisioning_of_cluster While scaling "up" the vm say from service offering "x" to "y" we will change dynamic min = new service_offering / memory_overprovisioning_of_cluster. dynamic max = new service_offering and ensure that new dynamic max (y) <= static max and new dynamic min (y / memory_overprovisioning_of_cluster) >= static min. > Unable to create Windows VMs using ISO > -- > > Key: CLOUDSTACK-2354 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: ISO >Affects Versions: 4.2.0 > Environment: Build No.#256 > (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server. >Reporter: Minying Bao >Assignee: Harikrishna Patnala >Priority: Blocker > Fix For: 4.2.0 > > Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, > ISO_XP_State.JPG.jpg, management-server.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack WebConsole and finish to build a cloud step > by step. (It should use workaround of build#256 when building a cloud.) > Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait > for "Status" showing "Successfully Installed". > Add instances from all above ISOs. > Expected Result > All the instances should be added successfully, and all the related VMs > should be launched successfully on XenServer Host. > Actual Result > Unable to create Windows VMs using ISO. > VMs based on the Win8/Win7 ISOs -> WebConsole show "Error" (refer to > screenshot "ISO_Win8.jpg") > VMs based on the XP/W2k8r2 ISO -> WebConsole show "Running" -> Auto-shutdown > during the OS installation -> WebConsole show "Stopped" (refer to screenshots > "ISO_XP-Auto-Shutdown.JPG" and "ISO_XP_State.JPG" ) -- 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-2354) Unable to create Windows VMs using ISO
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659449#comment-13659449 ] Harikrishna Patnala commented on CLOUDSTACK-2354: - This is more related to the xenserver memory constraints on guest vms, I'm gonna fix this based on the constraints provided by the xenserver. On 16-May-2013, at 5:00 PM, Sanjay Tripathi > Unable to create Windows VMs using ISO > -- > > Key: CLOUDSTACK-2354 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: ISO >Affects Versions: 4.2.0 > Environment: Build No.#256 > (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server. >Reporter: Minying Bao >Assignee: Harikrishna Patnala >Priority: Blocker > Fix For: 4.2.0 > > Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, > ISO_XP_State.JPG.jpg, management-server.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack WebConsole and finish to build a cloud step > by step. (It should use workaround of build#256 when building a cloud.) > Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait > for "Status" showing "Successfully Installed". > Add instances from all above ISOs. > Expected Result > All the instances should be added successfully, and all the related VMs > should be launched successfully on XenServer Host. > Actual Result > Unable to create Windows VMs using ISO. > VMs based on the Win8/Win7 ISOs -> WebConsole show "Error" (refer to > screenshot "ISO_Win8.jpg") > VMs based on the XP/W2k8r2 ISO -> WebConsole show "Running" -> Auto-shutdown > during the OS installation -> WebConsole show "Stopped" (refer to screenshots > "ISO_XP-Auto-Shutdown.JPG" and "ISO_XP_State.JPG" ) -- 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-2354) Unable to create Windows VMs using ISO
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659446#comment-13659446 ] Nitin Mehta commented on CLOUDSTACK-2354: - The observation is correct. The right design will remove the hard coding. It will set all the values as following static min = service_offering / memory_overprovisioning_of_cluster. dynamic min = service_offering / memory_overprovisioning_of_cluster. dynamic max = service_offering static max = (4 * service_offering) / memory_overprovisioning_of_cluster While scaling "up" the vm say from service offering "x" to "y" we will change dynamic min = new service_offering / memory_overprovisioning_of_cluster. dynamic max = new service_offering and ensure that new dynamic max (y) <= static max and new dynamic min (y / memory_overprovisioning_of_cluster) >= static min. > Unable to create Windows VMs using ISO > -- > > Key: CLOUDSTACK-2354 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: ISO >Affects Versions: 4.2.0 > Environment: Build No.#256 > (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server. >Reporter: Minying Bao >Assignee: Harikrishna Patnala >Priority: Blocker > Fix For: 4.2.0 > > Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, > ISO_XP_State.JPG.jpg, management-server.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack WebConsole and finish to build a cloud step > by step. (It should use workaround of build#256 when building a cloud.) > Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait > for "Status" showing "Successfully Installed". > Add instances from all above ISOs. > Expected Result > All the instances should be added successfully, and all the related VMs > should be launched successfully on XenServer Host. > Actual Result > Unable to create Windows VMs using ISO. > VMs based on the Win8/Win7 ISOs -> WebConsole show "Error" (refer to > screenshot "ISO_Win8.jpg") > VMs based on the XP/W2k8r2 ISO -> WebConsole show "Running" -> Auto-shutdown > during the OS installation -> WebConsole show "Stopped" (refer to screenshots > "ISO_XP-Auto-Shutdown.JPG" and "ISO_XP_State.JPG" ) -- 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-2354) Unable to create Windows VMs using ISO
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala reassigned CLOUDSTACK-2354: --- Assignee: Harikrishna Patnala > Unable to create Windows VMs using ISO > -- > > Key: CLOUDSTACK-2354 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: ISO >Affects Versions: 4.2.0 > Environment: Build No.#256 > (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server. >Reporter: Minying Bao >Assignee: Harikrishna Patnala >Priority: Blocker > Fix For: 4.2.0 > > Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, > ISO_XP_State.JPG.jpg, management-server.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack WebConsole and finish to build a cloud step > by step. (It should use workaround of build#256 when building a cloud.) > Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait > for "Status" showing "Successfully Installed". > Add instances from all above ISOs. > Expected Result > All the instances should be added successfully, and all the related VMs > should be launched successfully on XenServer Host. > Actual Result > Unable to create Windows VMs using ISO. > VMs based on the Win8/Win7 ISOs -> WebConsole show "Error" (refer to > screenshot "ISO_Win8.jpg") > VMs based on the XP/W2k8r2 ISO -> WebConsole show "Running" -> Auto-shutdown > during the OS installation -> WebConsole show "Stopped" (refer to screenshots > "ISO_XP-Auto-Shutdown.JPG" and "ISO_XP_State.JPG" ) -- 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-2539) VPC: Unable to create instance in Vpc ( when vpc is created with "Default VPC offering with Netscaler" offering)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala reassigned CLOUDSTACK-2539: -- Assignee: Rajesh Battala > VPC: Unable to create instance in Vpc ( when vpc is created with "Default > VPC offering with Netscaler" offering) > -- > > Key: CLOUDSTACK-2539 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2539 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Rajesh Battala >Assignee: Rajesh Battala >Priority: Blocker > Fix For: 4.2.0 > > > When VPC is created VpcVR got created successfully ( two nic ) > when created a Tier with Netscaler as LB provider, > VpcVR should get a new nic pluggged with ip (gateway ip) from the tier > network. > While plugging the Nic to the VpcVR NPE is happening in CitrixResourceBase. > 2013-05-16 11:49:08,551 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-28:null) Seq 1-2031484992: Executing request > 2013-05-16 11:49:08,738 DEBUG [xen.resource.CitrixResourceBase] > (DirectAgent-28:null) Lowest available Vif device number: 2 for VM: r-8-VM > 2013-05-16 11:49:08,738 DEBUG [xen.resource.CitrixResourceBase] > (DirectAgent-28:null) Creating VIF for r-8-VM on nic [Nic:Guest-10.0.1.1-null] > 2013-05-16 11:49:08,769 WARN [xen.resource.CitrixResourceBase] > (DirectAgent-28:null) Plug Nic failed due to java.lang.NullPointerException > java.lang.NullPointerException > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetwork(CitrixResourceBase.java:1011) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVif(CitrixResourceBase.java:1062) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:8038) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:589) > at > com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73) > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) -- 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-2354) Unable to create Windows VMs using ISO
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659443#comment-13659443 ] Sanjay Tripathi commented on CLOUDSTACK-2354: - Nitin, I have unassigned this ticket as it is related to your feature "Scaling up Memory of running VMs" and the fix for this bug is disabling the scaling up functionality. I have updated the ticket with my findings. Can you please assign it to yourself as you have the better idea about the functionality. --Sanjay > Unable to create Windows VMs using ISO > -- > > Key: CLOUDSTACK-2354 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: ISO >Affects Versions: 4.2.0 > Environment: Build No.#256 > (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server. >Reporter: Minying Bao >Priority: Blocker > Fix For: 4.2.0 > > Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, > ISO_XP_State.JPG.jpg, management-server.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack WebConsole and finish to build a cloud step > by step. (It should use workaround of build#256 when building a cloud.) > Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait > for "Status" showing "Successfully Installed". > Add instances from all above ISOs. > Expected Result > All the instances should be added successfully, and all the related VMs > should be launched successfully on XenServer Host. > Actual Result > Unable to create Windows VMs using ISO. > VMs based on the Win8/Win7 ISOs -> WebConsole show "Error" (refer to > screenshot "ISO_Win8.jpg") > VMs based on the XP/W2k8r2 ISO -> WebConsole show "Running" -> Auto-shutdown > during the OS installation -> WebConsole show "Stopped" (refer to screenshots > "ISO_XP-Auto-Shutdown.JPG" and "ISO_XP_State.JPG" ) -- 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-2541) remove the dependency on config file in the test_secondary_storage.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-2541: - Assignee: Srikanteswararao Talluri > remove the dependency on config file in the test_secondary_storage.py > - > > Key: CLOUDSTACK-2541 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2541 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test >Affects Versions: 4.2.0 >Reporter: Srikanteswararao Talluri >Assignee: Srikanteswararao Talluri > Fix For: 4.2.0 > > > Get the list of zones, pods and clusters by issuing list* instead of reading > them from config file -- 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-2354) Unable to create Windows VMs using ISO
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659439#comment-13659439 ] Sanjay Tripathi commented on CLOUDSTACK-2354: - Nitin, I have unassigned this ticket as it is related to your feature https://issues.apache.org/jira/browse/CLOUDSTACK-658 and the fix (to make the memoryStatixMax value dynamic) will disable the functionality of your feature. Can you please assign it to yourself. > Unable to create Windows VMs using ISO > -- > > Key: CLOUDSTACK-2354 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: ISO >Affects Versions: 4.2.0 > Environment: Build No.#256 > (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server. >Reporter: Minying Bao >Assignee: Sanjay Tripathi >Priority: Blocker > Fix For: 4.2.0 > > Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, > ISO_XP_State.JPG.jpg, management-server.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack WebConsole and finish to build a cloud step > by step. (It should use workaround of build#256 when building a cloud.) > Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait > for "Status" showing "Successfully Installed". > Add instances from all above ISOs. > Expected Result > All the instances should be added successfully, and all the related VMs > should be launched successfully on XenServer Host. > Actual Result > Unable to create Windows VMs using ISO. > VMs based on the Win8/Win7 ISOs -> WebConsole show "Error" (refer to > screenshot "ISO_Win8.jpg") > VMs based on the XP/W2k8r2 ISO -> WebConsole show "Running" -> Auto-shutdown > during the OS installation -> WebConsole show "Stopped" (refer to screenshots > "ISO_XP-Auto-Shutdown.JPG" and "ISO_XP_State.JPG" ) -- 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-2354) Unable to create Windows VMs using ISO
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi reassigned CLOUDSTACK-2354: --- Assignee: (was: Sanjay Tripathi) > Unable to create Windows VMs using ISO > -- > > Key: CLOUDSTACK-2354 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: ISO >Affects Versions: 4.2.0 > Environment: Build No.#256 > (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server. >Reporter: Minying Bao >Priority: Blocker > Fix For: 4.2.0 > > Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, > ISO_XP_State.JPG.jpg, management-server.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack WebConsole and finish to build a cloud step > by step. (It should use workaround of build#256 when building a cloud.) > Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait > for "Status" showing "Successfully Installed". > Add instances from all above ISOs. > Expected Result > All the instances should be added successfully, and all the related VMs > should be launched successfully on XenServer Host. > Actual Result > Unable to create Windows VMs using ISO. > VMs based on the Win8/Win7 ISOs -> WebConsole show "Error" (refer to > screenshot "ISO_Win8.jpg") > VMs based on the XP/W2k8r2 ISO -> WebConsole show "Running" -> Auto-shutdown > during the OS installation -> WebConsole show "Stopped" (refer to screenshots > "ISO_XP-Auto-Shutdown.JPG" and "ISO_XP_State.JPG" ) -- 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-2541) remove the dependency on config file in the test_secondary_storage.py
Srikanteswararao Talluri created CLOUDSTACK-2541: Summary: remove the dependency on config file in the test_secondary_storage.py Key: CLOUDSTACK-2541 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2541 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.2.0 Reporter: Srikanteswararao Talluri Fix For: 4.2.0 Get the list of zones, pods and clusters by issuing list* instead of reading them from config file -- 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-2539) VPC: Unable to create instance in Vpc ( when vpc is created with "Default VPC offering with Netscaler" offering)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659403#comment-13659403
]
Rajesh Battala commented on CLOUDSTACK-2539:
Exception Log :
=
Nic is prepared successfully for vm VM[DomainRouter|r-8-VM] in network
Ntwk[207|Guest|14]
2013-05-16 11:49:08,543 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-5:job-45) Plugging nic for vm VM[DomainRouter|r-8-VM] in network
Ntwk[207|Guest|14]
2013-05-16 11:49:08,550 DEBUG [agent.transport.Request] (Job-Executor-5:job-45)
Seq 1-2031484992: Sending { Cmd , MgmtId: 235715300172635, via: 1, Ver: v1,
Flags: 100111,
[{"PlugNicCommand":{"nic":{"deviceId":2,"networkRateMbps":200,"defaultNic":false,"uuid":"c6fdbf58-7e3f-482e-a261-42dc47ca86ae","ip":"10.0.1.1","netmask":"255.255.255.0","gateway":"10.0.1.1","mac":"02:00:64:e4:00:03","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","isSecurityGroupEnabled":false},"instanceName":"r-8-VM","wait":0}}]
}
2013-05-16 11:49:08,551 DEBUG [agent.transport.Request] (Job-Executor-5:job-45)
Seq 1-2031484992: Executing: { Cmd , MgmtId: 235715300172635, via: 1, Ver: v1,
Flags: 100111,
[{"PlugNicCommand":{"nic":{"deviceId":2,"networkRateMbps":200,"defaultNic":false,"uuid":"c6fdbf58-7e3f-482e-a261-42dc47ca86ae","ip":"10.0.1.1","netmask":"255.255.255.0","gateway":"10.0.1.1","mac":"02:00:64:e4:00:03","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","isSecurityGroupEnabled":false},"instanceName":"r-8-VM","wait":0}}]
}
2013-05-16 11:49:08,551 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-28:null) Seq 1-2031484992: Executing request
2013-05-16 11:49:08,738 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-28:null) Lowest available Vif device number: 2 for VM: r-8-VM
2013-05-16 11:49:08,738 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-28:null) Creating VIF for r-8-VM on nic [Nic:Guest-10.0.1.1-null]
2013-05-16 11:49:08,769 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-28:null) Plug Nic failed due to java.lang.NullPointerException
java.lang.NullPointerException
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetwork(CitrixResourceBase.java:1011)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVif(CitrixResourceBase.java:1062)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:8038)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:589)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2013-05-16 11:49:08,770 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-28:null) Seq 1-2031484992: Response Received:
2013-05-16 11:49:08,770 DEBUG [agent.transport.Request] (DirectAgent-28:null)
Seq 1-2031484992: Processing: { Ans: , MgmtId: 235715300172635, via: 1, Ver:
v1, Flags: 110, [{"PlugNicAnswer":{"result":false,"details":" Plug Nic failed
due to java.lang.NullPointerException","wait":0}}] }
2013-05-16 11:49:08,770 DEBUG [agent.transport.Request] (Job-Executor-5:job-45)
Seq 1-2031484992: Received: { Ans: , MgmtId: 235715300172635, via: 1, Ver: v1,
Flags: 110, { PlugNicAnswer } }
2013-05-16 11:49:08,771 WARN
[network.router.VpcVirtualNetworkApplianceManagerImpl] (Job-Executor-5:job-45)
Unable to plug nic for vm r-8-VM
2013-05-16 11:49:08,771 WARN [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-5:job-45) Failed to plug nic to the vm VM[DomainRouter|r-8-VM] in
network Ntwk[207|Guest|14]
2013-05-16 11:49:08,772 DEBUG [agent.manager.AgentAttache]
(DirectAgent-28:null) Seq 1-2031484992: No more commands found
2013-05-16 11:49:08,786 DEBUG [cloud.network.NetworkModelImpl]
(Job-Executor-5:job-45) Service SecurityGroup is not supported in the network
id=207
2013-05-16 11:49:08,797 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-5:job-45) Removed nic id=29
2013-05-16 11:49:08,799 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-5:job-45) Revoving nic secondary ip entry ...
2013-05-16 11:49:08,800 WARN
[jira] [Created] (CLOUDSTACK-2540) Cisco VNMC - Cleanup vservice node that gets created on Nexus switch during network cleanup
Koushik Das created CLOUDSTACK-2540: --- Summary: Cisco VNMC - Cleanup vservice node that gets created on Nexus switch during network cleanup Key: CLOUDSTACK-2540 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2540 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0 Environment: Vmware Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.2.0 Vservice node gets created on Nexus switch as part of guest network implementation involving Cisco VNMC. It needs to cleaned up as part of network cleanup. -- 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-2539) VPC: Unable to create instance in Vpc ( when vpc is created with "Default VPC offering with Netscaler" offering)
Rajesh Battala created CLOUDSTACK-2539: -- Summary: VPC: Unable to create instance in Vpc ( when vpc is created with "Default VPC offering with Netscaler" offering) Key: CLOUDSTACK-2539 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2539 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Rajesh Battala Priority: Blocker Fix For: 4.2.0 When VPC is created VpcVR got created successfully ( two nic ) when created a Tier with Netscaler as LB provider, VpcVR should get a new nic pluggged with ip (gateway ip) from the tier network. While plugging the Nic to the VpcVR NPE is happening in CitrixResourceBase. 2013-05-16 11:49:08,551 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-28:null) Seq 1-2031484992: Executing request 2013-05-16 11:49:08,738 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-28:null) Lowest available Vif device number: 2 for VM: r-8-VM 2013-05-16 11:49:08,738 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-28:null) Creating VIF for r-8-VM on nic [Nic:Guest-10.0.1.1-null] 2013-05-16 11:49:08,769 WARN [xen.resource.CitrixResourceBase] (DirectAgent-28:null) Plug Nic failed due to java.lang.NullPointerException java.lang.NullPointerException at com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetwork(CitrixResourceBase.java:1011) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVif(CitrixResourceBase.java:1062) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:8038) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:589) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- 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-2116) [Dedicated Resources : Public IP Addresses per tenant] Able to dedicate more Public IP addresses to an account than it's maximum limit.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Roy closed CLOUDSTACK-2116. --- Closing the bug after verifying the fix on latest master build > [Dedicated Resources : Public IP Addresses per tenant] Able to dedicate more > Public IP addresses to an account than it's maximum limit. > --- > > Key: CLOUDSTACK-2116 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2116 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Steps : > > 1. Deploy a advanced networking setup. > 2. Create an account A1 and set the Public IP limits = 5 > 3. Add 4 IP ranges, R1 having 5 IPs, R2 having 3 IPs , R3 having 6 IPs, R4 > having 10 IPs. > 4. Now execute the following cases : > Case I : Dedicate R1 to A1 and then dedicate R2 to A1 > Case II : Dedicate R1/R2 to A1 and then dedicate R3/R4 > Case II : Dedicate R3/R4 to A1 > Expected Behaviour : > === > In Case I: Dedication of R1 should be successful but R2 should fail as it > exceeds the limits. > In Case II : Dedication of R1/R2 should be successful but R3/R4 should fail > as it exceeds the limits. > In Case III : Dedication of R3/R4 should fail as it exceeds the limits. > Observed behaviour : > === > In Case I: Dedication of R1 is successful as expected but R2 also is > successful which is not expected as it exceeds the limits. > In Case II : Dedication of R1/R2 is successful as expected and R3/R4 fails > as expected > In Case III : Dedication of R3/R4 fails as expected. > Note : we see that only Case I doesn't behave as expected that's because I > guess here we are checking for one single range whose IP set is bigger than > the limit and then throwing the error. We are not actually counting the total > no of dedicated IPs to that account and then comparing it to the allowed > 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-2462) [GSLB] Failed to create GSLB rule with "proximity" algorithm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murali Reddy resolved CLOUDSTACK-2462.
--
Resolution: Fixed
added RTT support
> [GSLB] Failed to create GSLB rule with "proximity" algorithm
>
>
> Key: CLOUDSTACK-2462
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2462
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have CloudStack setup with at least 1 adv zone
> 2. Try to create a GSLB rule by setting "gslblbmethod" to "proximity"
> Observations :
> (i) It fails with the following error in the mgmt server logs
> 2013-05-13 16:20:35,421 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-22:job-327) Access to Rule[7-LoadBalancing-Active] granted to
> Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4
> 2013-05-13 16:20:35,467 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Sending { Cmd , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 100011,
> [{"routing.GlobalLoadBalancerConfigCommand":{"domainName":"proximity.cloud.xyztelcom.com","serviceType":"tcp","lbMethod":"proximity","persistenceType":"sourceip","gslbId":26,"revoked":false,"siteLoadBalancers":[{"local":true,"revoked":false,"serviceType":"tcp","servicePublicIp":"10.147.44.61","servicePort":"22","gslbProviderPrivateIp":"10.147.44.20","dataCenterId":1}],"wait":0}}]
> }
> 2013-05-13 16:20:35,467 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Executing: { Cmd , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 100011,
> [{"routing.GlobalLoadBalancerConfigCommand":{"domainName":"proximity.cloud.xyztelcom.com","serviceType":"tcp","lbMethod":"proximity","persistenceType":"sourceip","gslbId":26,"revoked":false,"siteLoadBalancers":[{"local":true,"revoked":false,"serviceType":"tcp","servicePublicIp":"10.147.44.61","servicePort":"22","gslbProviderPrivateIp":"10.147.44.20","dataCenterId":1}],"wait":0}}]
> }
> 2013-05-13 16:20:35,468 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-492:null) Seq 26-754647047: Executing request
> 2013-05-13 16:20:35,540 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,582 WARN [network.resource.NetscalerResource]
> (DirectAgent-492:null) Retrying GlobalLoadBalancerConfigCommand. Number of
> retries remaining: 1
> 2013-05-13 16:20:35,651 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,704 WARN [network.resource.NetscalerResource]
> (DirectAgent-492:null) Retrying GlobalLoadBalancerConfigCommand. Number of
> retries remaining: 0
> 2013-05-13 16:20:35,772 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,773 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-492:null) Seq 26-754647047: Response Received:
> 2013-05-13 16:20:35,773 DEBUG [agent.transport.Request]
> (DirectAgent-492:null) Seq 26-754647047: Processing: { Ans: , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 10,
> [{"routing.GlobalLoadBalancerConfigAnswer":{"result":false,"details":"Failed
> to apply GSLB configuration due to Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]","wait":0}}] }
> 2013-05-13 16:20:35,773 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Received: { Ans: , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 10, { GlobalLoadBalancerConfigAnswer
> } }
> 2013-05-13 16:20:35,773 DEBUG [agent.manager.AgentManagerImpl]
> (Job-Executor-22:job-327) Details from executing class
> com.cloud.agent.api.routing.GlobalLoadBalancerConfigCommand: Failed to apply
> GSLB configuration due to Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,774 DEBUG [network.element.NetscalerElement]
> (Job-Executor-22:job-327) Unable to apply global load balancer rule to the
>
[jira] [Resolved] (CLOUDSTACK-2461) [GSLB] createGSLBRule API is failing to pick the default algorithm "round robin" for parameter "gslblbmethod"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-2461. -- Resolution: Fixed > [GSLB] createGSLBRule API is failing to pick the default algorithm "round > robin" for parameter "gslblbmethod" > - > > Key: CLOUDSTACK-2461 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2461 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce: > 1. Have CloudStack setup with at least one advanced zone > 2. Try to create a GSLB rule without specifying the parameter "gslblbmethod" > Observations: > (i) It is supposed to pick a default algorithm i.e. "round robin" but, it > fails with the following error in the mgmt server log. > 2013-05-13 15:39:26,164 DEBUG [cloud.api.ApiServlet] > (1374637973@qtp-1391263288-331:null) ===START=== 10.104.255.13 -- GET > apiKey=M-bs_nL5nJkcbHm4G718MXguAsVPLjRB1pq9ovDpBHvr2qsYRGSuHm6LBfc7vBv2e3KXxeFIZXFEzBPmdaxtaA&command=createGlobalLoadBalancerRule&description=test&gslbdomainname=test&gslbservicetype=tcp&name=test®ionid=1&response=json&signature=o9CUzfi41FF0nlxj%2BTnSS4GEBgQ%3D > 2013-05-13 15:39:26,175 DEBUG [cloud.user.AccountManagerImpl] > (1374637973@qtp-1391263288-331:null) Access to Acct[5-dom1Acc3] granted to > Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-13 15:39:26,179 WARN [ha.gslb.CreateGlobalLoadBalancerRuleCmd] > (1374637973@qtp-1391263288-331:null) Exception: > com.cloud.exception.InvalidParameterValueException: Invalid Algorithm: null > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.createGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:103) > at > org.apache.cloudstack.api.command.user.region.ha.gslb.CreateGlobalLoadBalancerRuleCmd.create(CreateGlobalLoadBalancerRuleCmd.java:142) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:101) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:459) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:362) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) > 2013-05-13 15:39:26,182 INFO [cloud.api.ApiServer] > (1374637973@qtp-1391263288-331:null) Invalid Algorithm: null > Attaching all the required logs along with b dump. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2460) [GSLB] [EVENTS]
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-2460. -- Resolution: Fixed > [GSLB] [EVENTS] > > > Key: CLOUDSTACK-2460 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2460 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Trivial > Fix For: 4.2.0 > > > Steps to reproduce : > 1. Have CloudStack with at least one advanced zone > 2. add a GSLB device > 3. Login as a non-ROOT domain user and create a GSLB rule > 4. verify the EVENT > Observations: > (i) It successfully generated an event but, with little discrepancy in the > description > Here is the description: > Description creating a global load balancer: GSLB1 for account: null > (ii) we need to update the account with right information. -- 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-2529) [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the full GSLB domain name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-2529. -- Resolution: Fixed fixed to return full FQDN in GSLB rule response > [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the > full GSLB domain name > --- > > Key: CLOUDSTACK-2529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy > Fix For: 4.2.0 > > > Steps to reproduce : > 1. Have at least one GSLB enabled zone > 2. Have at least one non-ROOT domain user > 3. Login as the above user and create a GSLB rule and assign LB rules to GSLB > Observations: > (i) Everything goes fine but, there is no way currently to inform the user > what will be the full domain name. > (ii) It will be good if we can prompt a message and show the complete domain > name > Complete domain name will be "GSLB domain name specified by user + value of > the global setting cloud.dns.name" -- 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-2538) [Object_Store_Refactor] No option for the user to provide storage name
Sanjeev N created CLOUDSTACK-2538: - Summary: [Object_Store_Refactor] No option for the user to provide storage name Key: CLOUDSTACK-2538 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2538 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sanjeev N -- 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-2461) [GSLB] createGSLBRule API is failing to pick the default algorithm "round robin" for parameter "gslblbmethod"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659389#comment-13659389 ] ASF subversion and git services commented on CLOUDSTACK-2461: - Commit 3c51c4e7adb717b5cee3bd01be716d75e288aa0c in branch refs/heads/master from Murali Reddy [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3c51c4e ] CLOUDSTACK-2461: createGSLBRule API is failing to pick the default algorithm "round robin" for parameter "gslblbmethod" fix defaults to round robin when parameter not specified > [GSLB] createGSLBRule API is failing to pick the default algorithm "round > robin" for parameter "gslblbmethod" > - > > Key: CLOUDSTACK-2461 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2461 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce: > 1. Have CloudStack setup with at least one advanced zone > 2. Try to create a GSLB rule without specifying the parameter "gslblbmethod" > Observations: > (i) It is supposed to pick a default algorithm i.e. "round robin" but, it > fails with the following error in the mgmt server log. > 2013-05-13 15:39:26,164 DEBUG [cloud.api.ApiServlet] > (1374637973@qtp-1391263288-331:null) ===START=== 10.104.255.13 -- GET > apiKey=M-bs_nL5nJkcbHm4G718MXguAsVPLjRB1pq9ovDpBHvr2qsYRGSuHm6LBfc7vBv2e3KXxeFIZXFEzBPmdaxtaA&command=createGlobalLoadBalancerRule&description=test&gslbdomainname=test&gslbservicetype=tcp&name=test®ionid=1&response=json&signature=o9CUzfi41FF0nlxj%2BTnSS4GEBgQ%3D > 2013-05-13 15:39:26,175 DEBUG [cloud.user.AccountManagerImpl] > (1374637973@qtp-1391263288-331:null) Access to Acct[5-dom1Acc3] granted to > Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4 > 2013-05-13 15:39:26,179 WARN [ha.gslb.CreateGlobalLoadBalancerRuleCmd] > (1374637973@qtp-1391263288-331:null) Exception: > com.cloud.exception.InvalidParameterValueException: Invalid Algorithm: null > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.createGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:103) > at > org.apache.cloudstack.api.command.user.region.ha.gslb.CreateGlobalLoadBalancerRuleCmd.create(CreateGlobalLoadBalancerRuleCmd.java:142) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:101) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:459) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:362) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) > 2013-05-13 15:39:26,182 INFO [cloud.api.ApiServer] > (1374637973@qtp-1391263288-331:null) Invalid
[jira] [Commented] (CLOUDSTACK-2460) [GSLB] [EVENTS]
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659388#comment-13659388 ] ASF subversion and git services commented on CLOUDSTACK-2460: - Commit 565d829c006609251c18883b1007175b6a1d2f79 in branch refs/heads/master from Murali Reddy [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=565d829 ] CLOUDSTACK-2460: fix the event descriptions for create/delete/update/assign global load balancer rule apis > [GSLB] [EVENTS] > > > Key: CLOUDSTACK-2460 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2460 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Trivial > Fix For: 4.2.0 > > > Steps to reproduce : > 1. Have CloudStack with at least one advanced zone > 2. add a GSLB device > 3. Login as a non-ROOT domain user and create a GSLB rule > 4. verify the EVENT > Observations: > (i) It successfully generated an event but, with little discrepancy in the > description > Here is the description: > Description creating a global load balancer: GSLB1 for account: null > (ii) we need to update the account with right information. -- 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-2462) [GSLB] Failed to create GSLB rule with "proximity" algorithm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659386#comment-13659386
]
ASF subversion and git services commented on CLOUDSTACK-2462:
-
Commit 33e683915c3083ac60a578fc90a7d90a64cb028e in branch refs/heads/master
from Murali Reddy
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=33e6839 ]
CLOUDSTACK-2462: Failed to create GSLB rule with "proximity" algorithm
add RTT as load balancing method for GSLB vserver
> [GSLB] Failed to create GSLB rule with "proximity" algorithm
>
>
> Key: CLOUDSTACK-2462
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2462
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have CloudStack setup with at least 1 adv zone
> 2. Try to create a GSLB rule by setting "gslblbmethod" to "proximity"
> Observations :
> (i) It fails with the following error in the mgmt server logs
> 2013-05-13 16:20:35,421 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-22:job-327) Access to Rule[7-LoadBalancing-Active] granted to
> Acct[5-dom1Acc3] by DomainChecker_EnhancerByCloudStack_31a4ebb4
> 2013-05-13 16:20:35,467 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Sending { Cmd , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 100011,
> [{"routing.GlobalLoadBalancerConfigCommand":{"domainName":"proximity.cloud.xyztelcom.com","serviceType":"tcp","lbMethod":"proximity","persistenceType":"sourceip","gslbId":26,"revoked":false,"siteLoadBalancers":[{"local":true,"revoked":false,"serviceType":"tcp","servicePublicIp":"10.147.44.61","servicePort":"22","gslbProviderPrivateIp":"10.147.44.20","dataCenterId":1}],"wait":0}}]
> }
> 2013-05-13 16:20:35,467 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Executing: { Cmd , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 100011,
> [{"routing.GlobalLoadBalancerConfigCommand":{"domainName":"proximity.cloud.xyztelcom.com","serviceType":"tcp","lbMethod":"proximity","persistenceType":"sourceip","gslbId":26,"revoked":false,"siteLoadBalancers":[{"local":true,"revoked":false,"serviceType":"tcp","servicePublicIp":"10.147.44.61","servicePort":"22","gslbProviderPrivateIp":"10.147.44.20","dataCenterId":1}],"wait":0}}]
> }
> 2013-05-13 16:20:35,468 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-492:null) Seq 26-754647047: Executing request
> 2013-05-13 16:20:35,540 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,582 WARN [network.resource.NetscalerResource]
> (DirectAgent-492:null) Retrying GlobalLoadBalancerConfigCommand. Number of
> retries remaining: 1
> 2013-05-13 16:20:35,651 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,704 WARN [network.resource.NetscalerResource]
> (DirectAgent-492:null) Retrying GlobalLoadBalancerConfigCommand. Number of
> retries remaining: 0
> 2013-05-13 16:20:35,772 DEBUG [network.resource.NetscalerResource]
> (DirectAgent-492:null) Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]
> 2013-05-13 16:20:35,773 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-492:null) Seq 26-754647047: Response Received:
> 2013-05-13 16:20:35,773 DEBUG [agent.transport.Request]
> (DirectAgent-492:null) Seq 26-754647047: Processing: { Ans: , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 10,
> [{"routing.GlobalLoadBalancerConfigAnswer":{"result":false,"details":"Failed
> to apply GSLB configuration due to Failed to add GSLB virtual server:
> cloud-gslb-vserver-proximity.cloud.xyztelcom.com due to Invalid argument
> value [proximity]","wait":0}}] }
> 2013-05-13 16:20:35,773 DEBUG [agent.transport.Request]
> (Job-Executor-22:job-327) Seq 26-754647047: Received: { Ans: , MgmtId:
> 7280707764394, via: 26, Ver: v1, Flags: 10, { GlobalLoadBalancerConfigAnswer
> } }
> 2013-05-13 16:20:35,773 DEBUG [agent.manager.AgentManagerImpl]
> (Job-Executor-22:job-327) Details from executing class
> com.cloud.agent.api.routing.GlobalLoadBala
[jira] [Commented] (CLOUDSTACK-2529) [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the full GSLB domain name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659387#comment-13659387 ] ASF subversion and git services commented on CLOUDSTACK-2529: - Commit d2d0398e3321b819756a537c0b1fab0491e5a3e6 in branch refs/heads/master from Murali Reddy [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d2d0398 ] CLOUDSTACK-2529: GlobalLoadBalancerResponse should have the full FQDN for the global load balanced service > [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the > full GSLB domain name > --- > > Key: CLOUDSTACK-2529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy > Fix For: 4.2.0 > > > Steps to reproduce : > 1. Have at least one GSLB enabled zone > 2. Have at least one non-ROOT domain user > 3. Login as the above user and create a GSLB rule and assign LB rules to GSLB > Observations: > (i) Everything goes fine but, there is no way currently to inform the user > what will be the full domain name. > (ii) It will be good if we can prompt a message and show the complete domain > name > Complete domain name will be "GSLB domain name specified by user + value of > the global setting cloud.dns.name" -- 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-2537) [Object_Store_Refactor] System vms failed to come up with S3 as storage provider
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659384#comment-13659384
]
Sanjeev N commented on CLOUDSTACK-2537:
---
Template status from cloud DB:
mysql> select * from template_store_ref\G;
*** 1. row ***
id: 1
store_id: 2
template_id: 1
created: 2013-05-16 14:40:39
last_updated: 2013-05-16 14:41:23
job_id: 46e0c43d-a743-461f-8b88-16a57ac4bbb8
download_pct: 100
size: 140616708
store_role: Image
physical_size: 140616708
download_state: DOWNLOADED
error_str:
local_path: template/tmpl/1/1/routing-1/acton-systemvm-02062012.vhd.bz2
install_path: template/tmpl/1/1/routing-1
url: NULL
state: Ready
destroyed: 0
is_copy: 0
update_count: 3
updated: 2013-05-16 14:41:23
> [Object_Store_Refactor] System vms failed to come up with S3 as storage
> provider
>
>
> Key: CLOUDSTACK-2537
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2537
> 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 object_store branch
>Reporter: Sanjeev N
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> System vms failed to come up with S3 as storage provider
> Repro steps:
> ==
> 1.Bring CS in advanced zone with S3 as secondary storage provider
> 2.Enable the zone
> Expected Result:
> =
> As and when S3 gets added to CS, it should download system template to S3 and
> bring up system vms.
> Actual Result:
> ===
> System template was successfuly downloaded to S3 but failed to bring up
> system vms.
> Observations:
>
> 1.After step 1 system template was successfully downloaded to s3 bucket.
> 2013-05-16 10:40:49,434 INFO [storage.template.S3TemplateDownloader]
> (pool-2-thread-1:null) No credentials configured for host=10.147.28.7:80
> 2013-05-16 10:40:49,620 INFO [storage.template.S3TemplateDownloader]
> (pool-1-thread-1:null) Starting download from
> http://10.147.28.7/templates/acton/acton-systemvm-02062012.vhd.bz2 to s3
> bucket imagestore remoteSize=140616708 , max size=53687091200
> 2013-05-16 10:40:49,638 DEBUG [cloud.utils.S3Utils] (pool-1-thread-1:null)
> Creating S3 client with configuration: [protocol: http, connectionTimeOut:
> 100, maxErrorRetry: 3, socketTimeout: 100]
> 2013-05-16 10:40:49,995 DEBUG [cloud.utils.S3Utils] (pool-1-thread-1:null)
> Setting the end point for S3 client
> com.amazonaws.services.s3.AmazonS3Client@470edb99 to 10.147.29.56:8080.
> 2013-05-16 10:40:58,970 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-2:null) HostStatsCollector is running...
> 2013-05-16 10:40:58,972 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-3:null) VmStatsCollector is running...
> 2013-05-16 10:40:58,974 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-1:null) StorageCollector is running...
> 2013-05-16 10:40:59,036 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-4:null) Seq 1-1911750666: Executing request
> 2013-05-16 10:40:59,045 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-5:null) Seq 1-1911750667: Executing request
> 2013-05-16 10:40:59,271 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-4:null) Seq 1-1911750666: Response Received:
> 2013-05-16 10:40:59,272 DEBUG [agent.transport.Request]
> (StatsCollector-2:null) Seq 1-1911750666: Received: { Ans: , MgmtId:
> 7332683579487, via: 1, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
> 2013-05-16 10:40:59,356 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-5:null) Seq 1-1911750667: Response Received:
> 2013-05-16 10:40:59,357 DEBUG [agent.transport.Request]
> (StatsCollector-1:null) Seq 1-1911750667: Received: { Ans: , MgmtId:
> 7332683579487, via: 1, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-05-16 10:41:01,014 INFO [storage.template.S3TemplateDownloader]
> (pool-1-thread-1:null) download completed
> 2013-05-16 10:41:01,016 INFO [storage.template.DownloadManagerImpl]
> (pool-1-thread-1:null) Download Completion for jobId:
> 46e0c43d-a743-461f-8b88-16a57ac4bbb8, status=DOWNLOAD_FINISHED
> 2013-05-16 10:41:01,016 INFO [storage.template.DownloadManagerImpl]
> (pool-1-thread-1:null) local:
> template/tmpl/1/1/routing-1/acton-systemvm-02062012.vhd.bz2, bytes=140616708,
> error= , pct=100
> 2.After step2 CS tried to bring up the system vms. But failed to create
> volumes with following exceptions:
> 2013-05-16 10:43:44,843 DEBUG [cloud.storage.VolumeManagerImpl
[jira] [Updated] (CLOUDSTACK-2537) [Object_Store_Refactor] System vms failed to come up with S3 as storage provider
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N updated CLOUDSTACK-2537:
--
Attachment: management-server.rar
Attached mgmt server log file
> [Object_Store_Refactor] System vms failed to come up with S3 as storage
> provider
>
>
> Key: CLOUDSTACK-2537
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2537
> 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 object_store branch
>Reporter: Sanjeev N
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> System vms failed to come up with S3 as storage provider
> Repro steps:
> ==
> 1.Bring CS in advanced zone with S3 as secondary storage provider
> 2.Enable the zone
> Expected Result:
> =
> As and when S3 gets added to CS, it should download system template to S3 and
> bring up system vms.
> Actual Result:
> ===
> System template was successfuly downloaded to S3 but failed to bring up
> system vms.
> Observations:
>
> 1.After step 1 system template was successfully downloaded to s3 bucket.
> 2013-05-16 10:40:49,434 INFO [storage.template.S3TemplateDownloader]
> (pool-2-thread-1:null) No credentials configured for host=10.147.28.7:80
> 2013-05-16 10:40:49,620 INFO [storage.template.S3TemplateDownloader]
> (pool-1-thread-1:null) Starting download from
> http://10.147.28.7/templates/acton/acton-systemvm-02062012.vhd.bz2 to s3
> bucket imagestore remoteSize=140616708 , max size=53687091200
> 2013-05-16 10:40:49,638 DEBUG [cloud.utils.S3Utils] (pool-1-thread-1:null)
> Creating S3 client with configuration: [protocol: http, connectionTimeOut:
> 100, maxErrorRetry: 3, socketTimeout: 100]
> 2013-05-16 10:40:49,995 DEBUG [cloud.utils.S3Utils] (pool-1-thread-1:null)
> Setting the end point for S3 client
> com.amazonaws.services.s3.AmazonS3Client@470edb99 to 10.147.29.56:8080.
> 2013-05-16 10:40:58,970 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-2:null) HostStatsCollector is running...
> 2013-05-16 10:40:58,972 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-3:null) VmStatsCollector is running...
> 2013-05-16 10:40:58,974 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-1:null) StorageCollector is running...
> 2013-05-16 10:40:59,036 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-4:null) Seq 1-1911750666: Executing request
> 2013-05-16 10:40:59,045 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-5:null) Seq 1-1911750667: Executing request
> 2013-05-16 10:40:59,271 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-4:null) Seq 1-1911750666: Response Received:
> 2013-05-16 10:40:59,272 DEBUG [agent.transport.Request]
> (StatsCollector-2:null) Seq 1-1911750666: Received: { Ans: , MgmtId:
> 7332683579487, via: 1, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
> 2013-05-16 10:40:59,356 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-5:null) Seq 1-1911750667: Response Received:
> 2013-05-16 10:40:59,357 DEBUG [agent.transport.Request]
> (StatsCollector-1:null) Seq 1-1911750667: Received: { Ans: , MgmtId:
> 7332683579487, via: 1, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-05-16 10:41:01,014 INFO [storage.template.S3TemplateDownloader]
> (pool-1-thread-1:null) download completed
> 2013-05-16 10:41:01,016 INFO [storage.template.DownloadManagerImpl]
> (pool-1-thread-1:null) Download Completion for jobId:
> 46e0c43d-a743-461f-8b88-16a57ac4bbb8, status=DOWNLOAD_FINISHED
> 2013-05-16 10:41:01,016 INFO [storage.template.DownloadManagerImpl]
> (pool-1-thread-1:null) local:
> template/tmpl/1/1/routing-1/acton-systemvm-02062012.vhd.bz2, bytes=140616708,
> error= , pct=100
> 2.After step2 CS tried to bring up the system vms. But failed to create
> volumes with following exceptions:
> 2013-05-16 10:43:44,843 DEBUG [cloud.storage.VolumeManagerImpl]
> (secstorage-1:null) Checking if we need to prepare 1 volumes for
> VM[SecondaryStorageVm|s-1-VM]
> 2013-05-16 10:43:45,016 ERROR [storage.resource.NfsSecondaryStorageResource]
> (secstorage-1:null) Unable to create directory download directory 1 for
> download from S3.
> 2013-05-16 10:43:45,025 DEBUG [cloud.storage.VolumeManagerImpl]
> (secstorage-1:null) Unable to create
> Vol[1|vm=1|ROOT]:java.lang.NullPointerException
> 2013-05-16 10:43:45,026 INFO [cloud.vm.VirtualMachineManagerImpl]
> (secstorage-1:null) Unable to contact resource.
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1] is
> unreachable: Unable to create Vol[1|vm=1|ROOT]:java.lang.N
[jira] [Updated] (CLOUDSTACK-2536) parameters (cpu/memory)overcommit ratio and (cpu/memory).overprosioning.factor are redundant(cluster level)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2536: -- Attachment: screenshot-2.jpg > parameters (cpu/memory)overcommit ratio and > (cpu/memory).overprosioning.factor are redundant(cluster level) > > > Key: CLOUDSTACK-2536 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2536 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.2.0 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > Parameters > -- > --- > 1-(cpu overcommit ratio ;memory overcommit ratio) > > APIcalled : > http://10.147.*.*:8080/client/api?command=updateCluster&id=a407e95d-0081-44db-9ef0-812d23d6995c&cpuovercommitratio=1&memoryovercommitratio=3 > Result: > cluster_details table got updated with new overcommit ratio > 2-cpu.overprovisioning.factor;mem.overprovisioning.factor > -- > APIcalled: > http://10.147.*.*:8080/client/api?command=updateConfiguration&clusterid=a407e95d-0081-44db-9ef0-812d23d6995c&response=json&sessionkey=rARvjYlVHxDhU6sDx4Jmel%2F%2FFyY%3D&name=cpu.overprovisioning.factor&value=2 > Result: > Cluster_details table got updated with new overcommit value > Expected > - > - > Since both parameters are performing same job one of the parameter should be > removed -- 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-2537) [Object_Store_Refactor] System vms failed to come up with S3 as storage provider
Sanjeev N created CLOUDSTACK-2537:
-
Summary: [Object_Store_Refactor] System vms failed to come up with
S3 as storage provider
Key: CLOUDSTACK-2537
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2537
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 object_store branch
Reporter: Sanjeev N
Priority: Blocker
Fix For: 4.2.0
System vms failed to come up with S3 as storage provider
Repro steps:
==
1.Bring CS in advanced zone with S3 as secondary storage provider
2.Enable the zone
Expected Result:
=
As and when S3 gets added to CS, it should download system template to S3 and
bring up system vms.
Actual Result:
===
System template was successfuly downloaded to S3 but failed to bring up system
vms.
Observations:
1.After step 1 system template was successfully downloaded to s3 bucket.
2013-05-16 10:40:49,434 INFO [storage.template.S3TemplateDownloader]
(pool-2-thread-1:null) No credentials configured for host=10.147.28.7:80
2013-05-16 10:40:49,620 INFO [storage.template.S3TemplateDownloader]
(pool-1-thread-1:null) Starting download from
http://10.147.28.7/templates/acton/acton-systemvm-02062012.vhd.bz2 to s3 bucket
imagestore remoteSize=140616708 , max size=53687091200
2013-05-16 10:40:49,638 DEBUG [cloud.utils.S3Utils] (pool-1-thread-1:null)
Creating S3 client with configuration: [protocol: http, connectionTimeOut: 100,
maxErrorRetry: 3, socketTimeout: 100]
2013-05-16 10:40:49,995 DEBUG [cloud.utils.S3Utils] (pool-1-thread-1:null)
Setting the end point for S3 client
com.amazonaws.services.s3.AmazonS3Client@470edb99 to 10.147.29.56:8080.
2013-05-16 10:40:58,970 DEBUG [cloud.server.StatsCollector]
(StatsCollector-2:null) HostStatsCollector is running...
2013-05-16 10:40:58,972 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) VmStatsCollector is running...
2013-05-16 10:40:58,974 DEBUG [cloud.server.StatsCollector]
(StatsCollector-1:null) StorageCollector is running...
2013-05-16 10:40:59,036 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1911750666: Executing request
2013-05-16 10:40:59,045 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-5:null) Seq 1-1911750667: Executing request
2013-05-16 10:40:59,271 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1911750666: Response Received:
2013-05-16 10:40:59,272 DEBUG [agent.transport.Request] (StatsCollector-2:null)
Seq 1-1911750666: Received: { Ans: , MgmtId: 7332683579487, via: 1, Ver: v1,
Flags: 10, { GetHostStatsAnswer } }
2013-05-16 10:40:59,356 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-5:null) Seq 1-1911750667: Response Received:
2013-05-16 10:40:59,357 DEBUG [agent.transport.Request] (StatsCollector-1:null)
Seq 1-1911750667: Received: { Ans: , MgmtId: 7332683579487, via: 1, Ver: v1,
Flags: 10, { GetStorageStatsAnswer } }
2013-05-16 10:41:01,014 INFO [storage.template.S3TemplateDownloader]
(pool-1-thread-1:null) download completed
2013-05-16 10:41:01,016 INFO [storage.template.DownloadManagerImpl]
(pool-1-thread-1:null) Download Completion for jobId:
46e0c43d-a743-461f-8b88-16a57ac4bbb8, status=DOWNLOAD_FINISHED
2013-05-16 10:41:01,016 INFO [storage.template.DownloadManagerImpl]
(pool-1-thread-1:null) local:
template/tmpl/1/1/routing-1/acton-systemvm-02062012.vhd.bz2, bytes=140616708,
error= , pct=100
2.After step2 CS tried to bring up the system vms. But failed to create volumes
with following exceptions:
2013-05-16 10:43:44,843 DEBUG [cloud.storage.VolumeManagerImpl]
(secstorage-1:null) Checking if we need to prepare 1 volumes for
VM[SecondaryStorageVm|s-1-VM]
2013-05-16 10:43:45,016 ERROR [storage.resource.NfsSecondaryStorageResource]
(secstorage-1:null) Unable to create directory download directory 1 for
download from S3.
2013-05-16 10:43:45,025 DEBUG [cloud.storage.VolumeManagerImpl]
(secstorage-1:null) Unable to create
Vol[1|vm=1|ROOT]:java.lang.NullPointerException
2013-05-16 10:43:45,026 INFO [cloud.vm.VirtualMachineManagerImpl]
(secstorage-1:null) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1] is
unreachable: Unable to create Vol[1|vm=1|ROOT]:java.lang.NullPointerException
at
com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2355)
at
com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2404)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:812)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:529)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:522)
[jira] [Updated] (CLOUDSTACK-2536) parameters (cpu/memory)overcommit ratio and (cpu/memory).overprosioning.factor are redundant(cluster level)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2536: -- Attachment: screenshot-1.jpg > parameters (cpu/memory)overcommit ratio and > (cpu/memory).overprosioning.factor are redundant(cluster level) > > > Key: CLOUDSTACK-2536 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2536 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.2.0 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: screenshot-1.jpg > > > Parameters > -- > --- > 1-(cpu overcommit ratio ;memory overcommit ratio) > > APIcalled : > http://10.147.*.*:8080/client/api?command=updateCluster&id=a407e95d-0081-44db-9ef0-812d23d6995c&cpuovercommitratio=1&memoryovercommitratio=3 > Result: > cluster_details table got updated with new overcommit ratio > 2-cpu.overprovisioning.factor;mem.overprovisioning.factor > -- > APIcalled: > http://10.147.*.*:8080/client/api?command=updateConfiguration&clusterid=a407e95d-0081-44db-9ef0-812d23d6995c&response=json&sessionkey=rARvjYlVHxDhU6sDx4Jmel%2F%2FFyY%3D&name=cpu.overprovisioning.factor&value=2 > Result: > Cluster_details table got updated with new overcommit value > Expected > - > - > Since both parameters are performing same job one of the parameter should be > removed -- 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-948) QA - affinity and anti affinity rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659364#comment-13659364 ] Girish Shilamkar commented on CLOUDSTACK-948: - I created affinity group as a user and then as admin listed all the affinity groups on UI. I did not see the affinity group for the user in UI. Which I think admin should be able to ?? Then I spawned a vm from the same user account and as admin user I listed this vm. And did a "View Affinity groups" for this vm (as admin). It did list the affinity group. > QA - affinity and anti affinity rules > - > > Key: CLOUDSTACK-948 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-948 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0 >Reporter: Sudha Ponnaganti >Assignee: Sangeetha Hariharan > Fix For: 4.2.0 > > > core tasks that need to be done: > - review requirements/FS > - upload test plan/test cases > - get test cases reviewed > - add automation > - upload test results > - review documentation -- 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-2536) parameters (cpu/memory)overcommit ratio and (cpu/memory).overprosioning.factor are redundant(cluster level)
prashant kumar mishra created CLOUDSTACK-2536: - Summary: parameters (cpu/memory)overcommit ratio and (cpu/memory).overprosioning.factor are redundant(cluster level) Key: CLOUDSTACK-2536 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2536 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.2.0 Reporter: prashant kumar mishra Fix For: 4.2.0 Parameters -- --- 1-(cpu overcommit ratio ;memory overcommit ratio) APIcalled : http://10.147.*.*:8080/client/api?command=updateCluster&id=a407e95d-0081-44db-9ef0-812d23d6995c&cpuovercommitratio=1&memoryovercommitratio=3 Result: cluster_details table got updated with new overcommit ratio 2-cpu.overprovisioning.factor;mem.overprovisioning.factor -- APIcalled: http://10.147.*.*:8080/client/api?command=updateConfiguration&clusterid=a407e95d-0081-44db-9ef0-812d23d6995c&response=json&sessionkey=rARvjYlVHxDhU6sDx4Jmel%2F%2FFyY%3D&name=cpu.overprovisioning.factor&value=2 Result: Cluster_details table got updated with new overcommit value Expected - - Since both parameters are performing same job one of the parameter should be removed -- 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-2535) Cleanup port-profiles that gets created on Nexus switch
Koushik Das created CLOUDSTACK-2535: --- Summary: Cleanup port-profiles that gets created on Nexus switch Key: CLOUDSTACK-2535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2535 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.0.0, pre-4.0.0 Environment: Vmware Reporter: Koushik Das Fix For: 4.2.0 Port profiles are not cleaned up when a guest network using it gets removed. As part of network shutdown all port profiles that got created on the Nexus switch should be removed. The same problem is also there for vSwitch and dvSwitch. -- 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-2535) Cleanup port-profiles that gets created on Nexus switch as part of network cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-2535: Summary: Cleanup port-profiles that gets created on Nexus switch as part of network cleanup (was: Cleanup port-profiles that gets created on Nexus switch) > Cleanup port-profiles that gets created on Nexus switch as part of network > cleanup > -- > > Key: CLOUDSTACK-2535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Affects Versions: pre-4.0.0, 4.0.0 > Environment: Vmware >Reporter: Koushik Das > Fix For: 4.2.0 > > > Port profiles are not cleaned up when a guest network using it gets removed. > As part of network shutdown all port profiles that got created on the Nexus > switch should be removed. > The same problem is also there for vSwitch and dvSwitch. -- 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-2516) Create User API compability broken now
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659339#comment-13659339
]
Kishan Kavala commented on CLOUDSTACK-2516:
---
Adding Prasanna's comments from the ML discussion:
This change happened when the authenticators were moved in to use adapters.
That change was a logical one to support multiple Auth mechanisms. Hugo made
the change in (bd58cecc) and it is the right way to do it.
Prior to Hugo's fix the MD5 authenticator,although called so, would only do a
plaintext match of passwords with the database. Also the
createUser() would simply persist the password coming in over with wire into
the db. Thereby it assumed tht the passwd would be pre-encoded as MD5 at the
client.
So, why did MD5 passwds get into the DB at all?
The API documentation asks that the client send in a md5 hashed password and
our ui script (account.js, sharedFunction.js) is hashing the passwords into md5.
There was probably a reason behind this. I'm not sure: Here's the comment
indicating the change:
"""
// Will: The MD5Authenticator is now a straight pass-through comparison of the
// the passwords because we will not assume that the password passed in has //
already been MD5 hashed. I am keeping the above code in case this requirement
changes // or people need examples of how to MD5 hash passwords in java.
if (!user.getPassword().equals(password)) {
return false
"""
After Hugo's fix the MD5 Authenticator (the default authenticator) now
_actually_ does the encoding and not depend on the client. But the UI code
still seems to exist and double encodes the md5 entry in the form.
So the fix should be
- UI removes the double hashing when account creation happens.
- Fix the API doc to ask user to send in plaintext password and allow
to act based on authenticator configured in componentsContext.xml
As an aside:
Hugo, the SHA256 authenticator you introduced seems to have been removed from
the componentContexts. Do you want to include it back, commented?
> Create User API compability broken now
> --
>
> Key: CLOUDSTACK-2516
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2516
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Chip Childers
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
>
> From email thread:
> On Wed, May 15, 2013 at 04:22:14PM +0200, Ove Ewerlid wrote:
> > NB; The 402/410 deployments are on RHES64(OEL64) via RPMs built from
> > latest git repos.
> > /Ove
> >
> > On 05/15/2013 03:02 PM, Ove Ewerlid wrote:
> > >Hi!
> > >
> > >When testing a deploy script, that works as expected with 4.0.2, on 4.1
> > >I noticed that there was a need to pass plaintext passwords to
> > >createUser, rather then the documented MD5 hash. When passing MD5 hash,
> > >the password gets double MD5:hashed in 41.
> > >
> > >There is new code in 4.1 that encodes password using the authenticator
> > >plugins (encode method);
> > >
> > >cloudstack.4.1/server/src/com/cloud/user/AccountManagerImpl.java
> > >
> > >...
> > >String encodedPassword = null;
> > > for (UserAuthenticator authenticator : _userAuthenticators) {
> > > encodedPassword = authenticator.encode(password);
> > > if (encodedPassword != null) {
> > > break;
> > > }
> > > }
> > >...
> > >
> > >The 41 API docs still notes that an MD5 hash shall be passed in.
> > >What am I missing here?
> > >
> > >/Ove
--
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-2534) SSH public key for SSVMs is too open for Vmware hypervisor
Girish Shilamkar created CLOUDSTACK-2534: Summary: SSH public key for SSVMs is too open for Vmware hypervisor 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 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
