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

Bug 1529042

Summary:	[RFE] Changing of Cluster CPU Type does not trigger config update notification
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Shivraj <shipatil>
Component:	ovirt-engine	Assignee:	Liran Rotenberg <lrotenbe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	meital avital <mavital>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.1.1	CC:	klaas, lsurette, michal.skrivanek, mkalinin, mtessun, nobody, rbarry, Rhev-m-bugs, sraje, srevivo
Target Milestone:	ovirt-4.4.0	Keywords:	FutureFeature
Target Release:	---	Flags:	lsvaty: testing_plan_complete-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhv-4.4.0-29	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-16 10:36:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shivraj 2017-12-26 06:13:20 UTC

Description of problem:

Change in cluster config does not create a notification for VM config change.

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

How reproducible:
-----------------
Change CPU type for cluster, it will not trigger for notification in VM configuration.
The CPU type inside VM is reflected when it is shutdown/ Power-off and then started again.
e.g. When cluster compatibility is changed user gets notification flag for VM reboot for this change to be effective.

Steps to Reproduce:
-------------------
1. Check CPU type inside guest
2. Change CPU type for cluster with running VMs (lower the famliy) in deployed Environment.
3. There in no notification about this config change. 
4. Check CPU type inside guest again.

Actual results:
User expects to see notification flag on VM icon indicating there is change in config and VM needs to be shutdown and start again.

Expected results:
There is no such notification and VM cpu type is changed only when VM is shutdown/ powered off and started again (not reboted)

Additional info:

- This change inside guest is only seen when VM is shutdown/ powered off and started.
- When VM is rebooted from portal the CPU type does not change.

Comment 1 Michal Skrivanek 2017-12-27 14:49:45 UTC

that field is a cluster property and we do not watch for those.
We can also create a next run snapshot for all running VMs, same as we do with Cluster level upgrade

Comment 2 Klaas Weyermann 2017-12-28 16:34:59 UTC

(In reply to Michal Skrivanek from comment #1)
> that field is a cluster property and we do not watch for those.
> We can also create a next run snapshot for all running VMs, same as we do
> with Cluster level upgrade

Hi,
I was expecting it to be like cluster level upgrades, so yes that would fulfil my requirements. 

Greetings
Klaas

Comment 3 Klaas Weyermann 2018-01-10 15:59:16 UTC

This would come in handy for the cpu changes to -ibrs :)

Comment 12 RHV bug bot 2019-12-13 13:15:51 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 13 RHV bug bot 2019-12-20 17:45:25 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 14 RHV bug bot 2020-01-08 14:47:45 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 15 RHV bug bot 2020-01-08 15:17:13 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 16 RHV bug bot 2020-01-24 19:49:28 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 19 Lukas Svaty 2020-04-16 10:36:41 UTC

Closing low severity bugs, based on QE capacity, if you would like to still verify this issue please reopen.