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

infrastructures.config.openshift.io spec and status do not sync after removing 2nd VIP

XMLWordPrintable

    • Quality / Stability / Reliability
    • True
    • Hide

      Pending impact assessment based on whether the modification of 2nd VIP works or not

      Show
      Pending impact assessment based on whether the modification of 2nd VIP works or not
    • None
    • Important
    • No
    • None
    • None
    • Proposed
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:
      Deleting second VIP doesn't seem to work.

      apiVersion: config.openshift.io/v1
      kind: Infrastructure
      metadata:
        creationTimestamp: "2024-03-25T12:13:42Z"
        generation: 2
        managedFields:
        - apiVersion: config.openshift.io/v1
          fieldsType: FieldsV1
          fieldsV1:
            f:status:
              f:apiServerInternalURI: {}
              f:apiServerURL: {}
              f:controlPlaneTopology: {}
              f:cpuPartitioning: {}
              f:etcdDiscoveryDomain: {}
              f:infrastructureName: {}
              f:infrastructureTopology: {}
              f:platform: {}
              f:platformStatus:
                f:baremetal:
                  f:apiServerInternalIP: {}
                  f:apiServerInternalIPs:
                    v:"192.168.123.5": {}
                  f:ingressIP: {}
                  f:ingressIPs:
                    v:"192.168.123.10": {}
                  f:loadBalancer:
                    f:type: {}
                  f:machineNetworks:
                    v:"192.168.123.0/24": {}
                    v:"fd2e:6f44:5dd8::/64": {}
                f:type: {}
          manager: cluster-network-operator/infrastructureconfig
          operation: Apply
          subresource: status
          time: "2024-03-26T16:26:48Z"
        - apiVersion: config.openshift.io/v1
          fieldsType: FieldsV1
          fieldsV1:
            f:spec:
              .: {}
              f:cloudConfig:
                .: {}
                f:name: {}
              f:platformSpec:
                .: {}
                f:baremetal:
                  .: {}
                  f:apiServerInternalIPs:
                    .: {}
                    v:"192.168.123.5": {}
                  f:ingressIPs:
                    .: {}
                    v:"192.168.123.10": {}
                  f:machineNetworks:
                    .: {}
                    v:"192.168.123.0/24": {}
                    v:"fd2e:6f44:5dd8::/64": {}
                f:type: {}
          manager: cluster-bootstrap
          operation: Update
          time: "2024-03-25T12:13:42Z"
        - apiVersion: config.openshift.io/v1
          fieldsType: FieldsV1
          fieldsV1:
            f:status:
              .: {}
              f:apiServerInternalURI: {}
              f:apiServerURL: {}
              f:controlPlaneTopology: {}
              f:cpuPartitioning: {}
              f:etcdDiscoveryDomain: {}
              f:infrastructureName: {}
              f:infrastructureTopology: {}
              f:platform: {}
              f:platformStatus:
                .: {}
                f:baremetal:
                  .: {}
                  f:apiServerInternalIP: {}
                  f:apiServerInternalIPs:
                    .: {}
                    v:"192.168.123.5": {}
                    v:"fd2e:6f44:5dd8::5": {}
                  f:ingressIP: {}
                  f:ingressIPs:
                    .: {}
                    v:"192.168.123.10": {}
                    v:"fd2e:6f44:5dd8::a": {}
                  f:loadBalancer:
                    .: {}
                    f:type: {}
                  f:machineNetworks:
                    .: {}
                    v:"192.168.123.0/24": {}
                    v:"fd2e:6f44:5dd8::/64": {}
                f:type: {}
          manager: cluster-bootstrap
          operation: Update
          subresource: status
          time: "2024-03-25T12:13:42Z"
        name: cluster
        resourceVersion: "503129"
        uid: 5cc6788c-9e4b-417a-9a88-25f0c4d6a647
      spec:
        cloudConfig:
          name: ""
        platformSpec:
          baremetal:
            apiServerInternalIPs:
            - 192.168.123.5
            ingressIPs:
            - 192.168.123.10
            machineNetworks:
            - 192.168.123.0/24
            - fd2e:6f44:5dd8::/64
          type: BareMetal
      status:
        platform: BareMetal
        platformStatus:
          baremetal:
            apiServerInternalIP: 192.168.123.5
            apiServerInternalIPs:
            - 192.168.123.5
            - fd2e:6f44:5dd8::5
            ingressIP: 192.168.123.10
            ingressIPs:
            - 192.168.123.10
            - fd2e:6f44:5dd8::a
            loadBalancer:
              type: OpenShiftManagedDefault
            machineNetworks:
            - 192.168.123.0/24
            - fd2e:6f44:5dd8::/64
          type: BareMetal
       

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

      4.16.0-0.nightly-2024-03-24-191602
          

      How reproducible:

      Always
          

      Steps to Reproduce:

          1. oc patch infrastructure cluster --type='json' -p='[{"op": "remove", "path": "/spec/platformSpec/baremetal/apiServerInternalIPs/1"}, {"op": "remove", "path": "/spec/platformSpec/baremetal/ingressIPs/1"}]'
          2.
          3.
          

      Actual results:

      infrastructures.config.openshift.io/cluster status is unchanged.

      Expected results:

      infrastructures.config.openshift.io/cluster status matches spec

      Additional info:

              mkowalsk@redhat.com Mat Kowalski
              rbrattai@redhat.com Ross Brattain
              None
              None
              Anurag Saxena Anurag Saxena
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: