Bug 1067412 - broken link in /var/lib/ovirt-engine/deployments cause setup to fail
Summary: broken link in /var/lib/ovirt-engine/deployments cause setup to fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.3.2
Assignee: Alon Bar-Lev
QA Contact: Jiri Belka
URL:
Whiteboard: integration
Depends On: 1059480
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-20 12:27 UTC by rhev-integ
Modified: 2014-04-09 17:55 UTC (History)
12 users (show)

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.
Clone Of: 1059480
Environment:
Last Closed: 2014-04-09 17:55:19 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0384 0 normal SHIPPED_LIVE rhevm 3.3.2 bug fix update 2014-04-09 21:52:20 UTC
oVirt gerrit 23277 0 None None None Never
oVirt gerrit 23278 0 None None None Never
oVirt gerrit 23347 0 None None None Never
oVirt gerrit 23877 0 None None None Never
oVirt gerrit 23878 0 None None None Never
oVirt gerrit 23879 0 None None None Never
oVirt gerrit 23880 0 None None None Never
oVirt gerrit 23896 0 None None None Never

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


Note You need to log in before you can comment on or make changes to this bug.