Re: ACS 4.11 Domain router placeholder record.

[Daan Hoogland]

Glenn, this sounds like it is related to a bug that was just fixed;
https://github.com/apache/cloudstack/pull/2653
Did you do a AddNicToVMCmd manually or was it a consequential action as a
result?
When saying it is related I do not think it is the same.

On Mon, May 21, 2018 at 6:21 AM, Glen Baars 
wrote:

> Hello Devs,
>
> I was just chasing down as issue with not being able to add a NIC to a VM.
> Below is the relevant logs. I found that the NICs table's domain router
> placeholder for this network had a NULL MAC address and this was preventing
> new NICs from being added. When I added a MAC manually to the domain
> routers placeholder record all started working.
>
> My question is, should the router router's placeholder NIC entry have a
> MAC address? If so, none of mine do.
> Not all of my networks have placeholder entries, why is that?
> Should I be removing the placeholder entries?
>
> This seems to be almost the last issue we are facing from 4.3 -> 4.11
> upgrade. It has been very successful. ( 400 ish vms, 6 Datacenters, 80 VRs )
>
>
> 2018-05-21 11:48:16,423 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (qtp1401132667-595:ctx-310c59ef ctx-f99ddc35) (logid:51491bb7) submit
> async job-83360, details: AsyncJobVO {id:83360, userId: 98, accountId: 95,
> instanceType: None, instanceId: null, cmd: 
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd,
> cmdInfo: {"virtualmachineid":"22fbba97-2bee-42f9-80db-4bcbaa0ba1fc","
> response":"json","ctxUserId":"98","httpmethod":"GET","
> networkid":"a3e01c87-042a-44c5-870d-8676143940ee","
> ctxStartEventId":"2191577","ctxDetails":"{\"interface
> com.cloud.vm.VirtualMachine\":\"22fbba97-2bee-42f9-80db-4bcbaa0ba1fc\",\"interface
> com.cloud.network.Network\":\"a3e01c87-042a-44c5-870d-8676143940ee\"}","
> ctxAccountId":"95","cmdEventType":"NIC.CREATE","_":"1526874496277"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 52242469890, completeMsid: null, lastUpdated: null,
> lastPolled: null,
> created: null}
>
>
> 2018-05-21 11:48:16,424 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-1:ctx-dcdc8f3a job-83360) (logid:5254cc87) Executing
> AsyncJobVO {id:83360, userId: 98, accountId: 95, instanceType: None,
> instanceId: null, cmd: 
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd,
> cmdInfo: {"virtualmachineid":"22fbba97-2bee-42f9-80db-4bcbaa0ba1fc","
> response":"json","ctxUserId":"98","httpmethod":"GET","
> networkid":"a3e01c87-042a-44c5-870d-8676143940ee","
> ctxStartEventId":"2191577","ctxDetails":"{\"interface
> com.cloud.vm.VirtualMachine\":\"22fbba97-2bee-42f9-80db-4bcbaa0ba1fc\",\"interface
> com.cloud.network.Network\":\"a3e01c87-042a-44c5-870d-8676143940ee\"}","
> ctxAccountId":"95","cmdEventType":"NIC.CREATE","_":"1526874496277"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 52242469890, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2018-05-21 11:48:16,424 DEBUG [c.c.a.ApiServlet] 
> (qtp1401132667-595:ctx-310c59ef
> ctx-f99ddc35) (logid:51491bb7) ===END===  103.4.132.4 -- GET  command=
> addNicToVirtualMachine&response=json&virtualmachineid=22fbba97-
> 2bee-42f9-80db-4bcbaa0ba1fc&networkid=a3e01c87-042a-44c5-
> 870d-8676143940ee&_=1526874496277
>
>
> 2018-05-21 11:48:16,474 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-1:ctx-dcdc8f3a job-83360) (logid:5254cc87) Unexpected
> exception while executing org.apache.cloudstack.api.
> command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: A NIC with this MAC
> address exists for network: a3e01c87-042a-44c5-870d-8676143940ee
> at com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(
> UserVmManagerImpl.java:1203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.springframework.aop.support.AopUtils.
> invokeJoinpointUsingReflection(AopUtils.java:338)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:197)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:163)
> at org.apache.cloudstack.network.contrail.management.
> EventUtils$EventInterceptor.invoke(EventUtils.java:107)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:174)
> at com.cloud.event.ActionEventInterceptor.invoke(
> ActionEventInterceptor.java:51)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:174)
> at org.springframework.aop.interceptor.
> ExposeInvocationIntercept

build/replace.properties

[Daan Hoogland]

Anyone knows any reason we have this file called build/replace.properties
(still)? It is reported to be in the .gitignore file, yet it has a history
in git.

-- 
Daan

Re: build/replace.properties

[Rohit Yadav]

Daan - the replace.properties is used to replace @VAR@ like params in various 
config files by maven, a different properties file is used by packaging deb/rpm 
scripts.


- Rohit






From: Daan Hoogland 
Sent: Tuesday, May 22, 2018 2:56:34 PM
To: dev
Subject: build/replace.properties

Anyone knows any reason we have this file called build/replace.properties
(still)? It is reported to be in the .gitignore file, yet it has a history
in git.

