rook: Cannot make use of RADOS namespace for external cluster with EC block pool

When using an erasure-coded data pool for RBDs, there must exist an additional replicated metadata pool. Since Ceph does not support RADOS namespaces in EC pools, I only created it in the metadata pool. When I pass the flags

--rbd-data-pool-name ceph-block
--rbd-metadata-ec-pool-name ceph-block-metadata # afaik metadata pool can't be EC so the name is a bit misleading
--rados-namespace staging

to create-external-cluster-resources.py, the script looks for namespace staging in the EC data pool ceph-block (where it cannot exist) instead of the metadata pool.

How can I use tenant isolation with RADOS namespaces for external clusters when the data pool for RBDs is erasure-coded?

Thanks in advance!

Is this a bug report or feature request?

  • Bug Report

Deviation from expected behavior: create-external-cluster-resources.py script fails with

The provided rados Namespace, ‘staging’, is not found in the pool ‘ceph-block’

Expected behavior: To my understanding, the script should look for the provided namespace in the metadata block pool if the data pool is erasure-coded (please correct me if I am wrong here)

How to reproduce it: Apply below resources in source cluster and try to extract information for a Rook external consumer cluster with

python3 create-external-cluster-resources.py --rbd-data-pool-name ceph-block --rbd-metadata-ec-pool-name ceph-block-metadata --rados-namespace staging

File(s) to submit: Resources created in the source cluster:

# metadata pool (for use in consumer StorageClass.parameters.pool)
apiVersion: ceph.rook.io/v1
kind: CephBlockPool
metadata:
  name: ceph-block-metadata
spec:
  replicated:
    size: 3
---
# data pool (for use in consumer StorageClass.parameters.dataPool)
apiVersion: ceph.rook.io/v1
kind: CephBlockPool
metadata:
  name: ceph-block
spec:
  erasureCoded:
    codingChunks: 1
    dataChunks: 2
---
apiVersion: ceph.rook.io/v1
kind: CephBlockPoolRadosNamespace
metadata:
  name: staging
spec:
  blockPoolName: ceph-block-metadata
  name: staging

Environment: Source cluster:

  • OS: Ubuntu 20.04
  • Kernel: 5.15.0
  • Rook version: 1.13.3
  • Storage backend version: 18.2.1
  • Kubernetes version: 1.25
  • Kubernetes cluster type: bare metal

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 27 (15 by maintainers)

Commits related to this issue

Most upvoted comments

@bauerjs1 yes that is moreover the internal mode settings,

With this fix https://github.com/rook/rook/pull/13856 you can use just v2 port

@bauerjs1 Something seems to be wrong, please wait for @parth-gr to response he will back in next week. Thanks