Bug 1867221

Summary:	Metrics store deployment fails when using a VLAN tagged network (other than ovirtmgmt/rhevm)
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Abhishekh Patil <abpatil>
Component:	ovirt-engine-metrics	Assignee:	Shirly Radco <sradco>
Status:	CLOSED DUPLICATE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.9	CC:	mavital
Target Milestone:	---
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:	2020-08-13 13:45:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Abhishekh Patil 2020-08-07 18:09:34 UTC

Description of problem:

While deploying metrics-store using a VLAN tagged network, playbook created metrics-store-installer VM with 2 vNICs: 'eth0' and 'nic1'. Also, the VM remains unreachable over network.

Version-Release number of selected component (if applicable):
ovirt-engine-metrics-1.3.7-1.el7ev.noarch

How reproducible:
Sometimes

Steps to Reproduce:
1. While deploying metrics store edit metrics-store-config.yml and enter any other VLAN tagged VM network other than ovirtmgmt/rhevm
2. Run the playbook as mentioned in below documentation:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/metrics_store_installation_guide/installing_metrics_store#creating_metrics_store_virtual_machines

3. Login to RHV portal and check the number vNICs created for 'metrics-store-installer' VM.

Actual results:
There are 2 vNICs created for 'metrics-store-installer' VM: 'eth0' and 'nic1'. VM remains unreachable over network.

Expected results:
Only single vNIC should be created for 'metrics-store-installer' VM and VM should be reachable.

Additional info:

Comment 4 Sandro Bonazzola 2020-08-13 13:45:19 UTC

Closing as duplicate of bug #1814568

*** This bug has been marked as a duplicate of bug 1814568 ***