Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-7554

Puppet runs fail when hiera.yaml version 3 detected in a module

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: PUP 4.10.1
    • Fix Version/s: PUP 4.10.2, PUP 5.0.0
    • Component/s: None
    • Environment:

      PE 2016.4.5 with Hiera.yaml 3 files in modules

    • Template:
    • Epic Link:
    • Team:
      Agent
    • Sub-team:
    • Story Points:
      1
    • Sprint:
      Agent 2017-05-31, Agent 2017-06-14
    • CS Priority:
      Major
    • CS Impact:
      Customers will experience failures with the existing code set upon an upgrade to the latest LTS release.
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      With the introduction of Hiera 5 there were errors if a module or environment root contained a hiera.yaml in the hiera 3 format. These files were never used earlier, but now those files are part of the hiera 5 configuration. The issue is fixed by ignoring the files if they are version 3 and by logging a warning when encountered. Best practice is to migrate to hiera 5, and otherwise to move those files out of the way.
      Show
      With the introduction of Hiera 5 there were errors if a module or environment root contained a hiera.yaml in the hiera 3 format. These files were never used earlier, but now those files are part of the hiera 5 configuration. The issue is fixed by ignoring the files if they are version 3 and by logging a warning when encountered. Best practice is to migrate to hiera 5, and otherwise to move those files out of the way.
    • QA Risk Assessment:
      Automate
    • QA Risk Assessment Reason:
      covered by unit tests

      Description

      This is a regression when upgrading from the 2016.4.x LTS to 2016.4.5. Puppet version 4.10.1 runs fail when an hiera.yaml version 3 file is found in the module. For a number of reasons, customers may have hiera.yaml files in modules and the environment. There should be a warning about the version and it should be ignores instead of causing a failure.

      Impact
      Customers that upgrade to the latest LTS which have hiera.yaml 3 files in their modules will have failures. The upgrade should allow for customers to migrate into a hiera 5 type environment without failures.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                jarret.lavallee Jarret Lavallee
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support