Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-41846

Changes in configuration tab does not save to YAML tab

    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • CNV v4.16.0.rhel9-2575
    • ---
    • ---
    • No

      Description of problem:

      Changes in configuration tab does not save to YAML tab
      

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

      
      

      How reproducible:

      
      

      Steps to Reproduce:

      1. Create VM from instanceType 
      2. Click Customize VM
      3. Make some changes in configuration tab
      4. Click YAML tab
      

      Actual results:

      Changes in configuration does not save to YAML tab
      

      Expected results:

      Changes in configuration is visible in YAML tab
      

      Additional info:

      
      

            [CNV-41846] Changes in configuration tab does not save to YAML tab

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Moderate: OpenShift Virtualization 4.16.0 Images security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2024:4455

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Moderate: OpenShift Virtualization 4.16.0 Images security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:4455

            cnv-qe jira added a comment -

            The first build that contains https://github.com/kubevirt-ui/kubevirt-plugin/pull/1951 is CNV v4.16.0.rhel9-2575.

            cnv-qe jira added a comment - The first build that contains https://github.com/kubevirt-ui/kubevirt-plugin/pull/1951 is CNV v4.16.0.rhel9-2575.

            cnv-qe jira added a comment -

            A build that contains the fix PR for this bug is available, moving status from MODIFIED to ON_QA.

            cnv-qe jira added a comment - A build that contains the fix PR for this bug is available, moving status from MODIFIED to ON_QA.

            CPaaS Service Account mentioned this issue in a merge request of cpaas-midstream / openshift-virtualization / kubevirt-plugin on branch cnv-4.99-rhel-9_upstream_72bf34cbfefe856461459e94470da148:

            Updated US source to: c9ec07c Merge pull request #1955 from pcbailey/bug-virtctl-link-should-point-to-all-cli-tools

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of cpaas-midstream / openshift-virtualization / kubevirt-plugin on branch cnv-4.99-rhel-9_ upstream _72bf34cbfefe856461459e94470da148 : Updated US source to: c9ec07c Merge pull request #1955 from pcbailey/bug-virtctl-link-should-point-to-all-cli-tools

            CPaaS Service Account mentioned this issue in a merge request of cpaas-midstream / openshift-virtualization / kubevirt-plugin on branch cnv-4.16-rhel-9_upstream_72bf34cbfefe856461459e94470da148:

            Updated US source to: c9ec07c Merge pull request #1955 from pcbailey/bug-virtctl-link-should-point-to-all-cli-tools

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of cpaas-midstream / openshift-virtualization / kubevirt-plugin on branch cnv-4.16-rhel-9_ upstream _72bf34cbfefe856461459e94470da148 : Updated US source to: c9ec07c Merge pull request #1955 from pcbailey/bug-virtctl-link-should-point-to-all-cli-tools

              mschatzm@redhat.com Matan Schatzman
              gouyang1@redhat.com Guohua Ouyang
              Guohua Ouyang Guohua Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: