Bug 32364 – Interface-edit does not read model: always defaults to RealTek

Bug 32364 - Interface-edit does not read model: always defaults to RealTek


Summary:	Interface-edit does not read model: always defaults to RealTek

Status:	RESOLVED WORKSFORME

Product:	UCS manual
Classification:	Unclassified
Component:	Virtualisation / UVMM
Version:	unspecified
Hardware:	Other Linux

Importance:	P4 normal (vote)
Target Milestone:	---
Assigned To:	Docu maintainers
QA Contact:	UCS maintainers

URL:
Keywords:	interim-1

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-08-26 13:46 CEST by Moritz Muehlenhoff
Modified:	2018-04-14 13:41 CEST (History)
CC List:	4 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Troubleshooting, Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Moritz Muehlenhoff

2013-08-26 13:46:25 CEST

The rejection of multicast addresses should be documented.

+++ This bug was initially created as a clone of Bug #30806 +++

UMC → UVMM → VM edit → Devices → Interfaces → Edit

When an interface is modified, the current model (e1000, realtek, virtio) is not put into the combo box, but always defaults to using the "default (RealTek RTL-8139)" selection.

u-v-m-m/umc/js/uvmm/InterfaceWizard.js:113#_setInitialValues() seems to no longer do the right thing.

Comment 1 Moritz Muehlenhoff

2013-09-05 14:51:03 CEST

Actually, that's rather an internal detail and there's an error message anyway. No docs adaption needed.