Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-60085

Machine objects don't get labeled with region and zone after defining a new failureDomain in a vCenter cluster

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • Unspecified
    • None
    • None
    • None
    • CLOUD Sprint 275, CLOUD Sprint 276, CLOUD Sprint 277, CLOUD Sprint 278
    • 4
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      When coming from an Openshift cluster with no failureDomains defined, after changing the infrastructure object with new failureDomains, the Machine objects for new and old Nodes don't properly get updated with the new regions and zones

      Version-Release number of selected component (if applicable):

      4.16.z

      How reproducible:

          Reproduced it twice, once in 4.16 and once in 4.19

      Steps to Reproduce:

          1. Create a cluster with zero or one failureDomain
    2. Edit the infrastructure object as mentioned in the documentation [1]
    3. Create a new MachineSet to observe if the Machines get assigned with the right labels.

      [1]: Multiple regions and zones configuration for a cluster on VMware vSphere

      Actual results:

          When checking the Machine objects, the labels for zone and region of both the new and old Machines are empty.

      Expected results:

          The labels should get assigned to the corresponding zone and region fetching them from the respective vCenter's tags.

      Additional info:

              rh-ee-cschlott Christian Schlotter
              rhn-support-tdomingu Tomas Dominguez
              None
              None
              Milind Yadav Milind Yadav
              None
              Cisco - Waas Confidential Group, Iron Systems Confidential Group, JFrog Confidential Group, JP Morgan Chase Confidential Group, Jumptrading Confidential Group, Juniper Confidential Group, Kaloom Confidential Group, Kove Confidential Group, Kraftway Confidential Group, LINBIT Confidential Group, Lawrence Livermore National Laboratory Confidential Group, Lenovo Confidential Group, Marvell Confidential Group, Maxta Confidential Group, McAfee Confidential Group, Microchip Confidential Group, Micron Confidential Group, Microsemi Confidential Group, Microsoft Confidential Group, Motorola Solutions Confidential Group, NEC Confidential Group, NVIDIA (Mellanox) Confidential Group, NetApp Confidential Group, Netronome Confidential Group, Nokia Confidential Group, Nutanix Confidential Group, Nvidia Confidential Group, OnLogic Confidential Group, Oracle Confidential Group, Orange Confidential Group, PCS Confidential Group, PMC-Sierra Confidential Group, Palo Alto Networks Confidential Group, Panasas Confidential Group, Penguin Computing Confidential Group, Pensando Confidential Group, Promise Confidential Group, Pure Storage Confidential Group, Qlogic Confidential Group - Please use Marvell Confidential Group instead, Qualcomm Confidential Group, Quanta Confidential Group, Quantum Confidential Group, RLX Technologies Confidential Group, Rackable Systems Confidential Group, Red Hat Bugzilla Authorized, Rubrik Confidential Group, SAP Confidential Group, SAS Confidential Group, SEP Confidential Group, Sai Infosystems Confidential Group, Samsung Confidential Group, SanDisk Confidential Group, Seagate Confidential Group, SiPearl Confidential Group, Silicom Confidential Group, Softiron Confidential Group, Solarflare Confidential Group, Spirent Confidential Group, Splunk Confidential Group, Storware Confidential Group, Stratus Confidential Group, Sugon Confidential Group, Sun Confidential Group, Super Micro Computers Confidential Group, Sybase Confidential Group, Symantec Confidential Group, Synopsys Confidential Group, Sysdig Confidential Group, TSX/RH Confidential Group, Telefonica Confidential Group, Texas Instruments Confidential Group, Thales Confidential Group, Toshiba Confidential Group, Trilio Confidential Group, Unisys Confidential Group, VMware Confidential Group, VVDN Confidential Group, Veeam Confidential Group, Veritas Confidential Group, VerizonWireless Confidential Group, Wacom Confidential Group, Western Digital Confidential Group, Wind River Confidential Group, Wipro Limited Confidential Group, Wiwynn Confidential Group, Xilinx Confidential Group, Yahoo Confidential Group, ZTE Confidential Group, Zettaset Confidential Group
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: