Description of problem: ccs will not generate cacert.pem and privkey.pem files in ~/.ccs, if it's running for a first time on read-only NFS filesystem Version-Release number of selected component (if applicable): ccs-0.16.2-55.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. RHEL6.3 fresh install or manually remove ~/.ccs directory 2. service start ricci 3. mount some NFS storage as readonly and change current directory into it 3. ccs --lsmisc -h localhost sh: 1: Read-only file system Error opening Private Key /root/.ccs/privkey.pem 139859086989128:error:02001002:system library:fopen:No such file or directory:bss_file.c:355:fopen('/root/.ccs/privkey.pem','r') 139859086989128:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:357: unable to load Private Key Unable to connect to localhost, make sure the ricci server is started. 4. no certificates were generated # ls /root/.ccs cacert.config Actual results: ccs will not work without automatically generated certificates Expected results: ccs will generate certificates in any case
Created attachment 643824 [details] Patch to fix bz
Before Fix: [root@ask-02 ~]# rpm -q ccs ccs-0.16.2-55.el6.x86_64 [root@ask-02 ~]# adduser testuser [root@ask-02 ~]# su - testuser [testuser@ask-02 ~]$ cd /var/log [testuser@ask-02 log]$ ccs --lsmisc -h localhost sh: 1: Permission denied Error opening Private Key /home/testuser/.ccs/privkey.pem 139912025880392:error:02001002:system library:fopen:No such file or directory:bss_file.c:355:fopen('/home/testuser/.ccs/privkey.pem','r') 139912025880392:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:357: unable to load Private Key Unable to connect to localhost, make sure the ricci server is started. After Fix: [testuser@ask-02 log]$ rpm -q ccs ccs-0.16.2-57.el6.x86_64 [testuser@ask-02 log]$ ccs --lsmisc -h localhost localhost password: Resource Manager: CMAN: [testuser@ask-02 log]$
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-2013-0453.html