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

Bug 1067412

Summary:	broken link in /var/lib/ovirt-engine/deployments cause setup to fail
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-engine-setup	Assignee:	Alon Bar-Lev <alonbl>
Status:	CLOSED ERRATA	QA Contact:	Jiri Belka <jbelka>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	acathrow, alonbl, bazulay, eedri, gklein, iheim, lbopf, oschreib, pstehlik, Rhev-m-bugs, sbonazzo, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.3.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, when the reports package was updated or removed, a broken symlink was left within the engine's deployment directory, causing the engine to fail during start sequence. Now, engine recreates the deployments directory each time it starts, so start succeeds regardless of deployment directory content.	Story Points:	---
Clone Of:	1059480	Environment:
Last Closed:	2014-04-09 17:55:19 UTC	Type:	---
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:	1059480
Bug Blocks:

Comment 2 Jiri Belka 2014-03-17 14:21:44 UTC

ok, rhevm-setup-3.3.2-0.49.el6ev.noarch

engine-setup passed OK while having a symlink in /var/lib/ovirt-engine/deployments pointing to nonexistent object (file).

# cd /var/lib/ovirt-engine/deployments
# ls -l nonexistent 
lrwxrwxrwx. 1 root root 12 Mar 17 14:16 nonexistent -> /nonexistent

# ls -l /nonexistent
ls: cannot access /nonexistent: No such file or directory

Comment 3 Zac Dover 2014-04-03 02:26:24 UTC

This bug is currently attached to errata RHBA-2014:17286. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 5 errata-xmlrpc 2014-04-09 17:55:19 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.

http://rhn.redhat.com/errata/RHBA-2014-0384.html