Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1571

The function generate() should merge stdout and stderr

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 2.7.0
    • Component/s: None
    • Labels:
    • Environment:
    • Template:
    • Team:
      Systems Engineering
    • Story Points:
      3
    • Sprint:
      SE 2016-10-05, SE 2016-10-19
    • CS Priority:
      Reviewed
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      There was a bug in Puppet Server versions prior to 2.7.0 wherein calling the `generate()` function did not merge the output from {{STDERR}} into the output from {{STDOUT}}. This bug is fixed on 2.7.0 and the output from {{STDERR}} is now included.

      Description

      description

      The function generate() does not merge stdout and stderr using a puppet4 master. It works as expected on a v3 master, or using puppetv4 apply.

      #!/bin/sh
       
      echo -n stdin
      echo -n stderr 1>&2
      

      class manifests::test_util_exec {
        $_msg = generate('/tmp/test2')
        notify { 'test_util_exec':
          message => $_msg
        }
      }
      

      puppetv4 master

      Notice: stdin
      Notice: /Stage[main]/Manifests::Test_util_exec/Notify[test_util_exec]/message: defined 'message' as 'stdin'
      Notice: Finished catalog run in 32.46 seconds
      

      puppetv3 master

      Notice: stdinstderr
      Notice: /Stage[main]/Manifests::Test_util_exec/Notify[test_util_exec]/message: defined 'message' as 'stdinstderr'
      Notice: Finished catalog run in 32.50 seconds
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                chris Chris Price
                Reporter:
                faxmodem Fabien Wernli
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support