Uploaded image for project: 'Data Foundation Bugs'
  1. Data Foundation Bugs
  2. DFBUGS-864

osd pods are not coming up for odf 4.18 provider clusters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Critical Critical
    • odf-4.18
    • odf-4.18
    • rook
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • Important
    • Yes

      Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:
      osd pods are not coming up for odf 4.18 provider clusters

      storage-cluster yaml:
      ```
      apiVersion: ocs.openshift.io/v1
      kind: StorageCluster
      metadata:
      name: ocs-storagecluster
      namespace: openshift-storage
      spec:
      allowRemoteStorageConsumers: true
      arbiter: {}
      encryption:
      kms: {}
      externalStorage: {}
      flexibleScaling: true
      hostNetwork: true
      managedResources:
      cephBlockPools:
      disableSnapshotClass: true
      disableStorageClass: true
      cephCluster: {}
      cephConfig: {}
      cephDashboard: {}
      cephFilesystems:
      disableSnapshotClass: true
      disableStorageClass: true
      cephNonResilientPools: {}
      cephObjectStoreUsers: {}
      cephObjectStores:
      hostNetwork: false
      cephRBDMirror: {}
      cephToolbox: {}
      mirroring: {}
      monDataDirHostPath: /var/lib/rook
      nodeTopologies: {}
      providerAPIServerServiceType: NodePort
      storageDeviceSets:

      • config: {}
        count: 3
        dataPVCTemplate:
        metadata: {}
        spec:
        accessModes:
      • ReadWriteOnce
        resources:
        requests:
        storage: 256Gi
        storageClassName: localblock

      volumeMode: Block
      status: {}
      deviceClass: ssd
      name: local-storage-deviceset
      placement: {}
      preparePlacement: {}
      replica: 3
      resources: {}```
      The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI): ibm Bare Metal

       

      The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc): Provider

       

       

      The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):

      OCP: 4.18.0-ec.3
      ODF: 4.18.0-53.stable <also faced for 4.18.0-49.stable>

       

      Does this issue impact your ability to continue to work with the product?
      Yes

       

       

      Is there any workaround available to the best of your knowledge?
      No

       

      Can this issue be reproduced? If so, please provide the hit rate: Yes

       

       

      Can this issue be reproduced from the UI? yes

      If this is a regression, please provide more details to justify this: NA

      Steps to Reproduce:

      1. Deploy a provider cluster with ocp 4.18

      2. Install odf 4.18 on the cluster

      3. Create storage cluster
      4. Check the storage-cluster status and osd pods are created or not

      The exact date and time when the issue was observed, including timezone details:
      Observed today, 15th Nov 2024

       

      Actual results:

      osd pods are not coming up for odf 4.18 provider clusters

       

      Expected results:

      osd pods should be created successfully.

      Logs collected and log location:

      must-gather logs: http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/DFBUGS-864/

      Additional info:

       

              sapillai Santosh Pillai
              ammahapa@redhat.com Amrita Mahapatra
              Votes:
              0 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: