Red Hat Bugzilla – Bug 605561
Traceback from file /tmp/anamon after manual install via vnc
Last modified: 2012-10-11 19:50:02 EDT
Description of problem:
Traceback from file /tmp/anamon after a manual install via vnc from beaker
Version-Release number of selected component (if applicable):
Seems it's every time.
Steps to Reproduce:
On the machine web page,
1. choose distro RHEL6.0-Beta1-4.1_nfs-AP-x86_64;
2. type keyword manual in field "KickStart MetaData";
3. append keyword vnc to the string in field "Kernel Options (Install)";
4. keep others as default and provision the system;
5. after the manual install and reboot in vncviewer, we can see the Traceback in console window.
Press <enter> for a shell
04:54:54 Starting graphical installation.
disabling /dev/loop0 LOOP_CLR_FD failed: 16
Traceback (most recent call last):
File "/tmp/anamon", line 273, in <module>
File "/tmp/anamon", line 215, in anamon_loop
if alog.seen("step installpackages$") or (sysimage.stable() and watch.exists()):
File "/tmp/anamon", line 154, in stable
File "/tmp/anamon", line 136, in update
fd = open('/proc/mounts')
IOError: [Errno 2] No such file or directory: '/proc/mounts'
waiting for mdraid sets to become clean...
sending termination signals...done
sending kill signals...done
Although there is a traceback, system can boot successfully and run normally.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
anaconda is not responsible for anamon.
*** Bug 602299 has been marked as a duplicate of this bug. ***
On Gerrit: http://gerrit.beaker-project.org/1371
Beaker 0.9.4 has been released.