Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1719464

Summary:	[RFE] When changing network filters UI should advise that VMs need to be powered off then on
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Christopher Brown <chris.brown>
Component:	ovirt-engine	Assignee:	eraviv
Status:	CLOSED DUPLICATE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.8-4	CC:	dholler, eraviv, mburman, michal.skrivanek, mperina
Target Milestone:	ovirt-4.4.6	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-13 23:21:48 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:
Bug Depends On:	1848986
Bug Blocks:	1113630

Description Christopher Brown 2019-06-11 21:19:04 UTC

Description of problem:

Currently the UI does not indicate that after changing network filters, all VMs must be powered off then on (not rebooted) for this profile to apply.

In the OpenStack world we have a specific use case with virtualized OpenStack Director support and we see a number of issues where customers or consultants do not realise this is required.

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/director_installation_and_usage/index#virtualization_support

It would therefore be good, to increase successful usage of Red Hat OpenStack and for other use cases, to prompt users to power off then on VMs when changing network filters.

Currently this is documented in a KCS:

https://access.redhat.com/solutions/284493

however it needs to be clearer that a reboot does not change the network filter profile.

Comment 1 Michal Skrivanek 2020-03-18 15:44:48 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 2 Michal Skrivanek 2020-03-18 15:49:53 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 3 Christopher Brown 2020-03-18 15:56:17 UTC

Hello,

Thanks for the nudge. Hopefully this is a simple fix to add a prompt in the UI to cater for this.

Its a poor user experience if its not indicated that VMs need to be powered off/on (not rebooted) for new network profiles to take effect.

Ultimately, a better fix would be for the new network profile to be applied to running instances however that would likely be a much bigger change.

Comment 5 Michal Skrivanek 2020-06-23 12:34:59 UTC

This request is not currently committed to 4.4.z, moving it to 4.5

Comment 6 Christopher Brown 2021-02-13 23:21:48 UTC

Abandoning.

Comment 7 Michal Skrivanek 2021-04-07 12:24:51 UTC

even if this is no longer needed for OSP 13, I think in general this is what's being implemented in bug 1113630

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