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

machineConfigPool without nodes assigned stuck at 0% progress

    XMLWordPrintable

Details

    • ?
    • Low
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      When a custom machineConfigPool is created and no node is associated with it, the mcp remains at 0% progress.

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

       

      How reproducible:

      100%

      Steps to Reproduce:

      1. Create a custom mcp:
~~~
cat << EOF | oc create -f -
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfigPool
metadata:
  name: custom
spec:
  machineConfigSelector:
    matchExpressions:
      - {key: machineconfiguration.openshift.io/role, operator: In, values: [worker,custom]}
  nodeSelector:
    matchLabels:
      node-role.kubernetes.io/custom: "" 
EOF
~~~

      Actual results:

      The mcp is visible from the from "Administrator view > Cluster Settings > Details" at 0% progress

      Expected results:

      It shouldn't be stuck at 0%

      Additional info:

       

       

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2173 [release-4.9] machineConfigPool without nodes assigned stuck at 0% progress

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1463 machineConfigPool without nodes assigned stuck at 0% progress

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1463 machineConfigPool without nodes assigned stuck at 0% progress

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2173 [release-4.9] machineConfigPool without nodes assigned stuck at 0% progress

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/console#12061: OCPBUGS-938: do not show NodesUpdateGroup if there are 0 nodes

          Activity

            People

              rhn-engineering-rhamilto Robb Hamilton
              rhn-support-gmeghnag Gabriel Meghnagi
              YaDan Pei YaDan Pei
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: