+++ This bug was initially created as a clone of Bug #176195 +++ Description of problem: If a numeric attribute such as headerFetchCount, networkRetries, or headerCacheSize is changed to 1 (or 0), the resulting current value becomes "Yes" (or "No"). Once this happens, you can only change the current value between "No" and "Yes". Version-Release number of selected component (if applicable): up2date-4.4.56-3 How reproducible: always. Steps to Reproduce: 1. Run up2date-nox --configure 2. Choose a numeric attribute such as networkRetries 3. Change it to 1 4. <enter> to save and exit 5. Run up2date-nox --configure again to look at the current value. Actual results: networkRetries Yes Expected results: networkRetries 1 Additional info: Once the numeric attribute becomes snagged in the eddy of Yes/No, you can't change it back to a number. Here's an example. Note the networkRetries attribute (#24). I've snipped out everything else. [root@rlx-3-04 tmp]# up2date-nox --configure 24. networkRetries 5 Enter number of item to edit <return to exit, q to quit without saving>: 24 Attribute Name: networkRetries Comment: Number of attempts to make at network connections before giving up Current value: 5 <return for default, enter two spaces and return to clear> New Value: 1 24. networkRetries 1 Enter number of item to edit <return to exit, q to quit without saving>: <enter, save> Run it again: [root@rlx-3-04 tmp]# up2date-nox --configure 24. networkRetries Yes <-- now it says "Yes" instead of 1 Enter number of item to edit <return to exit, q to quit without saving>: 24 Attribute Name: networkRetries Comment: Number of attempts to make at network connections before giving up Current value: Yes New Value: 14 New Value: 1 <-- can't change it back to 1 New Value: 3 <-- can't change it to any number New Value: No <-- can only change it to "No" 24. networkRetries No Enter number of item to edit <return to exit, q to quit without saving>: q Workaround: Edit /etc/sysconfig/rhn/up2date manually.
verified fix with up2date-4.4.67-4 on i386 and x86_64
and ia64
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0098.html