--
Daan

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: build/replace.properties

[Daan Hoogland]

ok, so it should be removed from .gitignore than


On Tue, May 22, 2018 at 1:00 PM, Rohit Yadav 
wrote:

> Daan - the replace.properties is used to replace @VAR@ like params in
> various config files by maven, a different properties file is used by
> packaging deb/rpm scripts.
>
>
> - Rohit
>
> 
>
>
>
> 
> From: Daan Hoogland 
> Sent: Tuesday, May 22, 2018 2:56:34 PM
> To: dev
> Subject: build/replace.properties
>
> Anyone knows any reason we have this file called build/replace.properties
> (still)? It is reported to be in the .gitignore file, yet it has a history
> in git.
>
> --
> Daan
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>


-- 
Daan

RE: ACS 4.11 Domain router placeholder record.

[Glen Baars]

Hello Daan,

It seems that they are getting a similar result but from a different cause.

Is a network suppose to have a placeholder record?

Kind regards,
Glen Baars
-Original Message-
From: Daan Hoogland 
Sent: Tuesday, 22 May 2018 3:02 PM
To: dev 
Subject: Re: ACS 4.11 Domain router placeholder record.

Glenn, this sounds like it is related to a bug that was just fixed;
https://github.com/apache/cloudstack/pull/2653
Did you do a AddNicToVMCmd manually or was it a consequential action as a 
result?
When saying it is related I do not think it is the same.

On Mon, May 21, 2018 at 6:21 AM, Glen Baars 
wrote:

> Hello Devs,
>
> I was just chasing down as issue with not being able to add a NIC to a VM.
> Below is the relevant logs. I found that the NICs table's domain
> router placeholder for this network had a NULL MAC address and this
> was preventing new NICs from being added. When I added a MAC manually
> to the domain routers placeholder record all started working.
>
> My question is, should the router router's placeholder NIC entry have
> a MAC address? If so, none of mine do.
> Not all of my networks have placeholder entries, why is that?
> Should I be removing the placeholder entries?
>
> This seems to be almost the last issue we are facing from 4.3 -> 4.11
> upgrade. It has been very successful. ( 400 ish vms, 6 Datacenters, 80
> VRs )
>
>
> 2018-05-21 11:48:16,423 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (qtp1401132667-595:ctx-310c59ef ctx-f99ddc35) (logid:51491bb7) submit
> async job-83360, details: AsyncJobVO {id:83360, userId: 98, accountId:
> 95,
> instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd,
> cmdInfo: {"virtualmachineid":"22fbba97-2bee-42f9-80db-4bcbaa0ba1fc","
> response":"json","ctxUserId":"98","httpmethod":"GET","
> networkid":"a3e01c87-042a-44c5-870d-8676143940ee","
> ctxStartEventId":"2191577","ctxDetails":"{\"interface
> com.cloud.vm.VirtualMachine\":\"22fbba97-2bee-42f9-80db-4bcbaa0ba1fc\"
> ,\"interface
> com.cloud.network.Network\":\"a3e01c87-042a-44c5-870d-8676143940ee\"}","
> ctxAccountId":"95","cmdEventType":"NIC.CREATE","_":"1526874496277"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 52242469890, completeMsid: null, lastUpdated:
> null,
> lastPolled: null,
> created: null}
>
>
> 2018-05-21 11:48:16,424 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-1:ctx-dcdc8f3a job-83360) (logid:5254cc87) Executing
> AsyncJobVO {id:83360, userId: 98, accountId: 95, instanceType: None,
> instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd,
> cmdInfo: {"virtualmachineid":"22fbba97-2bee-42f9-80db-4bcbaa0ba1fc","
> response":"json","ctxUserId":"98","httpmethod":"GET","
> networkid":"a3e01c87-042a-44c5-870d-8676143940ee","
> ctxStartEventId":"2191577","ctxDetails":"{\"interface
> com.cloud.vm.VirtualMachine\":\"22fbba97-2bee-42f9-80db-4bcbaa0ba1fc\"
> ,\"interface
> com.cloud.network.Network\":\"a3e01c87-042a-44c5-870d-8676143940ee\"}","
> ctxAccountId":"95","cmdEventType":"NIC.CREATE","_":"1526874496277"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 52242469890, completeMsid: null, lastUpdated:
> null,
> lastPolled: null, created: null}
> 2018-05-21 11:48:16,424 DEBUG [c.c.a.ApiServlet]
> (qtp1401132667-595:ctx-310c59ef
> ctx-f99ddc35) (logid:51491bb7) ===END===  103.4.132.4 -- GET  command=
> addNicToVirtualMachine&response=json&virtualmachineid=22fbba97-
> 2bee-42f9-80db-4bcbaa0ba1fc&networkid=a3e01c87-042a-44c5-
> 870d-8676143940ee&_=1526874496277
>
>
> 2018-05-21 11:48:16,474 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-1:ctx-dcdc8f3a job-83360) (logid:5254cc87)
> Unexpected exception while executing org.apache.cloudstack.api.
> command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: A NIC with this MAC
> address exists for network: a3e01c87-042a-44c5-870d-8676143940ee
> at com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(
> UserVmManagerImpl.java:1203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.springframework.aop.support.AopUtils.
> invokeJoinpointUsingReflection(AopUtils.java:338)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:197)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:163)
> at org.apache.cloudstack.network.contrail.management.
> EventUtils$EventInterceptor.invoke(EventUtils.java:107)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(Re

Resource recalculation task warnings

[Nicolas Vazquez]

Hi guys,


I'm seeing these warnings in current master, are you experiencing it too or is 
it just my environment?


INFO  [c.c.r.ResourceLimitManagerImpl] (ResourceCountChecker-1:ctx-f538212d) 
(logid:34c33b65) Started resource counters recalculation periodic task.
WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d) 
(logid:34c33b65) txn: Commit called when it is not a transaction: 
-Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.recalculateAccountResourceCount:872-ResourceLimitManagerImpl$ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:49-DefaultManagedContext$1.call:56-DefaultManagedContext.callWithContext:103-DefaultManagedContext.runWithContext:53-ManagedContextRunnable.run:46-Executors$RunnableAdapter.call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301:180
WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d) 
(logid:34c33b65) txn: Commit called when it is not a transaction: 
-Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.recalculateAccountResourceCount:872-ResourceLimitManagerImpl$ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:49-DefaultManagedContext$1.call:56-DefaultManagedContext.callWithContext:103-DefaultManagedContext.runWithContext:53-ManagedContextRunnable.run:46-Executors$RunnableAdapter.call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301:180
WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d) 
(logid:34c33b65) txn: Commit called when it is not a transaction: 
-Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.recalculateAccountResourceCount:872-ResourceLimitManagerImpl$ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:49-DefaultManagedContext$1.call:56-DefaultManagedContext.callWithContext:103-DefaultManagedContext.runWithContext:53-ManagedContextRunnable.run:46-Executors$RunnableAdapter.call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301:180
WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d) 
(logid:34c33b65) txn: Commit called when it is not a transaction: 
-Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.recalculateAccountResourceCount:872-ResourceLimitManagerImpl$ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:49-DefaultManagedContext$1.call:56-DefaultManagedContext.callWithContext:103-DefaultManagedContext.runWithContext:53-ManagedContextRunnable.run:46-Executors$RunnableAdapter.call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301:180
WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d) 
(logid:34c33b65) txn: Commit called when it is not a transaction: 
-Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.recalculateAccountResourceCount:872-ResourceLimitManagerImpl$ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:49-DefaultManagedContext$1.call:56-DefaultManagedContext.callWithContext:103-DefaultManagedContext.runWithContext:53-ManagedContextRunnable.run:46-Executors$RunnableAdapter.call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301:180
WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d) 
(logid:34c33b65) txn: Commit called when it is not a transaction: 
-Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.recalculateAccountResourceCount:872-ResourceLimitManagerImpl$ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:49-DefaultManagedContext$1.call:56-DefaultManagedContext.callWithContext:103-DefaultManagedContext.runWithContext:53-ManagedContextRunnable.run:46-Executors$RunnableAdapter.call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301:180


