[jira] [Commented] (CLOUDSTACK-8923) Create storage network IP range failed, Unknown parameters : zoneid
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943016#comment-14943016
]
ASF GitHub Bot commented on CLOUDSTACK-8923:
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/911#discussion_r41117252
--- Diff: server/src/com/cloud/network/StorageNetworkManagerImpl.java ---
@@ -223,7 +225,7 @@ public StorageNetworkIpRange createIpRange(final
CreateStorageNetworkIpRangeCmd
checkOverlapPrivateIpRange(podId, startIp, endIp);
checkOverlapStorageIpRange(podId, startIp, endIp);
-StorageNetworkIpRangeVO range = null;
+//StorageNetworkIpRangeVO range = null;
--- End diff --
please don't comment out code, remove it
> Create storage network IP range failed, Unknown parameters : zoneid
> ---
>
> Key: CLOUDSTACK-8923
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8923
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Secondary Storage
>Affects Versions: 4.6.0
> Environment: CentOS 6 HVs and MGMT
>Reporter: Nux
>Priority: Blocker
>
> I am installing ACS from today's master (3ded3e9
> http://tmp.nux.ro/acs460snap/ ).
> Adding an initial zone via the web UI wizard fails at the secondary storage
> setup stage:
> 2015-09-29 14:07:40,319 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Add job-27 into job monitoring
> 2015-09-29 14:07:40,322 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-314bbaae ctx-2db63923) ===END=== 85.13.192.198 -- GET
> command=createStorageNetworkIpRange&response=json&gateway=192.168.200.67&netmask=255.255.255.0&vlan=123&startip=192.168.200.200&endip=192.168.200.222&zoneid=2f0efdcf-adf6-4373-858e-87de6af4cc08&podid=eb7814d2-9a22-4ca4-93af-4a6b8abac67c&_=1443532060283
> 2015-09-29 14:07:40,327 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Executing AsyncJobVO {id:27,
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd,
> cmdInfo: {"response":"json","ctxDetails":"{\"interface
> com.cloud.dc.Pod\":\"eb7814d2-9a22-4ca4-93af-4a6b8abac67c\"}","cmdEventType":"STORAGE.IP.RANGE.CREATE","ctxUserId":"2","gateway":"192.168.200.67","podid":"eb7814d2-9a22-4ca4-93af-4a6b8abac67c","zoneid":"2f0efdcf-adf6-4373-858e-87de6af4cc08","startip":"192.168.200.200","vlan":"123","httpmethod":"GET","_":"1443532060283","ctxAccountId":"2","ctxStartEventId":"68","netmask":"255.255.255.0","endip":"192.168.200.222"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 266785867798693, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2015-09-29 14:07:40,330 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Received unknown
> parameters for command createStorageNetworkIpRange. Unknown parameters :
> zoneid
> 2015-09-29 14:07:40,391 WARN [o.a.c.a.c.a.n.CreateStorageNetworkIpRangeCmd]
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Create storage network
> IP range failed
> com.cloud.utils.exception.CloudRuntimeException: Unable to commit or close
> the connection.
> at
> com.cloud.utils.db.TransactionLegacy.commit(TransactionLegacy.java:730)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
> at
> com.cloud.network.StorageNetworkManagerImpl.createIpRange(StorageNetworkManagerImpl.java:229)
> at
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd.execute(CreateStorageNetworkIpRangeCmd.java:118)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl
[jira] [Commented] (CLOUDSTACK-8923) Create storage network IP range failed, Unknown parameters : zoneid
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943028#comment-14943028
]
ASF GitHub Bot commented on CLOUDSTACK-8923:
Github user borisroman commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/911#discussion_r41118074
--- Diff: server/src/com/cloud/network/StorageNetworkManagerImpl.java ---
@@ -223,7 +225,7 @@ public StorageNetworkIpRange createIpRange(final
CreateStorageNetworkIpRangeCmd
checkOverlapPrivateIpRange(podId, startIp, endIp);
checkOverlapStorageIpRange(podId, startIp, endIp);
-StorageNetworkIpRangeVO range = null;
+//StorageNetworkIpRangeVO range = null;
--- End diff --
I know :) Still busy testing, please read the last comment of my PR
message. I PR'd the first commit, then pushed the second one for testing.
> Create storage network IP range failed, Unknown parameters : zoneid
> ---
>
> Key: CLOUDSTACK-8923
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8923
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Secondary Storage
>Affects Versions: 4.6.0
> Environment: CentOS 6 HVs and MGMT
>Reporter: Nux
>Priority: Blocker
>
> I am installing ACS from today's master (3ded3e9
> http://tmp.nux.ro/acs460snap/ ).
> Adding an initial zone via the web UI wizard fails at the secondary storage
> setup stage:
> 2015-09-29 14:07:40,319 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Add job-27 into job monitoring
> 2015-09-29 14:07:40,322 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-314bbaae ctx-2db63923) ===END=== 85.13.192.198 -- GET
> command=createStorageNetworkIpRange&response=json&gateway=192.168.200.67&netmask=255.255.255.0&vlan=123&startip=192.168.200.200&endip=192.168.200.222&zoneid=2f0efdcf-adf6-4373-858e-87de6af4cc08&podid=eb7814d2-9a22-4ca4-93af-4a6b8abac67c&_=1443532060283
> 2015-09-29 14:07:40,327 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Executing AsyncJobVO {id:27,
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd,
> cmdInfo: {"response":"json","ctxDetails":"{\"interface
> com.cloud.dc.Pod\":\"eb7814d2-9a22-4ca4-93af-4a6b8abac67c\"}","cmdEventType":"STORAGE.IP.RANGE.CREATE","ctxUserId":"2","gateway":"192.168.200.67","podid":"eb7814d2-9a22-4ca4-93af-4a6b8abac67c","zoneid":"2f0efdcf-adf6-4373-858e-87de6af4cc08","startip":"192.168.200.200","vlan":"123","httpmethod":"GET","_":"1443532060283","ctxAccountId":"2","ctxStartEventId":"68","netmask":"255.255.255.0","endip":"192.168.200.222"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 266785867798693, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2015-09-29 14:07:40,330 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Received unknown
> parameters for command createStorageNetworkIpRange. Unknown parameters :
> zoneid
> 2015-09-29 14:07:40,391 WARN [o.a.c.a.c.a.n.CreateStorageNetworkIpRangeCmd]
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Create storage network
> IP range failed
> com.cloud.utils.exception.CloudRuntimeException: Unable to commit or close
> the connection.
> at
> com.cloud.utils.db.TransactionLegacy.commit(TransactionLegacy.java:730)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
> at
> com.cloud.network.StorageNetworkManagerImpl.createIpRange(StorageNetworkManagerImpl.java:229)
> at
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd.execute(CreateStorageNetworkIpRangeCmd.java:118)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContext
[jira] [Commented] (CLOUDSTACK-8915) Cannot SSH into VMs deployed Redundant VPC routers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943116#comment-14943116 ] ASF GitHub Bot commented on CLOUDSTACK-8915: Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/908#issuecomment-145473615 Hi @remibergsma and @bvbharat, Please have a look at my comment from 2 days ago. I mentioned that indeed the change would create a regression. So this PR won't get merged with the current change on the copy/copy_if_needed stuff. I will change it back and also refactor the code of the copy() function, which is not duplicate from the copy_if_needed. Concerning the current way theVR is being configured - and having the configuration applied every time update_config is called - I agree it's not optimal. Our plan is to stabilise all the VRs in the coming 2 weeks. If we get the BVTs to work as expected, we will then move towards the next phase: refactor the persistent configuration, which should be available for a 4.6.1 release. Cheers, Wilder > Cannot SSH into VMs deployed Redundant VPC routers > -- > > Key: CLOUDSTACK-8915 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8915 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues >Priority: Blocker > > The Marvin test under componenet/test_vpc_redundant.py no longer passes. I > also tried to test it manually, but unfortunately the feature is now broken. > * Create a Redundant VPC > * Add a tier > * Add a new VM to the tier > * Add an ACL, open port 22 and associate the ACL with the tier > * Acquire a pub IP > * Add a PF rule to port 22 towards the VM > * Try to SSH to the VM through the Pub IP > It fails with "No route to host" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8923) Create storage network IP range failed, Unknown parameters : zoneid
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943166#comment-14943166
]
Rajani Karuturi edited comment on CLOUDSTACK-8923 at 10/5/15 10:07 AM:
---
[~remibergsma] looks like [~borisroman] already started on it.
was (Author: rajanik):
[~remibergsma]looks like [~borisroman] already started on it.
> Create storage network IP range failed, Unknown parameters : zoneid
> ---
>
> Key: CLOUDSTACK-8923
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8923
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Secondary Storage
>Affects Versions: 4.6.0
> Environment: CentOS 6 HVs and MGMT
>Reporter: Nux
>Priority: Blocker
>
> I am installing ACS from today's master (3ded3e9
> http://tmp.nux.ro/acs460snap/ ).
> Adding an initial zone via the web UI wizard fails at the secondary storage
> setup stage:
> 2015-09-29 14:07:40,319 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Add job-27 into job monitoring
> 2015-09-29 14:07:40,322 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-314bbaae ctx-2db63923) ===END=== 85.13.192.198 -- GET
> command=createStorageNetworkIpRange&response=json&gateway=192.168.200.67&netmask=255.255.255.0&vlan=123&startip=192.168.200.200&endip=192.168.200.222&zoneid=2f0efdcf-adf6-4373-858e-87de6af4cc08&podid=eb7814d2-9a22-4ca4-93af-4a6b8abac67c&_=1443532060283
> 2015-09-29 14:07:40,327 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Executing AsyncJobVO {id:27,
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd,
> cmdInfo: {"response":"json","ctxDetails":"{\"interface
> com.cloud.dc.Pod\":\"eb7814d2-9a22-4ca4-93af-4a6b8abac67c\"}","cmdEventType":"STORAGE.IP.RANGE.CREATE","ctxUserId":"2","gateway":"192.168.200.67","podid":"eb7814d2-9a22-4ca4-93af-4a6b8abac67c","zoneid":"2f0efdcf-adf6-4373-858e-87de6af4cc08","startip":"192.168.200.200","vlan":"123","httpmethod":"GET","_":"1443532060283","ctxAccountId":"2","ctxStartEventId":"68","netmask":"255.255.255.0","endip":"192.168.200.222"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 266785867798693, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2015-09-29 14:07:40,330 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Received unknown
> parameters for command createStorageNetworkIpRange. Unknown parameters :
> zoneid
> 2015-09-29 14:07:40,391 WARN [o.a.c.a.c.a.n.CreateStorageNetworkIpRangeCmd]
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Create storage network
> IP range failed
> com.cloud.utils.exception.CloudRuntimeException: Unable to commit or close
> the connection.
> at
> com.cloud.utils.db.TransactionLegacy.commit(TransactionLegacy.java:730)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
> at
> com.cloud.network.StorageNetworkManagerImpl.createIpRange(StorageNetworkManagerImpl.java:229)
> at
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd.execute(CreateStorageNetworkIpRangeCmd.java:118)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:494)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run
[jira] [Commented] (CLOUDSTACK-8923) Create storage network IP range failed, Unknown parameters : zoneid
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943166#comment-14943166
]
Rajani Karuturi commented on CLOUDSTACK-8923:
-
[~remibergsma]looks like [~borisroman] already started on it.
> Create storage network IP range failed, Unknown parameters : zoneid
> ---
>
> Key: CLOUDSTACK-8923
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8923
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Secondary Storage
>Affects Versions: 4.6.0
> Environment: CentOS 6 HVs and MGMT
>Reporter: Nux
>Priority: Blocker
>
> I am installing ACS from today's master (3ded3e9
> http://tmp.nux.ro/acs460snap/ ).
> Adding an initial zone via the web UI wizard fails at the secondary storage
> setup stage:
> 2015-09-29 14:07:40,319 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Add job-27 into job monitoring
> 2015-09-29 14:07:40,322 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-5:ctx-314bbaae ctx-2db63923) ===END=== 85.13.192.198 -- GET
> command=createStorageNetworkIpRange&response=json&gateway=192.168.200.67&netmask=255.255.255.0&vlan=123&startip=192.168.200.200&endip=192.168.200.222&zoneid=2f0efdcf-adf6-4373-858e-87de6af4cc08&podid=eb7814d2-9a22-4ca4-93af-4a6b8abac67c&_=1443532060283
> 2015-09-29 14:07:40,327 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Executing AsyncJobVO {id:27,
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd,
> cmdInfo: {"response":"json","ctxDetails":"{\"interface
> com.cloud.dc.Pod\":\"eb7814d2-9a22-4ca4-93af-4a6b8abac67c\"}","cmdEventType":"STORAGE.IP.RANGE.CREATE","ctxUserId":"2","gateway":"192.168.200.67","podid":"eb7814d2-9a22-4ca4-93af-4a6b8abac67c","zoneid":"2f0efdcf-adf6-4373-858e-87de6af4cc08","startip":"192.168.200.200","vlan":"123","httpmethod":"GET","_":"1443532060283","ctxAccountId":"2","ctxStartEventId":"68","netmask":"255.255.255.0","endip":"192.168.200.222"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 266785867798693, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2015-09-29 14:07:40,330 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Received unknown
> parameters for command createStorageNetworkIpRange. Unknown parameters :
> zoneid
> 2015-09-29 14:07:40,391 WARN [o.a.c.a.c.a.n.CreateStorageNetworkIpRangeCmd]
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Create storage network
> IP range failed
> com.cloud.utils.exception.CloudRuntimeException: Unable to commit or close
> the connection.
> at
> com.cloud.utils.db.TransactionLegacy.commit(TransactionLegacy.java:730)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
> at
> com.cloud.network.StorageNetworkManagerImpl.createIpRange(StorageNetworkManagerImpl.java:229)
> at
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd.execute(CreateStorageNetworkIpRangeCmd.java:118)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:494)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.sql.SQLException: Connection is closed.
> at
> org.apache.commons.dbcp.PoolingDataSource$PoolGua
[jira] [Commented] (CLOUDSTACK-8832) Update Nuage VSP plugin to work with Nuage VSP release 3.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943183#comment-14943183 ] ASF GitHub Bot commented on CLOUDSTACK-8832: Github user KrisSterckx commented on the pull request: https://github.com/apache/cloudstack/pull/801#issuecomment-145488778 I would like to bring attention to the reviewers that only a few CS core extensions were made - all other modifications are NuageVsp plugin internal, for Nuage Virtualized Services Platform Release 3.2 support. api/src/com/cloud/network/Network.java * Remove the unused NuageVspVpc constant engine/schema/src/com/cloud/network/dao/IPAddressDao.java engine/schema/src/com/cloud/network/dao/IPAddressDaoImpl.java * new DAO method added engine/schema/src/com/cloud/network/vpc/VpcOfferingVO.java * new constructor added server/src/com/cloud/configuration/ConfigurationManagerImpl.java * Exclude shared networks from DirectNetworkGuru canHandle() in case the offering is NuageVsp as then NuageVsp guru is handling. server/src/com/cloud/configuration/ConfigurationManagerImpl.java * Add extra check on isPersistent() for nuageVpc check > Update Nuage VSP plugin to work with Nuage VSP release 3.2 > -- > > Key: CLOUDSTACK-8832 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Nick Livens >Assignee: Nick Livens > Attachments: nuageVspMarvinLogs.tar.gz > > > Nuage VSP 3.2 is being released, we want to bring the plugin up to date for > this release -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8832) Update Nuage VSP plugin to work with Nuage VSP release 3.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943795#comment-14943795 ] ASF GitHub Bot commented on CLOUDSTACK-8832: Github user Pradeepgjain commented on the pull request: https://github.com/apache/cloudstack/pull/801#issuecomment-145624812 @jburwell For testing NuageVsp plugin on cloudstack, first nuage VSP needs to be installed: http://www.nuagenetworks.net/products/virtualized-services-platform/ Once installed, NuageVsp marvin tests can be run to test plugin functionality. > Update Nuage VSP plugin to work with Nuage VSP release 3.2 > -- > > Key: CLOUDSTACK-8832 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Nick Livens >Assignee: Nick Livens > Attachments: nuageVspMarvinLogs.tar.gz > > > Nuage VSP 3.2 is being released, we want to bring the plugin up to date for > this release -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-1074) Scaling up CPU and RAM for running VMs - KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943878#comment-14943878 ] Frank Louwers commented on CLOUDSTACK-1074: --- Am willing to look at this, if I can get a hand with some config stuff? In particular, I'd like to make this feature configureable in the config. Could be disabled by default (for those who don't want it), but enabled by those who mitigate the risk of someone accessing ram memory instead of via virt_balloon... > Scaling up CPU and RAM for running VMs - KVM > > > Key: CLOUDSTACK-1074 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1074 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Nitin Mehta > Fix For: Future > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8922) Unable to delete IP tag
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943981#comment-14943981
]
ASF GitHub Bot commented on CLOUDSTACK-8922:
Github user runseb commented on the pull request:
https://github.com/apache/cloudstack/pull/905#issuecomment-145661688
@yvsubhash we should try to remove manual testing. Can you write a marvin
test for it. thanks. cc @wilderrodrigues
> Unable to delete IP tag
> ---
>
> Key: CLOUDSTACK-8922
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8922
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.5.2
>Reporter: subhash yedugundla
>
> 1. Acquire new IP address
> 2. Create tags for the IP
> 3. Delete the tag from Step#2
> an error occurs at Step#3 whereby the delete tag operation fails with
> "Acct[f4d0c381-e0b7-4aed-aa90-3336d42f7540-7100017] does not have
> permission to operate within domain id\u003d632"
> TROUBLESHOOTING
> ==
> Acquire new IP address
> *
> {noformat}
> 2014-11-19 15:08:15,870 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-20:ctx-faed32b5 ctx-712308cb ctx-401bfcaf) submit async
> job-72419, details: AsyncJobVO {id:72419, userId: 17, accountId: 15,
> instanceType: IpAddress, instanceId: 672, cmd:
> org.apache.cloudstack.api.command.user.address.AssociateIPAddrCmd, cmdInfo:
> {"id":"672","response":"json","cmdEventType":"NET.IPASSIGN","ctxUserId":"17","zoneid":"a117e75f-d02e-4074-806d-889c61261394","httpmethod":"GET","ctxAccountId":"15","networkid":"0ca7c69e-c281-407b-a152-2559c10a81a6","ctxStartEventId":"166725","signature":"3NZRU6dIBxg1HMDiP/MkY2agRn4\u003d","apikey":"tuwHXs1AfpQheJeJ9BcLdoVxIBCItASnguAbus76AMUcIXuyFgHOJiIB44fO57p_bBaqyfppmxrC-rQSb-nxXg"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 345048681027, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-11-19 15:08:15,870 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-68:ctx-fca9add6 job-72419) Executing AsyncJobVO {id:72419,
> userId: 17, accountId: 15, instanceType: IpAddress, instanceId: 672, cmd:
> org.apache.cloudstack.api.command.user.address.AssociateIPAddrCmd, cmdInfo:
> {"id":"672","response":"json","cmdEventType":"NET.IPASSIGN","ctxUserId":"17","zoneid":"a117e75f-d02e-4074-806d-889c61261394","httpmethod":"GET","ctxAccountId":"15","networkid":"0ca7c69e-c281-407b-a152-2559c10a81a6","ctxStartEventId":"166725","signature":"3NZRU6dIBxg1HMDiP/MkY2agRn4\u003d","apikey":"tuwHXs1AfpQheJeJ9BcLdoVxIBCItASnguAbus76AMUcIXuyFgHOJiIB44fO57p_bBaqyfppmxrC-rQSb-nxXg"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 345048681027, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-11-19 15:08:15,890 DEBUG [c.c.u.AccountManagerImpl]
> (API-Job-Executor-68:ctx-fca9add6 job-72419 ctx-96bbdee5) Access to
> Ntwk[216|Guest|8] granted to
> Acct[f4d0c381-e0b7-4aed-aa90-3336d42f7540-7100017] by DomainChecker
> 2014-11-19 15:08:15,911 DEBUG [c.c.n.IpAddressManagerImpl]
> (API-Job-Executor-68:ctx-fca9add6 job-72419 ctx-96bbdee5) Successfully
> associated ip address 210.140.170.160 to network Ntwk[216|Guest|8]
> 2014-11-19 15:08:15,922 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-68:ctx-fca9add6 job-72419 ctx-96bbdee5) Complete async
> job-72419, jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.IPAddressResponse/ipaddress/{"id":"3d7c3a2a-1f2d-46dc-9905-4a7ce620e7e9","ipaddress":"210.140.170.160","allocated":"2014-11-19T15:08:15+0900","zoneid":"a117e75f-d02e-4074-806d-889c61261394","zonename":"tesla","issourcenat":false,"account":"7100017","domainid":"cc27e32c-6acd-4fdf-a1e5-734cef8a7fe0","domain":"7100017","forvirtualnetwork":true,"isstaticnat":false,"issystem":false,"associatednetworkid":"0ca7c69e-c281-407b-a152-2559c10a81a6","associatednetworkname":"network1","networkid":"79132c74-fe77-4bd5-9915-ce7c577fb95f","state":"Allocating","physicalnetworkid":"4a00ce42-6a30-4494-afdd-3531d883237b","tags":[],"isportable":false}
> 2014-11-19 15:08:15,932 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-68:ctx-fca9add6 job-72419) Remove job-72419 from job
> monitoring
> +---+---++---+---+-+-+
> | id| job_cmd |
> job_status | job_init_msid | job_complete_msid | created |
> last_updated|
> +---+--
[jira] [Commented] (CLOUDSTACK-8929) After a load balancer rule is created and if another VM is assigned to it, it still shows up in the list of VMs that can be assigned to it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943983#comment-14943983 ] ASF GitHub Bot commented on CLOUDSTACK-8929: Github user runseb commented on the pull request: https://github.com/apache/cloudstack/pull/904#issuecomment-145662123 @rags22489664 any comments based on the reviews ? > After a load balancer rule is created and if another VM is assigned to it, it > still shows up in the list of VMs that can be assigned to it > -- > > Key: CLOUDSTACK-8929 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8929 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.6.0 >Reporter: Ramamurti Subramanian >Assignee: Ramamurti Subramanian > Fix For: 4.6.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8928) While adding VMs to LB rule, default NIC IP is always displayed rather than the IP corresponding to the NIC where LB is being created
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943984#comment-14943984 ] ASF GitHub Bot commented on CLOUDSTACK-8928: Github user runseb commented on the pull request: https://github.com/apache/cloudstack/pull/903#issuecomment-145662476 @nitin-maharana Any automated tests for this ? if not, can you spend the time to write some. thanks > While adding VMs to LB rule, default NIC IP is always displayed rather than > the IP corresponding to the NIC where LB is being created > - > > Key: CLOUDSTACK-8928 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8928 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > Issue : > - > While creating LB rule, if the VM belongs to multiple NICs, always the > default NIC IP is the only one displayed. This causes issues in cases where > we want to create an LB using the non-default NIC of the VM. It fails with an > error message. This IP is never displayed in UI and only way is use the API > directly to create such an LB rule. > Steps > = > 1. Create a VM with multiple NICs (VM belongs to multiple networks) > 2. Navigate to the non-default Network of the VM -> IP Address -> > Configuration -> Load Balancing -> Create an LB rule -> Add -> Choose the VM > created > Observe that the IP listed does not belong to that Network. It is always the > IP of the default NIC. By choosing this IP, the LB creation will fail since > the IP and network ids would not match. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8919) Slow UI response while loading the list of networks in network tab.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943989#comment-14943989 ] ASF GitHub Bot commented on CLOUDSTACK-8919: Github user runseb commented on the pull request: https://github.com/apache/cloudstack/pull/897#issuecomment-145662988 thanks @nitin-maharana maybe we should have a small performance study to show that it actually speeds things up > Slow UI response while loading the list of networks in network tab. > --- > > Key: CLOUDSTACK-8919 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8919 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Nitin Kumar Maharana > > Root cause of this Issue: Invokes 3 APIs, the 2nd API to check whether any > network is having security group service, this consumes 90% of the time. API > fetches network list and for each network calls DB to get services associated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8933) SSVm and CPVM do not survice a reboot from API
Remi Bergsma created CLOUDSTACK-8933: Summary: SSVm and CPVM do not survice a reboot from API Key: CLOUDSTACK-8933 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8933 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.6.0 Environment: KVM Advanced / Basic zone Reporter: Remi Bergsma Priority: Blocker Fix For: 4.6.0 These tests fail: - integration.smoke.test_ssvm.TestSSVMs.test_07_reboot_ssvm - integration.smoke.test_ssvm.TestSSVMs.test_08_reboot_cpvm Stopping works, then CloudStack successfully deploys a new one. Rebooting doesn’t work as it doesn’t complete the boot sequence. Looking at the agent.log I noticed the systemvm doesn’t get patched so it is probably waiting for that to happen. A successful start shows this: 2015-10-05 21:26:12,748 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) Executing: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n v-1-VM -p %template=domP%type=consoleproxy%host=192.168.22.61%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.168.23.2%eth2mask=255.255.255.0%gateway=192.168.23.1%eth0ip=169.254.1.20%eth0mask=255.255.0.0%eth1ip=192.168.22.137%eth1mask=255.255.255.0%mgmtcidr=192.168.22.0/24%localgw=192.168.22.1%internaldns1=8.8.4.4%dns1=8.8.8.8 2015-10-05 21:26:12,777 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) Execution is successful. The reboot doesn’t do this. When I hit reboot and run this command manually, it works: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n v-1-VM -p %template=domP%type=consoleproxy%host=192.168.22.61%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy1%proxy_vm=1%disable_rp_filter=tru%eth2ip=192.168.23.2%eth2mask=255.255.255.0%gateway=192.168.23.1%eth0ip=169.254.1.20%eth0mask=255.255.0.0%eth1ip=192.168.22.137%eth1mask=255.255.255.0%mgmtcidr=192.168.22.0/24%localgw=192.168.22.1%internaldns1=8.8.4.4%dns1=8.8.8.8 I basically copy/pasted the patch line from the stop/start and used it when rebooting. Now everything works. We need to figure out why it doesn’t patch the system vms on reboot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8933) SSVm and CPVM do not survice a reboot from API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma updated CLOUDSTACK-8933: - Attachment: Console screenshot.png > SSVm and CPVM do not survice a reboot from API > -- > > Key: CLOUDSTACK-8933 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8933 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.6.0 > Environment: KVM Advanced / Basic zone >Reporter: Remi Bergsma >Priority: Blocker > Fix For: 4.6.0 > > Attachments: Console screenshot.png > > > These tests fail: > - integration.smoke.test_ssvm.TestSSVMs.test_07_reboot_ssvm > - integration.smoke.test_ssvm.TestSSVMs.test_08_reboot_cpvm > Stopping works, then CloudStack successfully deploys a new one. Rebooting > doesn’t work as it doesn’t complete the boot sequence. Looking at the > agent.log I noticed the systemvm doesn’t get patched so it is probably > waiting for that to happen. > A successful start shows this: > 2015-10-05 21:26:12,748 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Executing: > /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n > v-1-VM -p > %template=domP%type=consoleproxy%host=192.168.22.61%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.168.23.2%eth2mask=255.255.255.0%gateway=192.168.23.1%eth0ip=169.254.1.20%eth0mask=255.255.0.0%eth1ip=192.168.22.137%eth1mask=255.255.255.0%mgmtcidr=192.168.22.0/24%localgw=192.168.22.1%internaldns1=8.8.4.4%dns1=8.8.8.8 > 2015-10-05 21:26:12,777 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Execution is successful. > The reboot doesn’t do this. When I hit reboot and run this command manually, > it works: > /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n > v-1-VM -p > %template=domP%type=consoleproxy%host=192.168.22.61%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy1%proxy_vm=1%disable_rp_filter=tru%eth2ip=192.168.23.2%eth2mask=255.255.255.0%gateway=192.168.23.1%eth0ip=169.254.1.20%eth0mask=255.255.0.0%eth1ip=192.168.22.137%eth1mask=255.255.255.0%mgmtcidr=192.168.22.0/24%localgw=192.168.22.1%internaldns1=8.8.4.4%dns1=8.8.8.8 > I basically copy/pasted the patch line from the stop/start and used it when > rebooting. Now everything works. > We need to figure out why it doesn’t patch the system vms on reboot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
