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.
Bug 1167196 - schema update on RHEL-6.6 using latest copy-schema-to-ca.py from RHEL-7.1 build fails
Summary: schema update on RHEL-6.6 using latest copy-schema-to-ca.py from RHEL-7.1 bui...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-24 08:01 UTC by Kaleem
Modified: 2015-03-05 10:15 UTC (History)
2 users (show)

Fixed In Version: ipa-4.1.0-9.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 10:15:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0442 0 normal SHIPPED_LIVE Moderate: ipa security, bug fix, and enhancement update 2015-03-05 14:50:39 UTC

Description Kaleem 2014-11-24 08:01:40 UTC 
Description of problem:

I found this while verifying https://bugzilla.redhat.com/show_bug.cgi?id=1108199 which requires a RHEL-7.1 replica install with a RHEL-6.6 based master.
I copied latest copy-schema-to-ca.py from RHEL-7.1 to RHEL-6.6 master for schema update on RHEL-6.6 master and saw following.

[root@dhcp207-202 ~]# python copy-schema-to-ca.py 
Traceback (most recent call last):
  File "copy-schema-to-ca.py", line 18, in <module>
    from ipaplatform import services
ImportError: No module named ipaplatform
[root@dhcp207-202 ~]#

Version-Release number of selected component (if applicable):
RHEL-7.1 machine:
[root@dhcp207-194 ~]# rpm -q ipa-server
ipa-server-4.1.0-7.el7.x86_64
[root@dhcp207-194 ~]# 

RHEL-6.6 machine:
[root@dhcp207-202 ~]# rpm -q ipa-server
ipa-server-3.0.0-42.el6.x86_64
[root@dhcp207-202 ~]#

How reproducible:
Always

Steps to Reproduce:
1.Copy copy-schema-to-ca.py to RHEL-6.6 machine and execute it

Actual results:
[root@dhcp207-202 ~]# python copy-schema-to-ca.py 
Traceback (most recent call last):
  File "copy-schema-to-ca.py", line 18, in <module>
    from ipaplatform import services
ImportError: No module named ipaplatform
[root@dhcp207-202 ~]#

Expected results:
Schema should have been updated on RHEL-6.6 machine

Additional info:
[root@dhcp207-202 ~]# diff copy-schema-to-ca.py_old copy-schema-to-ca.py_new 
1c1
< #! /usr/bin/python2
---
> #! /usr/bin/python
18,19c18
< from ipaplatform import services
< from ipapython import ipautil, dogtag
---
> from ipapython import services, ipautil, dogtag
34d32
<     "65ipacertstore.ldif",
[root@dhcp207-202 ~]#
Comment 2 Martin Kosek 2014-11-24 11:45:29 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4763
Comment 3 Martin Kosek 2014-11-25 08:22:23 UTC 
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/e57b7b5e87f6510cce5a56e3f050d93b0fefe760
ipa-4-1:
https://fedorahosted.org/freeipa/changeset/f287378534c9b3607b08f71b0c3aa17d2e4008dd
Comment 5 Kaleem 2014-11-26 07:26:50 UTC 
Verified.

[root@dhcp207-194 ~]# rpm -q ipa-server
ipa-server-4.1.0-9.el7.x86_64
[root@dhcp207-194 ~]# 

[root@dhcp207-202 ~]# grep -r "from ipapython import services  # pylint: disable=no-name-in-module" copy-schema-to-ca.py
    from ipapython import services  # pylint: disable=no-name-in-module
[root@dhcp207-202 ~]#

[root@dhcp207-202 ~]# python copy-schema-to-ca.py
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/60kerberos.ldif
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/60samba.ldif
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/60ipaconfig.ldif
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/60basev2.ldif
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/60basev3.ldif
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/60ipadns.ldif
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/61kerberos-ipav3.ldif
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/65ipasudo.ldif
ipa         : INFO     Installed /etc/dirsrv/slapd-PKI-IPA//schema/05rfc2247.ldif
ipa         : INFO     Restarting CA DS
ipa         : INFO     Schema updated successfully
[root@dhcp207-202 ~]#
Comment 7 errata-xmlrpc 2015-03-05 10:15:45 UTC 
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/RHSA-2015-0442.html
Note You need to log in before you can comment on or make changes to this bug.