Bug 2325395 - Namespace creation with Kb size is not supported
Summary: Namespace creation with Kb size is not supported
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: NVMeOF
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 8.1
Assignee: Aviv Caro
QA Contact: Manohar Murthy
ceph-doc-bot
URL:
Whiteboard:
Depends On:
Blocks: 2325397
TreeView+ depends on / blocked
 
Reported: 2024-11-12 08:21 UTC by Sunil Kumar Nagaraju
Modified: 2024-11-13 12:33 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2325397 (view as bug list)
Environment:
Last Closed: 2024-11-13 12:30:29 UTC
Embargoed:


Attachments (Terms of Use)
Namespace-in-KB (1.06 MB, image/png)
2024-11-12 08:21 UTC, Sunil Kumar Nagaraju
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-10222 0 None None None 2024-11-12 08:24:18 UTC

Description Sunil Kumar Nagaraju 2024-11-12 08:21:24 UTC
Created attachment 2057255 [details]
Namespace-in-KB

Description of problem:

Namespace creation with Kb size is not supported, so if it is not supported it should be taken out from help usage.

Note: Ceph dashboard also has same issue, attaching screenshot for reference.


[root@ceph-sunilkumar-00-61s1lj-node6 ~]# nm --server-address 10.0.66.43 namespace add -n nqn.2016-06.io.spdk:cnode2 --rbd-pool rbd --rbd-create-image --rbd-image sub2-image-111 --size 1 --help
usage: python3 -m control.cli namespace add [-h] --subsystem SUBSYSTEM
                                            [--uuid UUID] [--nsid NSID]
                                            --rbd-pool RBD_POOL --rbd-image
                                            RBD_IMAGE [--rbd-create-image]
                                            [--block-size BLOCK_SIZE]
                                            [--load-balancing-group LOAD_BALANCING_GROUP]
                                            [--size SIZE] [--force]

Create a namespace

optional arguments:
  -h, --help            show this help message and exit
  --subsystem SUBSYSTEM, -n SUBSYSTEM
                        Subsystem NQN
  --uuid UUID, -u UUID  UUID
  --nsid NSID           Namespace ID
  --rbd-pool RBD_POOL, -p RBD_POOL
                        RBD pool name
  --rbd-image RBD_IMAGE, -i RBD_IMAGE
                        RBD image name
  --rbd-create-image, -c
                        Create RBD image if needed
  --block-size BLOCK_SIZE, -s BLOCK_SIZE
                        Block size
  --load-balancing-group LOAD_BALANCING_GROUP, -l LOAD_BALANCING_GROUP
                        Load balancing group
  --size SIZE           Size in bytes or specified unit (K, KB, M, MB, G, GB,
                        T, TB, P, PB)
  --force               Create a namespace even its image is already used by
                        another namespace
[root@ceph-sunilkumar-00-61s1lj-node6 ~]# nm --server-address 10.0.66.43 namespace add -n nqn.2016-06.io.spdk:cnode2 --rbd-pool rbd --rbd-create-image --rbd-image sub2-image-111 --size 1K
usage: python3 -m control.cli [-h] [--format {text,json,yaml,plain,python}]
                              [--output {log,stdio}]
                              [--log-level {debug,DEBUG,info,INFO,warning,WARNING,error,ERROR,critical,CRITICAL}]
                              [--server-address SERVER_ADDRESS]
                              [--server-port SERVER_PORT]
                              [--client-key CLIENT_KEY]
                              [--client-cert CLIENT_CERT]
                              [--server-cert SERVER_CERT] [--verbose]
                              {version,gw,spdk_log_level,subsystem,listener,host,connection,namespace,ns,get_subsystems}
                              ...
error: size value must be aligned to MiBs
[root@ceph-sunilkumar-00-61s1lj-node6 ~]# nm --server-address 10.0.66.43 namespace add -n nqn.2016-06.io.spdk:cnode2 --rbd-pool rbd --rbd-create-image --rbd-image sub2-image-111 --size 1KB
usage: python3 -m control.cli [-h] [--format {text,json,yaml,plain,python}]
                              [--output {log,stdio}]
                              [--log-level {debug,DEBUG,info,INFO,warning,WARNING,error,ERROR,critical,CRITICAL}]
                              [--server-address SERVER_ADDRESS]
                              [--server-port SERVER_PORT]
                              [--client-key CLIENT_KEY]
                              [--client-cert CLIENT_CERT]
                              [--server-cert SERVER_CERT] [--verbose]
                              {version,gw,spdk_log_level,subsystem,listener,host,connection,namespace,ns,get_subsystems}
                              ...
error: size value must be aligned to MiBs


[root@ceph-sunilkumar-00-61s1lj-node6 ~]# alias nm="podman run --rm cp.stg.icr.io/cp/ibm-ceph/nvmeof-cli-rhel9:1.3.3-1"
[root@ceph-sunilkumar-00-61s1lj-node6 ~]# nm --server-address 10.0.66.43 namespace add -n nqn.2016-06.io.spdk:cnode2 --rbd-pool rbd --rbd-create-image --rbd-image sub2-image-111 --size 1KB
Trying to pull cp.stg.icr.io/cp/ibm-ceph/nvmeof-cli-rhel9:1.3.3-1...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 4d5d1cbd7ece skipped: already exists
Copying blob c765b3f71f66 done   |
Copying config c1bf8f3909 done   |
Writing manifest to image destination
Storing signatures
usage: python3 -m control.cli [-h] [--format {text,json,yaml,plain,python}]
                              [--output {log,stdio}]
                              [--log-level {debug,DEBUG,info,INFO,warning,WARNING,error,ERROR,critical,CRITICAL}]
                              [--server-address SERVER_ADDRESS]
                              [--server-port SERVER_PORT]
                              [--client-key CLIENT_KEY]
                              [--client-cert CLIENT_CERT]
                              [--server-cert SERVER_CERT] [--verbose]
                              {version,gw,spdk_log_level,subsystem,listener,host,connection,namespace,ns,get_subsystems}
                              ...
error: size value must be aligned to MiBs


Version-Release number of selected component (if applicable): 19.2.0-52
8.0
Nvme 1.3.3-6
NVMe 1.3.3-1

How reproducible: always


Note You need to log in before you can comment on or make changes to this bug.