Hide Forgot
Description of problem: [i386.c yi@dhcp-120 /iparhts/acceptance/ipa-getcert] sudo ipa-getcert request -k /tmp/getcert28343/request_1036.key.pem -f request_1036/28364/NoSuchPem Path "request_1036/28364/NoSuchPem" is not absolute, using "/iparhts/acceptance/ipa-getcert/request_1036/28364/NoSuchPem" instead. The parent of location "/iparhts/acceptance/ipa-getcert/request_1036/28364/NoSuchPem" must be a valid directory. In this test, the file value "request_1036/28364/NoSuchPem" is not acceptable since absolute value required. However, the suggested value "/iparhts/acceptance/ipa-getcert/request_1036/28364/NoSuchPem", which being automatic applied, is also not valid due to suggested file does not exist. --- this is a minor issue, since the command does fail as expected. but giving an incorrect suggesting (and also failed in such scenario) might not be the best implementation. Version-Release number of selected component (if applicable):ipa-client-2.0.0-23.el6.i686 How reproducible: always Steps to Reproduce: 1. install ipa server 2. install ipa client and config it connect to ipa server 3. as root, run command: ipa-getcert request -k /tmp/getcert28343/request_1036.key.pem -f request_1036/28364/NoSuchPem Actual results: failed Expected results: failed, command also recommend a value to use, but also failed after recommend value applied Additional info:
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Verified. RHEL Version: ============= [root@dhcp201-220 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.2 Beta (Santiago) Certmonger Version: ================== [root@dhcp201-220 ~]# rpm -q certmonger certmonger-0.48-1.el6.x86_64 [root@dhcp201-220 ~]# Steps used to verify: ===================== (1)Install certmonger [root@dhcp201-220 ~]# yum install certmonger -y Loaded plugins: product-id, subscription-manager . . Installed: certmonger.x86_64 0:0.48-1.el6 [root@dhcp201-220 ~]# (2)start certmonger service [root@dhcp201-220 ~]# service certmonger start Starting certmonger: [ OK ] [root@dhcp201-220 ~]# (3)Generate a cert request with non-existent file storage [root@dhcp201-220 ~]# getcert request -k /tmp/kaleem/tmp.key -f non-existent/tmp.pem Path "non-existent/tmp.pem" is not absolute, attempting to use "/root/non-existent/tmp.pem" instead. Path "/root/non-existent": No such file or directory. [root@dhcp201-220 ~]# Result: ======= Now certmonger prompts proper error message "No such file or directory" if suggested path does not exists instead of earlier error message "The parent of location /non-existent/tmp.pem must be a valid directory".
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1708.html