cloudstack+Linstor

Hi Team, I have followed the below youtube link to install the linstor, it works fine. I have completed the cloudstack-4.19.1.1 with NFS primary, I am able to create vm with the NFS primary storage. But later added the linstor as another primary storage which got added and status showing UP and also shows the available total storage. But while creating instance with Linstor storage its not creating, and also tried just creating a new volume, its throwing as error…Anyone plz help…below is the errors from Management log is when working VM created on NFS storage and trying to migrate the same VM to Linstor primary storage.

Sample Cloudstack Management log: (only the error and couple of lines)

IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 8796747758516, completeMsid: null, lastUpdated: null, lastPolled: null, created: Mon Aug 26 05:06:03 UTC 2024, removed: null}
2024-08-26 05:06:04,494 DEBUG [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-8:ctx-7dba49d1 job-268/job-269) (logid:ab914068) Run VM work job: com.cloud.vm.VmWorkStorageMigration for VM 12, job origin: 268
2024-08-26 05:06:04,504 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-8:ctx-7dba49d1 job-268/job-269 ctx-dae902a6) (logid:ab914068) Execute VM work job: com.cloud.vm.VmWorkStorageMigration{"volumeToPool":{"12":4},"userId":2,"accountId":2,"vmId":12,"handlerName":"VirtualMachineManagerImpl"}
2024-08-26 05:06:04,543 ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-8:ctx-7dba49d1 job-268/job-269 ctx-dae902a6) (logid:ab914068) Invocation exception, caused by: java.lang.NullPointerException
2024-08-26 05:06:04,545 INFO  [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-8:ctx-7dba49d1 job-268/job-269 ctx-dae902a6) (logid:ab914068) Rethrow exception java.lang.NullPointerException
2024-08-26 05:06:04,545 DEBUG [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-8:ctx-7dba49d1 job-268/job-269) (logid:ab914068) Done with run of VM work job: com.cloud.vm.VmWorkStorageMigration for VM 12, job origin: 268
2024-08-26 05:06:04,547 ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-8:ctx-7dba49d1 job-268/job-269) (logid:ab914068) Unable to complete AsyncJobVO: {id:269, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkStorageMigration, cmdInfo: rO0ABXNyACNjb20uY2xvdWQudm0uVm1Xb3JrU3RvcmFnZU1pZ3JhdGlvboeRn3LBtueeAgABTAAMdm9sdW1lVG9Qb29sdAAPTGphdmEvdXRpbC9NYXA7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAAMdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbHNyABFqYXZhLnV0aWwuSGFzaE1hcAUH2sHDFmDRAwACRgAKbG9hZEZhY3RvckkACXRocmVzaG9sZHhwP0AAAAAAAAx3CAAAABAAAAABc3IADmphdmEubGFuZy5Mb25nO4vkkMyPI98CAAFKAAV2YWx1ZXhyABBqYXZhLmxhbmcuTnVtYmVyhqyVHQuU4IsCAAB4cAAAAAAAAAAMc3EAfgAIAAAAAAAAAAR4, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 8796747758516, completeMsid: null, lastUpdated: null, lastPolled: null, created: Mon Aug 26 05:06:03 UTC 2024, removed: null}, job origin:268
java.lang.NullPointerException
        at com.cloud.vm.VirtualMachineManagerImpl.executeManagedStorageChecksWhenTargetStoragePoolProvided(VirtualMachineManagerImpl.java:3005)
        at com.cloud.vm.VirtualMachineManagerImpl.buildMapUsingUserInformation(VirtualMachineManagerImpl.java:2982)
        at com.cloud.vm.VirtualMachineManagerImpl.createMappingVolumeAndStoragePool(VirtualMachineManagerImpl.java:2945)
        at com.cloud.vm.VirtualMachineManagerImpl.prepareVmStorageMigration(VirtualMachineManagerImpl.java:2558)
        at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStorageMigration(VirtualMachineManagerImpl.java:2387)
        at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStorageMigration(VirtualMachineManagerImpl.java:5604)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:105)
        at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5610)
        at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
        at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:654)
        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:602)
        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)
2024-08-26 05:06:04,581 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-8:ctx-7dba49d1 job-268/job-269) (logid:ab914068) Complete async job-269, jobStatus: FAILED, resultCode: 0,

EDIT: formatted log text

Hi mpb,

Are there any LINSTOR logs to go with these? What are the LINSTOR errors you see when attempting to create volumes using CloudStack? Are you able to create LINSTOR resources using LINSTOR directly (linstor resource-group spawn ... )?

Also, please try to format your log output so that it is easier to read and doesn’t wrap.

Hi Kermat…I have already copied the relevant log in the initial post…let me know if you looking for any thing other than that…2ndly. The log is exactly same as from the log file…I was trying to migrate the volume which was created with NFS store to Linstor

And yes I was able to create the Linstor Resource directly…and confirmed the status with drbdadm status.

Sorry for the confusion, I was asking for the LINSTOR logs.

Something like this during the relevant time frame might be helpful:

grep -e Controller -e Satellite /var/log/messages