[Bug 517149] New: ALL Yast Network Services Cannot Effect any NIC Device that is Controlled by Network Manager if the User Elects to Use it!

bugzilla_noreply＠novell.com

28 Jun 2009 28 Jun '09

07:26

http://bugzilla.novell.com/show_bug.cgi?id=517149 Summary: ALL Yast Network Services Cannot Effect any NIC Device that is Controlled by Network Manager if the User Elects to Use it! Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alpha096@virginbroadband.com.au QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.10) Gecko/2009042700 SUSE/3.0.10-1.1.1 Firefox/3.0.10 In V11.1 we made the decision that if the user chooses to Manage their NIC, via Network Manager in Yast, that this NIC was only configurable via KDE3 Network Manager. Major problems have occured as a result of this change, the greatest being the Network Manager Applet cannot determine a NIC Device, it only can see any active NIC connection. This being the case Network Manager only Identifies that a NIC is active and assigns this as eth0 For Example. A Motherboard has a MCP61 NIC Disabled in BIOS and a Realtech is present in a PCI slot and active with a connection, NM only sees the Active NIC. Yast for example identifies the NIC as a Device. This is the reason for the vast majority of Network Services that exist in Yast not being able to govern, the NIC that is identified in Network Devices as a device without any configuration. Network Manager holds control over the currently active connection/s I will try to expand the problem from each end below. 1.When Yast is not managing the device, and its not configured due to Network Manager assuming the role, NO Yast service which seeks to effect any Network Device is rendered useless and unable to do this. 2. Thus Network Manager only managing active connections and all Yast Services can only govern a configured device which is not configured due to the above, renders all Yast Services which seek to govern the NIC completely useless. If you need screen shots to illustrate more clearly this information please ask. This explains the issue of the firewall not being able to effect any NIC controlled by Network Manager. Reproducible: Always Steps to Reproduce: 1.As Above 2. 3. Actual Results: The issue of removing Yast control if the user elects to use Network Manager, in retrospect should have never been made as KDE4 Network Manager was not ready and KDE3 Network Manager appears to have been written with little thought, testing and understanding. Expected Results: I trust Network Manager KDE4 in 11.2 will actually work correctly AND IFUP will actually work correctly and be able to assign a static IP with DNS Services with success QA - Due to the severity of thiactually work correctlys issue - request upgrade to Blocker category!!!!!! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date