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

Bug 1703723

Summary:	Change of cluster compatibility version drops virtio-console from VM config
Product:	[oVirt] ovirt-engine	Reporter:	Lars Seipel <ls>
Component:	General	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Beni Pelled <bpelled>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.3.3.5	CC:	bugs, rbarry
Target Milestone:	ovirt-4.4.0	Keywords:	ZStream
Target Release:	---	Flags:	pm-rhel: ovirt-4.4+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhv-4.4.0-29	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1723571 (view as bug list)		Environment:
Last Closed:	2020-05-20 20:01:07 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:
Bug Depends On:
Bug Blocks:	1723571

Description Lars Seipel 2019-04-28 01:04:51 UTC

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.

Comment 1 Lucia Jelinkova 2019-05-10 11:40:13 UTC

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

Comment 4 Beni Pelled 2020-04-22 12:26:15 UTC

Verified with:
- RHV 4.4.0-0.33.master.el8ev
- libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64
- vdsm-4.40.13-1.el8ev.x86_64

Verification steps:
1. Creat DC & Cluster configured with compatible version == 4.3
2. Create a VM with serial console enabled
3. Update the DC & Cluster to be configured with compatible version == 4.4
4. Verify serial console is remains enabled after the compatible version has been updated

Result:
- Serial Console is enabled after the compatible version has been updated.

Comment 5 Sandro Bonazzola 2020-05-20 20:01:07 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.