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

Bug 1723571

Summary:	[downstream clone - 4.3.5] Change of cluster compatibility version drops virtio-console from VM config
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	RHV bug bot <rhv-bugzilla-bot>
Component:	ovirt-engine	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED ERRATA	QA Contact:	Liran Rotenberg <lrotenbe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	bugs, rbarry, Rhev-m-bugs
Target Milestone:	ovirt-4.3.5	Keywords:	ZStream
Target Release:	4.3.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1703723	Environment:
Last Closed:	2019-08-12 11:53:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1703723
Bug Blocks:

Description RHV bug bot 2019-06-24 20:23:44 UTC

+++ This bug is an upstream to downstream clone. The original bug is: +++
+++   bug 1703723 +++
======================================================================

Description of problem:

After changing the cluster and DC compatibility levels to 4.3, the "Next Run configuration" for VMs no longer has the virtio serial console enabled.
On the next VM restart, the VM comes up without the console.

With some guest systems (e.g. Debian and Ubuntu official cloud images), the consequences of this are quite ugly: guest system hangs on boot, apparently blocking on I/O to the console.


Version-Release number of selected component (if applicable):
At point of VM restart: ovirt-engine-4.3.3.5-1.el7.noarch
At creation of next run config: ovirt-engine-4.3.2.1-1.el7.noarch


Steps to Reproduce:
1. Start with 4.2 installation, create VM with virtio-console enabled
2. Upgrade engine and hosts to 4.3
3. Change cluster (and possibly DC) compat version to 4.3
4. Restart VMs

Actual results:
Virtio-console is disabled for all VMs.

Expected results:
Virtio-console is enabled iff it was enabled prior to the upgrade

Additional info:
I vaguely remember that this used to be an issue already with earlier upgrades within 4.x.

(Originally by ls)

Comment 1 RHV bug bot 2019-06-24 20:23:46 UTC

This bug has the same root cause as: https://bugzilla.redhat.com/show_bug.cgi?id=1658101

(Originally by Lucia Jelinkova)

Comment 2 Ryan Barry 2019-06-24 20:26:30 UTC

Already in ovirt-engine-4.3

Comment 4 RHV bug bot 2019-06-27 11:39:43 UTC

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

[Tag 'ovirt-engine-4.3.5.2' doesn't contain patch 'https://gerrit.ovirt.org/99893']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.3.5.2

For more info please contact: rhv-devops

Comment 5 RHV bug bot 2019-06-27 11:48:33 UTC

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

[Tag 'ovirt-engine-4.3.5.2' doesn't contain patch 'https://gerrit.ovirt.org/99893']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.3.5.2

For more info please contact: rhv-devops

Comment 6 Liran Rotenberg 2019-07-03 15:51:26 UTC

Verified on:
ovirt-engine-4.3.5.2-0.1.el7.noarch

Steps:
1. Deploy RHV 4.2.
2. Create a VM, virtio-console enabled.
3. Run the VM.
4. Upgrade to RHV 4.3.
5. Change the compatibility version to 4.3.
6. Reboot the VM.
7. Check the virtio-console.

Results:
I tested on a running VM and a down VM. virtio-console was set on both.
After upgrade and restarting the running VM both VMs still had the virtio-console enabled.

Comment 7 RHV bug bot 2019-07-04 13:11:01 UTC

INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Tag 'ovirt-engine-4.3.5.3' doesn't contain patch 'https://gerrit.ovirt.org/99893']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.3.5.3

For more info please contact: rhv-devops

Comment 8 RHV bug bot 2019-07-11 12:37:02 UTC

INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Tag 'ovirt-engine-4.3.5.4' doesn't contain patch 'https://gerrit.ovirt.org/99893']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.3.5.4

For more info please contact: rhv-devops

Comment 9 RHV bug bot 2019-07-18 11:02:10 UTC

INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Tag 'ovirt-engine-4.3.5.4' doesn't contain patch 'https://gerrit.ovirt.org/99893']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.3.5.4

For more info please contact: rhv-devops

Comment 11 errata-xmlrpc 2019-08-12 11:53:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2019:2431