RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 696198 - KeyError: dbus.String(u'eth0', variant_level=1)
Summary: KeyError: dbus.String(u'eth0', variant_level=1)
Keywords:
Status: CLOSED DUPLICATE of bug 696127
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 678354
Blocks: 670159
TreeView+ depends on / blocked
 
Reported: 2011-04-13 14:18 UTC by Alexander Todorov
Modified: 2011-04-13 19:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 678354
Environment:
Last Closed: 2011-04-13 19:53:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
syslog from the beaker (121.74 KB, text/plain)
2011-04-13 15:04 UTC, Radek Vykydal 		no flags Details
anaconda.log from the beaker (7.49 KB, text/plain)
2011-04-13 15:05 UTC, Radek Vykydal 		no flags Details
View All

Description Alexander Todorov 2011-04-13 14:18:00 UTC 
+++ This bug was initially created as a clone of Bug #678354 +++

When trying to use VNC from a live cd I get this traceback:

16:52:15 Starting VNC...
Traceback (most recent call last):
  File "/usr/sbin/anaconda", line 851, in <module>
    runVNC()
  File "/usr/sbin/anaconda", line 300, in runVNC
    vncS.startServer()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line 217, in startServer
    self.initialize()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line 108, in initialize
    dev = devices[active_devs[0]]
KeyError: dbus.String(u'eth0', variant_level=1)

This happens with the F14 and F15 isos. It happens in runlevel 3 and from a gnome-terminal in runlevel 5.
Comment 1 Alexander Todorov 2011-04-13 14:19:46 UTC 
I got this traceback with the latest RHEL6.1 nightly:

Running anaconda 13.21.111, the Red Hat Enterprise Linux system installer - please wait.
10:15:27 Starting VNC...
Traceback (most recent call last):
  File "/usr/bin/anaconda", line 1014, in <module>
    runVNC()
  File "/usr/bin/anaconda", line 340, in runVNC
    vncS.startServer()
  File "/usr/lib/anaconda/vnc.py", line 203, in startServer
    self.initialize()
  File "/usr/lib/anaconda/vnc.py", line 104, in initialize
    dev = devices[active_devs[0]]
KeyError: dbus.String(u'eth0', variant_level=1)
install exited abnormally [1/1] 
The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete.


The system was processing an automated test job in Beaker. I connected to the serial console and saw that there was an error bringing up the network interface.
Afte clicking OK I saw eht0 and eth1 and a usb interface I think. I selected eth0 and pressed Next. After a while I saw this traceback on the console.
Comment 3 Radek Vykydal 2011-04-13 15:04:43 UTC 
Created attachment 491794 [details]
syslog from the beaker
Comment 4 Radek Vykydal 2011-04-13 15:05:24 UTC 
Created attachment 491795 [details]
anaconda.log from the beaker
Comment 5 Radek Vykydal 2011-04-13 15:31:09 UTC 
I suspect removal of HWADDR from ifcfg file (bug #690589) being responsible. From the logs it can be seen that NM tries to bring up all network devices regardless of NM_CONTROLLED and ONBOOT value and I guess this bug is a consequence of this. I confirmed with Fedora master that bringing the HWADDR value back fixes this.
Comment 6 David Cantrell 2011-04-13 19:53:00 UTC 

*** This bug has been marked as a duplicate of bug 696127 ***
Note You need to log in before you can comment on or make changes to this bug.