Bug 654121

Summary: Satellite 5.4: Configuration File Macro Delimiter parsed incorrectly resulting in "Invalid macro function name" error
Product: Red Hat Satellite 5 Reporter: Xixi <xdmoon>
Component: Configuration ManagementAssignee: Tomas Lestach <tlestach>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: high Docs Contact:
Priority: urgent    
Version: 540CC: cperry, xdmoon
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-17 22:33:55 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 Xixi 2010-11-16 22:44:30 UTC
Description of problem:
Customer tries to create a configuration file (rhn/configuration/ChannelCreateFiles.do) containing more than 2 "|"s, which results in "Invalid macro function name" error.  For example, attempting to create a file with content "part1|part2|part3" gives "Invalid macro function name part2" error.  Apparently it's mistaking the |'s for macro delimiters {| and |}.  Uploading instead of creating gives same error.

Version-Release number of selected component (if applicable):
Red Hat Network (RHN) Satellite 5.4.0

How reproducible:
Always.

Steps to Reproduce:
1. Create a config channel on Satellite and either create or upload a text file with >= 2 "|"s in it.

Actual results:
"Invalid macro function name" error, config file unable to be created/uploaded

Expected results:
config file created/uploaded successfully

Additional info:
This is a regression from Satellite 5.3.

Comment 1 Xixi 2010-11-16 22:46:37 UTC
Saw 2 diffs between 5.3->5.4 in ConfigurationValidation and filecreate.jsp but doesn't seem that would cause this bug...

Comment 2 Clifford Perry 2010-11-17 22:20:19 UTC
This maybe a dupe/associated with bug 645829.