Bug 783394 - Unexpected error output in screen after installing and then rebooting RHEV-H
Summary: Unexpected error output in screen after installing and then rebooting RHEV-H
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ovirt-node
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 7.0
Assignee: Mike Burns
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-20 09:10 UTC by Ying Cui
Modified: 2019-03-06 01:18 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-05 06:08:40 UTC
Target Upstream Version:


Attachments (Terms of Use)
picture (193.14 KB, image/x-xcf)
2012-01-20 09:11 UTC, Ying Cui
no flags Details
output.log (18.10 KB, text/plain)
2012-01-20 09:12 UTC, Ying Cui
no flags Details

Description Ying Cui 2012-01-20 09:10:03 UTC
Description:
 Install RHEV-H first, and then reboot RHEV-H, the unexpected error output: .

*********************************************
Stopping ovirt-firstboot: [  OK  ]
Sending all processes the TERM signal... [  OK  ]

Terminated
Sending all processes the KILL signal... [  OK  ]

Saving random seed:  [  OK  ]

Syncing hardware clock to system time [  OK  ]

Unmounting loopback filesystems:  umount: /dev/.initramfs/live: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[FAILED]

Detaching loopback device /dev/loop0:  loop: can't delete device /dev/loop0: Device or resource busy
[FAILED]

Unmounting loopback filesystems (retry): umount: /dev/.initramfs/live: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[FAILED]

Detaching loopback device /dev/loop0:  loop: can't delete device /dev/loop0: Device or resource busy
[FAILED]

Unmounting loopback filesystems (retry): umount: /dev/.initramfs/live: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[FAILED]

Detaching loopback device /dev/loop0:  loop: can't delete device /dev/loop0: Device or resource busy
[FAILED]

Unmounting file systems:  [  OK  ]

umount2: Device or resource busy
umount: /etc: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
umount: /dev/.initramfs/live: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
init: Re-executing /sbin/init
**********************************************


Test Build:rhev-hypervisor6-6.2-20120119.1.el6_2

Comment 2 Ying Cui 2012-01-20 09:11:52 UTC
Created attachment 556476 [details]
picture

Comment 3 Ying Cui 2012-01-20 09:12:40 UTC
Created attachment 556477 [details]
output.log

Comment 4 Mike Burns 2012-01-20 14:01:31 UTC
I'm not sure that we can actually fix this.  The important thing is that it does reboot after trying and failing to umount those locations.  We had bugs in the past where we failed to reboot and it just looped forever on those errors.

Lowering priority and severity because it's only really a cosmetic problem.

Comment 6 RHEL Program Management 2012-07-10 05:56:03 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2012-07-11 01:47:50 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 8 Mike Burns 2012-07-11 13:14:20 UTC
low prio and cosmetic only, deferring to 7.0

Comment 11 cshao 2013-07-05 05:23:17 UTC
No unexpected error output in screen after installing and then rebooting RHEV-H in build rhev-hypervisor6-6.5-20130222.0.auto1707.el6.
Suggest to close this bug since no such issue in latest bulid.

Comment 12 Ying Cui 2013-07-05 06:08:40 UTC
as comment 11, close this bug now, if we encounter such issue during 7.0 testing, we will reopen or submit new one.

Thanks
Ying


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