Regards,

Nicolas Vazquez

nicolas.vazq...@shapeblue.com 
www.shapeblue.com
,   
@shapeblue
  
 

4.11.1 install feedback

[Rene Moser]

Hi

I ran the update from 4.9.3 to 4.11.1 (rohit lab) and got into the issue
where I can still not login with admin after upgrade. I immediately get
a "session expired" in the UI. I remember an issue related to roles but
can not find the "workaround" and thought it were fixed for 4.11.1.

Any help is appreciated.

René

Re: 4.11.1 install feedback

[Rene Moser]

appending some logs

2018-05-22 17:45:49,929 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-11:ctx-0a395356) (logid:33635259) ===START===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003949904
2018-05-22 17:45:49,932 DEBUG [c.c.a.ApiServer]
(qtp1386767190-11:ctx-0a395356 ctx-7a746d15) (logid:33635259) CIDRs from
which account 'Acct[2-admin]' is allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:49,937 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-11:ctx-0a395356 ctx-7a746d15) (logid:33635259) ===END===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003949904
2018-05-22 17:45:50,025 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-16:ctx-8f4234ef) (logid:53421488) ===START===
10.184.2.226 -- GET  command=cloudianIsEnabled&response=json&_=1527003949976
2018-05-22 17:45:50,028 DEBUG [c.c.a.ApiServer]
(qtp1386767190-16:ctx-8f4234ef ctx-1c7598cc) (logid:53421488) CIDRs from
which account 'Acct[2-admin]' is allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:50,032 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-16:ctx-8f4234ef ctx-1c7598cc) (logid:53421488) ===END===
10.184.2.226 -- GET  command=cloudianIsEnabled&response=json&_=1527003949976
2018-05-22 17:45:50,093 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-17:ctx-16bff054) (logid:1abefa91) ===START===
10.184.2.226 -- GET  command=quotaIsEnabled&response=json&_=1527003950074
2018-05-22 17:45:50,097 DEBUG [c.c.a.ApiServer]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) CIDRs from
which account 'Acct[2-admin]' is allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:50,098 DEBUG [c.c.a.ApiServer]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) The given
command 'quotaIsEnabled' either does not exist, is not available for
user, or not available from ip address '/10.184.2.226'.
2018-05-22 17:45:50,098 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) ===END===
10.184.2.226 -- GET  command=quotaIsEnabled&response=json&_=1527003950074
2018-05-22 17:45:50,232 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-20:ctx-5a7f0d91) (logid:9a3f5b56) ===START===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003950156
2018-05-22 17:45:50,232 DEBUG [c.c.a.ApiServer]
(qtp1386767190-20:ctx-5a7f0d91 ctx-382a670b) (logid:9a3f5b56) Expired
session, missing signature, or missing apiKey -- ignoring request.
Signature: null, apiKey: null


