Uploaded image for project: 'Puppet Enterprise'
  1. Puppet Enterprise
  2. ENTERPRISE-1249

Puppet Master Installation on FIPS enabled RHEL fails for PE 2018.1.7


    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Won't Do
    • Affects Version/s: PE 2018.1.7
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Method Found:
      Customer Feedback
    • QA Risk Assessment:
      Needs Assessment


      Puppet Version: 5.5.10
      Puppet Server Version: 2018.1.7
      OS Name/Version: RHEL 7.6

      Immediately after a successful installation/upgrade of Puppet 2018.1.7 on a FIPS enabled RHEL7.6 system, running puppet agent -t on the master node fails with the following error:

      Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Unable to generate package repository configuration. Platform described by facts['platform_tag'] 'redhatfips-7-x86_64' is not a known master platform. (file: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/repo/config.pp, line: 158, column: 9)


      This issue isn't observed after a successful installation of Puppet 2019.0.1 in the same configuration.

      Desired Behavior:

      Puppet installation of the LTS branch should not have an issue installing on FIPS enabled systems.

      Actual Behavior:

      Using 'puppet facts show' on the system for two different configurations (2018 and 2019) shows the platform_tag fact to be identical in both configurations when FIPS mode is enabled for the system:

      "platform_tag": "redhatfips-7-x86_64",

      When the system is configured with 2018 puppet installed, the fipsmode issue arises while when installed with 2019, the issue does not occur.





          Issue Links



              • Assignee:
                fishy Matt Mason
              • Votes:
                2 Vote for this issue
                7 Start watching this issue


                • Created:

                  Zendesk Support