Bug 170603 - Default Values for Macros in Config file channels not supported as documented
Summary: Default Values for Macros in Config file channels not supported as documented
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: RHN Stable
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike McCune
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-13 11:59 UTC by Bowe Strickland
Modified: 2008-10-16 13:52 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-10-16 13:52:56 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.