The default storageclasses(consumer) and storageclassclaims(consumer and provider) are missing on a consumer cluster where one storageclient is present. This is now observed in ODF to ODF on ROSA configuration without agent. ODF version is 4.13.0-130.stable. The storageclasses(on consumer) and storageclassclaims (provider and consumer) were getting created with the earlier builds of ODF 4.13.0. The storagecluster on provider contain storageprofile parameters. Storageclient is in Ready state. $ oc get storageclient NAME PHASE CONSUMER ocs-storageclient Connected 1ff1a228-caad-423e-b5b5-27d90f0ac4aa $ oc get storageconsumer storageconsumer-6ff74037-f6a7-4a74-aabb-6e71b332d597 -o yaml apiVersion: ocs.openshift.io/v1alpha1 kind: StorageConsumer metadata: annotations: ocs.openshift.io/provider-onboarding-ticket: eyJpZCI6IjU2OWFhNjliLWMzNTMtNDlkOC05MjJlLTZlMGRmOTMyOTE3MiIsImV4cGlyYXRpb25EYXRlIjoiMTY4MTI5OTM0NSJ9.xAoncEAMeG6Zq6Sr74N+djP4zEDxvqx+qKzjNi2lVxnkBFeEMcaM85na0q6qYmkiQlj58jV7aUR0IQxQRYNZHR2thsjgvJ9V4Xy4my95kZ7Pbg0JxTfOmsF+QDzqdCtLarZno/H1bNKDJCWOuEPWKP86YldoVKGnFsGIPffHxFbHbLfMQ6iJ3yPMvSflz8VXVDQ5h73qM9Yw4xMKNFXnMmRLCPCmnsqeL4gwAkZyQFWI47OSW7Ig1ADDvJQ7X6md2E20oWUfXsyCbY9D/Fv+X/gKk3jYs12lIf8GwQCGotxxkPjbkK9v8vrbiMX+YH8yWc1Ww6ySctqcfyBYph9CGMuc0WK/p+LU+EaQretYDpTBPUTygKrJLWN7cc8R4CmuoM/5EBPbsc520qNdTDFX4wYzDk3p5Ef12Um1LoimNxByC1HmxiBpRoDopse9kNX6fO1O5tZffI3qnROCFT4xNw8yymIiLyVVqxjxhq2NgHPpMxGLvoLtGzV1Gg8fxId1boPEG+3JNC3uNwsxxS0IPwbRgOqDgkNZXRk+AD6FkTGMiRCpQKJf0KKomprRTuTYV7HgOk2589idJTyE0r7fWEiQRCfCngoB3IfHrcoEYZI4V30LFg/WR5BFW43x7dUkK72Ka0S4nPaoKjHsms8IUGQ1ZxnDQ250YmS+fTwy6G4= creationTimestamp: "2023-04-10T11:40:46Z" generation: 2 name: storageconsumer-6ff74037-f6a7-4a74-aabb-6e71b332d597 namespace: openshift-storage resourceVersion: "227390" uid: 1ff1a228-caad-423e-b5b5-27d90f0ac4aa spec: capacity: 1T enable: true status: cephResources: - kind: CephClient name: a0527a4403b5d47486e00bced41f9ec9 status: Ready grantedCapacity: 1T lastHeartbeat: "2023-04-10T12:58:03Z" state: Ready $ oc get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE gp2 kubernetes.io/aws-ebs Delete WaitForFirstConsumer true 4h36m gp2-csi ebs.csi.aws.com Delete WaitForFirstConsumer true 4h33m gp3 (default) ebs.csi.aws.com Delete WaitForFirstConsumer true 4h36m gp3-csi ebs.csi.aws.com Delete WaitForFirstConsumer true 4h33m Version: OCP 4.12.9 Consumer: $ oc get csv NAME DISPLAY VERSION REPLACES PHASE configure-alertmanager-operator.v0.1.520-680d50b configure-alertmanager-operator 0.1.520-680d50b configure-alertmanager-operator.v0.1.518-ec4c3cd Succeeded observability-operator.v0.0.20 Observability Operator 0.0.20 observability-operator.v0.0.19 Succeeded ocs-client-operator.v4.13.0-130.stable OpenShift Data Foundation Client 4.13.0-130.stable Succeeded odf-csi-addons-operator.v4.13.0-130.stable CSI Addons 4.13.0-130.stable Succeeded route-monitor-operator.v0.1.493-a866e7c Route Monitor Operator 0.1.493-a866e7c route-monitor-operator.v0.1.489-7d9fe90 Succeeded Provider: $ oc get csv NAME DISPLAY VERSION REPLACES PHASE configure-alertmanager-operator.v0.1.520-680d50b configure-alertmanager-operator 0.1.520-680d50b configure-alertmanager-operator.v0.1.518-ec4c3cd Succeeded mcg-operator.v4.13.0-130.stable NooBaa Operator 4.13.0-130.stable Succeeded observability-operator.v0.0.20 Observability Operator 0.0.20 observability-operator.v0.0.19 Succeeded ocs-operator.v4.13.0-130.stable OpenShift Container Storage 4.13.0-130.stable Succeeded odf-csi-addons-operator.v4.13.0-130.stable CSI Addons 4.13.0-130.stable Succeeded odf-operator.v4.13.0-130.stable OpenShift Data Foundation 4.13.0-130.stable Succeeded route-monitor-operator.v0.1.493-a866e7c Route Monitor Operator 0.1.493-a866e7c route-monitor-operator.v0.1.489-7d9fe90 Succeeded On provider: $ oc get storagecluster -o yaml | grep storageProfiles -A 13 storageProfiles: - blockPoolConfiguration: parameters: pg_autoscale_mode: "on" pg_num: "128" pgp_num: "128" deviceClass: ssd name: default sharedFilesystemConfiguration: parameters: pg_autoscale_mode: "on" pg_num: "128" pgp_num: "128" status: $ oc get storagecluster -o yaml | grep defaultStorageProfile defaultStorageProfile: default
Yes , the agent on the consumer will create default storageclassclaims.
Yes, currently can be closed as NOTABUG because DF client build is not yet released for testing