Due to a recent update on Javascript code a full page refresh on your browser might be needed.
Bug 620823 - Ifcfg-rh plugin is not loaded when NM is run in anaconda's loader
Summary: Ifcfg-rh plugin is not loaded when NM is run in anaconda's loader
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 624939 625385 627897 631557 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-03 15:07 UTC by Radek Vykydal
Modified: 2010-09-29 14:26 UTC (History)
12 users (show)

Fixed In Version: anaconda-14.17-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-29 14:26:25 UTC
Type: ---


Attachments (Terms of Use)
Syslog (52.81 KB, text/plain)
2010-08-03 15:07 UTC, Radek Vykydal
no flags Details

Description Radek Vykydal 2010-08-03 15:07:31 UTC
Created attachment 436293 [details]
Syslog

Description of problem:

Ifcfg-rh plugin is not loaded when NM is run in anaconda's loader. Or is it something that should be configured on anaconda side?

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

Fedora 14 TC1
NetworkManager 0.8.1-1.fc14

How reproducible:

Always

Steps to Reproduce:
1. Install F14 TC1 using network repo or stage2
  
Actual results:

Network enablement dialog in anaconda loader is skipped because network had already been brought up automatically when NM was started.

Expected results:

ifcfg config files written by anaconda prevent automatic network activation.

Additional info:

Attaching syslog

Comment 1 Dan Williams 2010-08-17 16:54:20 UTC
We tracked this down to a change NM made for config files; we deprecated nm-system-settings long ago (F13 timeframe) but only now is the NM tarball actually shipping NetworkManager.conf.  So the anaconda image creation scripts should get updated to:

s/nm-system-settings.conf/NetworkManager.conf

everywhere; there are two places to fix for that.

Comment 2 Chris Lumens 2010-08-17 17:02:18 UTC

*** This bug has been marked as a duplicate of bug 623937 ***

Comment 3 Radek Vykydal 2010-08-18 12:05:47 UTC
*** Bug 624939 has been marked as a duplicate of this bug. ***

Comment 4 Radek Vykydal 2010-08-18 13:28:51 UTC
Moving back to assigned as the fix is not in f14-branch yet.

Comment 5 Radek Vykydal 2010-08-18 13:38:15 UTC
Should be fixed in anaconda-14.17-1.

Comment 6 Radek Vykydal 2010-08-19 10:17:16 UTC
*** Bug 625385 has been marked as a duplicate of this bug. ***

Comment 7 Radek Vykydal 2010-08-19 10:33:31 UTC
*** Bug 624992 has been marked as a duplicate of this bug. ***

Comment 8 Radek Vykydal 2010-08-27 10:55:59 UTC
*** Bug 627897 has been marked as a duplicate of this bug. ***

Comment 9 Radek Vykydal 2010-09-13 16:52:21 UTC
*** Bug 631557 has been marked as a duplicate of this bug. ***

Comment 10 Adam Williamson 2010-09-28 00:27:39 UTC
this should be fixed in Beta, can anyone confirm with testing?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 11 Kamil Páral 2010-09-29 11:06:31 UTC
I can confirm that 624939 and 625385 (duplicates of this bug) are fixed in F14 Beta.

Comment 12 Adam Williamson 2010-09-29 14:26:25 UTC
Then let's closerificate it.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


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