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

Bug 1490824

Summary:	Empty line is inserted at the beginning of versionlock.list after upgrade
Product:	[oVirt] ovirt-engine	Reporter:	Radim Hrazdil <rhrazdil>
Component:	Setup.Engine	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.2.0	CC:	bugs, irosenzw, lleistne, lsvaty, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	4.2.0
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:07:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Radim Hrazdil 2017-09-12 10:26:48 UTC

Description of problem:
After performing an upgrade, there is an empty line at the beginning of 
/etc/yum/pluginconf.d/versionlock.list file.


Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20170907100709

How reproducible:
100%

Steps to Reproduce:
1. Install ovirt-engine, 
2. check /etc/yum/pluginconf.d/versionlock.list
3. upgrade engine (yum update ovirt-engine-setup*; engine-setup)
4. check /etc/yum/pluginconf.d/versionlock.list

Actual results:
there is an empty line at the beginning of the versionlock.list file

Expected results:
no empty lines

Additional info:
reproduced with local dwh and with dwh on a remote machine, doesn't happen on the machine where is the dwh

Comment 1 Lucie Leistnerova 2017-11-03 14:24:31 UTC

no empty line, the one from previous version was removed

verified in ovirt-engine-setup-4.2.0-0.4.master.el7.noarch

Comment 2 Sandro Bonazzola 2017-12-20 11:07:29 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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