Puppet Community

Yes, I'm aware of this.  I'm just trying to  see the output of the hash  it has going through the code is all.  I know I wont be able to decrypt it.  I have already verified the pw hashes don't match what they should be.

Hello everybody ! I am new here and I am wondering how to run acceptance testing over an specific node instead of running acceptance testing over modules. In example, I am creating system users in a linux machine using the <https://forge.puppet.com/modules/puppetlabs/accounts/readme|Accounts Puppetlabs module> and I set the module configuration to create users and groups via hiera and it works perfect. How can I run the acceptance tests to check that this node has created the users I expect ?

Depends on which acceptance testing tool is in use. For serverspec, that'd be a test against a user resource:

<https://serverspec.org/resource_types.html#user>

Thankyou <@U11MDJNGZ> , about the tests place, as I am using a component from puppetlabs, which path should I use to place this kind of tests?, I am using a copy of puppet-control porject and I have implemented roles and profiles

I am running the module acceptance testing with `bundle exec rspec`  and unit tests with pdk

I'm not sure if this is the proper way but things is going well by the moment :slightly_smiling_face:

`spec/acceptance` is a common location, but again will depend on which acceptance testing tool is in use. Acceptance tests are often run with a different command than unit tests as they are a much, much, much different animal.

Beaker and Litmus are two common acceptance test runners.

The big difference is that a unit test often runs with a lot of logic or context mocked out or simulated (for example, canned Facts instead of actual data from a system) and does not typically go all the way through enforcing a resource.

Acceptance tests, on the other hand, are often run with nothing simulated. A VM or container with the target operating system is created, `puppet-agent` is installed, and resources are enforced for realsies. Then the test runner inspects what actually happened to the operating system and asserts that it meets some expectation.

Yes, I have already written some acceptance tests for severeal modules, I just trying to figure out how to run acceptance test for a node that has an specific role and it uses third party components like the accounts module from puppetlabs.  This information is very apreciated :slightly_smiling_face:

Putting acceptance tests in the `role` or `profile` modules that make assertions about what happens when those components are applied to a node is a reasonable way to do it :+1:

I am sure someone will give you a better answer, but what I do is search through <http://github.com|github.com>.  It has a lot of great repos/commits with examples.

so, I would start with something simple like puppet-chrony first, then puppetlabs-apache (or puppet-nginx) and puppetlabs-postgresql/puppetlabs-mysql

See the `puppet-chrony` module at <https://forge.puppet.com/puppet/chrony?src=slack&amp;channel=puppet>

generally everyone has their own wants on how they configure those services, so there are sane defaults in the puppet modules, but they leave it to the person making the app to choose

<@U9E3APQJK> question for content and tooling team I’d say! It might be good idea to create some simple control repo with a few modules, unit tests and acceptance tests maybe 

a good place to start is probably the control repo template <https://github.com/puppetlabs/control-repo>

if you look at the forks you will find loads of real working control repos

I have this <https://github.com/jay7x/puppetbolt-control_repo|https://github.com/jay7x/puppetbolt-control_repo>.. but 1) it’s designed for Puppet Bolt mainly (though trying to be as close to the usual control repo as possible) and 2) it’s not that simple and easy to understand I think 

I also started with <https://github.com/puppetlabs/control-repo>

Wow thanks everyone for your responses. I am going to be checking these options and try them out.

:indeed: _:teacher:PE Console_ is about to start up in <#CFD8Z9A4T|>

If --debug and --trace does not give you a hint which fact fails, you must check all facts manually. Check each file in /opt/puppetlabs/puppet/cache/lib/facter and /opt/puppetlabs/puppet/cache/lib/facts.d. This is the location of the pluginsync. Remove all facts and add them one-by-one. When you get no output from facter you have found the broken one.

Thank you! I will try that. I hope it is just a custom fact, so i can fix that without a PR on a project xD

It is kinda sad that facter isn't able to give me any error output and handle the situation without becoming dead

<@U11QGB2PN> Thanks again, that was surprisingly easy. It is the kmod fact. Sadly, not one of our custom facts.

you can disable fact collection of specific facts in facter.conf <https://www.puppet.com/docs/puppet/7/configuring_facter.html>

I am currently debugging that fact and it seems like the problem happens when it tries to read from `/sys/module/kvm_intel/parameters/eptad`

People who come after me and have the same problem: I created an issue on github <https://github.com/voxpupuli/puppet-kmod/issues/96>

Late to the party, but wanna ask: how did you get process state? I'm asking because, in `ps o stat`, state "D" doesn't mean dead, but in I/O wait. Which would be the natural state when retrieving facts.

ah this is probably a chicken and egg problem

functions are evaluated on the puppetserver, during catalog compilation

but you use that within another function, postgresql::postgresql_password

