Bug 2211452

Summary:	Red Hat Satellite 6 upgrade fails with Error : Error while evaluating a Function Call, Class[Apache]: parameter 'trace_enable' expects a match for Enum['Off', 'On', 'extended']
Product:	Red Hat Satellite	Reporter:	vivek singh <vivsingh>
Component:	Upgrades	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.12.4	CC:	ehelms, mkalyat, rlavi
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused	Flags:	ehelms: needinfo?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 vivek singh 2023-05-31 16:41:06 UTC

Description of problem: Red Hat Satellite 6 upgrade fails with Error : Error while evaluating a Function Call, Class[Apache]: parameter 'trace_enable' expects a match for Enum['Off', 'On', 'extended']


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


How reproducible: always


Steps to Reproduce:

1. Uncomment  parameter "apache::trace_enable: Off" from file /etc/foreman-installer/custom-hiera.yaml

2. Now try to upgrade satellite from 6.12 to 6.13.

3. Upgrade will fail with below error.  
~~~~~~~~
[ERROR ] [configure] Evaluation Error: Error while evaluating a Function Call, Class[Apache]: 
 parameter 'trace_enable' expects a match for Enum['Off', 'On', 'extended'], got Boolean (file: /usr/share/foreman- 
 installer/modules/foreman/manifests/config/apache.pp, line: 161, column: 5) on node satellite.example.com
~~~~~~~~

Actual results: Upgrade fails. 


Expected results: upgrade should be a success


Additional info: 
1- By-default parameter "apache::trace_enable: Off" is commented on satellite inside file - /etc/foreman-installer/custom-hiera.yaml 

2- Upgrade check does not give or hint about any such error. this error comes only running actual upgrade .

Comment 2 Eric Helms 2023-06-01 13:04:21 UTC

Do you know why customers are setting this value through custom hiera?

Comment 4 Eric Helms 2023-06-13 18:52:28 UTC

Any value set in custom hiera is subject to breakage as the use of custom_hiera is not a supported API and relies on internal APIs that can break between releases. Any values in custom_hiera should be done so with caution and understanding that it may change, or need to be removed. There are KCS articles, and even some references at times in our tuning guide to values being set in there if there is no other options. Therefore, if upgrade is broken with this value in custom hiera it is expected that the user will remove it and perform a clean upgrade. If this functionality is needed in a permanent way for the user, a bugzilla should be filed requesting support for this.