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.
Created attachment 1029505[details]
console output with steps
Description of problem:
While verifying https://bugzilla.redhat.com/show_bug.cgi?id=1220788 i encounter this that copy-schema-to-ca.py does not overwrites schema files
Version-Release number of selected component (if applicable):
[root@dhcp207-203 ~]# rpm -q ipa-server
ipa-server-4.1.0-18.el7_1.3.x86_64
[root@dhcp207-203 ~]#
How reproducible:
Always
Steps to Reproduce:
1. Copy copy-schema-to-ca.py to RHEL-6.x master and run there.
2. Run copy-schema-to-ca.py again on RHEL-6.x master
Actual results:
It does not overrides existing schema files
Expected results:
---------
ab> pvoborni_: may be we can add an interactive question and provide some information like size of the file, sha-1 sum of it, then ask whether override is needed
---------
Additional info:
(1) Please find the attached console output with steps.
Verified.
Version ::
ipa-server-4.2.0-12.el7.x86_64
Results ::
[root@vm-idm-004 ~]# vim /etc/dirsrv/slapd-PKI-IPA//schema/05rfc2247.ldif
# added a comment to test this
[root@vm-idm-004 ~]# python /root/copy-schema-to-ca.py
ipa : INFO Target exists, not overwriting: /etc/dirsrv/slapd-PKI-IPA//schema/60kerberos.ldif
ipa : INFO Target exists, not overwriting: /etc/dirsrv/slapd-PKI-IPA//schema/60samba.ldif
ipa : INFO Target exists, not overwriting: /etc/dirsrv/slapd-PKI-IPA//schema/60ipaconfig.ldif
ipa : INFO Target exists, not overwriting: /etc/dirsrv/slapd-PKI-IPA//schema/60basev2.ldif
ipa : INFO Target exists, not overwriting: /etc/dirsrv/slapd-PKI-IPA//schema/60basev3.ldif
ipa : INFO Target exists, not overwriting: /etc/dirsrv/slapd-PKI-IPA//schema/60ipadns.ldif
ipa : INFO Target exists, not overwriting: /etc/dirsrv/slapd-PKI-IPA//schema/61kerberos-ipav3.ldif
ipa : INFO Target exists, not overwriting: /etc/dirsrv/slapd-PKI-IPA//schema/65ipasudo.ldif
ipa : INFO Target file /etc/dirsrv/slapd-PKI-IPA//schema/05rfc2247.ldif exists but the content is different
ipa : INFO Target file: sha1: 8918c442c9d12916a0f4f92dd06517efa823b6e7, size: 3552 B
ipa : INFO Source file: sha1: cf41111c02d7a994709a1d36634adbcaefcf6c33, size: 3518 B
Do you want replace /etc/dirsrv/slapd-PKI-IPA//schema/05rfc2247.ldif file? [yes]: yes
ipa : INFO Installed /etc/dirsrv/slapd-PKI-IPA//schema/05rfc2247.ldif
ipa : INFO Restarting CA DS
ipa : INFO Schema updated successfully
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.
https://rhn.redhat.com/errata/RHBA-2015-2362.html