Bug 1791537
Summary: | [machines] Editing network interface will cause network source changed to wrong characters. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | YunmingYang <yunyang> |
Component: | cockpit-appstream | Assignee: | Katerina Koukiou <kkoukiou> |
Status: | CLOSED ERRATA | QA Contact: | YunmingYang <yunyang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.2 | CC: | leiwang, mmarusak, mpitt, skobyda, wshi, xchen, ymao |
Target Milestone: | rc | ||
Target Release: | 8.2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 15:43:08 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
YunmingYang
2020-01-16 05:48:37 UTC
Sorry for miss a step in 'Steps to Reproduce:' before step 3: the network interface which is edited should be changed 'Interface Type' to 'Bridge to LAN' firstly.And the source should be chosen to the bridge which is created in step 1. There is also another condition which can reproduce: 1. Prepare a linux bridge and an off VM 2. Switch to the 'Network Interfaces' tab of the VM 3. Change the network interface to 'Diect attachment', and choose the bridge which is created in the step 1 for the source. 4. Re-click 'Add Network Interfaces' button, then click 'Add' button without changing @YunmingYang how do you create the bridge? If you create it by libvirt CLI, aka with `# virsh iface-bridge $IFACE $BRIDGE_NAME` things should work as expected, but if you create the bridge by some other way the new bridge will not be available in the cockpit-machines UI till you refresh the page because we won't have gotten any event which will lead us to update our net node devices list. Katerina fixes this in https://github.com/cockpit-project/cockpit/pull/13408 , thanks! @Katerina, I created the bridge through cockpit UI. In fact, I refresh the page after creating the bridge, sorry for missing this step in the 'Steps to Reproduce' Does the other bridge you created have the same name as the bridge you deleted? It has different name for the second bridge. But I tried the same name too, it has the same problem. I think the name does not matter because the steps in comment 1 can also reproduce the problem. Verified with package: cockpit-machines-211-1.el8.noarch libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64 Steps: 1. Prepare an off VM 2. Prepare a linux bridge on "Networking" page 3. Refresh the "Virtual Machines" Page, switch to the 'Network Interfaces' tab of the VM 4. Edit the network interface to the bridge which is created in step 2 5. Click 'Edit' button, then click 'Add', no changing for the network interface which is edited 6. Delete the bridge on "Networking" page, then create a new one with different name 7. Refresh the "Virtual Machines" Page, edit the VM network interface to the new bridge In step 4, the source is changed to the new bridge. In step 5, the source of the edited network interface will not be changed to wrong characters In step 7, the source can be changed to the new bridge created in step 6 So verified. 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/RHBA-2020:1639 |