Teams,
I have had my VNFs created on 4.20 and all worked, all of the sudden are not
working, when I try to retest the VNFs on 4.20.1. and Unable to deploy any VNFS
from the templates, I am unable to deploy pfsense from ISOs either.
I can create any other VMs, but pfSense, I was tinking is maybe related to
FreeBSD?
The S-VM creates a decoding link to NULL, secondary storage is mounted properly.
When I try to create a new VNF
2025-08-06 01:24:06,779 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-13:[ctx-0555d00d, job-5003, ctx-d625ffeb]) (logid:2a8c2798)
Trying to deploy VM [error decoding VM instance
{"id":163,"instanceName":"i-2-163-VM","state":"Stopped","type":"User","uuid":"91ad88b9-b9d6-4109-9209-55edc12f640d"}]
and details: Plan
[{"_dcId":1,"_recreateDisks":false,"preferredHostIds":[],"migrationPlan":false,"hostPriorities":{}}];
avoid list [{}] and planner: [].
2025-08-06 01:24:06,799 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-13:[ctx-0555d00d, job-5003, ctx-d625ffeb]) (logid:2a8c2798)
Adding pods [[]], clusters [[]] and hosts [[]] to the avoid list in the deploy
process of user VM [error decoding VM instance
{"id":163,"instanceName":"i-2-163-VM","state":"Stopped","type":"User","uuid":"91ad88b9-b9d6-4109-9209-55edc12f640d"}],
because this VM is not explicitly dedicated to these components.
2025-08-06 01:30:25,702 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-13:[ctx-0555d00d, job-5003, ctx-d625ffeb]) (logid:2a8c2798)
VM instance
{"id":163,"instanceName":"i-2-163-VM","state":"Error","type":"User","uuid":"91ad88b9-b9d6-4109-9209-55edc12f640d"}
state transited from [Stopped] to [Error] with event [OperationFailedToError].
VM's original host: null, new host: null, host before state transition: null
2025-08-06 01:30:25,823 WARN [c.c.a.AlertManagerImpl]
(API-Job-Executor-13:[ctx-0555d00d, job-5003, ctx-d625ffeb]) (logid:2a8c2798)
alertType=[8] dataCenterId=[1] podId=[1] clusterId=[null] message=[Failed to
deploy Vm VM instance
{"id":163,"instanceName":"i-2-163-VM","state":"Error","type":"User","uuid":"91ad88b9-b9d6-4109-9209-55edc12f640d"},
on Host null with Id: null].
2025-08-06 01:30:25,833 WARN [c.c.a.AlertManagerImpl]
(API-Job-Executor-13:[ctx-0555d00d, job-5003, ctx-d625ffeb]) (logid:2a8c2798)
No recipients set in global setting 'alert.email.addresses', skipping sending
alert with subject [Failed to deploy Vm VM instance
{"id":163,"instanceName":"i-2-163-VM","state":"Error","type":"User","uuid":"91ad88b9-b9d6-4109-9209-55edc12f640d"},
on Host null with Id: null] and content [Failed to deploy Vm VM instance
{"id":163,"instanceName":"i-2-163-VM","state":"Error","type":"User","uuid":"91ad88b9-b9d6-4109-9209-55edc12f640d"},
on Host null with Id: null].
2025-08-06 01:30:25,883 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-13:[ctx-0555d00d, job-5003]) (logid:2a8c2798) Unexpected
exception while executing
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin
com.cloud.utils.exception.CloudRuntimeException: Unable to orchestrate the
start of VM instance
{"instanceName":"i-2-163-VM","uuid":"91ad88b9-b9d6-4109-9209-55edc12f640d"}.
2025-08-06 01:30:25,886 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-13:[ctx-0555d00d, job-5003]) (logid:2a8c2798) Complete async
job-5003, jobStatus: FAILED, resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Unable
to orchestrate the start of VM instance
{"instanceName":"i-2-163-VM","uuid":"91ad88b9-b9d6-4109-9209-55edc12f640d"}."}
Tata Y.
