Bug 1275962

Summary: Traceback ERROR messages display on screen output during Automatic and TUI installation
Product: Red Hat Enterprise Virtualization Manager Reporter: yileye <lyi>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED ERRATA QA Contact: cshao <cshao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: cshao, cwu, gklein, huiwa, huzhao, leiwang, lsurette, yaniwang, ycui, ykaul
Target Milestone: ovirt-3.6.1Keywords: Regression
Target Release: 3.6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 14:42:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/* +sosreport-log
none
ovirt-node.log none

Description yileye 2015-10-28 08:18:35 UTC
Created attachment 1087161 [details]
/var/log/* +sosreport-log

Description of problem:
when AUTO/TUI install RHEV-H scuccessful,check /var/log/ovirt-node.log,it show
traceback error.Like 'ERROR Can't umount /tmp/tmp0xeLmdRootUpdate'


Version-Release number of selected component (if applicable):
RHEV-H 7.2-20151025.0.el7ev
ovirt-node-3.30-0.18.20151022git93dc63c.el7ev.noarch

How reproducible:
100%

Regression bug

1.Boot via PXE.
2.Clean TUI/AUTO install  RHEV-H 7.2-20151025.0.el7ev
3.One by one step util install successful.
4.Reboot and login with no error.
5.Then check /var/log/ovirt-node.log

Actual results:
After Step5 , the ovirt-node.log show traceback error

Expected results:
After Step5 , the ovirt-node.log have no traceback error

Additional info:
#ovirt-node.log:

<snip>
2015-10-27 02:54:33,667       INFO Mounting '/tmp/tmp0xeLmdRootUpdate' to /boot
2015-10-27 02:54:33,746       INFO Generating new initramfs '/var/tmp/initrd0.img.new' for kver 3.10.0-325.el7.x86_64 (this can take a while)
2015-10-27 02:55:39,851       INFO Installing the new initramfs '/var/tmp/initrd0.img.new' to '/boot/initrd0.img'
2015-10-27 02:55:40,460      ERROR Can't umount /tmp/tmp0xeLmdRootUpdate
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/ovirt/node/utils/system.py", line 1064, in umount
    utils.process.check_call(["umount", self.path])
  File "/usr/lib/python2.7/site-packages/ovirt/node/utils/process.py", line 139, in check_call
    return int(subprocess.check_call(*args, **kwargs))
  File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['umount', '/tmp/tmp0xeLmdRootUpdate']' returned non-zero exit status 32
2015-10-27 02:55:40,461       INFO Successfully unmounted /liveos and /boot
2015-10-27 02:55:40,462       INFO Initramfs regenration completed successfully
2015-10-27 02:55:50,313       INFO Captured nothing
2015-10-27 02:55:57,725       INFO Captured nothing
</snip>

Comment 1 yileye 2015-10-28 08:19:31 UTC
Created attachment 1087162 [details]
ovirt-node.log

Comment 2 Ying Cui 2015-10-28 08:35:36 UTC
Updated the bug description, these error messages also display on screen output, not only in ovirt-node.log.

Comment 4 yileye 2015-10-28 09:40:10 UTC
I can' t  reproduce in same steps on RHEV-H 7.2-20151009.0.el7e,so i think the Keywords will be Regression.

Comment 5 Fabian Deutsch 2015-11-02 08:44:06 UTC
This bug seems to be visual only and has no functional impact.
The root cause - why the path can not be unmounted - is unknown.

Comment 6 yileye 2015-11-02 08:50:12 UTC
(In reply to Fabian Deutsch from comment #5)
> This bug seems to be visual only and has no functional impact.
> The root cause - why the path can not be unmounted - is unknown.

Yeah,but this bug also display in TUI install process, I think it is necessary to pay attention to it.

Comment 7 Fabian Deutsch 2015-11-02 09:25:39 UTC
Yes, that is why it already got a patch.

I'm targeting it for the RC, but dropping the blocker flag.

Comment 10 yileye 2015-11-12 10:38:38 UTC
I have to reproduce this bug on RHEV-H 7.2-20151025.0.el7ev 

test Version-Release number of selected component (if applicable):

rhev-hypervisor7-7.2-20151104.0 
ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev

Steps to Reproduce:
1.Boot via PXE.
2.Clean TUI/AUTO install  RHEV-H 7.2-20151025.0.el7ev
3.One by one step util install successful.
4.Reboot and login with no error.
5.Then check /var/log/ovirt-node.log

Actual results:
After Step5 , the ovirt-node.log have no traceback error 

Expected results:
After Step5 , the ovirt-node.log ,the  ‘ERROR Can't umount /tmp/tmp0xeLmdRootUpdate’ is already changed ‘WARNING Can't umount /tmp/tmp0xeLmdRootUpdate’

So this bug is fixed.Can change Status to VERIFIED

Comment 14 errata-xmlrpc 2016-03-09 14:42:06 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.

https://rhn.redhat.com/errata/RHBA-2016-0378.html