Description of problem: kudzu fails to cope with quoted parameters in ifcfg files Version-Release number of selected component (if applicable): 1.1.95-22 How reproducible: always Steps to Reproduce: 1. edit ifcfg-* files and quote DEVICE/HWADDR lines 2. run kudzu 3. Actual results: kudzu does not match devices and regenerates files Expected results: copes with quoted parameters and uses existing files Additional info:
Created attachment 156685 [details] patch to handle quoted parameters
Seems reasonable. Is there some tool doing this, or is it just admin error?
----- Additional Comments From jon.thomas.com (prefers email at jrthomas.com) 2007-06-14 11:32 EDT ------- RedHat, Looks like Kudzu went thru some some changes between rhel4 and 5 specific to s390 and the functionality of using quotes in the ifcfg-* files was lost. The functionality seems to be present in rhel5 for other platforms. Please let us know how you want to proceed. This event sent from IssueTracker by jkachuck issue 122098
There's nothing specific that would change s390 behavior here - it would be just as broken (or non-broken) as anything else.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
kudzu change built as 1.1.95.24-1.
Actually, re-reading the IBM comments: - We don't want to dequote device - quotes in the device name is legal (if odd). - HWADDR isn't what's causing their issue here Ergo, I don't see any kudzu changes for RHEL 4 that would apply here.
Hi, the RHEL5.2 release notes will be dropped to translation on April 15, 2008, at which point no further additions or revisions will be entertained. a mockup of the RHEL5.2 release notes can be viewed at the following link: http://intranet.corp.redhat.com/ic/intranet/RHEL5u2relnotesmockup.html please use the aforementioned link to verify if your bugzilla is already in the release notes (if it needs to be). each item in the release notes contains a link to its original bug; as such, you can search through the release notes by bug number. Cheers, Don