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 1328807 - IPA upgrade fails for upgrade path 7.0 to 7.2up4.
Summary: IPA upgrade fails for upgrade path 7.0 to 7.2up4.
Keywords:
Status: CLOSED DUPLICATE of bug 1328522
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Harmsen
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 10:21 UTC by Nikhil Dehadrai
Modified: 2016-05-07 01:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-05 19:43:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Console output ipa update 7.0 to 7.2up4 (139.06 KB, text/plain)
2016-04-20 10:21 UTC, Nikhil Dehadrai 		no flags Details
ipaupgrade.log (4.29 MB, text/plain)
2016-04-20 10:29 UTC, Nikhil Dehadrai 		no flags Details
pki logs (157.36 KB, application/x-gzip)
2016-04-20 10:31 UTC, Nikhil Dehadrai 		no flags Details
View All

Description Nikhil Dehadrai 2016-04-20 10:21:39 UTC 
Created attachment 1148990 [details]
Console output ipa update 7.0 to 7.2up4

Description of problem:
IPA upgrade fails for upgrade path 7.0 to 7.2up4.

Description of problem:
IPA upgrade fails for upgrade path 7.1.z to 7.2up4.

Version-Release number of selected component (if applicable):
ipa-server-4.2.0-15.el7_2.15.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Setup IPA server at RHEL 7.0 version (ipa-server-3.3.3-28.el7.x86_64)
2. Setup 7.2 up4 repo links on this server.  
3. Now update the ipa server using command "yum -y update ipa*"

Actual results:
After step3, Following error message is observed on the console:

IPA server upgrade failed: Inspect /var/log/ipaupgrade.log and run command ipa-server-upgrade manually.
Unexpected error - see /var/log/ipaupgrade.log for details:
CalledProcessError: Command ''/bin/systemctl' 'start' 'pki-tomcatd'' returned non-zero exit status 1
(Refer attachment)

Expected results:
No error message should be observed during IPA server upgrade and update should be successful.

Additional info:
1. This issue was not observed for upgrade path from 7.0(GA) to 7.2 up2.
Comment 1 Nikhil Dehadrai 2016-04-20 10:27:57 UTC 
Kindly ignore only the following line inside  above description, since it got copied mistakenly:

"Description of problem:
IPA upgrade fails for upgrade path 7.1.z to 7.2up4."
Comment 2 Petr Vobornik 2016-04-20 10:29:31 UTC 
seems to me as dup of bug 1328602, i.e. caused by bug 1328522. Could you attach both ipaupgrade.log and /var/log/pki/pki-server-upgrade-10.2.5.log or similar to verify.
Comment 3 Nikhil Dehadrai 2016-04-20 10:29:47 UTC 
Created attachment 1149007 [details]
ipaupgrade.log

Please find attached ipaupgrade log.
Comment 4 Nikhil Dehadrai 2016-04-20 10:31:05 UTC 
Created attachment 1149009 [details]
pki logs

Please find the attached pki logs.
Comment 7 Petr Vobornik 2016-04-20 11:20:20 UTC 
pki-server-upgrade-10.2.5.log shows:

Upgrading server at Wed Apr 20 15:23:25 IST 2016.
Traceback (most recent call last):
  File "/sbin/pki-server-upgrade", line 194, in <module>
    main(sys.argv)
  File "/sbin/pki-server-upgrade", line 187, in main
    upgrader.upgrade()
  File "/usr/lib/python2.7/site-packages/pki/upgrade.py", line 650, in upgrade
    versions = self.versions()
  File "/usr/lib/python2.7/site-packages/pki/upgrade.py", line 483, in versions
    current_version = self.get_current_version()
  File "/usr/lib/python2.7/site-packages/pki/server/upgrade.py", line 299, in get_current_version
    tracker = self.get_server_tracker(instance, subsystem)
  File "/usr/lib/python2.7/site-packages/pki/server/upgrade.py", line 259, in get_server_tracker
    tracker = self.subsystem_trackers[instance]
TypeError: unhashable type: 'PKIInstance'

which is the same as in bug 1328522

connection errors follows in system and debug log
Comment 8 Petr Vobornik 2016-04-20 11:38:41 UTC 
moving to PKI component to assess. I would close it as a dup of bug 1328522.
Comment 9 Ade Lee 2016-05-05 19:43:08 UTC 

*** This bug has been marked as a duplicate of bug 1328522 ***
Note You need to log in before you can comment on or make changes to this bug.