On 05/22/2018 05:39 PM, Rene Moser wrote:
> Hi
> 
> I ran the update from 4.9.3 to 4.11.1 (rohit lab) and got into the issue
> where I can still not login with admin after upgrade. I immediately get
> a "session expired" in the UI. I remember an issue related to roles but
> can not find the "workaround" and thought it were fixed for 4.11.1.
> 
> Any help is appreciated.
> 
> René
> 

Re: Resource recalculation task warnings

[Suresh Kumar Anaparti]

Hi Nicolas,

I could see these warnings in my environment as well, with the master build.

-Suresh

On Tue, May 22, 2018 at 8:44 PM, Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:

> Hi guys,
>
>
> I'm seeing these warnings in current master, are you experiencing it too
> or is it just my environment?
>
>
> INFO  [c.c.r.ResourceLimitManagerImpl] (ResourceCountChecker-1:ctx-f538212d)
> (logid:34c33b65) Started resource counters recalculation periodic task.
> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
> (logid:34c33b65) txn: Commit called when it is not a transaction:
> -Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.
> recalculateAccountResourceCount:872-ResourceLimitManagerImpl$
> ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:
> 49-DefaultManagedContext$1.call:56-DefaultManagedContext.
> callWithContext:103-DefaultManagedContext.runWithContext:53-
> ManagedContextRunnable.run:46-Executors$RunnableAdapter.
> call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301:180
> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
> (logid:34c33b65) txn: Commit called when it is not a transaction:
> -Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.
> recalculateAccountResourceCount:872-ResourceLimitManagerImpl$
> ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:
> 49-DefaultManagedContext$1.call:56-DefaultManagedContext.
> callWithContext:103-DefaultManagedContext.runWithContext:53-
> ManagedContextRunnable.run:46-Executors$RunnableAdapter.
> call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301:180
> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
> (logid:34c33b65) txn: Commit called when it is not a transaction:
> -Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.
> recalculateAccountResourceCount:872-ResourceLimitManagerImpl$
> ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:
> 49-DefaultManagedContext$1.call:56-DefaultManagedContext.
> callWithContext:103-DefaultManagedContext.runWithContext:53-
> ManagedContextRunnable.run:46-Executors$RunnableAdapter.
> call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301:180
> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
> (logid:34c33b65) txn: Commit called when it is not a transaction:
> -Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.
> recalculateAccountResourceCount:872-ResourceLimitManagerImpl$
> ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:
> 49-DefaultManagedContext$1.call:56-DefaultManagedContext.
> callWithContext:103-DefaultManagedContext.runWithContext:53-
> ManagedContextRunnable.run:46-Executors$RunnableAdapter.
> call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301:180
> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
> (logid:34c33b65) txn: Commit called when it is not a transaction:
> -Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.
> recalculateAccountResourceCount:872-ResourceLimitManagerImpl$
> ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:
> 49-DefaultManagedContext$1.call:56-DefaultManagedContext.
> callWithContext:103-DefaultManagedContext.runWithContext:53-
> ManagedContextRunnable.run:46-Executors$RunnableAdapter.
> call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301:180
> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
> (logid:34c33b65) txn: Commit called when it is not a transaction:
> -Transaction.execute:41-Transaction.execute:47-ResourceLimitManagerImpl.
> recalculateAccountResourceCount:872-ResourceLimitManagerImpl$
> ResourceCountCheckTask.runInContext:1065-ManagedContextRunnable$1.run:
> 49-DefaultManagedContext$1.call:56-DefaultManagedContext.
> callWithContext:103-DefaultManagedContext.runWithContext:53-
> ManagedContextRunnable.run:46-Executors$RunnableAdapter.
> call:511-FutureTask.runAndReset:308-ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301:180
>
>
> Regards,
>
> Nicolas Vazquez
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>

RE: 4.11.1 install feedback

[Paul Angus]

Had you 'upgraded' to dynamic roles in your 4.9 environment Rene?

Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Rene Moser  
Sent: 22 May 2018 16:48
To: dev@cloudstack.apache.org
Subject: Re: 4.11.1 install feedback

appending some logs

