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

Installation fails with 1 master and 2 workers as the console deployment set the number of replicas based on the InfrastructureTopology rather than the ControlPlaneTopology

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Undefined
    • None
    • 4.12.z
    • Management Console
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None

    Description

      This is a clone of issue OCPBUGS-31619. The following is the description of the original issue:

      Description of problem:

      The node selector for the console deployment requires deploying it on the master nodes, The node selector for the console deployment requires deploying it on the master nodes, while the replica count is determined by the infrastructureTopology, which primarily tracks the workers' setup.
      
      When an OpenShift cluster is installed with a single master node and multiple workers, this leads the console deployment to request 2 replicas as infrastructureTopology is set to HighlyAvailable. Instead, ControlPlaneTopology is set to SingleReplica as expected.
      
      

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

      4.16

      How reproducible:

      Always    

      Steps to Reproduce:

          1. Install an openshift cluster with 1 master and 2 workers
      

      Actual results:

      The installation fails as the replicas for the console deployment is set to 2.
      
        apiVersion: config.openshift.io/v1
        kind: Infrastructure
        metadata:
          creationTimestamp: "2024-01-18T08:34:47Z"
          generation: 1
          name: cluster
          resourceVersion: "517"
          uid: d89e60b4-2d9c-4867-a2f8-6e80207dc6b8
        spec:
          cloudConfig:
            key: config
            name: cloud-provider-config
          platformSpec:
            aws: {}
            type: AWS
        status:
          apiServerInternalURI: https://api-int.adstefa-a12.qe.devcluster.openshift.com:6443
          apiServerURL: https://api.adstefa-a12.qe.devcluster.openshift.com:6443
          controlPlaneTopology: SingleReplica
          cpuPartitioning: None
          etcdDiscoveryDomain: ""
          infrastructureName: adstefa-a12-6wlvm
          infrastructureTopology: HighlyAvailable
          platform: AWS
          platformStatus:
            aws:
              region: us-east-2
            type: AWS
      
      
      apiVersion: apps/v1
      kind: Deployment
      metadata:
        annotations:
         .... 
        creationTimestamp: "2024-01-18T08:54:23Z"
        generation: 3
        labels:
          app: console
          component: ui
        name: console
        namespace: openshift-console
      spec:
        progressDeadlineSeconds: 600
        replicas: 2
      
      
      

      Expected results:

      The replica is set to 1, tracking the ControlPlaneTopology value instead of hte infrastructureTopology.

      Additional info:

          

      Attachments

        Issue Links

          Activity

            People

              jhadvig@redhat.com Jakub Hadvig
              openshift-crt-jira-prow OpenShift Prow Bot
              YaDan Pei YaDan Pei
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: