Bug 1683523

Summary:	ipv6 gateway removal from old default route role network - move message from alerts tab to main events tab
Product:	[oVirt] ovirt-engine	Reporter:	eraviv
Component:	BLL.Network	Assignee:	eraviv
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	bugs, dholler
Target Milestone:	ovirt-4.3.2	Flags:	pm-rhel: ovirt-4.3+
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-19 10:03:19 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 eraviv 2019-02-27 06:07:48 UTC

Description of problem: On removing default route role from network its ipv6 gateway is removed by engine. This action should be reported in the main events tab as a warning instead of in the alerts tab as an alert.


Version-Release number of selected component (if applicable):
4.3.0

How reproducible:
100%

Steps to Reproduce:
1. create ipv6 configuration for the current default route role
2. attach a second network to a nic on the host, and provide ipv6 configuration
3. move the default route role to the second network

Actual results:
Message appears in alerts tab

Expected results:
Message should appear in main events tab

Additional info:

Comment 1 Michael Burman 2019-03-06 08:05:23 UTC

Verified on - 4.3.2-0.1.el7

Note, that currently this message is also shown if changing the default route role for a network that has only IPv4 bootprotocol and it's a bug. This message should never been seen if the network has only IPv4 bootproto. See BZ 1685818

Comment 2 Sandro Bonazzola 2019-03-19 10:03:19 UTC

This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.