2018-05-22 17:45:49,929 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-11:ctx-0a395356) (logid:33635259) ===START===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003949904
2018-05-22 17:45:49,932 DEBUG [c.c.a.ApiServer]
(qtp1386767190-11:ctx-0a395356 ctx-7a746d15) (logid:33635259) CIDRs from which 
account 'Acct[2-admin]' is allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:49,937 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-11:ctx-0a395356 ctx-7a746d15) (logid:33635259) ===END===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003949904
2018-05-22 17:45:50,025 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-16:ctx-8f4234ef) (logid:53421488) ===START===
10.184.2.226 -- GET  command=cloudianIsEnabled&response=json&_=1527003949976
2018-05-22 17:45:50,028 DEBUG [c.c.a.ApiServer] (qtp1386767190-16:ctx-8f4234ef 
ctx-1c7598cc) (logid:53421488) CIDRs from which account 'Acct[2-admin]' is 
allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:50,032 DEBUG [c.c.a.ApiServlet] (qtp1386767190-16:ctx-8f4234ef 
ctx-1c7598cc) (logid:53421488) ===END===
10.184.2.226 -- GET  command=cloudianIsEnabled&response=json&_=1527003949976
2018-05-22 17:45:50,093 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-17:ctx-16bff054) (logid:1abefa91) ===START===
10.184.2.226 -- GET  command=quotaIsEnabled&response=json&_=1527003950074
2018-05-22 17:45:50,097 DEBUG [c.c.a.ApiServer]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) CIDRs from which 
account 'Acct[2-admin]' is allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:50,098 DEBUG [c.c.a.ApiServer]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) The given command 
'quotaIsEnabled' either does not exist, is not available for user, or not 
available from ip address '/10.184.2.226'.
2018-05-22 17:45:50,098 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) ===END===
10.184.2.226 -- GET  command=quotaIsEnabled&response=json&_=1527003950074
2018-05-22 17:45:50,232 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-20:ctx-5a7f0d91) (logid:9a3f5b56) ===START===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003950156
2018-05-22 17:45:50,232 DEBUG [c.c.a.ApiServer]
(qtp1386767190-20:ctx-5a7f0d91 ctx-382a670b) (logid:9a3f5b56) Expired session, 
missing signature, or missing apiKey -- ignoring request.
Signature: null, apiKey: null


On 05/22/2018 05:39 PM, Rene Moser wrote:
> Hi
> 
> I ran the update from 4.9.3 to 4.11.1 (rohit lab) and got into the 
> issue where I can still not login with admin after upgrade. I 
> immediately get a "session expired" in the UI. I remember an issue 
> related to roles but can not find the "workaround" and thought it were fixed 
> for 4.11.1.
> 
> Any help is appreciated.
> 
> René
> 

Re: Resource recalculation task warnings

[Suresh Kumar Anaparti]

Nicolas,

Forgot to add that I observed these logs for Snapshot scheduler.

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97


-Suresh

On Tue, May 22, 2018 at 9:32 PM, Suresh Kumar Anaparti <
sureshkumar.anapa...@gmail.com> wrote:

> Hi Nicolas,
>
> I could see these warnings in my environment as well, with the master
> build.
>
> -Suresh
>
> On Tue, May 22, 2018 at 8:44 PM, Nicolas Vazquez <
> nicolas.vazq...@shapeblue.com> wrote:
>
>> Hi guys,
>>
>>
>> I'm seeing these warnings in current master, are you experiencing it too
>> or is it just my environment?
>>
>>
>> INFO  [c.c.r.ResourceLimitManagerImpl] (ResourceCountChecker-1:ctx-f538212d)
>> (logid:34c33b65) Started resource counters recalculation periodic task.
>> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
>> (logid:34c33b65) txn: Commit called when it is not a transaction:
>> -Transaction.execute:41-Transaction.execute:47-ResourceLimit
>> ManagerImpl.recalculateAccountResourceCount:872-ResourceLimi
>> tManagerImpl$ResourceCountCheckTask.runInContext:1065-Manage
>> dContextRunnable$1.run:49-DefaultManagedContext$1.call:
>> 56-DefaultManagedContext.callWithContext:103-DefaultManagedC
>> ontext.runWithContext:53-ManagedContextRunnable.run:46-Execu
>> tors$RunnableAdapter.call:511-FutureTask.runAndReset:308-Sch
>> eduledThreadPoolExecutor$ScheduledFutureTask.access$301:180
>> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
>> (logid:34c33b65) txn: Commit cal

Re: 4.11.1 install feedback

[Dag Sonstebo]

Rene – did you set dynamic.apichecker.enabled to true?

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 22/05/2018, 16:48, "Rene Moser"  wrote:

appending some logs

