| When running the `puppetlabs-docker` acceptance test with puppet 7 nightly on Windows we get:
puppet.bat : Warning: Facter: Command C:\Windows\System32\WindowsPowerShell\v1.0\powershell.EXE -NoProfile -NonInteractive -NoLogo -ExecutionPolicy Bypass -c docker network ls | tail -n +2 resulted with the following stderr message: 'tail' is not recognized as an internal or external command, |
+ CategoryInfo : NotSpecified: (Warning:...ternal command,:String) [], RemoteException |
+ FullyQualifiedErrorId : NativeCommandError |
operable program or batch file.
|
The command that generates the error is: https://github.com/puppetlabs/puppetlabs-docker/blob/91a6d69716c78f4f753d45d8359536db72aaad5b/lib/facter/docker.rb#L115 Does not happen on Puppet 6 or Puppet 6 nightly builds. It’s occurring on stock, out-of-the-box” images on Google Cloud and Windows images in VMPooler too. Seems to have been introduced about a week ago - still looking through the previous builds to determine exactly when, however, I do notice this PR made changes to the Facter::Core::Execution::Base.execute_command 6 days ago. |