Bug 1105899
| Summary: | RHEV Admin Portal presents "Empty" as a vnic profile on VM Edit dialogue | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Marina Kalinin <mkalinin> |
| Component: | ovirt-engine-webadmin-portal | Assignee: | Nobody <nobody> |
| Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.3.0 | CC: | acathrow, ecohen, iheim, lvernia, mkalinin, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | network | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-29 12:11:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marina Kalinin
2014-06-08 21:40:43 UTC
Are there any ways to debug this issue? Let me know if there are any logs I can provide you. Possibly a duplicate of Bug 1078215? Lior, sounds a bit different. But I will inform the customer and see where we go. In my case, described here, is that the database is not updated, does not matter what you set in UI. On the same note, the UI dialogue shows Empty each times it is opened, while the database has the correct info. The second behavior is definitely consistent with that bug. The first one could be as well. When the customer opens the profiles combo box, are the profiles presented the ones that exist in the VM's cluster? Or ones from another cluster? Profiles presented from VM's cluster. Does seem like a duplicate of the aforementioned bug, as this only happens in DCs that have more than a single cluster (and for VMs not in the first cluster, when ordered alphabetically). I guess I just didn't remember the exact symptoms (it has been a couple of months). So no good workaround, just need to be cautious when editing VMs. If most VMs in the DC are members of one cluster, I would name that cluster so it'd appear alphabetically before others (and then only VMs from other clusters will suffer from the bug). And of course, an upgrade to 3.3.3 should solve this issue. *** This bug has been marked as a duplicate of bug 1078215 *** |