This may be mentioned elsewhere, but I am curious if there is an intended release date for

Puppet v8

, and/or any planned changes? I see that

v6

is planned for EOL July 2023 and some developers are already referring to

v6

as deprecated...

@canihavethisone just saw that on puppet-dev@:

This note is to inform you that starting with our February release of Open Source Puppet 8, we'll be dropping support for JDK 8.

Hi there, would anyone have experience which puppet module like https://forge.puppet.com/modules/thias/tuned supports Rocky Linux or anything that is part of the RedHat os_family?

that module should be able to, but may need some work to make it happen (given that it hasn't been released in 3 years)

it supports RH/CentOS per the forge page, Rocky is in the same os_family

The latest version of the mysql puppet forge module does not allow for the 'package_name' parameter to be overridden, change my mind! I've tried forcing the mysql-server value for this parameter when calling the class several times, in each case it installs MariaDB instead. The relevant code for this module in the server.pp and params.pp manifests does not look like it cares about that parameter in the class declaration at all. Is this a bug or am I doing something wrong?

The latest version of the mysql puppet forge module does not allow for the 'package_name' parameter to be overridden, change my mind! I've tried forcing the mysql-server value for this parameter when calling the class several times, in each case it installs MariaDB instead. The relevant code for this module in the server.pp and params.pp manifests does not look like it cares about that parameter in the class declaration at all. Is this a bug or am I doing something wrong?

@Daehnomel It does allow the package name to be overidden. See: https://github.com/puppetlabs/puppetlabs-mysql/blob/v13.0.1/manifests/server/install.pp#L11 Note that the title of the resource is hard-coded to

mysql-server

, but the

name

parameter does take its value from

$mysql::server::package_name

So it may appear that the

mysql-server

package is being installed if all you're looking at is the Puppet run's output.... for example you might see something like:

Class[mysql::server::install]/Package[mysql-server]: ensure changed from purged to present

But that's only showing you the title of the resource, not the actual package name being installed.

@Daehnomel It does allow the package name to be overidden. See: https://github.com/puppetlabs/puppetlabs-mysql/blob/v13.0.1/manifests/server/install.pp#L11 Note that the title of the resource is hard-coded to

mysql-server

, but the

name

parameter does take its value from

$mysql::server::package_name

So it may appear that the

mysql-server

package is being installed if all you're looking at is the Puppet run's output.... for example you might see something like:

Class[mysql::server::install]/Package[mysql-server]: ensure changed from purged to present

But that's only showing you the title of the resource, not the actual package name being installed.

To clarify, I had the below class declaration added to my mysql servers, and the module installed mariaDb, not MySQL. I need MySQL, not MariaDB, but this package is damn near hard coded to install mariadb if you're running ubuntu. Can you tell me how to resolve this to get Mysql installed? I have never considered chaning a forge modules code, but I'm about to with this one.

class { '::mysql::server':

                             package_name            => 'mysql-server',

                             package_ensure          => 'present',

                             root_password            =>          $root_password,

                             override_options         =>          $override_options,

                             restart                                             =>          true,

}

To clarify, I had the below class declaration added to my mysql servers, and the module installed mariaDb, not MySQL. Can you tell me why? I have never considered chaning a forge modules code, but I'm about to with this one.

class { '::mysql::server':

                             package_name            => 'mysql-server',

                             package_ensure          => 'present',

                             root_password            =>          $root_password,

                             override_options         =>          $override_options,

                             restart                                             =>          true,

}

if there's an obsoletes the package manager might have replaced it and told puppet "I did what you wanted"

it's not my package manager.

What operating system and version is that Puppet agent running on? And what happens when you try to install "mysql-server" manually using your OS's package manager?

it's not my package manager.

How do you know that? What did you test to verify that to yourself?

To clarify, I had the below class declaration added to my mysql servers, and the module installed mariaDb, not MySQL. I need MySQL, not MariaDB, but this package is damn near hard coded to install mariadb if you're running ubuntu. Can you tell me how to resolve this to get Mysql installed? I have never considered chaning a forge modules code, but I'm about to with this one.

class { '::mysql::server':

                             package_name            => 'mysql-server',

                             package_ensure          => 'present',

                             root_password            =>          $root_password,

                             override_options         =>          $override_options,

                             restart                                             =>          true,

}

As a test, try running this by hand on that host:

sudo puppet resource package mysql-server ensure=present name=mysql-server --debug

What do the debug logs show is happening behind the scenes? You should see exactly the command that Puppet is running to install the package.

Thank you, I'm running Ubuntu 20.04, Puppet Community 7.20.0. and the "apt-get install mysql-server" command installs mysql on this host. I'll post the requested debug logs shortly.

I'm having some sort of cache issue running the debug command, it's not picking up the changes I've made to the development environment since the first time I ran it. The particular issue is that the "package_ensure => 'present" statement was set to " package_ensure => '8.0.31-0ubuntu0.20.04.1" for testing, and this won't change no matter how many times I run it or restart the local puppet agent, or even reload the puppet server service.

In any case, it's not my pacakge manager, I think we've established that.

This message was deleted.

I'd verify that the

class { '::mysql::server': ... }

that you got on the system is the same as what you think was added to your mysql servers. You can look at the catalog in

/opt/puppetlabs/puppet/cache/client_data/catalog/<certname>.json

. Search for

"title": "Mysql::Server",

and verify that the parameters landed as expected.

Does anybody else have this problem: https://tickets.puppetlabs.com/browse/FACT-3168 ?

ah, nice one

is that caused by /etc/resolv.conf being a symlink or by the search entry?

by the search entry

by the search entry

well actually by both

but if you remove the

search .

the fact networking.fqdn resolves to the hostname

but after the reboot

search .

is back because this file (the symlinked one) is written by the service systemd-resolved.