Bug 1296196

Summary: Sysrestore did not restore state if a key is specified in mixed case
Product: Red Hat Enterprise Linux 7 Reporter: Petr Vobornik <pvoborni>
Component: ipaAssignee: Pavel Picka <ppicka>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.3CC: ekeck, enewland, ksiddiqu, mbasti, mkosek, ppicka, rcritten
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: ipa-4.2.0-16.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1298101 (view as bug list) Environment:
Last Closed: 2016-11-04 05:48:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1298101    
Attachments:
Description Flags
evidence none

Description Petr Vobornik 2016-01-06 15:05:36 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/5574

When DNSSEC master is installed on server, after uninstallation state
{{{
[ods-enforcerd]
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]
evidence

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.

https://rhn.redhat.com/errata/RHBA-2016-2404.html