Missing ;

In the main file the Macros for ESP_ERROR_CHECK(err_code) do not have terminating semicolons
This creates compile issues for me...

Thank you, I've fixed this.

That was amazingly fast, thanks =D


README for Shunting Yard

First attempt at an exhaustive README for Shunting Yard.

Pull Request Test Coverage Report for Build 372

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.632%

Totals

Change from base Build 363:
0.0%

Covered Lines:
736

Relevant Lines:
936

💛  - Coveralls

I definitely wasn't looking for a missing full stop on purpose :)

I think you were 🙈


User from domain can't deploy VM in pod dedicated to that domain

ISSUE TYPE

Bug Report

CLOUDSTACK VERSION
4.16.0

CONFIGURATION
XCP-NG 8.2
Advanced Zone
OS / ENVIRONMENT
Oracle Linux 8.4 - Management server, MYSQL 8.0.26
XCP-NG 8.2 - hypervisor
SUMMARY
User from domain1 can't deploy VM in dedicated to domain1 pod.
STEPS TO REPRODUCE
Create domain. Create user in this domain. Dedicate pod to this domain. Create Compute offering with ImplicitDedicationPlanner with strict policy and choose domain1.

EXPECTED RESULTS
All users from this domain can deploy VMs only in this Pod

ACTUAL RESULTS
User from this domain can't deploy VM in dedicated pod.

Is this new? Did you test in 4.15 @edikevich?
@sureshanaparti is this one good for 4.16.1?

Hi. Sorry for delay. I didn't test this feature in 4.15.2 :( I think problem is near Affinity group which is created after dedicate host/cluster/pod. I tried create VM from root Admin then grand this VM to user from domain but not user or root admin can't start VM in dedicated host/cluster/pod :(

Hey @edikevich do you mean to say that the issue is
Create domain.
Create user in this domain.
Dedicate pod to this domain.
Create Compute offering with ImplicitDedicationPlanner with strict policy and choose domain1.
Add an affinity group ???

now user can't a VM in this domain?

Hi. Not exactly. When pod is dedicated affinity group is created automatically by CS. Other steps are correct.

@edikevich can you add some error logs and preferably a stack trace. I am trying to reproduce this, but haven't succeeded yet. Mostly due to environment build.

Hi. I don't have any errors in log. I see only that no suitable hosts found.

Sorry. Have Error:
2022-01-12 12:42:14,559 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"}Scope=interface com.cloud.dc.DataCenter; id=1
2022-01-12 12:42:14,559 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Unable to create a deployment for VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"}
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"}Scope=interface com.cloud.dc.DataCenter; id=1
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:225)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:202)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:5207)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4693)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4682)
at jdk.internal.reflect.GeneratedMethodAccessor1658.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
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:175)
at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:696)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
2022-01-12 12:42:14,561 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Complete async job-3810, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"533","errortext":"Unable to create a deployment for VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"}"}

This message says that there is no deployment plan suitable, but above this message there should be more info on how this was tried, @edikevich . If you grep for 'job-3810' in the log you should get all the info related to the failure. Can you do that and see if there is more relevant info?
What I am looking for is:
Is the lack of host the capacity problem or something else? (most likely storage then)
Did it even try the dedicated domain? and if so, why did it refuse them?

2022-01-12 12:42:14,354 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:0d4e47c6) Add job-3810 into job monitoring
2022-01-12 12:42:14,358 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (qtp239372207-1931187:ctx-e0fcca0e ctx-b49fa34b) (logid:ccaa1505) submit async job-3810, details: AsyncJobVO {id:3810, userId: 37, accountId: 34, instanceType: VirtualMachine, instanceId: 334, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: {"iptonetworklist[0].networkid":"35d851d4-ccf2-4aaa-a372-5946aa1fd432","boottype":"BIOS","httpmethod":"POST","templateid":"445f7bc5-4d1e-4dff-a171-962adf124733","ctxAccountId":"34","uuid":"88d9976d-0b1a-4c78-a201-b6d153cf0e58","cmdEventType":"VM.CREATE","startvm":"true","bootmode":"LEGACY","serviceofferingid":"29710aa1-50be-472d-b76b-3dbcad42fc1b","response":"json","ctxUserId":"37","displayname":"test-vm1","name":"test-vm1","zoneid":"a5a0c8c3-f4ed-48e9-b3bf-3d645c96d252","ctxStartEventId":"13128","id":"334","ctxDetails":"{"interface com.cloud.offering.ServiceOffering":"29710aa1-50be-472d-b76b-3dbcad42fc1b","interface com.cloud.dc.DataCenter":"a5a0c8c3-f4ed-48e9-b3bf-3d645c96d252","interface com.cloud.template.VirtualMachineTemplate":"445f7bc5-4d1e-4dff-a171-962adf124733","interface com.cloud.vm.VirtualMachine":"88d9976d-0b1a-4c78-a201-b6d153cf0e58"}","affinitygroupids":""}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 172320828, completeMsid: null, lastUpdated: null, lastPolled: null, created: null, removed: null}
2022-01-12 12:42:14,359 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Executing AsyncJobVO {id:3810, userId: 37, accountId: 34, instanceType: VirtualMachine, instanceId: 334, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: {"iptonetworklist[0].networkid":"35d851d4-ccf2-4aaa-a372-5946aa1fd432","boottype":"BIOS","httpmethod":"POST","templateid":"445f7bc5-4d1e-4dff-a171-962adf124733","ctxAccountId":"34","uuid":"88d9976d-0b1a-4c78-a201-b6d153cf0e58","cmdEventType":"VM.CREATE","startvm":"true","bootmode":"LEGACY","serviceofferingid":"29710aa1-50be-472d-b76b-3dbcad42fc1b","response":"json","ctxUserId":"37","displayname":"test-vm1","name":"test-vm1","zoneid":"a5a0c8c3-f4ed-48e9-b3bf-3d645c96d252","ctxStartEventId":"13128","id":"334","ctxDetails":"{"interface com.cloud.offering.ServiceOffering":"29710aa1-50be-472d-b76b-3dbcad42fc1b","interface com.cloud.dc.DataCenter":"a5a0c8c3-f4ed-48e9-b3bf-3d645c96d252","interface com.cloud.template.VirtualMachineTemplate":"445f7bc5-4d1e-4dff-a171-962adf124733","interface com.cloud.vm.VirtualMachine":"88d9976d-0b1a-4c78-a201-b6d153cf0e58"}","affinitygroupids":""}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 172320828, completeMsid: null, lastUpdated: null, lastPolled: null, created: null, removed: null}
2022-01-12 12:42:14,361 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Ignoring paremeter displayvm as the caller is not authorized to pass it in
2022-01-12 12:42:14,361 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Ignoring paremeter deploymentplanner as the caller is not authorized to pass it in
2022-01-12 12:42:14,369 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Access to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} granted to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} by DomainChecker
2022-01-12 12:42:14,374 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Access to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} granted to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} by DomainChecker
2022-01-12 12:42:14,380 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Access to Tmpl[228-VHD-0219c594-238a-4cba-af52-65609364d5f7 granted to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} by DomainChecker
2022-01-12 12:42:14,380 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Ignoring paremeter displayvm as the caller is not authorized to pass it in
2022-01-12 12:42:14,380 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Ignoring paremeter deploymentplanner as the caller is not authorized to pass it in
2022-01-12 12:42:14,394 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Access to VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"} granted to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} by DomainChecker
2022-01-12 12:42:14,412 DEBUG [c.c.n.NetworkModelImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Service SecurityGroup is not supported in the network id=260
2022-01-12 12:42:14,418 DEBUG [c.c.n.NetworkModelImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Service SecurityGroup is not supported in the network id=260
2022-01-12 12:42:14,433 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) DeploymentPlanner allocation algorithm: null
2022-01-12 12:42:14,433 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Trying to allocate a host and storage pools from dc:1, pod:null,cluster:null, requested cpu: 2000, requested ram: (2.00 GB)<PHONE_NUMBER>
2022-01-12 12:42:14,433 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Is ROOT volume READY (pool already allocated)?: No
2022-01-12 12:42:14,441 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Deploy avoids pods: [2], clusters: [], hosts: []
2022-01-12 12:42:14,442 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Searching all possible resources under this Zone: 1
2022-01-12 12:42:14,444 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Listing clusters in order of aggregate capacity, that have (at least one host with) enough CPU and RAM capacity under this Zone: 1
2022-01-12 12:42:14,448 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Removing from the clusterId list these clusters from avoid set: []
2022-01-12 12:42:14,454 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) The clusterId list for the given offering tag: []
2022-01-12 12:42:14,454 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) No clusters found after removing disabled clusters and clusters in avoid list, returning.
2022-01-12 12:42:14,457 DEBUG [c.c.v.UserVmManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Destroying vm VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"} as it failed to create on Host with Id:null
2022-01-12 12:42:14,468 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"} state transited from [Stopped] to [Error] with event [OperationFailedToError]. VM's original host: null, new host: null, host before state transition: null
2022-01-12 12:42:14,492 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Updating resource Type = volume count for Account = 34 Operation = decreasing Amount = 1
2022-01-12 12:42:14,502 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Updating resource Type = primary_storage count for Account = 34 Operation = decreasing Amount = (10.00 GB)<PHONE_NUMBER>0
2022-01-12 12:42:14,517 WARN  [c.c.a.AlertManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) alertType=[8] dataCenterId=[1] podId=[null] clusterId=[null] message=[Failed to deploy Vm with Id: 334, on Host with Id: null].
2022-01-12 12:42:14,523 WARN  [c.c.a.AlertManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) No recipients set in 'alert.email.addresses', skipping sending alert with subject: Failed to deploy Vm with Id: 334, on Host with Id: null and content: Failed to deploy Vm with Id: 334, on Host with Id: null
2022-01-12 12:42:14,525 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Updating resource Type = user_vm count for Account = 34 Operation = decreasing Amount = 1
2022-01-12 12:42:14,535 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Updating resource Type = cpu count for Account = 34 Operation = decreasing Amount = 1
2022-01-12 12:42:14,544 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Updating resource Type = memory count for Account = 34 Operation = decreasing Amount = 2048
2022-01-12 12:42:14,559 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"}Scope=interface com.cloud.dc.DataCenter; id=1
2022-01-12 12:42:14,559 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Unable to create a deployment for VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"}
2022-01-12 12:42:14,561 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Complete async job-3810, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"533","errortext":"Unable to create a deployment for VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"}"}
2022-01-12 12:42:14,562 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Publish async job-3810 complete on message bus
2022-01-12 12:42:14,562 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Wake up jobs related to job-3810
2022-01-12 12:42:14,562 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Update db status for job-3810
2022-01-12 12:42:14,563 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Wake up jobs joined with job-3810 and disjoin all subjobs created from job- 3810
2022-01-12 12:42:14,570 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Done executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-3810
2022-01-12 12:42:14,570 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:7ebaa05f) Remove job-3810 from job monitoring
or you want all log before job start?

