Bug 680421 - install fails due to unmount/mounting issues with logging
Summary: install fails due to unmount/mounting issues with logging
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-25 13:53 UTC by Joey Boggs
Modified: 2016-04-26 13:59 UTC (History)
4 users (show)

Fixed In Version: ovirt-node-1.9.3-19.el6
Doc Type: Bug Fix
Doc Text:
During the installation process, you would receive a traceback error because the host volume group logging volume could not be unmounted. The error was caused by the ovirt-node package attempting to kill processes with incorrect process names before unmounting the volume. The ovirt-node package now uses the correct process names and can now successfully unmount the host volume group logging volume.
Clone Of:
Environment:
Last Closed: 2011-08-19 15:16:19 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 3 Mohua Li 2011-03-04 06:14:55 UTC 
this is fixed in 6.1-8 don't have such error now, but have other install error, tracked by other bugs,
Comment 4 Kate Grainger 2011-05-06 03:59:08 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
During the installation process, you would receive a traceback error because the host volume group logging volume could not be unmounted. The error was caused by the ovirt-node package attempting to kill processes with incorrect process names before unmounting the volume. The ovirt-node package now uses the correct process names and can now successfully unmount the host volume group logging volume.
Note You need to log in before you can comment on or make changes to this bug.