2018-05-22 17:45:49,929 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-11:ctx-0a395356) (logid:33635259) ===START===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003949904
2018-05-22 17:45:49,932 DEBUG [c.c.a.ApiServer]
(qtp1386767190-11:ctx-0a395356 ctx-7a746d15) (logid:33635259) CIDRs from
which account 'Acct[2-admin]' is allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:49,937 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-11:ctx-0a395356 ctx-7a746d15) (logid:33635259) ===END===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003949904
2018-05-22 17:45:50,025 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-16:ctx-8f4234ef) (logid:53421488) ===START===
10.184.2.226 -- GET  command=cloudianIsEnabled&response=json&_=1527003949976
2018-05-22 17:45:50,028 DEBUG [c.c.a.ApiServer]
(qtp1386767190-16:ctx-8f4234ef ctx-1c7598cc) (logid:53421488) CIDRs from
which account 'Acct[2-admin]' is allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:50,032 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-16:ctx-8f4234ef ctx-1c7598cc) (logid:53421488) ===END===
10.184.2.226 -- GET  command=cloudianIsEnabled&response=json&_=1527003949976
2018-05-22 17:45:50,093 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-17:ctx-16bff054) (logid:1abefa91) ===START===
10.184.2.226 -- GET  command=quotaIsEnabled&response=json&_=1527003950074
2018-05-22 17:45:50,097 DEBUG [c.c.a.ApiServer]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) CIDRs from
which account 'Acct[2-admin]' is allowed to perform API calls:
0.0.0.0/0,::/0
2018-05-22 17:45:50,098 DEBUG [c.c.a.ApiServer]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) The given
command 'quotaIsEnabled' either does not exist, is not available for
user, or not available from ip address '/10.184.2.226'.
2018-05-22 17:45:50,098 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-17:ctx-16bff054 ctx-b0e8c230) (logid:1abefa91) ===END===
10.184.2.226 -- GET  command=quotaIsEnabled&response=json&_=1527003950074
2018-05-22 17:45:50,232 DEBUG [c.c.a.ApiServlet]
(qtp1386767190-20:ctx-5a7f0d91) (logid:9a3f5b56) ===START===
10.184.2.226 -- GET  command=listZones&response=json&_=1527003950156
2018-05-22 17:45:50,232 DEBUG [c.c.a.ApiServer]
(qtp1386767190-20:ctx-5a7f0d91 ctx-382a670b) (logid:9a3f5b56) Expired
session, missing signature, or missing apiKey -- ignoring request.
Signature: null, apiKey: null


On 05/22/2018 05:39 PM, Rene Moser wrote:
> Hi
> 
> I ran the update from 4.9.3 to 4.11.1 (rohit lab) and got into the issue
> where I can still not login with admin after upgrade. I immediately get
> a "session expired" in the UI. I remember an issue related to roles but
> can not find the "workaround" and thought it were fixed for 4.11.1.
> 
> Any help is appreciated.
> 
> René
> 



dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: 4.11.1 install feedback

[Rene Moser]

On 05/22/2018 06:08 PM, Paul Angus wrote:
> Had you 'upgraded' to dynamic roles in your 4.9 environment Rene?

right, it was for 4.9. Yes, did that.

the "session expired" issue seems only related to UI. api keys still work.

Re: Resource recalculation task warnings

[Nicolas Vazquez]

Thanks Suresh. I'll try to investigate the issue and come with a fix.


Regards,

Nicolas Vazquez


From: Suresh Kumar Anaparti 
Sent: Tuesday, May 22, 2018 1:08:36 PM
To: dev
Subject: Re: Resource recalculation task warnings

Nicolas,

Forgot to add that I observed these logs for Snapshot scheduler.

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97

WARN  [c.c.u.d.T.Transaction:709] (main:null) (logid:) txn: Commit called
when it is not a transaction:
-SnapshotSchedulerImpl.scheduleNextSnapshotJob:345-SnapshotSchedulerImpl.start:415-CloudStackExtendedLifeCycle$1.with:75-CloudStackExtendedLifeCycle.with:154-CloudStackExtendedLifeCycle.startBeans:72-CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.with:105-DefaultModuleDefinitionSet.withModule:245-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:250-DefaultModuleDefinitionSet.withModule:233-DefaultModuleDefinitionSet.startContexts:97


-Suresh

On Tue, May 22, 2018 at 9:32 PM, Suresh Kumar Anaparti <
sureshkumar.anapa...@gmail.com> wrote:

> Hi Nicolas,
>
> I could see these warnings in my environment as well, with the master
> build.
>
> -Suresh
>
> On Tue, May 22, 2018 at 8:44 PM, Nicolas Vazquez <
> nicolas.vazq...@shapeblue.com> wrote:
>
>> Hi guys,
>>
>>
>> I'm seeing these warnings in current master, are you experiencing it too
>> or is it just my environment?
>>
>>
>> INFO  [c.c.r.ResourceLimitManagerImpl] (ResourceCountChecker-1:ctx-f538212d)
>> (logid:34c33b65) Started resource counters recalculation periodic task.
>> WARN  [c.c.u.d.T.Transaction] (ResourceCountChecker-1:ctx-f538212d)
>> (logid:34c33b65) txn: Commit called when it is not a transaction:
>> -Transaction.execute:41-Transaction.execute:47-ResourceLimit
>> ManagerImpl.recalculateAccountResourceCount:872-ResourceLimi
>> tManagerImpl$ResourceCountCheckTask.runInContext:1065-Manage
>> dContextRunnable$1.run:49-DefaultManagedContext$1.call:
>> 56-DefaultManagedContext.callWithContext:103-DefaultManagedC
>> ontext.runWithContext:53-ManagedCon

Re: 4.11.1 install feedback

[Dag Sonstebo]

