Created attachment 1455250 [details] inconsistentDisplay Description of problem: If someone reaches the maximum number of VMs he/she can take from the pool, he/she should not see the pools, only the VMs. That's the case for automatic VM Pool Type, in a case of manual type, it doesn't work as expected. Version-Release number of selected component (if applicable): RHV 4.2 How reproducible: it looks like 100% Steps to Reproduce: With a manual type of pool, a pool is created (named for example Pool-Win7-manual-??) composed of the VMs and a maximum attribution of 2 VM per user. When VMs are running, there are no issues. However, once the VM Pool-Win7-manual-01 is stopped, there is the following situation : - Pool-Win7-manual-01 stopped but still visible, because it's still attributed to the user (principle of a manual pool) - Pool-Win7-manual-02 is running, therefore visible - Pool-Win7-manual-?? which reappears (and which remains visible if we refresh the page), while we already reached the maximum number of VM that the user can take Actual results: Not consistent behaviour Expected results: It behaves consistently. Additional info: recorded video in an attachment
opened https://github.com/oVirt/ovirt-web-ui/issues/655 upstream
target? (wondering for web-ui)
Actually, this behavior may change in redesign -- we may want to always show a pool card for both manual and automatic. Currently under discussion. I'll update this BZ when we have a decision.
sync2jira
Steps: With a manual type of pool, a pool is created (named for example Pool-Win7-manual-??) composed of the VMs and a maximum attribution of 2 VM per user. When VMs are running, there are no issues. However, once the VM Pool-Win7-manual-01 is stopped, there is the following situation : - Pool-Win7-manual-01 stopped but still visible, because it's still attributed to the user (principle of a manual pool) - Pool-Win7-manual-02 is running, therefore visible - Pool-Win7-manual-?? which reappears (and which remains visible if we refresh the page), while we already reached the maximum number of VM that the user can take Then tested the same steps with automatic pools with the difference of expecting the allocated VMs disappearing after shutting them down and VM pool appearing, because VMs got deallocated. Results: Manual type pool works as intended. VMs do not disappear after shutdown and VM pool does not appear after reaching maximum of user allocated VMs or maximum VMs in the VM pool. Automatic type pool almost works as intended. After shutting down one of the allocated VMs, the VM stays in the dashboard with status Off and the VM pool appears. VM does not disappear after the webui refreshing, only after force refresh with F5. If you click on the run button on the VM pool, it just starts the off VM, so I guess the functionality is not broken and it's only a problem with updating the dashboard. Bohdan, I'm not sure, if this is relevant for this bug or if I should open a new one and verify this one, because the manual pools work. Tested in: ovirt-engine-4.4.0-0.17.master.el7.noarch ovirt-web-ui-1.6.0-2.el7ev.noarch
The changes (redesign pools) seems not to be in the build for QE. Please move to ON_QA when we will get the proper build. Also please fill in 'Fixed in version' that will help with verification.
Steps: With a manual type of pool, a pool is created (named for example Pool-Win7-manual-??) composed of the VMs and a maximum attribution of 2 VM per user. When VMs are running, there are no issues. However, once the VM Pool-Win7-manual-01 is stopped, there is the following situation : - Pool-Win7-manual-01 stopped but still visible, because it's still attributed to the user (principle of a manual pool) - Pool-Win7-manual-02 is running, therefore visible - Pool-Win7-manual-?? which reappears (and which remains visible if we refresh the page), while we already reached the maximum number of VM that the user can take Then tested the same steps with automatic pools with the difference of expecting the allocated VMs disappearing after shutting them down and VM pool appearing, because VMs got deallocated. Results: Manual type pool works as intended. VMs do not disappear after shutdown and VM pool does not appear after reaching maximum of user allocated VMs or maximum VMs in the VM pool. Automatic type pool works as intended as well. Shutting down allocated VM causes it to disappear and in case the maximum limit of allocated VMs per user is not maxed anymore the VM pool appears again. VM pool also disappears in case the maximum number of VMs in the pool itself is exceeded. Verified in: ovirt-engine-4.4.0-0.33.master.el8ev.noarch ovirt-web-ui-1.6.2-0.20200415.gitbc758a4.el8ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement 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-2020:3247