no, this is what we need to find the culprit in

@edikevich , Are you expecting the dedicated POD to be automatically choosen? this line says there is no POD chosen:
2022-01-12 12:42:14,433 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Trying to allocate a host and storage pools from dc:1, pod:null,cluster:null, requested cpu: 2000, requested ram: (2.00 GB)<PHONE_NUMBER>

Are there any not-dedicated PODs in your environment? the following line says there are 2 POD that will be avoided.
2022-01-12 12:42:14,441 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Deploy avoids pods: [2], clusters: [], hosts: []

the decision to not deploy is at the cluster level:
2022-01-12 12:42:14,444 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Listing clusters in order of aggregate capacity, that have (at least one host with) enough CPU and RAM capacity under this Zone: 1
2022-01-12 12:42:14,448 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Removing from the clusterId list these clusters from avoid set: []
2022-01-12 12:42:14,454 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) The clusterId list for the given offering tag: []
2022-01-12 12:42:14,454 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) No clusters found after removing disabled clusters and clusters in avoid list, returning.

It looks like there is a tag on the offering that none of the (1) cluster(s) has so there is a mismatch in tags.

I have dedicated pod in my environment

I created offering without tag before and had same result

I have recreated this scenario and the user can deploy a vm in the but the admin cannot. I think there is some extra environmental issue @edikevich .
That picture shows no netmask or gateway, can you add those? In my environment (which is a lab environment) , these have the same values as the main pod in the zone. If you have a real datacentre deployment you'd want to take more care about what you are choosing.

All our pods have different CIDRs. But all out hypervisords can see Management server. When I release dedicated Pod I can deploy VMs in this Pod.

Ok, than I have no clue left @edikevich . I have recreated it with KVM so it might be a Xen(CPng(8.2)) thing, though I doubt that is the case.

