Red Hat Bugzilla – Bug 128058
Deleting ppp options doesn't work correctly
Last modified: 2008-08-02 19:40:37 EDT
Description of problem:After adding the 'active-filter option' to a ppp device and having the activate fail I tried to delete the option. However the option remained in the config file. Version-Release number of selected component (if applicable): How reproducible:For my specific example 100%. I didn't try any varients though. Steps to Reproduce: 1.Go in to network config and using edit add the option 'active-filter outbound' to a dialup ppp device 2.activate the device. You save the config as part of doing this. The activation will fail. 3.Delete the option and then try to activate the device again. The delete will look like it worked in network config, but the option won't get removed from the underlying device config file. Actual results:Removing a ppp option appears to work in network config, but the option remains in the config file. Expected results:The option should get removed. Additional info:
Changing version to correct one. (test1 -> fc3test1, and some were filed as test3 accidentally instead; but clearly must be fc3test1 given the date of filing.)
This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks.
I retested this in FC5 and things still work as described above.
Fix commited to git repository. Should be available in next update.
can this bugs be closed based on the last comment?
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Sorry I took so long to retest this. Adding removing valid options works. Adding active-filter outbound specifically works. Adding bogus options doesn't always give you a warning right away in at least one case results in the option not being saved without a warning. (This happened when I used active filter outbound without the hypen.) So the bug I reported is fixed, but sometimes you don't get warned about bad data.