You may want to try a update cloud.configuration set value='true' where 
name='dynamic.apichecker.enabled' and see if that lets you login.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 22/05/2018, 17:25, "Rene Moser"  wrote:

On 05/22/2018 06:08 PM, Dag Sonstebo wrote:
> Rene – did you set dynamic.apichecker.enabled to true?

I checked, it is false.








dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Can't build master

[Tutkowski, Mike]

Hi Rohit,

I’ve tried a few things so far, but none seem to install genisoimage in 
/usr/bin as the test indicates is required.

From 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+Up+a+CloudStack+Development+Environment+on+Mac+OS+X,
 I’ve tried these steps:

• sudo port install cdrtools; or using brew: brew install cdrtools (could take 
a long time)
'brew install cdrtools' did not work for me on OSX 10.9.  However, 'brew 
install dvdrtools' did work for me...
• NOTE - If after the above steps, for any reason, mkisofs is still not 
installed, download it from the net. One good link to get mkisofs for mac is - 
http://www.helios.de/viewart.html?id=1000-en#download . Follow the instructions 
in the section "Download HELIOS “mkisofs” tested binary versions". Use the 
macosx86 binary if you're running mac os x on an intel platform. After 
downloading the mkisofs binary, copy it over to /usr/local/bin/.

I only use Mac OS X to build the code locally. I don’t actually run the 
management server from this machine (I run it on Ubuntu).

For the time being at least, I can just use –DskipTests=true when building on 
Mac OS X.

Talk to you later,
Mike

On 5/22/18, 12:19 AM, "Rohit Yadav"  wrote:

Hi Mike,


Is genisoimage or mkisofs available on osx? This is usually installed at 
/usr/bin/ on CentOS6/CentOS7/Ubuntu Linux. Can you try brew or something else 
to install it?

They are also used by injectkeys.sh/.py when the management server starts. 
The change is part of a recent PR I did and added a unit test for it where it 
tries to build a config drive ISO file. If genisoimage is not availabe on OSX, 
we can add some environment check to the unit test to skip on non-Linux 
environments.


- Rohit






From: Tutkowski, Mike 
Sent: Tuesday, May 22, 2018 2:13:23 AM
To: dev@cloudstack.apache.org
Subject: Re: Can't build master

Just an FYI that this is on OS X Version 10.11.6.

From: "Tutkowski, Mike" 
Date: Monday, May 21, 2018 at 2:42 PM
To: "dev@cloudstack.apache.org" 
Subject: Can't build master

Hi,

Did I miss an e-mail or something? I’m having trouble building master 
(below).

Thanks!
Mike

Running org.apache.cloudstack.storage.configdrive.ConfigDriveBuilderTest
log4j:WARN No appenders could be found for logger 
(org.apache.cloudstack.storage.configdrive.ConfigDriveBuilder).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for 
more info.
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.296 sec 
<<< FAILURE! - in 
org.apache.cloudstack.storage.configdrive.ConfigDriveBuilderTest

testConfigDriveBuild(org.apache.cloudstack.storage.configdrive.ConfigDriveBuilderTest)
  Time elapsed: 0.278 sec  <<< ERROR!
