Closed jackdpeterson closed 6 years ago
This was a local environment issue.
@jackdpeterson what was your exact problem? i have the same problem here only for debian & php7.1
My issue was actually pretty weird — the librarian puppet dependency installation was installing the wrong cached library. If I recall i was referencing the other similarly named library that’s as an older version.
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: ubuntu@ip-172-31-20-126:/usr/lib/php$ dpkg -l | grep puppet ii librarian-puppet 2.2.1-2 all bundler for your puppet modules ii puppet-agent 1.10.9-1xenial amd64 The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective. ii puppetlabs-release-pc1 1.1.0-2xenial all Release packages for the Puppet Labs PC1 repository ii ruby-puppet-forge 2.1.3-1 all Access the Puppet Forge API from Ruby ii ruby-semantic-puppet 0.1.1-1 all Useful tools for working with semantic versions with Puppet
Ruby: (ruby points to 2.3). ii libruby2.3:amd64 2.3.1-2~16.04.5 amd64 Libraries necessary to run Ruby 2.3 ii ruby2.3 2.3.1-2~16.04.5 amd64 Interpreter of object-oriented scripting language Ruby
Distribution: Ubuntu 16.04 (as of 2018-01-12)
Module version: Both 4.0.0-beta1 and puppet-php 5.1.0 are impacted.
How to reproduce (e.g Puppet code you use)
Puppet:
Hiera:
What are you seeing
everything but php7.2-pdo-mysql are installed and configured correctly.
What behavior did you expect instead
Configuration file existing and pointing to the correct pdo_mysql.so (/usr/lib/php/20170718/pdo_mysql.so)
Output log
Repeated execution continues to display:
Any additional information you'd like to impart
manually executing the phpenmod displays a warning.