Log when Compute Offering don't contains any tags
2022-01-12 17:14:30,364 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:85ae8d9d) Add job-3832 into job monitoring
2022-01-12 17:14:30,368 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (qtp239372207-1939856:ctx-5eab9574 ctx-c6dff037) (logid:c28fe315) submit async job-3832, details: AsyncJobVO {id:3832, userId: 37, accountId: 34, instanceType: VirtualMachine, instanceId: 337, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: {"iptonetworklist[0].networkid":"35d851d4-ccf2-4aaa-a372-5946aa1fd432","boottype":"BIOS","httpmethod":"POST","templateid":"445f7bc5-4d1e-4dff-a171-962adf124733","ctxAccountId":"34","uuid":"0f5625b4-f8f4-4221-9752-d119efd00e6a","cmdEventType":"VM.CREATE","startvm":"true","bootmode":"LEGACY","serviceofferingid":"d5fc1f4e-940e-4b79-ac0a-be61e9792e36","response":"json","ctxUserId":"37","zoneid":"a5a0c8c3-f4ed-48e9-b3bf-3d645c96d252","ctxStartEventId":"13167","id":"337","ctxDetails":"{"interface com.cloud.offering.ServiceOffering":"d5fc1f4e-940e-4b79-ac0a-be61e9792e36","interface com.cloud.dc.DataCenter":"a5a0c8c3-f4ed-48e9-b3bf-3d645c96d252","interface com.cloud.template.VirtualMachineTemplate":"445f7bc5-4d1e-4dff-a171-962adf124733","interface com.cloud.vm.VirtualMachine":"0f5625b4-f8f4-4221-9752-d119efd00e6a"}","affinitygroupids":""}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 172320828, completeMsid: null, lastUpdated: null, lastPolled: null, created: null, removed: null}
2022-01-12 17:14:30,368 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:c0e092ad) Executing AsyncJobVO {id:3832, userId: 37, accountId: 34, instanceType: VirtualMachine, instanceId: 337, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: {"iptonetworklist[0].networkid":"35d851d4-ccf2-4aaa-a372-5946aa1fd432","boottype":"BIOS","httpmethod":"POST","templateid":"445f7bc5-4d1e-4dff-a171-962adf124733","ctxAccountId":"34","uuid":"0f5625b4-f8f4-4221-9752-d119efd00e6a","cmdEventType":"VM.CREATE","startvm":"true","bootmode":"LEGACY","serviceofferingid":"d5fc1f4e-940e-4b79-ac0a-be61e9792e36","response":"json","ctxUserId":"37","zoneid":"a5a0c8c3-f4ed-48e9-b3bf-3d645c96d252","ctxStartEventId":"13167","id":"337","ctxDetails":"{"interface com.cloud.offering.ServiceOffering":"d5fc1f4e-940e-4b79-ac0a-be61e9792e36","interface com.cloud.dc.DataCenter":"a5a0c8c3-f4ed-48e9-b3bf-3d645c96d252","interface com.cloud.template.VirtualMachineTemplate":"445f7bc5-4d1e-4dff-a171-962adf124733","interface com.cloud.vm.VirtualMachine":"0f5625b4-f8f4-4221-9752-d119efd00e6a"}","affinitygroupids":""}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 172320828, completeMsid: null, lastUpdated: null, lastPolled: null, created: null, removed: null}
2022-01-12 17:14:30,371 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Ignoring paremeter displayvm as the caller is not authorized to pass it in
2022-01-12 17:14:30,371 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Ignoring paremeter deploymentplanner as the caller is not authorized to pass it in
2022-01-12 17:14:30,382 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Access to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} granted to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} by DomainChecker
2022-01-12 17:14:30,388 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Access to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} granted to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} by DomainChecker
2022-01-12 17:14:30,393 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Access to Tmpl[228-VHD-0219c594-238a-4cba-af52-65609364d5f7 granted to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} by DomainChecker
2022-01-12 17:14:30,393 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Ignoring paremeter displayvm as the caller is not authorized to pass it in
2022-01-12 17:14:30,393 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Ignoring paremeter deploymentplanner as the caller is not authorized to pass it in
2022-01-12 17:14:30,409 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Access to VM instance {id: "337", name: "i-34-337-VM", uuid: "0f5625b4-f8f4-4221-9752-d119efd00e6a", type="User"} granted to Acct[160ae17c-428d-4486-ac32-18c172a02735-esm] -- Account {"id": 34, "name": "esm", "uuid": "160ae17c-428d-4486-ac32-18c172a02735"} by DomainChecker
2022-01-12 17:14:30,424 DEBUG [c.c.n.NetworkModelImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Service SecurityGroup is not supported in the network id=260
2022-01-12 17:14:30,429 DEBUG [c.c.n.NetworkModelImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Service SecurityGroup is not supported in the network id=260
2022-01-12 17:14:30,442 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) DeploymentPlanner allocation algorithm: null
2022-01-12 17:14:30,442 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Trying to allocate a host and storage pools from dc:1, pod:null,cluster:null, requested cpu: 4000, requested ram: (4.00 GB)<PHONE_NUMBER>
2022-01-12 17:14:30,442 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Is ROOT volume READY (pool already allocated)?: No
2022-01-12 17:14:30,449 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Deploy avoids pods: [2], clusters: [], hosts: []
2022-01-12 17:14:30,450 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Searching all possible resources under this Zone: 1
2022-01-12 17:14:30,451 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Listing clusters in order of aggregate capacity, that have (at least one host with) enough CPU and RAM capacity under this Zone: 1
2022-01-12 17:14:30,455 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Removing from the clusterId list these clusters from avoid set: []
2022-01-12 17:14:30,514 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 1 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,515 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 1 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,520 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 2 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,521 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 2 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,525 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 3 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,526 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 3 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,529 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 4 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,530 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 4 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,534 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 5 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,535 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 5 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,539 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 6 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,540 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 6 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,544 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 7 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,545 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 7 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,548 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 8 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,549 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 8 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,555 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 9 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,556 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 9 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,560 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 10 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,560 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 10 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,564 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 11 found to be unsuitable for implicit dedication as it is running instances of another account
2022-01-12 17:14:30,565 INFO  [c.c.d.ImplicitDedicationPlanner] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Host 11 found to be running a vm created by a planner other than implicit.
2022-01-12 17:14:30,566 DEBUG [c.c.v.UserVmManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Destroying vm VM instance {id: "337", name: "i-34-337-VM", uuid: "0f5625b4-f8f4-4221-9752-d119efd00e6a", type="User"} as it failed to create on Host with Id:null
2022-01-12 17:14:30,576 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) VM instance {id: "337", name: "i-34-337-VM", uuid: "0f5625b4-f8f4-4221-9752-d119efd00e6a", type="User"} state transited from [Stopped] to [Error] with event [OperationFailedToError]. VM's original host: null, new host: null, host before state transition: null
2022-01-12 17:14:30,596 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Updating resource Type = volume count for Account = 34 Operation = decreasing Amount = 1
2022-01-12 17:14:30,604 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Updating resource Type = primary_storage count for Account = 34 Operation = decreasing Amount = (10.00 GB)<PHONE_NUMBER>0
2022-01-12 17:14:30,618 WARN  [c.c.a.AlertManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) alertType=[8] dataCenterId=[1] podId=[null] clusterId=[null] message=[Failed to deploy Vm with Id: 337, on Host with Id: null].
2022-01-12 17:14:30,623 WARN  [c.c.a.AlertManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) No recipients set in 'alert.email.addresses', skipping sending alert with subject: Failed to deploy Vm with Id: 337, on Host with Id: null and content: Failed to deploy Vm with Id: 337, on Host with Id: null
2022-01-12 17:14:30,625 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Updating resource Type = user_vm count for Account = 34 Operation = decreasing Amount = 1
2022-01-12 17:14:30,633 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Updating resource Type = cpu count for Account = 34 Operation = decreasing Amount = 2
2022-01-12 17:14:30,641 DEBUG [c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Updating resource Type = memory count for Account = 34 Operation = decreasing Amount = 4096
2022-01-12 17:14:30,654 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM instance {id: "337", name: "i-34-337-VM", uuid: "0f5625b4-f8f4-4221-9752-d119efd00e6a", type="User"}Scope=interface com.cloud.dc.DataCenter; id=1
2022-01-12 17:14:30,655 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Unable to create a deployment for VM instance {id: "337", name: "i-34-337-VM", uuid: "0f5625b4-f8f4-4221-9752-d119efd00e6a", type="User"}
2022-01-12 17:14:30,656 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:c0e092ad) Complete async job-3832, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"533","errortext":"Unable to create a deployment for VM instance {id: "337", name: "i-34-337-VM", uuid: "0f5625b4-f8f4-4221-9752-d119efd00e6a", type="User"}"}
2022-01-12 17:14:30,657 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:c0e092ad) Publish async job-3832 complete on message bus
2022-01-12 17:14:30,657 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:c0e092ad) Wake up jobs related to job-3832
2022-01-12 17:14:30,657 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:c0e092ad) Update db status for job-3832
2022-01-12 17:14:30,658 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:c0e092ad) Wake up jobs joined with job-3832 and disjoin all subjobs created from job- 3832
2022-01-12 17:14:30,663 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:c0e092ad) Done executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-3832
2022-01-12 17:14:30,663 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:c0e092ad) Remove job-3832 from job monitoring

Can I ask you? When we dedicated Pod something change in host_pod_ref?

Can I ask you? When we dedicated Pod something change in host_pod_ref?

I don't think it does.

Where in DB I can see dedication?

in the above you have
2022-01-12 17:14:30,449 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-24:ctx-3fefa540 job-3832 ctx-befc08f1) (logid:c0e092ad) Deploy avoids pods: [2], clusters: [], hosts: []

which basically means it's going to avoid both your pods I have not discovered why.

why do you want to see it in the DB? (i'd have to query, but what is the use?)

MB I can see some anomaly there:)

ah, in my case it does contain the account id, that might be the culprit

But in one domain we can have many accounts

yes. i'll try that as well

I could still deploy in the pod if it was only dedicated to the domain.

What I should check now? Maybe you need some more logs?

I found the answer and I think it should not work like this:) When user deploys the VM he must select in advanced mode Affinity Group whith this domain! BUT! I think that Compute Offerings with Deployment planner equal ImplicitDedicationPlanner with strict policy must deploy VM in dedicated resources without this affinity group

Hi @edikevich , I'm not sure if I follow. Are you saying this is not an issue?

