Bug 469163 - traceback when activating network from boot.iso rescue mode
traceback when activating network from boot.iso rescue mode
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F10Blocker/F10FinalBlocker
  Show dependency treegraph
 
Reported: 2008-10-30 07:33 EDT by James Laska
Modified: 2013-09-02 02:28 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-30 10:17:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
anacdump.txt (56.28 KB, text/plain)
2008-10-30 07:53 EDT, James Laska
no flags Details

  None (edit)
Description James Laska 2008-10-30 07:33:15 EDT
Description of problem:

Traceback when activating network from boot.iso rescuemode

Version-Release number of selected component (if applicable):
anaconda-11.4.1.52 (rawhide-20081030)

How reproducible:
100%

Steps to Reproduce:
1. Boot boot.iso
2. Select rescue and recover system
3. Select lang
                   +---------+ Choose a Language +---------+
                   |                                       |
                   | What language would you like to use   |
                   | during the installation process?      |
                   |                                       |
                   |       Catalan                ^        |
                   |       Chinese(Simplified)    :        |
                   |       Chinese(Traditional)   #        |                    
                   |       Croatian               :        |                    
                   |       Czech                  :        |                    
                   |       Danish                 :        |                    
                   |       Dutch                  :        |                    
                   |       English                v        |
                   |                                       |
                   |                +----+                 |
                   |                | OK |                 |
                   |                +----+                 |
                   |                                       |
                   |                                       |
                   +---------------------------------------+
Running anaconda 11.4.1.52, the Fedora rescue mode - please wait...            
4. Select Yes to enable networking
                    ┌────────┤ Setup Networking ├─────────┐
                    │                                     │
                    │ Do you want to start the network    │
                    │ interfaces on this system?          │
                    │                                     │
                    │      ┌─────┐           ┌────┐       │
                    │      │ Yes │           │ No │       │
                    │      └─────┘           └────┘       │
                    │                                     │
                    │                                     │
                    └─────────────────────────────────────┘
5. Enable eth0, dhcp, and select continue
     ┌───────────────────┤ Enable network interface ├────────────────────┐
     │                                                                   │
     │ This requires that you have an active network connection during   │
     │ the installation process.  Please configure a network interface.  │
     │                                                                   │      
     │  [ ] eth0 - Realtek Semiconductor Co., Ltd. RTL-8139/8139C/813 ↑  │      
     │                                                                ▮  │      
     │                                                                ↓  │      
     │                                                                   │      
     │ [*] Use dynamic IP configuration (DHCP)                           │      
     │ [*] Enable IPv4 support                                           │      
     │ IPv4 Address: ____________________/____________________           │      
     │ Gateway: ____________________  Nameserver: ____________________   │      
     │             ┌────┐                          ┌──────┐              │      
     │             │ OK │                          │ Back │              │      
     │             └────┘                          └──────┘              │
     │                                                                   │
     │                                                                   │
     └───────────────────────────────────────────────────────────────────┘

  
Actual results:

Traceback (most recent call last):              │      
 File "/usr/bin/anaconda", line 748, in <module>
    rescue.runRescue(anaconda, instClass)                              ___________   │
 File "/usr/lib/anaconda/rescue.py", line 195, in runRescue
    if not anaconda.intf.enableNetwork(anaconda): └────┘                          └──────┘              │
 File "/usr/lib/anaconda/rescue.py", line 87, in enableNetwork
    ret = w.run()                                                        
 File "/usr/lib/anaconda/textw/netconfig_text.py", line 265, in run
    result = self.anaconda.id.network.bringUp()   
 File "/usr/lib/anaconda/network.py", line 717, in bringUp
    self.write()                    
 File "/usr/lib/anaconda/network.py", line 662, in write
    shutil.copy('/etc/resolv.conf', destresolv)
 File "/usr/lib64/python2.5/shutil.py", line 80, in copy
    copyfile(src, dst)                                                                       
 File "/usr/lib64/python2.5/shutil.py", line 41, in copyfile
    raise Error, "`%s` and `%s` are the same file" % (src, dst)
shutil.Error: `/etc/resolv.conf` and `/etc/resolv.conf` are the same file

install exited abnormally [1/1] 
disabling swap...
unmounting filesystems...
/mnt/runtime done
disabling /dev/loop0 LOOP_CLR_FD failed: 16
/proc done
/dev/pts done
/sys done
/mnt/stage2 done
/selinux done
sending termination signals...done
sending kill signals...done
you may safely reboot your system


Expected results:


Additional info:

Even with dhcp selected, I am able to change the ipv4 static ip fields.
Comment 1 James Laska 2008-10-30 07:41:20 EDT
Additional info:
 * This same traceback occurs when trying to enable networking in stage#2.
Comment 2 James Laska 2008-10-30 07:53:12 EDT
Created attachment 321919 [details]
anacdump.txt

Attaching anacdump.txt from stage#2 network activation (same traceback different 'steps to reproduce')
Comment 3 Chris Lumens 2008-10-30 10:17:25 EDT
Fixed with commit 4eed53799fe8cc91e4065a4ddc9b5bab2a3e6ace, which I thought had a bug number associated with it but I guess not.  This should be in the next build of anaconda.

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