Bug 1196909

Summary: Confusing error message in Dogtag 9
Product: Red Hat Enterprise Linux 7 Reporter: Matthew Harmsen <mharmsen>
Component: pki-coreAssignee: Matthew Harmsen <mharmsen>
Status: CLOSED NOTABUG QA Contact: Asha Akkiangady <aakkiang>
Severity: low Docs Contact:
Priority: low    
Version: 7.0CC: arubin, ksiddiqu, nkinder
Target Milestone: rc   
Target Release: 7.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-15 18:06:58 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:

Description Matthew Harmsen 2015-02-27 00:25:49 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/1282

If the IPA proxy configuration is missing, the installation wizard will generate a cryptic message about XML parsing error:

{{{
[30/Jan/2015:00:05:04][http-9445-1]: WizardPanelBase: pingCS: parser
failedorg.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 50;
White spaces are required between publicId and systemId.
}}}

The installation wizard probably should have checked the HTTP error code before parsing the response data, so a missing proxy problem could be handled in a better way. Also, if the XML parsing failed, the data being parsed should be displayed so it can be troubleshot.

See the following threads:
* https://www.redhat.com/archives/freeipa-users/2015-January/msg00352.html
* https://www.redhat.com/archives/freeipa-users/2015-February/msg00041.html

See also error reporting improvement for Dogtag 10 in ticket #942.

Proposed milestone: 9.0.x
Comment 2 Matthew Harmsen 2016-01-07 01:00:11 UTC 
Per discussions in the RHEL 7.3 Triage meeting of 01/06/2016: priority low

* check to see if this issue is already corrected in Dogtag 10
* remove the proxy configuration file in order to test for the message
Comment 3 Nathan Kinder 2016-06-15 18:06:58 UTC 
This error has only popped up in Dogtag 9.  It does not apply to RHEL 7.x, which uses Dogtag 10.x.  Closing as NOTABUG.