Currently (after my nm-c-e integration set of patches) we set a network device
as NM_CONTROLLED only if it is selected when enabling network (be it in stage
1 or stage 2) or in pre nm-c-e dialog when configuring network in stage 2.

I was thinking about writing out "yes" by default specifically for wireless devices. I wanted to do it already in stage 1, so that setting the wlan as not controlled by NM in stage 2 UI by user is preserved. I've already added some bits we'd need to do this (wireless device detection) to master while working on support for wireless (bug 473803), but wireless support is not going to rhel 6.0.

Alternatively, for 6.0, independently of wireless support patches, I can set wireless devices as NM_CONTROLLED at the beginning of stage 2 with a simple patch below. Maybe it is even better than setting in stage 1 when I am thinking about it now.


diff --git a/network.py b/network.py
index 8b0d109..7c664bf 100644
--- a/network.py
+++ b/network.py
@@ -316,6 +316,8 @@ class Network:
         self.overrideDHCPhostname = False
 
         self.update()
+        # We want wireless devices to be nm controlled by default
+        self.controlWireless()
 
     def update(self):
 
@@ -441,6 +443,11 @@ class Network:
                 ifaces.append(iface)
         return ifaces
 
+    def controlWireless(self):
+        for devname, device in self.netdevices.items():
+            if isys.isWireless(devname):
+                device.set(('NM_CONTROLLED', 'yes'))
+

I think that the simpler solution is to just not write NM_CONTROLLED, period. (either yes or no)

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
inclusion.

This should be fixed in anaconda-13.21.52-1.

*** Bug 606745 has been marked as a duplicate of this bug. ***

Verified on anaconda-13.21.54-1.el6  

I was facing this issue as well and I haven't met this issue on clean install of RHEL 6.0-{20100628, 20100629}.

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.