Bug 1713213
| Summary: | [downstream clone - 4.3.5] RHV-M requesting four GetDeviceListVDSCommand when editing storage domain | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
| Component: | ovirt-engine | Assignee: | shani <sleviim> |
| Status: | CLOSED ERRATA | QA Contact: | Shir Fishbain <sfishbai> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.4 | CC: | aefrat, emarcus, lsurette, rgolan, Rhev-m-bugs, sleviim, srevivo, tnisan |
| Target Milestone: | ovirt-4.3.5 | Keywords: | Performance, ZStream |
| Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
In this release, a new notification has been added when loading a large number of LUNs: "Loading...
A large number of LUNs may slow down the operation."
|
Story Points: | --- |
| Clone Of: | 1475774 | Environment: | |
| Last Closed: | 2019-08-12 11:53:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1475774 | ||
| Bug Blocks: | |||
|
Description
RHV bug bot
2019-05-23 07:43:08 UTC
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. (Originally by Sandro Bonazzola) Shani, please add a message in the dialog that having a high number of LUNs will slow the operation down (Originally by Tal Nisan) Verified GetDeviceListVDSCommand still appears 4 times in the engine log. When clicking on manage domain, a message in the dialog appears: "Loading... A large number of LUNs may slow down the operation" ovirt-engine-4.3.5.3-0.1.el7.noarch vdsm-4.30.23-2.el7ev.x86_64 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, 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/RHEA-2019:2431 sync2jira sync2jira |