High Performance Software-Defined Block Storage for container, cloud and virtualisation. Fully integrated with Docker, Kubernetes, Openstack, Proxmox etc.
Latest Linstor/DRBD stack. When creating a new resource/volume definition, the new resource does not seem to pickup the "storage-pool" value from RG. When manually specifying "storage-pool" at the resource creation, then it works as expected.
root@linstor1:~# dpkg -l|grep linstor
ii linstor-client 1.20.0-1ppa1~jammy1 all Linstor client command line tool
ii linstor-common 1.25.0~rc.1-1ppa1~jammy1 all DRBD distributed resource management utility
ii linstor-controller 1.25.0~rc.1-1ppa1~jammy1 all DRBD distributed resource management utility
ii linstor-satellite 1.25.0~rc.1-1ppa1~jammy1 all DRBD distributed resource management utility
ii python-linstor 1.20.0-1ppa1~jammy1 all Linstor python api library
LINSTOR ==> rd c test01 --resource-group iscsi_group2
SUCCESS:
Description:
New resource definition 'test01' created.
Details:
Resource definition 'test01' UUID is: 40039b52-a28c-47cb-97d1-410d1eb00a33
LINSTOR ==> rd l
╭─────────────────────────────────────────────╮
┊ ResourceName ┊ Port ┊ ResourceGroup ┊ State ┊
╞═════════════════════════════════════════════╡
┊ linstor_db ┊ 7000 ┊ DfltRscGrp ┊ ok ┊
┊ nfs1 ┊ 7001 ┊ iscsi_group ┊ ok ┊
┊ test01 ┊ ┊ iscsi_group2 ┊ ok ┊
╰─────────────────────────────────────────────╯
LINSTOR ==> r c linstor3 test01
INFO:
Updated test01 DRBD auto verify algorithm to 'crct10dif-pclmul'
SUCCESS:
Description:
New resource 'test01' on node 'linstor3' registered.
Details:
Resource 'test01' on node 'linstor3' UUID is: 94ee32a7-6574-4f48-9532-541bd877799a
SUCCESS:
Created resource 'test01' on 'linstor3'
WARNING:
No volumes have been defined for resource 'test01'
LINSTOR ==> vd c test01 1G
ERROR:
Description:
The storage pool 'null' for resource 'test01' for volume number '0' is not deployed on node 'linstor3'.
Cause:
Dependency not found
Details:
The resource which should be deployed had at least one volume definition (volume number '0') which LINSTOR tried to automatically create. The storage pool name for this new volume was looked for, in order, in: the properties of the resource, volume definition, resource definition and node, and finally in a system wide default storage pool name defined by the LINSTOR Controller.
Volume definitions for resource definition 'test01'
Show reports:
linstor error-reports show 6533B693-00000-000006
LINSTOR ==> r d linstor3 test01
SUCCESS:
Description:
Node: linstor3, Resource: test01 preparing for deletion.
Details:
Node: linstor3, Resource: test01 UUID is: 94ee32a7-6574-4f48-9532-541bd877799a
SUCCESS:
Preparing deletion of resource on 'linstor3'
SUCCESS:
Description:
Node: linstor3, Resource: test01 marked for deletion.
Details:
Node: linstor3, Resource: test01 UUID is: 94ee32a7-6574-4f48-9532-541bd877799a
SUCCESS:
Cleaning up 'test01' on 'linstor3'
SUCCESS:
Description:
Node: linstor3, Resource: test01 deletion complete.
Details:
Node: linstor3, Resource: test01 UUID was: 94ee32a7-6574-4f48-9532-541bd877799a
LINSTOR ==> r c linstor3 test01 --storage-pool pool2
SUCCESS:
Successfully set property key(s): StorPoolName
SUCCESS:
Description:
New resource 'test01' on node 'linstor3' registered.
Details:
Resource 'test01' on node 'linstor3' UUID is: d9338981-c6ed-4203-9793-774e425aeb56
SUCCESS:
Created resource 'test01' on 'linstor3'
WARNING:
No volumes have been defined for resource 'test01'
LINSTOR ==> vd c test01 1G
SUCCESS:
New volume definition with number '0' of resource definition 'test01' created.
SUCCESS:
Created volume for resource 'test01' on 'linstor3'
Latest Linstor/DRBD stack. When creating a new resource/volume definition, the new resource does not seem to pickup the "storage-pool" value from RG. When manually specifying "storage-pool" at the resource creation, then it works as expected.