I don't know:)
If user from domain try do deploy instance with CO with Deployment planner equal ImplicitDedicationPlanner with strict policy and DON'T choose Affinity Group deploy is failed.
If user from domain try do deploy instance with CO with Deployment planner equal FirstFitPlanner and choose Affinity Group deploy is passed.
If user from domain try do deploy instance with CO with Deployment planner equal FirstFitPlanner and DON'T choose Affinity Group deploy is passed.
I think main thing there is "choose Affinity Group". For me, VM with CO with Deployment planner equal ImplicitDedicationPlanner with strict policy shoud deploy on dedicated resources and ignoring Affinity Group (it doesn't matter whether it is chosen or not).

I finally reproduced the issue @edikevich \o/, looking for a fix.

@edikevich I did a deep code dive and think I need to move this to 4.17, if at all we will change this behaviour.
The reason:

What if there are two dedicated PODs or even two dedicated resource pools, maybe even at different levels? This is not something that allows for the implicit choice of an affinity group on an explicitly dedicated resource group. We wouldn't know if both are valid or even if either is valid.
The behaviour of the strict mode is to strictly deploy on the resources that belong to the affinity group and if no one is known no deployment is possible.
These two points combined make your expectations hard to achieve.

Let's think on how to address your need.

One possibility would be in the UI; make sure that the planner is retrieved and it is scanned for the requirement of a dedication, and force the user to pick one.
another one is in the backend, to scan dedicated resources for this user and allow all if none is choosen
a third is to make a default choice.

In any case I am moving this to 4.17, sorry.

HI @DaanHoogland
Can I ask you to look at one thing? Root Admin can't migrate VM between host in dedicated Pod. I think is very useful feature for host maintenance.

@edikevich I don;t understand, please describe in more detail in a new ticket?

@DaanHoogland I think better in this becouse it related to this issue I think.
Dedicate Pod. Pod contains cluster with 3 hosts for example. Root Admin wants to put one host into maintenance mode (hardware or software issue). Root Admin wants migrate all VMs from "broken" host to some specific host.

Root Admin can't migrate VM because VM Migrate Visard is empty.
Root Admin can only place host into maitenance mode

and then VMs migrate to random hosts.
If you want I can create new issue:)

Hi @edikevich @DaanHoogland sorry I tried following up but I'm still not clear - in case there are 2 different issues please create a new ticket for the migration issue. Is the migration issue related to the original issue?

@edikevich I did a deep code dive and think I need to move this to 4.17, if at all we will change this behaviour.
The reason:
1. What if there are two dedicated PODs or even two dedicated resource pools, maybe even at different levels? This is not something that allows for the implicit choice of an affinity group on an explicitly dedicated resource group. We wouldn't know if both are valid or even if either is valid.

2. The behaviour of the strict mode is to strictly deploy on the resources that belong to the affinity group and if no one is known no deployment is possible.
   These two points combined make your expectations hard to achieve.

Let's think on how to address your need.
* One possibility would be in the UI; make sure that the planner is retrieved and it is scanned for the requirement of a dedication, and force the user to pick one.

* another one is in the backend, to scan dedicated resources for this user and allow all if none is choosen

* a third is to make a default choice.

In any case I am moving this to 4.17, sorry.

Just as a quick thought reading through this:
Maybe the whole topic of "dedication" of ressources, at least on host level, could be "solved" with the usage of the tagging feature for this purposes?
Currently we are using this to determine and find suitable hosts for VM-Deployment. Why not concider "ownership" or something similar as another "characteristic" of the host which can be changed on the fly? I guess we would have all the logic for deployment-decisions already in the backend...

@edikevich @Hudratronium with one weeks before code freeze I have no clear idea on what to do on this yet. I will move this to "unplanned". Please let's define the required functionality on this subject clearly.

As far as i understand, @edikevich would expect that if host is stictly dedicated to a specific domain a account within that domain should automatically make use of this ressource without choosing the affinity group during deployment.
I was only suggesting, that it might be usefull to shift from the usage of affinity groups for realization of the whole dedication strictness to the 'tagging' functionalities. Which are quiet flexible to handel.
Without going into to much trouble, the intended behaviour from @edikevich might be achieved without the "dedicattion and strictness" but with tagging and service offerings makeing use of the tags.

@edikevich We are postponing this yet again as requirements are not clear yet. cc @alexandremattioli @rajujith

Hi all! As @Hudratronium sad above I expect that if host/cluster is dedicated to a domain a account within that domain should automatically make use of this host/cluster without choosing the affinity group.

@edikevich does VM deployment using the implicit dedication strict offering succeed when you choose the affinity group?

@rajujith As I correctly remember - yes, VM are deployed in dedicated host/cluster

@edikevich  I believe what you are observing is expected behavior as per the current design. I believe this is your use scenario:
Zone with multiple pods
At least one pod is shared but it is running VMs( all hosts) belonging to other domain/s.
Compute offering uses strict Implicit Dedication.
DeployVirtualMachine API call doesn't have an affinity group
In this scenario, the dedicated pod won't be selected for deployment since the related affinity group is selected subsequently the 'strict Implicit Dedication' avoid the shared pod since it has VMs belonging to other domain/s resulting in no remaining host to deploy in the given zone. To the best of my knowledge, this VM deployment error in this scenario is expected.  You could use the affinity group for VM deployment to avoid this failure. CC @DaanHoogland
Note: My verifications are based on CS v 4.18.

