Bug 170603

Summary: Default Values for Macros in Config file channels not supported as documented
Product: [Retired] Red Hat Network Reporter: Bowe Strickland <bowe>
Component: RHN/Web SiteAssignee: Mike McCune <mmccune>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: RHN StableCC: acarter, rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-16 13:52:56 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 Bowe Strickland 2005-10-13 11:59:27 UTC
Description of problem:

macros should be able to provide default values, but don't seem to.


Version-Release number of selected component (if applicable):
4.0.1


How reproducible:
very

Steps to Reproduce:
1. create Custom Info tag named "asset"
2. create config channel file w/ following macro cut and pasted from Docs:

	 asset={@ rhn.system.custom_info(asset) =
	  'Asset #' @} 

3. submit edits
  
Actual results:

  top of page error: Invalid macro function name in file contents: 'Asset #'


Expected results:

   clean submission of edits

Additional info:

  surprisingly, seems to be whitespace dependent... if new line is removed
  (and possible offending '#' metacharacter is removed):

       asset={@ rhn.system.custom_info(asset) =  'Asset default' @} 

  error messgae becomes:

     Invalid macro token in file contents: rhn.system.custom_info(asset) =
'Asset default'

  if default value is removed: 

        asset={@ rhn.system.custom_info(asset) @} 

   all is fine.

Comment 1 Bret McMillan 2006-08-29 16:55:53 UTC
Old, mis-filed bug.  Mike, I think this was meant to report an issue with the
webui, can you triage this?

Comment 2 Amanda Carter 2008-10-16 13:52:40 UTC
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.