Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 744798 - Traceback when upgrading from ipa-server-2.1.1-1 to ipa-server-2.1.2-2
Traceback when upgrading from ipa-server-2.1.1-1 to ipa-server-2.1.2-2
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa (Show other bugs)
6.2
Unspecified Unspecified
urgent Severity unspecified
: rc
: ---
Assigned To: Rob Crittenden
IDM QE LIST
:
Depends On:
Blocks: 748554
  Show dependency treegraph
 
Reported: 2011-10-10 09:56 EDT by Jakub Hrozek
Modified: 2011-12-06 13:42 EST (History)
3 users (show)

See Also:
Fixed In Version: ipa-2.1.3-1.el6
Doc Type: Bug Fix
Doc Text:
Do not document
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-12-06 13:42:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1533 normal SHIPPED_LIVE Moderate: ipa security and bug fix update 2011-12-05 20:23:31 EST

  None (edit)
Description Jakub Hrozek 2011-10-10 09:56:59 EDT
Description of problem:
I was upgrading a devel VM (RHEL6.2 nightly repos) and saw a traceback:

Updating   : ipa-server-.1.2-2.el6.x86_64                                 90/273 
Upgraded /etc/httpd/conf.d/ipa-pki-proxy.conf to version 1
Traceback (most recent call last):
  File "/usr/sbin/ipa-upgradeconfig", line 187, in <module>
    sys.exit(main())
  File "/usr/sbin/ipa-upgradeconfig", line 184, in main
    upgrade_pki()
  File "/usr/sbin/ipa-upgradeconfig", line 152, in upgrade_pki
    'proxy.securePort', '=') and \
  File "/usr/lib/python2.6/site-packages/ipaserver/install/installutils.py", line 422, in get_directive
    fd = open(filename, "r")
IOError: [Errno 2] No such file or directory: '/etc/pki-ca/CS.cfg'


Version-Release number of selected component (if applicable):
ipa-server-2.1.2-2

Steps to Reproduce:
1. upgrade from ipa-server-2.1.1-1 to ipa-server-2.1.2-2

Additional info:
This instance was installed with --selfsign
Comment 1 Rob Crittenden 2011-10-10 10:17:58 EDT
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1951
Comment 2 Rob Crittenden 2011-10-12 10:18:29 EDT
fixed upstream

master: 5c10f66e4abd35dc24fe65d5916e429bee221093

ipa-2-1: c2ae286e4bcaa64d12b3578c434d2f3f0fed95b4
Comment 4 Martin Kosek 2011-10-31 15:17:12 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Do not document
Comment 5 Namita Soman 2011-11-07 07:56:59 EST
Can you please list which pages to verify the changes on?
Comment 6 Namita Soman 2011-11-07 07:58:02 EST
Oops! Updated wrong bug above...sorry!
Comment 7 Namita Soman 2011-11-07 15:43:22 EST
in looking for ipa-server versions - ipa-server-2.1.1-1 and ipa-server-2.1.2-2
checked brew builds (https://brewweb.devel.redhat.com/packageinfo?packageID=4384) to get these rpms.

But these versions have been deleted.

Any suggestions on how to verify this?
Comment 8 Rob Crittenden 2011-11-07 15:50:37 EST
It was a bug introduced in ipa-server-2.1.2-2 so upgrading from any previous version to any version later than 2.1.2-2 should work. I'd suggest ipa-2.1.1-4 and updating to 2.1.3-9.
Comment 9 Namita Soman 2011-11-07 23:06:46 EST
testing
Comment 10 Namita Soman 2011-11-07 23:50:31 EST
# rpm -q ipa-server
ipa-server-2.1.1-4.el6.x86_64

installed, kinit'd as admin, added new user, kinit'd as this user
upgraded to
# rpm -q ipa-server
ipa-server-2.1.3-8.el6.x86_64
Restarted services:
# ipactl restart
Successfuly kinit'd as user added above
Comment 11 errata-xmlrpc 2011-12-06 13:42:41 EST
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-2011-1533.html

Note You need to log in before you can comment on or make changes to this bug.