Red Hat Bugzilla – Bug 1003489
copy_dir_if_not_exist raises exception during boot
Last modified: 2014-01-21 14:49:39 EST
Created attachment 792734 [details] Relevant part of the logfile Description of problem: On boot copy_dir_if_not_exist is called, but it raises an exception which is logged in /var/log/ovirt.log Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20130725.0.iso How reproducible: always Steps to Reproduce: 1. Install ISO 2. reboot 3. Actual results: Exception occurs Expected results: No exception occurs Additional info:
This bug is currently attached to errata RHBA-2013:15277. 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.
Can reproduce this bug with build rhev-hypervisor6-6.5-20130725.0.iso. Verified this build on rhevh-6.5-20131031.1.0, ovirt-node-3.0.1-7.el6.noarch After rhevh install, reboot, check the ovirt.log, no such error in log file. The bug is fixed.
Hi there, just checking to see if this needs document text, and if so, what was causing the problem and what was the fix? Thanks
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-0033.html