Bug 1290346 - Upgrading to ipa-server-4.2.0-15.el7_2.3 breaks data version check, breaking entire IPA server
Summary: Upgrading to ipa-server-4.2.0-15.el7_2.3 breaks data version check, breaking ...
Keywords:
Status: CLOSED DUPLICATE of bug 1290142
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-10 09:49 UTC by Patrick Uiterwijk
Modified: 2015-12-10 10:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-10 10:05:49 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Patrick Uiterwijk 2015-12-10 09:49:28 UTC
Description of problem:
After upgrading from ipa-server-4.2.0-15.el7 to 4.2.0-15.el7_2.3, the data version check fails.

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

How reproducible:
Consistent

Steps to Reproduce:
1. Install ipa-server-4.2.0-15.el7
2. Configure ipa
3. Upgrade the package to ipa-server-4.2.0-15.el7_2.3

Actual results:
IPA server fails to start with: IPA version error: data are in newer version than IPA (data version '4.2.0-15.el7', IPA version '4.2.0-15.el7_2.3')

Expected results:
IPA server starts

Additional info:
[root@account log]# ipa-server-upgrade 
session memcached servers not running
IPA server upgrade failed: Inspect /var/log/ipaupgrade.log and run command ipa-server-upgrade manually.
("Unable to execute IPA upgrade: data are in newer version than IPA (data version '4.2.0-15.el7', IPA version '4.2.0-15.el7_2.3')", 1)

Comment 1 Patrick Uiterwijk 2015-12-10 09:54:11 UTC
Downgrading to ipa*-4.2.0-15.el7 fixed it, and allowed me to start the instance back up.

Comment 2 Martin Bašti 🖰 2015-12-10 10:05:49 UTC

*** This bug has been marked as a duplicate of bug 1290142 ***


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