Bug 75960 - neat-control should be aware of current profile
neat-control should be aware of current profile
Status: CLOSED DUPLICATE
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-15 05:01 EDT by diego.santacruz
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:49:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Snapshot of neat-control showing the problem (21.05 KB, image/png)
2002-10-15 05:02 EDT, diego.santacruz
no flags Details

  None (edit)
Description diego.santacruz 2002-10-15 05:01:14 EDT
Description of Problem:
neat-control should be aware of the current profile and show the
devices for the current profile accordingly. Currently if a device is
present in several profiles redhat-control-network will show the configs
as active in all profiles when the device has been activated in one
profile (see screenshot).

Version-Release number of selected component (if applicable):
redhat-config-network-1.1.20-1

How Reproducible:
Always

Steps to Reproduce:
1. configure a net device eth1 (nickname lts-lan) under profile "LAN"
2. configure a net device eth1 (nickname wireless) under profile "Wireless"
3. set profile to "LAN"
4. activate eth0

Actual Results:
Despite being under different profiles, both devices are shown (without any
mention of their profile nor the active profile). Furthermore both are shown as
active. See next snapshot.

Expected Results:
The current profile should be show.
The devices under the current profile only should be shown (maybe the devices
under other profiles should be shown but differently?).

Additional Information:
redhat-config-network-1.1.20-1
Comment 1 diego.santacruz 2002-10-15 05:02:01 EDT
Created attachment 80465 [details]
Snapshot of neat-control showing the problem
Comment 2 Jon DeSena 2002-11-04 11:18:44 EST
See attached patch to bug #77267 for a solution to this.
Comment 3 Harald Hoyer 2003-01-13 07:25:47 EST

*** This bug has been marked as a duplicate of 77267 ***
Comment 4 Red Hat Bugzilla 2006-02-21 13:49:58 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Comment 5 David Lawrence 2006-04-24 15:17:04 EDT
Adding to blocker bug 185483 and also adding IBM confidential group.
Comment 6 David Lawrence 2006-04-24 15:34:58 EDT
Oops. I am sorry for these changes. I searched on the wrong bug list and
mistakenly made these changes. Removing from blocker bug 185483 and also
removing IBM confidential group.

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