Bug 1059480

Summary:	broken link in /var/lib/ovirt-engine/deployments cause setup to fail
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Alon Bar-Lev <alonbl>
Component:	ovirt-engine-setup	Assignee:	Alon Bar-Lev <alonbl>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Belka <jbelka>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	acathrow, alonbl, bazulay, eedri, gklein, iheim, Rhev-m-bugs, sbonazzo, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	av2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1067412 (view as bug list)		Environment:
Last Closed:	2014-06-12 14:05:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1067412, 1078909, 1142926

Description Alon Bar-Lev 2014-01-29 23:02:55 UTC

Due to a bug in 3.2 setup in which some of the files at /var/lib were owned by root, the setup tries to chown files to ovirt user.

A broken link cause setup to fail.

Broken links happens because old reports package that was installed and removed/changed.

Comment 2 Alon Bar-Lev 2014-01-30 08:37:12 UTC

Sandro, whatever has simple workaround is not high.

 Sandro Bonazzola 2014-01-30 02:07:21 EST
Priority: unspecified → medium
Severity: unspecified → high

Comment 3 Eyal Edri 2014-02-10 09:47:30 UTC

moving to 3.3.2 since 3.3.1 was built and moved to QE.
(wasn't cloned yet to zstream, even though moving to modified before the build)

Comment 5 Jiri Belka 2014-03-07 10:11:35 UTC

what are the steps for verification please? Thx!

Comment 6 Alon Bar-Lev 2014-03-07 11:11:31 UTC

(In reply to Jiri Belka from comment #5)
> what are the steps for verification please? Thx!

for 3.4 it is difficult as this was backported to 3.3.z...

sequence was to create broken link at /var/lib/ovirt-engine/deployments, run engine-setup -- engine-setup fails.

now the deployments are created every time service starts, so cannot hold unexpected data.

Comment 7 Jiri Belka 2014-03-10 14:41:48 UTC

nothing to test here

15:41 < alonbl> jbelka: this issue is irrelevant to 3.4
15:41 < alonbl> jbelka: it was opened just to be able to clone to 3.3

Comment 8 Itamar Heim 2014-06-12 14:05:27 UTC

Closing as part of 3.4.0