I don't know:) If user from domain try do deploy instance with CO with Deployment planner equal ImplicitDedicationPlanner with strict policy and DON'T choose Affinity Group deploy is failed. If user from domain try do deploy instance with CO with Deployment planner equal FirstFitPlanner and choose Affinity Group deploy is passed. If user from domain try do deploy instance with CO with Deployment planner equal FirstFitPlanner and DON'T choose Affinity Group deploy is passed.
I think main thing there is "choose Affinity Group". For me, VM with CO with Deployment planner equal ImplicitDedicationPlanner with strict policy shoud deploy on dedicated resources and ignoring Affinity Group (it doesn't matter whether it is chosen or not).

As @edikevich wrote above that the problem is not, that he can't deploy anything at all.
From my understanding the problem is, that a user, who wants to deploy a vm needs actively to select the affinity group.
The intention when creating a service offering with:
"Deployment Planner = Implicit dedication & Planner mode = strict"seems to be that when using this service offering it is only deployed on dedicated hosts. everything else shall not be possible.
So why a user of the serviceoffering needs to select the correct affinity group while deploying a vm? The decision on "which" is the correct affinity group (at least for deployment) is already made due to dedication (as we learned realized with a affinity group).
One would expect, that this affinity group is the only availeable one and therefore afaik 'standard' / preselected.


The OpenAPI description field under info is displaying a hard-coded registry name

Took that from Model Matcher registry:

The description was incorrect, but the title should be interpolated just fine.


[BUG] Tween system uses out of date math functions

The methods used in the game currently need an updated selection of math to be used, as they are very dated.

Fixed in <IP_ADDRESS>


ngrok: fix running x86_64-darwin build

Motivation for this change
Fixes SEGFAULT trying to run on x86_64-darwin
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

 The change makes sense to me and ngrok still works fine here :+1:


Plugin cannot find WAR to deploy?

I am getting a really strange error trying to deploy a WAR which is provably there and available (see screenshot attahced below). Here is a snippet of my build file - any clue:
...
apply plugin: 'liberty'
apply plugin: 'war'

dependencies {

    //Java EE
    providedCompile ("javax:javaee-api:${java_ee_version}")

}

liberty {
    server {
        name = 'myServer'
        apps = [file('build/libs/openliberty-jaxrs-example.war')]
        dropins = [war]
        stripVersion = true
    }

    install {
        version = '17.0.0_03'
        type = "microProfile1"
    }
}

Is anyone from the Liberty staff watching these issues, please? I am getting the feeling Gradle is not well supported ...
I think my issue has something to do with the stripping the version from the war. Why is liberty expecting version wars at all  ?
Launching myServer (WebSphere Application Server <IP_ADDRESS>/wlp-1.0.18.cl170320170927-1854) on Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_131-b11 (en_US)
[AUDIT   ] CWWKE0001I: The server myServer has been launched.
[AUDIT   ] CWWKE0100I: This product is licensed for development, and limited production use. The full license terms can be viewed here: https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/license/base_ilan/ila
n/<IP_ADDRESS>/lafiles/en.html
[ERROR   ] CWWKG0075E: The value ${default.http.port} is not valid for attribute httpPort of configuration element httpEndpoint. The validation message was: Value "${default.http.port}" is not a number..
[AUDIT   ] CWWKZ0058I: Monitoring dropins for applications.
[WARNING ] CWWKZ0014W: The application openliberty-jaxrs-example-1.0-SNAPSHOT could not be started as it could not be found at location openliberty-jaxrs-example-1.0-SNAPSHOT.jar.
[AUDIT   ] CWWKZ0022W: Application openliberty-jaxrs-example has not started in 29.992 seconds.
[AUDIT   ] CWWKF0012I: The server installed the following features: [servlet-3.1, json-1.0, jaxrs-2.0, jaxrsClient-2.0].
[AUDIT   ] CWWKF0011I: The server myServer is ready to run a smarter planet.
<===========--> 87% EXECUTING [1m 21s]

This is happening regardless if  I have stripVersion = true

Will close this for now - it seems as Cindy gave me more info here

Will close this for now - it seems as Cindy gave me more info here


chore:fix: set env var fall back for MANIFEST, ICON, APP_LOGO

Not having these env vars defined leads to webpack CopyPlugin validation errors:
[dev-ui] ValidationError: CopyPlugin Invalid Options
[dev-ui]
[dev-ui] options.0 should be string
[dev-ui] options.0 should have required property 'from'
[dev-ui] options.0 should match some schema in anyOf
[dev-ui] options.1 should be string
[dev-ui] options.1 should have required property 'from'
[dev-ui] options.1 should match some schema in anyOf
[dev-ui] options.2 should be string
[dev-ui] options.2 should have required property 'from'
[dev-ui] options.2 should match some schema in anyOf

They weren't mentioned in the README, so I suggest defining fall back values directly in webpack.ui.config.json.
In addition I am adding further values that have be configured in  the config.sample.json.

haha i just did that on my dev branch too - merging


Check for errors in application e2e test

This changes the end-to-end test that integrates with a client application to perform error checking on all Terraform commands, not just checking that the application had exit code 0.

Looks good. The run.sh script concatenates the "errors" variable - we might want to initialize to "" at the beginning just in case someone does a errors="something" test/app/run.sh or runs the script twice (unlikely cases).

Good catch.


Language picker

we need to display language name in that language's language and not in the user's current language
e.g. now its
en
English
German

de
Englisch
Deutsch

but should be
English
Deutsch

always

https://docs.djangoproject.com/en/1.8/topics/i18n/translation/#switching-language-in-templates


Issue 315

Fixes for issue https://github.com/Islandora-CLAW/CLAW/issues/315
This doesn't add support for Silex, just fixes the build issues.

From what I recall from attempting the build, generating the artefacts for the two micro-services failed so that seems to line up with it being removed when it all got pulled out of the one repo.
Might as well merge the build fixes here though, and pick up on the implementation of Silex, etc afterwards.


x/tools/gopls: support showing all interfaces that a given type implements

Should this be part of the textDocument/implementation request or is this a separate feature? Perhaps we need to request clarification in the protocol.

@stamblerre I've run into this a couple times. I come across a concrete method and run find-references on it, but get nothing back. I'm mildly confused until I figure the method might be used to satisfy an interface, but there is no way to find that interface easily to continue my code exploration.
Would you be opposed to making textDocument/implementation also work backwards from concrete type/method -> interface type/method for now?
We should also explore a proposal to add "implements" to the LSP spec, but it is sort of a unique problem to Go since most languages require you to explicitly declare when a type implements an interface, so going from concrete -> interface isn't hard for the user.
Personally, I don't really want another flavor of find-something-something to choose from as a user, but of course I could always just make my editor search both and combine results if I don't want to think about it.

Would you be opposed to making textDocument/implementation also work backwards from concrete type/method -> interface type/method for now?

Yes, I think it's time to give this a try. I think it's a reasonable solution. But I think we could also try having find references include these results.

Any progress?

The above CL has been merged at master, but it is not part of the gopls/v0.3.3 release.

A use @master. Does it work only with interfaces/types located within same module? I don't see this feature working:

Yes, it only works on packages in your module and their transitive dependencies.

So there is no chance to see if we implement smth like fmt.Stringer, or io.Reader? Do you think it's okay to have such limited fuctionality?
Still, it doesn't work:

Are you sure you have the changes in your running gopls? Your example works for me, and fmt.Stringer/io.Reader also work.

Well, I update from master every day, so I suppose this was merged few hours ago? Let me check. Is there any chance, for instance, if I ask to find implementations navigating at Stringer in fmt package, that it will also find that it's implemented by some of my project's types?

Yes, find-implementations on fmt.Stringer should list a ton of things including any types in your workspace that implement fmt.Stringer.

Nice, finally it looks like something usable and helpful. Like it was with bingo > than a year ago :P

So does it work for you now? What was the problem?

When I open this project: https://github.com/benthosdev/benthos-plugin-example
and navigate to https://pkg.go.dev/github.com/Jeffail/benthos/v3/lib/types?tab=doc#Output
It shows that there is no local type implementing it:

However this type implements it:
https://github.com/benthosdev/benthos-plugin-example/blob/master/output/blue_stdout.go#L35
To be honest before that I saw just one single time that feature worked (but this particular type was missing as well in list of implementations of types.Output, so I was going to file that particular issue), but after several restarts I never seen this been working again, just "no implementaions" message.

I can reproduce it not working when you run find-implementations on the declaration of the Output type. But, it works when you run find-implementations on types.Output within blue_stdout.go, and running find-implementations on the declaration of BlueStdout also works (i.e. it lists the "Output" interface). Is that consistent with what you see, or does it not work at all for you?

Yes, right now it's same.

The issue is the github.com/Jeffail/benthos/v3/lib/types dependency is loaded in ParseExported mode when github.com/benthosdev/benthos-plugin-example/output is loaded, but when you run find-implementations from github.com/Jeffail/benthos/v3/lib/types/interface.go it uses the ParseFull version, so the named types in the interface no longer match.
@stamblerre I guess the solution is to re-type check a package's dependents when it transitions from ParseExported to ParseFull? In other words if you directly open a file that was previously parsed in ParseExported, you need to invalidate type data of any dependent packages so they properly depend on the ParseFull version.

Actually I don't open it directly, I just Ctrl-Click on types.Output, and that's it. Another question is that I don't see unexported interfaces or implementations. This forces me to use exported things most of the time, otherwise how do I know there is something else if tool doesn't show it? Goland shows both exported and unexported, and this makes it very useful.

gopls shows unexported interfaces and implementations. Do you have steps to reproduce them not showing up?

For example, mentioned above BlueStdout implements this interface: https://github.com/Jeffail/benthos/blob/v3.10.0/lib/broker/fan_in.go#L79
It's shown in Goland but missing with gopls.

That is related to the other issue. The broker package is loaded in ParseExported mode which means the function bodies are elided. That type is defined in the function body, so gopls can't find it.

Is this gonna be fixed?

Fixing the first issue of finding implementations starting from a non-workspace dependency seems relatively straight forward, but fixing the second issue will take more consideration. gopls loads non-workspace dependencies in export-only mode to reduce memory usage, which is a concern for many users.

I understand it's not trivial. Would be nice to have it anyways, thank you.

I've reached the same problem. But another maybe unrelated puzzle: why ubuntu(in a virtual machine) vscode can successfully find all references even without gopls? I compared them side by side and cannot figure out why... But the same time, ubuntu vscode seems missing a lot of syntax check.

Ok, I got what i am missing. The references result turned normal after I moved the project into $GOPATH/src. Noticed in ubuntu, the same project has a copy under $GOPATH/src. When I use "Find All References" inside other copy, it will show result in $GOPATH copy.
Sorry, newbie to Go world. A lot "weired" to learn to make sense.

I think this issue falls under the broader category of figuring out how to better handle the full vs exported ASTs. This needs to be resolved in the context of running analyses correctly too, but I don't think it will happen until after gopls/v0.1.0. We can perhaps continue the conversation on https://github.com/golang/go/issues/38278. Closing this as a result.


kvm: flannel networking

Based on #1530
Provides flannel networking support in kvm flavor.

What I miss is "follow up TODO list"

[ ] unittests - loadFlannelNetConftranformation
[ ] functionall tests - flannel integration tests if possible

@jellonek let us know when you might have time to work on this or if we can help shepherd it through

This PR is follow up on #1530 so (hopefully) tomorrow i'll do based on and rebase of this.

thanks!

Both PRs are rebased.

@steveeJ can you review this?

@steveeJ Could You look at this?

It should be rebased again, now that #1530 is merged.

@steveeJ Your comments are interesting (and I have to address them, but in separate issue IMO) but are disconnected from this PR. It's because this PR was based on #1530 where this comments would be more adequate.
I'll make a separate PR with cleanup in kvm flavor (docstrings are outdated, --net parameter handling in kvm flavor should be reworked, and so on).

ACK. If semaphoreci turns green so we know it doesn't break things we should merge it an iterate through the next PR(s) in short term.

@steveeJ @jellonek semaphoreci is green! Should we take it for the v0.12.0 release today as well?

IMO yes.


Add support for async T_exp! and T_lim!

@tapios suggested adding this if it's not too difficult, and here it is:
This PR adds support for asynchronous T_exp! and T_lim! on both CPU and GPU.
We can try it out by passing the comms context, but we don't need to use it if we don't want.

Nice! When you know how much it affects performance, please let us know.

Trying it out here: https://buildkite.com/clima/climaatmos-target-gpu-simulations/builds/122

New build at: https://buildkite.com/clima/climaatmos-ci/builds/14157

Interesting, we're hitting maxiter reached in saturation_adjustment:. Ah, right, it was reduced to 3. 🤷🏻

I guess, maybe, we need a smaller timestep? (we could try increasing maxiter, but I assume it was reduced for good reason).

Update on this: the failures in ClimaAtmos were because the device was not synchronized, adding proper syncs did fix this.
I've updated the PR in a couple ways:

The multiple streams version is now in a CUDA extension, so that we don't need to directly depend on CUDA
I've kept both the multiple streams and multiple tasks for CUDADevices (we should compare them)
I've added a multithreaded version for the CPU

We should compare the streams vs tasks on the CUDA side. The multiple streams version with events do seem to be executing T_exp! and T_lim! asynchronously on separate streams, however, are not executing concurrently. The reason being that we're probably utilizing too many resources, and the scheduler is deciding to execute them serially.
One way we can try getting concurrent execution is by reducing the number of blocks in our kernel launches, but we might only want to (somehow) do that in T_exp! and T_lim!, rather than globally.
So, all in all, this isn't actually offering any performance improvement for GPU jobs yet. The CPU multithreaded implementation might be an improvement, but it's not yet been tested/benchmarked. Also, there could be interplay with threads being used in the broadcast kernels (which, perhaps, we could/should just remove).

Further update: we will not add async support with T_exp! and T_lim!, as fusing these allowed us to eliminate dss calls. Instead, we'll add async support with f! and j!.

This could be really good for strong scaling


Issue when uploading multiple .obj files

Laravel Version: #.#.#
Voyager Version: #.#.#
PHP Version:
Database Driver & Version:

Description:
Hi, I'm trying to upload to a model via a multiple files object, some .obj files (~2-3 Mbs), but when i submit it, i got the message:
ErrorException in FilesystemAdapter.php line 146:
fopen(/var/www/voyager/public): failed to open stream: Is a directory
in FilesystemAdapter.php line 146
at HandleExceptions->handleError(2, 'fopen(/var/www/voyager/public): failed to open stream: Is a directory', '/var/www/voyager/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php', 146, array('path' => 'tridimensionals/March2017/', 'file' => object(UploadedFile), 'name' => 'Ne3irGf6komW4lQQ4tSN.obj', 'options' => array()))
at fopen('/var/www/voyager/public', 'r+') in FilesystemAdapter.php line 146
at FilesystemAdapter->putFileAs('tridimensionals/March2017/', object(UploadedFile), 'Ne3irGf6komW4lQQ4tSN.obj', array()) in UploadedFile.php line 84
at UploadedFile->storeAs('tridimensionals/March2017/', 'Ne3irGf6komW4lQQ4tSN.obj', array()) in Controller.php line 172
at Controller->getContentBasedOnType(object(Request), 'tridimensionals', object(DataRow)) in Controller.php line 60
I don't know if the problem is the .obj file, because I tried with any image type and also zip or mtl file types and i don't have any issue or problem.
Can you help me?
Regards!
Steps To Reproduce:
Upload .obj files into a multiple files input on a data model/object.

I think is solved... I was trying to upload an smaller .obj file and there is no problem.
I'm lefting this issue as solved, maybe it can help to others.
Thanks!

this happen because of upload_max_filesize (default 2), post_max_size (default 8) in php.ini. change your php setting and increase those values then everything will be alright. I faced the same problem and solved in same manner


04-polaron_transformed_redfield.jmd bug

The unitary used in the Redfield equation is not correct.

Close by the new update


React Native app crashing due to assertion error

Started experiencing this crash today, have not encountered it before:
Build and run project in Xcode
Works for a while, then suddenly exits the app:
In system log, I see this:

Jul 20 17:37:34 Thomass-MacBook-Pro Acuris[21009]: assertion failed: 17G65 15F79: libxpc.dylib + 71445 [C070AA3B-6F2B-3D85-887C-5A00FAE39163]: 0x7d
Jul 20 17:37:35 Thomass-MacBook-Pro Acuris[21009]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?

dev/mobile-notifications-native >react-native info
Scanning folders for symlinks in /Users/thomasclarke/dev/mobile-notifications-native/node_modules (15ms)
Environment:
OS: macOS High Sierra 10.13.6
Node: 10.7.0
Yarn: 1.7.0
npm: 6.2.0
Watchman: Not Found
Xcode: Xcode 9.4.1 Build version 9F2000
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.3.2 => 16.3.2
react-native: 0.55.4 => 0.55.4

Please provide repro (steps or code) on how to reproduce this. For me, it seems that it's unrelated to react native.

I just started getting this on a release build. Not sure if this is related but same error and all. Here are some more logs...
Jul 20 16:15:40 COMPUTER_NAME APP_NAME[19094]: assertion failed: 17G65 15F79: libxpc.dylib + 71445 [C070AA3B-6F2B-3D85-887C-5A00FAE39163]: 0x7d
Jul 20 16:15:43 COMPUTER_NAME com.apple.CoreSimulator.SimDevice.7D3870F0-2782-4EF7-9E6C-E1068F3DE8EB[89769] (com.apple.securityuploadd): Service only ran for 6 seconds. Pushing respawn out by 4 seconds.
Jul 20 16:15:47 COMPUTER_NAME com.apple.CoreSimulator.SimDevice.7D3870F0-2782-4EF7-9E6C-E1068F3DE8EB[89769] (com.apple.videosubscriptionsd[19106]): Service exited with abnormal code: 1
Jul 20 16:15:47 COMPUTER_NAME com.apple.CoreSimulator.SimDevice.7D3870F0-2782-4EF7-9E6C-E1068F3DE8EB[89769] (com.apple.videosubscriptionsd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Jul 20 16:15:53 COMPUTER_NAME com.apple.CoreSimulator.SimDevice.7D3870F0-2782-4EF7-9E6C-E1068F3DE8EB[89769] (com.apple.securityuploadd): Service only ran for 5 seconds. Pushing respawn out by 5 seconds.

Was a solution ever found? Happens to me only on release when upgraded to RN 0.56.0

Happening to us as well, only on iPhone X inside Expo or in the native built app.
Not finding much help here.
I know this is closed, but I have an App Store app that experiences it on iPhone X if that's any help.

I just rant into very much the same problem, but we are not using firebase

@macnibblet did you find a solution? I have the same issue

Is anyone has information about this issue ?


Anemometer does not support 5.7 as backend DB

The install sql file does not create the tables properly during first setup. It appears to be due to a change in the default timestamp format in 5.7.

I fixed it by doing following changes:
 ts_mindatetime NOT NULL DEFAULT '1990-01-01 00:00:00',  ts_max datetime NOT NULL DEFAULT '1990-01-01 00:00:00',
Ran it on Server version: 5.7.8-rc MySQL Community Server (GPL)

I can have a look at it when I'm on my workstation :)


import action array

https://github.com/zalmoxisus/redux-devtools-extension/issues/173#issuecomment-236831433
tests arent working yet :(
  1) instrument Import Actions should replay all the steps when a state is imported:
     TypeError: Cannot read property 'type' of undefined
      at counter (instrument.spec.js:9:11)
      at computeNextEntry (instrument.js:80:21)
      at recomputeStates (instrument.js:145:17)
      at instrument.js:394:22
      at Object.dispatch (node_modules/redux/lib/createStore.js:179:22)
      at Context.<anonymous> (instrument.spec.js:613:34)

  2) instrument Import Actions should replace the existing action log with the one imported:
     TypeError: Cannot read property 'type' of undefined
      at counter (instrument.spec.js:9:11)
      at computeNextEntry (instrument.js:80:21)
      at recomputeStates (instrument.js:145:17)
      at instrument.js:394:22
      at Object.dispatch (node_modules/redux/lib/createStore.js:179:22)
      at Context.<anonymous> (instrument.spec.js:624:34)

Not sure why the tests fail -- any ideas?

@ccorcos, it says that shouldn't be comma here.

oh, oops. just updated

https://travis-ci.org/zalmoxisus/redux-devtools-instrument/builds/149286756#L208-L224

Ok,  I had to filter out timestamps from the actions before comparison because they were off by a ms. Otherwise, tests pass!

wait, i didnt lint yet

Better to just use expect's toMatch or toInclude.

I'm not sure that those help though -- the issue is that beforeAll runs a millisecond before the actual test, so the actions timestamps are 1ms different. I suppose toInclude would work if you want me to write out the actions, but then you'd have to rewrite the test anytime you change the lifted action schema...

I see, thanks  for the details and the contribution! Will publish the extension tomorrow.

Sweet! Will the chrome extension update automatically? Or do I need to update in chrome?

Yes, Chrome will autoupdate the extension in several hours.


Matplotlib 3.0.0 needs ncl 6.5.0

Not an issue per se but more of a heads up for deps versioning - both matplotlib and ncl have been upgraded recently(ish) - 3.0.0 and 6.5.0 respectively. Note that matplotlib=3.0.0 is suffering from an issue reported here https://github.com/ESMValGroup/ESMValTool/issues/614 and may not be 100% stable so a reversion to 2.2.2 may be needed; to do so one can not just conda install matplotlib=2.2.2 but rather need to downgrade the overarching package which is ncl so need to do conda install -c conda-forge ncl=6.4.0. the matplotlib=3.0.0+ncl=6.5.0 in other words matplotlib and ncl are version-interlinked; the new environment is dodgy since it asks for downgrading a number of deps among which qt and pyqt are the most significant. I am going to assign @bouweandela and @bjoernbroetz just for heads up, no action needed

I think it is very unlikely that matplotlib depends on NCL.

It's not matplotlib directly but their common dependencies in the conda
tree. Try installing matplotlib=3.0.0 yourself via conda and you'll see the
bugger
Dr Valeriu Predoi.
Computational scientist
NCAS-CMS
University of Reading
Department of Meteorology
Reading RG6 6BB
United Kingdom
On Fri, 5 Oct 2018, 08:56 Bouwe Andela<EMAIL_ADDRESS>wrote:

I think it is very unlikely that matplotlib depends on NCL.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ESMValGroup/ESMValTool/issues/637#issuecomment-427278635,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbpCo-NujJv1EF6ioFbMbTa_tB47z8x1ks5uhxCsgaJpZM4XIe7V
.

@bouweandela @bjoernbroetz gents, shall we pin matplotlib to 2.2.2 for now? The (famous by now, have talked to other devs at the Crescendo GA) _hold error in matplotlib 3.0 is affecting iris-quickplot as well:
  File "/home/users/valeriu/miniconda2/envs/esmvaltool/lib/python3.6/site-packages/iris/quickplot.py", line 241, in pcolormesh
    result = iplt.pcolormesh(cube, *args, **kwargs)
  File "/home/users/valeriu/miniconda2/envs/esmvaltool/lib/python3.6/site-packages/iris/plot.py", line 1041, in pcolormesh
    result = _draw_2d_from_bounds('pcolormesh', cube, *args, **kwargs)
  File "/home/users/valeriu/miniconda2/envs/esmvaltool/lib/python3.6/site-packages/iris/plot.py", line 267, in _draw_2d_from_bounds
    cube, plot_defn, *args, **kwargs)
  File "/home/users/valeriu/miniconda2/envs/esmvaltool/lib/python3.6/site-packages/iris/plot.py", line 754, in _map_common
    return plotfn(*new_args, **kwargs)
  File "/home/users/valeriu/miniconda2/envs/esmvaltool/lib/python3.6/site-packages/matplotlib/pyplot.py", line 2716, in pcolormesh
    data=data, **kwargs)
  File "/home/users/valeriu/miniconda2/envs/esmvaltool/lib/python3.6/site-packages/cartopy/mpl/geoaxes.py", line 1451, in pcolormesh
    result = self._pcolormesh_patched(*args, **kwargs)
  File "/home/users/valeriu/miniconda2/envs/esmvaltool/lib/python3.6/site-packages/cartopy/mpl/geoaxes.py", line 1469, in _pcolormesh_patched
    if not self._hold:
