Skip to content

RDR setup with LSO: ODF deployment skipped on primary cluster, fails on secondary cluster due to missing node labels #14880

@sidhant-agrawal

Description

@sidhant-agrawal

Summary

When deploying RDR setup with LSO configuration, ODF installation is skipped on the primary managed cluster and incorrectly proceeds on the secondary managed cluster without proper node labeling, causing the deployment to fail.

Environment

  • OCP Version: 4.17-ga
  • OCS-CI Branch: release-4.17
  • Platform: vSphere (UPI, LSO VMDK)
  • Deployment: RDR with 3 clusters (ACM hub + 2 managed clusters)
  • Cluster conf used: conf/deployment/vsphere/upi_1az_rhcos_vsan_lso_vmdk_3m_3w.yaml

Steps to Reproduce

  1. Trigger RDR deployment job with LSO based deployment configuration for two managed clusters (Primary + Secondary)
  2. Let the DR - Install ODF stage execute

Jenkins Job:

Metadata

Metadata

Assignees

No one assigned

    Labels

    DRMetro and Regional DR related PRsbugSomething isn't workingteam/ecosystemEcosystem team related issues/PRs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions