Bug 1296196 - Sysrestore did not restore state if a key is specified in mixed case
Summary: Sysrestore did not restore state if a key is specified in mixed case
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: All
OS: All
Target Milestone: rc
: ---
Assignee: Pavel Picka
QA Contact: Namita Soman
Depends On:
Blocks: 1298101
TreeView+ depends on / blocked
Reported: 2016-01-06 15:05 UTC by Petr Vobornik
Modified: 2016-11-04 05:48 UTC (History)
7 users (show)

Fixed In Version: ipa-4.2.0-16.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1298101 (view as bug list)
Last Closed: 2016-11-04 05:48:04 UTC
Target Upstream Version:

Attachments (Terms of Use)
evidence (3.95 KB, text/plain)
2016-08-16 10:11 UTC, Pavel Picka
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Petr Vobornik 2016-01-06 15:05:36 UTC
This bug is created as a clone of upstream ticket:

When DNSSEC master is installed on server, after uninstallation state
kasp_db_configured = True
is still there, even if uninstaller tries to remove it with restore_state().

This is caused by mixed case of "KASP_DB_configured" that is used in code (see that this has been saved as lower case in statefile). When I changed this value to lower case in code, it worked.

Possible solutions:
1) fix sysrestore

2) change key "KASP_DB_configured" to lower case and allow to store only keys in lower case

Comment 3 Martin Kosek 2016-01-12 15:59:59 UTC
Upgrade breakage - high prio/sev.

Comment 7 Pavel Picka 2016-08-16 10:11:41 UTC
Created attachment 1191191 [details]

Verified on 4.4.0-7.el7.x86_64

Comment 9 errata-xmlrpc 2016-11-04 05:48:04 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.


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