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

[cee.Next]Adding same value to the Vmware plugin on OCP console should not lead to nodes reboot

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, after you submitted the same value into the {vmw-first} configuration dialog, cluster nodes unintentionally rebooted. With this release, nodes reboot after you enter new values into the dialog and not the same values.(link:https://issues.redhat.com/browse/OCPBUGS-33938[*OCPBUGS-33938*])
      Show
      * Previously, after you submitted the same value into the {vmw-first} configuration dialog, cluster nodes unintentionally rebooted. With this release, nodes reboot after you enter new values into the dialog and not the same values.(link: https://issues.redhat.com/browse/OCPBUGS-33938 [* OCPBUGS-33938 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-31613. The following is the description of the original issue:
      —
      Description of problem:

      On OCP console if we added a parameter related to VMware,add the same value back again and click on save the nodes are rebooted

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

          4.14

      How reproducible:

      Steps to Reproduce:

          1. On any 4.14+ cluster go to ocp console page
    2. Click on the vmware plugin
    3. Edit any parameter and add the same value again.
    4. Click on save

      Actual results:

          The nodes reboot to pickup change

      Expected results:

       nodes should not reboot if the same values are entered

      Additional info:

              rawagner@redhat.com Rastislav Wagner
              openshift-crt-jira-prow OpenShift Prow Bot
              YaDan Pei YaDan Pei
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: