Bug 1660467
Summary: | Can create a new vm with the MAC address in use on rhel8.0 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | zonglin jiang <zjiang> |
Component: | virt-manager | Assignee: | Pavel Hrdina <phrdina> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | crobinso, juzhou, mxie, mzhan, tzheng, xiaodwan, zili |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virt-manager-2.2.0-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-05 21:19:13 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
zonglin jiang
2018-12-18 11:51:48 UTC
Nice catch! This is fixed upstream now: commit d61f9d99958be45f1c53f5440ba8ccba13d3db69 (HEAD -> master, origin/master) Author: Cole Robinson <crobinso> Date: Fri Jun 14 21:11:37 2019 -0400 details: Check for mac conflict in customize wizard https://bugzilla.redhat.com/show_bug.cgi?id=1660467 I can reproduce this issue with build: virt-manager-common-2.0.0-5.el8.noarch Then try to verify this bug with new build: virt-manager-2.2.0-2.el8.noarch virt-install-2.2.0-2.el8.noarch libvirt-4.5.0-24.module+el8.1.0+3205+41ff0a42.x86_64 qemu-kvm-2.12.0-77.module+el8.1.0+3382+49219945.x86_64 Steps: 1, Create a new vm follow giving the os a different name, and different image, others are the same, especially make sure the MAC is completely the same as the prepared one. 2. After Click "Finish". Result: An error window pops up with information: Error applying changes: The MAC address '52:54:00:24:b8:d7' is in use by another virtual machine. Above result is as expected, so I move this bug from ON_QA to VERIFIED, thanks. 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/RHSA-2019:3464 |