AttributeError: 'GeoAxesSubplot' object has no attribute '_hold'

Looks like the iris people also noticed https://github.com/SciTools/iris/pull/3176#issuecomment-424676271
There are now three problems with matplotlib 3.0.0 out of our reach of fixing:

Basemap (#610)
ncl conda package (this issue)
iris (see above)

So IMHO enough reasons to pin the version till things are getting more stable.

Cartopy issue is here https://github.com/SciTools/cartopy/issues/1126.
If anyone is going to make a PR for this: pin matplotlib both in meta.yml (for the conda build) and in setup.py (for the python installation).
I would suggest pinning matplotlib to versions <3 instead of specifically to 2.2.2.

sounds like a solid plan @bjoernbroetz - I suspect, though, that we need to collaterally pin ncl to 6.4 otherwise conda will get fussy with us

NCL 6.4 should be no problem, there is no need for NCL 6.5 at the moment.

If anyone is going to make a PR for this: pin matplotlib both in meta.yml (for the conda build) and in setup.py (for the python installation).

So, I will do this fast...


Group hash to curve - rejection sapling?

I have been reading the hash to curve RFC (thanks @A-Manning) and reflecting on some of the issues that arise. One proposed group hash implementation (among others) can be summarized:

BLAKE2 hash an arbitrary length asset identifier string to a 32-byte internal identifier
BLAKE2 hash the internal identifier to another 32 byte image
Use 255 bits of the latter image to construct a y value and 1 bit for an x_sign
If the candidate y value is not on the curve, or if the y value exceeds the modulus of the finite field, then reject the image and update the first hash with the internal identifier to get a new internal identifier
output (x,y) point on the curve

We could also increment the last byte of the asset identifier string. These will give us a uniformly random point on the curve (under random oracle assumption), but the RFC does not like rejection sampling:

Implementors MUST NOT use rejection sampling to generate a uniformly
random element of F.  The reason is that rejection sampling
procedures are difficult to implement in constant time, and later
well-meaning "optimizations" may silently render an implementation
non-constant-time.

This document does not cover rejection sampling methods, sometimes
known as "try-and-increment" or "hunt-and-peck," because the goal is
to describe algorithms that can plausibly be made constant time.  Use
of these rejection methods is NOT RECOMMENDED, because they have been
a perennial cause of side-channel vulnerabilities.

Setting aside the constant time issue (is the rest of librustzcash constant time? could fixed-iteration hashing be done in constant time?) we have a perhaps bigger issue: is it possible to do any of the RFC methods feasibly in circuit? (assume substitute blake2s for sha256). Each hash is pretty expensive by itself.

Am I correct in understanding that this method requires at least two hashes and possibly more? What is the chance of the candidate y value being rejected in step 4? (or, alternatively, what is the "expected number of hashes", although we might also care about maliciously-crafted inputs)
Do we care about constant-time operation? A lot of algorithms in the Sapling user-side code deal with secret data (amount, sender, recipient, keys, etc.); asset denomination is another piece of data we'd like to keep secret, but it only really matters if the other algorithms are already constant-time.

Or is the first hash one which can be performed outside the circuit?

yeah the first hash is outside of the circuit (and actually, its not critically important that it be secure in any sense as it's mostly used for compression)
I think the status is that librustzcash uses constant time operations where feasible but that side channel prevention/constant time implementation is not a target feature right now. In any case these details can be elaborated in comments and/or spec.
Also I need to add more details to the rejection sampling comment about the rejection probability.

closing as:

not a circuit issue, and
rejection sampling is sufficient for now


Merge Bugfixing

Hi,
I think it's time to merge the whole bugfixing stuff to the development branch.
@62BRAINS @hirt93de please review and approve the merge.

I thin this issue should be fixed before merging into develop branch: https://github.com/CircleBilling/CircleBilling/issues/31 What do you think?


Dynamic groups time range is fixed in 24 hours

Dynamic groups with Update Managmeent is not running well if you use a time range above 24 hours to calculate the list of your computers. UM use a fixed time range of 24 hours.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 9aac8847-f559-3f92-4d1f-47ed622db5c3
Version Independent ID: 6dc36690-57fe-cfdb-b129-fb24cb872995
Content: Use dynamic groups with Azure Automation Update Management
Content Source: articles/automation/update-management/configure-groups.md
Service: automation
Sub-service: update-management
GitHub Login: @SnehaSudhirG
Microsoft Alias: sudhirsneha

@dmrellan
Thanks for your feedback! We will investigate and update as appropriate.

#product-feedback
@dmrellan Thanks for the feedback and sharing your experience. I will share this as a feedback with product team to see what can done to improve the experience if time range is above 24 hours to calculate the list of computers.
If possible and if you have a support plan, I also recommend you to open a support ticket as mentioned here so that Azure technical support team would be able to check your environment directly and validate if its environment level issue or a broader issue and can share the feedback with product team as appropriate. If you don't have a support plan to open a support ticket then please send mail to<EMAIL_ADDRESS>with "Attn:Krishna" as subject and share your
subscription ID and a link of this Github thread for context and we will assist you with engaging Azure technical support.
At this point it appears that there's no edits or updates needed for the documentation so closing this issue for now. If there are further questions regarding this matter or questions or feedback on the documentation, please do let us know and we will gladly continue the discussion.


Update use_cases,md - revised document

Added more content based on feedback from @toddreifsteck and also content and corrections from Amiya Gupta

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: nhelfman sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

PR 104 is has more current changes.


Performance significantly decreased with 1.9

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Submission validity

[X] This is not a personal support request, that should be posted on discussions community.
[X] I checked current issues and this request isn't a duplicate of an existing issue, opened or closed.

Self troubleshooting

[X] I've read the documentation and made sure to follow it.
[X] I've read the troubleshooting first steps and frequent issues guides.

Version
1.9
Description
Immediately after upgrading to 1.9, performance took a hit.
I use Nagios to monitor my server with a simple check_http using SSL looking for a string (the  tag).
It now times out after 10 seconds after upgrading to 1.9.  No other changes on my server were made.
Additionally, loading the page in my browser feels significantly slower.
Expectation
Page should load in about 0.5 seconds
Reproduction steps

Upgrade from 1.8.2 on OpenBSD 7.0 with a mariadb back-end
Connect to YOURLS URI and experience slow connection

Context
OpenBSD 7.0
nginx 1.20.1p1
php-8.0.17
mariadb-server-10.6.7v1

Thanks for opening this issue @merdely.
Right now, two ideas in my mind:

A potential cache issue on php server; if a service restart is possible it's worth a try.
A plugin validation delay

@ozh there isn't db change indeed, but significant plugin load changes
https://github.com/YOURLS/YOURLS/blame/27375bc813f2ddc38030800e466babb72d7a5a66/includes/functions-plugins.php#L604
@merdely You didn't specify if any plugin is installed on your deployment. Any?

This plugin load changes shouldn't have any performance side effect, it's merely the previous code wrapped into a try catch block

I have 3 plugins:

Change Password
Random ShortURLs
A custom plugin I wrote

My plugin simply has:
<?php
/*
Plugin Name: REDACTED Plugin
Plugin URI: REDACTED
Description: Simple overrides for REDACTED
Version: 0.1
Author: Mike Erdely
Author URI: REDACTED
*/

// No direct call
if( !defined( 'YOURLS_ABSPATH' ) ) die();

/* Override the Title
 *
 * We're going to modify the <title> of pages in the admin area
 *
 * The <title> tag is generated by function yourls_html_head() in includes/functions-html.php
 * Notice the following function call:
 * $title = yourls_apply_filter( 'html_title', 'YOURLS: Your Own URL Shortener' );
 * This function means: give $title the value "YOURLS: Your Own URL Shortener", unless a
 * filter modifies this value.
 *
 * We're going to hook into this filter and modify this value.
 */

yourls_add_filter( 'html_title', 'erdely_change_title' );
function erdely_change_title( $value ) {
        $value = 'REDACTED URL Shortener';
        return $value; // a filter *always* has to return a value
}

yourls_add_filter( 'admin_url', 'erdely_change_admin_url' );
// return yourls_apply_filter( 'admin_url', $admin, $page );
function erdely_change_admin_url( $value ) {
        $value = preg_replace('#/admin/#', '/REDACTED/', $value);
        return $value;
}
```

I just rebooted my server and with the Plugins page loaded in my browser, I hit refresh.  It took 10 seconds to load, so likely not a cache issue.

I just disabled all plugins: same issue.

https://docs.yourls.org/guide/troubleshooting/first-steps.html : YOURLS_DEBUG


Add code generator for OCPP 2.1

This PR introduces support for OCPP 2.1. The code in ocpp/v21 is generated by the newly
introduced code generator.
I've created this draft to gather feedback on the generated code in ocpp/v21, not on the code generator itself.
The generator requires some clean up and tests.
Unfortunately, I'm not allowed to include the JSON schemas with this PR at the moment. The OCA
distributed these files to members only. I'm in touch with the OCA to see if they allow me to include
the schemas in this project.
Fixes: #452

I think we should remove from the PR the calls and calls results .json for now - maybe only include the generator components and then I can read in the schemas and compare the output results, then give feed back if it comes out correctly?

It is frustrating that the OCA doesn't allow these artefacts to be in the public domain! I know this isn't the place to discuss this, so I'll not go on for too long... 😁
It's the same for the OCPP docs. They're available in PDF, not HTML, which makes creating tools that link to specific sections tricky. You have to add a reference to, for example, 5.16. Set Charging Profile.
It'd be 🆒 to get these specifications in the public domain and reduce the friction for contribution and innovation.


Add Red-Point

Ha! Thanks makes sense Gerald. I still find it super cool we are on the MAUI showcase list 🤯


Add exercise: protein-translation 🧬

Link to forum posts

https://forum.exercism.org/t/kotlin-protein-translation-exercise-48in24/9605
https://forum.exercism.org/t/48in24-exercise-02-13-protein-translation/9556

What has been done

Use configlet to generate common files
Update some config files
Implement test cases (got the idea for a parameterized test from the JS track: https://github.com/exercism/javascript/blob/main/exercises/practice/protein-translation/protein-translation.spec.js#L22)
Write stub implementation: provide a starting point for students
Write an example solution that passes all the tests

./gradlew practice:protein-translation:test

Notes
First PR here. Let me know if I missed anything 😊

Ping @exercism-kotlin 🙂 🛎


Allow predicates to traverse Postgres array and jsonb columns

Currently doobie array (and in the future jsonb) columns are handled as special kinds of leaf types as far as GraphQL query execution is concerned. It should be possible to consider array elements and json fields as an extension of the model and allow predicates to index in to them.

This is done for jsonb via the circe mapping. We could probably do something similar for arrays by handling array elements using a value or generic mapping.


Update base1.8

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@ericvn: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ericvn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-distroless-k8s-tests_istio

release-test_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-distroless-k8s-tests_istio

release-test_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-security-k8s-tests_istio

unit-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-distroless-k8s-tests_istio

release-test_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
8afec21c30801ca7ffeeb3e9f982aecc229fe418
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.