so you would need to defer both function calls. or none of them

I'll try that.  I believe I had done that before ( a little bit different setup of vars ) and it worked...however, it was storing a value in the DB for  password that  wasn't correct.

I changed it to this.  The puppet code ran without error and updated the DB password......but it's not correct password hash in the DB :slightly_frowning_face:

cause I'm a n00b and that's what I found  in other code :confused:

what you want to do is defer postgresql::postgresql_password

This?
```password_hash =&gt; Deferred(postgresql::postgresql_password($db_user, $db_password)),```

that might work. I don't know if the function actually supports it

same error of `expects a value of type string.... but got Deferred`

can you paste the code you currently have?

if possible as actual code, not a screenshot :slightly_smiling_face:

```# Setup Postgress for Strapi
class profile::postgresql::config_strapi_db () {

  # DB Variables
  $db_name = 'strapi-db'
  $db_user = 'strapi-admin'
  $db_password_1 = Deferred('vault_key', ['<https://vault00:8200/v1/puppet/data/strapi>', 'puppet-pki', 'tds_strapi_db_password', 'v2'])

# Create Strapi role/user

  # Environment: TDS
  if /^10\.30\./ in $facts['networking']['ip'] {
    $db_password = Deferred('vault_key', ['<https://vault00:8200/v1/puppet/data/strapi>', 'puppet-pki', 'tds_strapi_db_password', 'v2'])
    }
  # Environment: Prod
  elsif /^10\.40\./ in $facts['networking']['hostname'] {
    $db_password = Deferred('vault_key', ['<https://vault00:8200/v1/puppet/data/strapi>', 'puppet-pki', 'prod_strapi_db_password', 'v2'])
  } else {
  # Environment: Infra
  }

  postgresql::server::role { $db_user:
    superuser     =&gt; true,
    password_hash =&gt; Deferred(postgresql::postgresql_password($db_user, $db_password)),
    hash          =&gt; 'scram-sha-256'
  }
  notify { 'debug':
    message =&gt; $db_password
  }
  notify { 'debug1':
    message =&gt; $db_password_1
  }
# Create Strapi db and assign user

  # postgresql::server::db { $db_name:
  #     user     =&gt; $db_user,
  # }
}```

```Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, 'postgresql::postgresql_password' parameter 'password' expects a value of type String, Sensitive[String], or Integer, got Deferred (file: /etc/puppetlabs/code/environments/strapi/local_modules/profile/manifests/postgresql/config_strapi_db.pp, line: 24, column: 31) on node strapi

Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run```

can you try `Deferred(postgresql::postgresql_password($db_user, Sensitive($db_password)))`

```Function Call, 'postgresql::postgresql_password' parameter 'password' expects a value of type String[1], Sensitive[String], or Integer, got Sensitive[Object[{name =&gt; 'Deferred', attributes =&gt; {'name' =&gt; Pattern[/\A[$]?[a-z][a-z0-9_]*(?:::[a-z][a-z0-9_]*)*\z/], 'arguments' =&gt; {type =&gt; Optional[Array], value =&gt; undef}}}]] ```

Why is this sooo hard.  It shouldn't be...ugghh

I'm not sure if nesting two deferred function calls is possible

the `inline_epp` seems to work without error, but can't figure out why it's populating the wrong value in the DB.  Maybe somehow the code is returning an error of `string` type and just passing that in the `password` part and it just hashes that?

your inline_epp example does something completely different

well initially I had the `dp_password` inside of something like this:;

```$variables = {
     'db_password' =&gt; Deferred('vault_key', .......)
}```
And then used a:
```password_hash =&gt; Deferred('inline_epp', [postgresql::postgresql_password($variables[db_user], '&lt;%= $db_password.unwrap %&gt;'),$variables]),```

because that doesn't look like a valid epp template to me

that puts the wrong hash in  the db, but no errors on the puppet deploy side.

yes. It does not execute the `postgresql::postgresql_password` function

it did.  it populated the db with a password

are you sure it was a password? And not just any random string?

It’s a pretty dope community around here.  Welcome

Just tried to run install.sh against Amazon Linux 2023 and for some reason it's thinking it's EL6 but in fact it should be a flavor of FC 34, 35, 36 and CentOS 9 Streams

EL6 might be a fallback since Amazon Linux is Frankenstein's monster.

"FC 34, 35, 36 and CentOS 9" what a abomination :smile:

<@U11JKRSCF> install.sh from which PE version?

:face_with_open_eyes_and_hand_over_mouth:

now is amazon linux 2 the same as amazon linux 2023

<https://www.puppet.com/docs/pe/2019.8/supported_operating_systems.html#supported_operating_systems_and_devices-supported-agent-platforms>

huh i expected this to be about windows :smile:

it's the successor to EL7 ... i'm not moving to Stream