Bug 888128

Summary: Unable to match Server configurations when missing slashes
Product: [Community] PressGang CCMS Reporter: Lee Newson <lnewson>
Component: CSProcessorAssignee: pressgang-ccms-dev
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: jwulf
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 0.28.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-07 01:29:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lee Newson 2012-12-18 03:34:25 UTC 
Given the following settings:

csprocessor.ini

    # Production Server settings
    production.url=http://localhost:8080/TopicIndex
    production.username=jwulf

csprocessor.cfg

    SPEC_ID=12807
    SERVER_URL=http://localhost:8080/TopicIndex

The following error occurs:

ERROR: No credentials are setup for the "http://localhost:8080/TopicIndex" server specified in the csprocessor.cfg file. Please setup the server in your csprocessor.ini configuration file.


Workaround:

You can work around this error by adding the trailing slash in the csprocessor.cfg file. eg:

csprocessor.cfg

    SPEC_ID=12807
    SERVER_URL=http://localhost:8080/TopicIndex/
Comment 1 Lee Newson 2012-12-18 23:32:17 UTC 
Fixed in version 0.28.5.

Cause:

The java URI equals method assumes that the above two mentioned URL's are different. The csprocessor.ini is run through a method to clean it and make sure it is standard, however the csprocessor.cfg did not.

Consequence:

You'd get the error above.

Fix:

Run the csprocessor.cfg url's through the same cleaning and validation method.
Comment 2 Lee Newson 2013-06-07 01:29:48 UTC 
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.