com.cloud.utils.exception.CloudRuntimeException: Unable to create iso file: 
i-x-y.iso due to java.io.IOException: Cannot run program 
"/usr/bin/genisoimage": error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at com.cloud.utils.script.Script.execute(Script.java:215)
at com.cloud.utils.script.Script.execute(Script.java:183)
at 
org.apache.cloudstack.storage.configdrive.ConfigDriveBuilder.buildConfigDrive(ConfigDriveBuilder.java:152)
at 
org.apache.cloudstack.storage.configdrive.ConfigDriveBuilderTest.testConfigDriveBuild(ConfigDriveBuilderTest.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at 
org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at 
org.junit.runners.Pare

Re: Can't build master

[Khosrow Moossavi]

Mike

I have no idea about your issue on OS X but if you only need and care to
build the artifacts,
you can use docker based cloudstack-deb-builder[1] or if you only want to
run maven phases
(test, verify, etc) you can override docker image entrypoint, such as:

docker run  -it ... --entrypoint "/usr/bin/mvn"
khos2ow/cloudstack-deb-builder 

[1]: https://khos2ow.github.io/cloudstack-deb-builder/




On Tue, May 22, 2018 at 2:58 PM Tutkowski, Mike 
wrote:

> Hi Rohit,
>
> I’ve tried a few things so far, but none seem to install genisoimage in
> /usr/bin as the test indicates is required.
>
> From
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+Up+a+CloudStack+Development+Environment+on+Mac+OS+X,
> I’ve tried these steps:
>
> • sudo port install cdrtools; or using brew: brew install cdrtools (could
> take a long time)
> 'brew install cdrtools' did not work for me on OSX 10.9.  However, 'brew
> install dvdrtools' did work for me...
> • NOTE - If after the above steps, for any reason, mkisofs is still not
> installed, download it from the net. One good link to get mkisofs for mac
> is - http://www.helios.de/viewart.html?id=1000-en#download . Follow the
> instructions in the section "Download HELIOS “mkisofs” tested binary
> versions". Use the macosx86 binary if you're running mac os x on an intel
> platform. After downloading the mkisofs binary, copy it over to
> /usr/local/bin/.
>
> I only use Mac OS X to build the code locally. I don’t actually run the
> management server from this machine (I run it on Ubuntu).
>
> For the time being at least, I can just use –DskipTests=true when building
> on Mac OS X.
>
> Talk to you later,
> Mike
>
> On 5/22/18, 12:19 AM, "Rohit Yadav"  wrote:
>
> Hi Mike,
>
>
> Is genisoimage or mkisofs available on osx? This is usually installed
> at /usr/bin/ on CentOS6/CentOS7/Ubuntu Linux. Can you try brew or something
> else to install it?
>
> They are also used by injectkeys.sh/.py when the management server
> starts. The change is part of a recent PR I did and added a unit test for
> it where it tries to build a config drive ISO file. If genisoimage is not
> availabe on OSX, we can add some environment check to the unit test to skip
> on non-Linux environments.
>
>
> - Rohit
>
> 
>
>
>
> 
> From: Tutkowski, Mike 
> Sent: Tuesday, May 22, 2018 2:13:23 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Can't build master
>
> Just an FYI that this is on OS X Version 10.11.6.
>
> From: "Tutkowski, Mike" 
> Date: Monday, May 21, 2018 at 2:42 PM
> To: "dev@cloudstack.apache.org" 
> Subject: Can't build master
>
> Hi,
>
> Did I miss an e-mail or something? I’m having trouble building master
> (below).
>
> Thanks!
> Mike
>
> Running
> org.apache.cloudstack.storage.configdrive.ConfigDriveBuilderTest
> log4j:WARN No appenders could be found for logger
> (org.apache.cloudstack.storage.configdrive.ConfigDriveBuilder).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig
> for more info.
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.296
> sec <<< FAILURE! - in
> org.apache.cloudstack.storage.configdrive.ConfigDriveBuilderTest
>
> testConfigDriveBuild(org.apache.cloudstack.storage.configdrive.ConfigDriveBuilderTest)
> Time elapsed: 0.278 sec  <<< ERROR!
> com.cloud.utils.exception.CloudRuntimeException: Unable to create iso
> file: i-x-y.iso due to java.io.IOException: Cannot run program
> "/usr/bin/genisoimage": error=2, No such file or directory
> at
> java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at
> com.cloud.utils.script.Script.execute(Script.java:215)
> at
> com.cloud.utils.script.Script.execute(Script.java:183)
> at
> org.apache.cloudstack.storage.configdrive.ConfigDriveBuilder.buildConfigDrive(ConfigDriveBuilder.java:152)
> at
> org.apache.cloudstack.storage.configdrive.ConfigDriveBuilderTest.testConfigDriveBuild(ConfigDriveBuilderTest.java:56)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.sta

ISO upload fails on 4.11

[Glen Baars]

Hello Devs,

It seems that cross zone ISO downloads are broken in 4.11. I have had a look at 
the github issues and can't see it listed. Is it fixed in the upcoming 4.11.1?

Also, I see that there is a direct download option for ISO uploads, does this 
make sense? I understand its usage in templates.

2018-05-23 12:39:37,916 DEBUG [c.c.a.ApiServlet] 
(qtp1401132667-554:ctx-cabc63ba) (logid:54b42f92) ===START===  103.4.132.4 -- 
GET  
command=registerIso&response=json&name=(x64)+Centos+7.5&displayText=(x64)+Centos+7.5&url=http%3A%2F%2Ftemplates.here.com%2FCentOS-7-x86_64-Minimal-1804.iso&zoneid=-1&isextractable=false&bootable=true&directdownload=false&osTypeId=4dd2aa12-2fdc-11e8-a2cf-000c29e4d402&ispublic=true&isfeatured=false&_=1527050379358

2018-05-23 12:39:37,962 INFO  [c.c.a.ApiServer] (qtp1401132667-554:ctx-cabc63ba 
ctx-c3c3bbf4) (logid:54b42f92) Please specify a valid zone.

2018-05-23 12:39:37,963 DEBUG [c.c.a.ApiServlet] 
(qtp1401132667-554:ctx-cabc63ba ctx-c3c3bbf4) (logid:54b42f92) ===END===  
103.4.132.4 -- GET  
command=registerIso&response=json&name=(x64)+Centos+7.5&displayText=(x64)+Centos+7.5&url=http%3A%2F%2Ftemplates.
 
here.com%2FCentOS-7-x86_64-Minimal-1804.iso&zoneid=-1&isextractable=false&bootable=true&directdownload=false&osTypeId=4dd2aa12-2fdc-11e8-a2cf-000c29e4d402&ispublic=true&isfeatured=false&_=1527050379358


Kind regards,
Glen Baars
BackOnline Manager

This e-mail is intended solely for the benefit of the addressee(s) and any 
other named recipient. It is confidential and may contain legally privileged or 
confidential information. If you are not the recipient, any use, distribution, 
disclosure or copying of this e-mail is prohibited. The confidentiality and 
legal privilege attached to this communication is not waived or lost by reason 
of the mistaken transmission or delivery to you. If you have received this 
e-mail in error, please notify us immediately.