Bug 1348388

Summary: Should remove ";vdsmdummy;" in cockpit after register to RHEVM
Product: [oVirt] vdsm Reporter: wanghui <huiwa>
Component: CoreAssignee: Dan Kenigsberg <danken>
Status: CLOSED WONTFIX QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: medium    
Version: 4.18.10CC: bugs, cshao, danken, fdeutsch, gklein, huzhao, leiwang, rbarry, weiwang, yaniwang, ycui, ykaul
Target Milestone: ---Flags: sbonazzo: ovirt-4.1-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-29 12:50:33 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 wanghui 2016-06-21 04:56:52 UTC
Description of problem:
It should remove ";vdsmdummy;" in cockpit after register to RHEVM.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-ng-4.0-20160608.0.x86_64
cockpit-ovirt-dashboard-0.10.3-0.0.1.el7ev.noarch
imgbased-0.7.0-0.1.el7ev.noarch
redhat-release-rhev-hypervisor-4.0-0.6.el7.x86_64
vdsm-4.18.2-0.el7ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. install rhev-hypervisor7-ng-4.0-20160608.0.x86_64
2. Register to RHEVM
3. Check the network page in cockpit

Actual results:
It shows ";vdsmdummy;" as a interface.

Expected results:
It should remove ";vdsmdummy;" as a interface.

Additional info:

Comment 1 Fabian Deutsch 2016-06-21 12:21:15 UTC
Dan, can vdsm learn to not create this bridge?

Comment 2 Dan Kenigsberg 2016-06-21 15:06:42 UTC
Vdsm needs this VM for implementing non-wired vNICs. Theoretically, we can create it much later (e.g. before starting a VM), but it won't be fun.

What's the big problem in reporting oVirt bridges as Cockpit interfaces?

Comment 3 wanghui 2016-06-29 09:21:24 UTC
(In reply to Dan Kenigsberg from comment #2)
> Vdsm needs this VM for implementing non-wired vNICs. Theoretically, we can
> create it much later (e.g. before starting a VM), but it won't be fun.
> 
> What's the big problem in reporting oVirt bridges as Cockpit interfaces?

If you report this as cockpit interface, it means it can be managed or modified which should not. So it should be better not to report this bridge at all.

Comment 5 Ying Cui 2016-07-26 08:53:00 UTC
QE suggest to include this fix in RHV 4.0 GA.

Comment 6 Fabian Deutsch 2016-08-04 12:58:00 UTC
Cockpit is showing all network devices. if it should not be shown, then it must not be created.
Thus moving to vdsm which can consider to remove this device.

Comment 7 Dan Kenigsberg 2016-08-04 13:07:29 UTC
We cannot just remove it, it's required for disconnected vNICs.

Fabian, do you think that cockpit could add a blacklist of devices not to show in its UI?

Comment 8 Fabian Deutsch 2016-08-29 12:24:28 UTC
Hm, there is actually no cockpit specific configuration, so it would be an NM blacklist. But to me that does not look like the right direction.

IMO if the bridge is needed, then we should expose it.