Red Hat Satellite 6 upgrade fails with Evaluation Error: Error while evaluating a Function Call, Lookup of key 'lookup_options' failed

Solution Verified - Updated

Environment

  • Red Hat Satellite 6

Issue

  • Upgrading Red Hat Satellite Server fails with the following error message:

    [ERROR 2020-01-01T12:00:00 main]  Evaluation Error: Error while evaluating a Function Call, Lookup of key 'lookup_options' failed: Unable to parse (/tmp/kafo_hiera20200613-12345-1d89abc/data/custom.yaml): mapping values are not allowed in this context at line 35 column 29 (file: /usr/share/gems/gems/kafo-2.1.0/modules/kafo_configure/manifests/init.pp, line: 14, column: 3) on node satellite.example.com.
    

Resolution

  • Remove/Comment out the following line: =================Memory Tuning========================== from /etc/foreman-installer/custom-hiera.yaml file and re-run the upgrade. The custom-hiera.yaml file should look like as follows:

    mongodb::server::config_data:
       storage.wiredTiger.engineConfig.cacheSizeGB: 4
    

For more KB articles/solutions related to Red Hat Satellite 6.x Installation/Upgrade/Update Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Installation/Upgrade/Update Issues.

Diagnostic Steps

  • The following errors were observed in /var/log/foreman-installer/satellite.log on the Red Hat Satellite server.

    [ WARN 2020-06-13T09:26:39 main]  The function 'hiera_include' is deprecated in favor of using 'lookup'. See https://docs.puppet.com/puppet/5.5/reference/deprecated_language.html\n   (file & line not available)
    [ WARN 2020-06-13T09:26:39 main]  /tmp/kafo_hiera20200613-12345-1d89abc/hiera.conf: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
    [ WARN 2020-06-13T09:26:39 main]    (file: /tmp/kafo_hiera20200613-12345-1d89abc/hiera.conf)
    [ERROR 2020-06-13T09:26:39 main]  Evaluation Error: Error while evaluating a Function Call, Lookup of key 'lookup_options' failed: Unable to parse (/tmp/kafo_hiera20200613-12345-1d89abc/data/custom.yaml): mapping values are not allowed in this context at line 35 column 29 (file: /usr/share/gems/gems/kafo-2.1.0/modules/kafo_configure/manifests/init.pp, line: 14, column: 3) on node satellite.example.com
    [ERROR 2020-06-13T09:26:39 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/functions/yaml_data.rb:36:in `rescue in block in yaml_data'
    [ERROR 2020-06-13T09:26:39 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/functions/yaml_data.rb:23:in `block in yaml_data'
    [ERROR 2020-06-13T09:26:39 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/lookup/context.rb:52:in `cached_file_data'
    
  • Following entries were present in in /etc/foreman-installer/custom-hiera.yaml file on the Red Hat Satellite server.

    =================Memory Tuning==========================
    mongodb::server::config_data:
       storage.wiredTiger.engineConfig.cacheSizeGB: 4
    
  • Make a note of line, column number observed in error trace (For example: (file: /usr/share/gems/gems/kafo-2.1.0/modules/kafo_configure/manifests/init.pp, line: 14, column: 3)). Look for the entries made on line: 14, column: 3 in /etc/foreman-installer/custom-hiera.yaml file.

SBR
Product(s)
Components
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.