Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
During the yum update from 2.2.0-16 to 3.0.0-20 I'm seeing this:
Updating : ipa-server-3.0.0-20.el6.x86_64 43/86
Cannot move CRL file to new directory: [Errno 2] No such file or directory: '/var/lib/ipa/pki-ca/publish/MasterCRL.bin'
Updating : ipa-server-selinux-3.0.0-20.el6.x86_64 44/86
But, afterwards, I do see that:
[root@rhel6-1 ipa-upgrade]# ls -ld /var/lib/ipa/pki-ca/publish/MasterCRL.bin
lrwxrwxrwx. 1 root root 57 Jan 9 11:55 /var/lib/ipa/pki-ca/publish/MasterCRL.bin -> /var/lib/ipa/pki-ca/publish/MasterCRL-20130109-113944.der
[root@rhel6-1 ipa-upgrade]# file /var/lib/ipa/pki-ca/publish/MasterCRL-20130109-113944.der
/var/lib/ipa/pki-ca/publish/MasterCRL-20130109-113944.der: data
Looking at the /var/log/ipaupgrade.log file:
2013-01-09T17:55:42Z DEBUG copy_crl_file: /var/lib/pki-ca/publish/MasterCRL.bin -> /var/lib/ipa/pki-ca/publish/MasterCRL.bin
2013-01-09T17:55:42Z DEBUG copy_crl_file: Create symlink /var/lib/ipa/pki-ca/publish/MasterCRL.bin -> /var/lib/ipa/pki-ca/publish/MasterCRL-20130109-113944.der
2013-01-09T17:55:42Z ERROR Cannot move CRL file to new directory: [Errno 2] No such file or directory: '/var/lib/ipa/pki-ca/publish/MasterCRL.bin'
2013-01-09T17:55:42Z DEBUG copy_crl_file: /var/lib/pki-ca/publish/MasterCRL-20130109-113944.der -> /var/lib/ipa/pki-ca/publish/MasterCRL-20130109-113944.der
It looks like it's failing because it tries to create the symlink before copying the .der file to the new location?
Version-Release number of selected component (if applicable):
2.2.0 to 3.0.0 yum update 'ipa*'
How reproducible:
always
Steps to Reproduce:
1. setup rhel 6.3 IPA master server
2. point to rhel 6.4 repos for yum
3. yum update 'ipa*'
Actual results:
works but see this error:
Updating : ipa-server-3.0.0-20.el6.x86_64 43/86
Cannot move CRL file to new directory: [Errno 2] No such file or directory: '/var/lib/ipa/pki-ca/publish/MasterCRL.bin'
Updating : ipa-server-selinux-3.0.0-20.el6.x86_64 44/86
Expected results:
Files copied in appropriate order and no error should be seen here?
Additional info:
see above in description.
This bug could lead to unreachable CRL file as exactly this symlink is read served by httpd to clients and mentioned in published certificates.
I would rather see this included in RHEL-6.4 (if possible) - I will create a patch.
I just found when reproducing the issue in real server that this error message is actually benign and is reported not in the copy phase, but when we try to do `chown' on the copied symlink. This should still be fixed, but it is not a blocker for RHEL 6.4.
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/RHSA-2013-0528.html