ffslcschools opened a new issue, #9931:
URL: https://github.com/apache/cloudstack/issues/9931

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   
   ##### COMPONENT NAME
   <!--
   -->
   ~~~
   UI
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   -->
   
   ~~~
   4.19.3
   ~~~
   
   ##### CONFIGURATION
   <!--
   -->
   ~~~
   UI bug not related to a specific configuration.
   ~~~
   
   ##### OS / ENVIRONMENT
   <!--
   -->
   ~~~
   Management server OS Ubuntu 24.04.01 LTS
   Client browser Edge or Chrome Ver 130+
   ~~~
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   ~~~
   When modifying virtual machine settings, after committing a setting the ui 
will not let you see new settings, only the last setting committed.
   ~~~
   
   ##### STEPS TO REPRODUCE
   <!--
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   Add a setting and value to a virtual machine and click the green check.
   Click add setting then click the Name field.
   Only the previous setting will be displayed.
   Leaving the current virtual machine view and going back, or deleting the 
added setting are the only way to get the settings list to come back.
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   To see the full list of Named settings so that another setting can be added.
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Only the previously configured setting Name is listed.
   ~~~
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to