Description of problem: If the up2date config file (/etc/sysconfig/rhn/up2date) has storageDir empty or set to an invalid or read-only directory, an error message will pop up when you try to run up2date: "The storage directory /var/spool/up2date could not be found, or was not accessable." The error message should give the actual storage directory you are attempting to access, which is not always '/var/spool/up2date'. It is configurable. Also, "accessable" should be "accessible". Version-Release number of selected component (if applicable): up2date-4.4.67-3 How reproducible: always Steps to Reproduce: 1. Install up2date on a rhel 3 u6 system. Make sure the system has gnome desktop environment installed (up2date '@GNOME Desktop Environment'). 2. Make sure you log in using ssh -Y. 3. Edit /etc/sysconfig/rhn/up2date 4. Change storageDir to something that doesn't exist. 5. Register the system. 6. Run up2date. Actual results: Error window pops up: "The storage directory /var/spool/up2date could not be found, or was not accessable." Expected results: Error window pops up that has the actual directory you configured, not necessarily /var/spool/up2date. And accessible is spelled correctly. Additional info: up2date.checkForStorageDir() calls os.access(storageDir, os.X_OK)
User bnackash's account has been closed
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.