Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-6215

Edit Deployment form drops strategy data when switching type

XMLWordPrintable

    • ODC Sprint 205, ODC Sprint 206, ODC Sprint 207
    • Low

      Description of problem:

      When the user edit a deployment (via "Edit Deployment" or "Edit DeploymentConfig", not "Edit <application-name>") and changes the strategy type to the current value the sub-form data are removed.

      If the user switches to another type and then back to the previously selected type, the form data are replaced with the default (always none?) configuration as well.

      Prerequisites (if any, like setup, operators/versions):

      None

      Steps to Reproduce

      1. Switch to developer perspective, add page, import from git
      2. Enter a git URL and create the Deployment
      3. Right click the Deployment in topology and select "Edit Deployment"
      4. Change "Strategy type" via the dropdown

      Actual results:

      1. When switching "Strategy type" to the current value the sub form is cleared. (Rolling Update has some sub configurations.)
      2. When switching "Strategy type" to another value and then back also cleared the current values. (Switching from Rolling Update to Recreate and back for example.)

      Expected results:

      1. When switching "Strategy type" to the current value the sub form should keep its data.
      2. When switching "Strategy type" to another value and then back the latest values should be restored again (latest input from the user, not the initial values).

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      4.9 (tested with console commit 10da2737b412748a75ca1c9e38eb14b83b71cab6)

      Additional info:

      None

              dsantra12 Debsmita Santra
              cjerolim Christoph Jerolimov
              Vikram Raj Vikram Raj
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: