Puppet Community

Enjoy your holidays and take your time :blush:

<@U17J6MKV5> i know you have a few open PRs and things wiht us right now! thank you! iv got a few holidays and things on my team right now, but we will do a review and merge as soon as we can, most of them look good!

<@U17J6MKV5> i know you have a few open PRs and things with us right now! thank you! iv got a few holidays and things on my team right now, but we will do a review and merge as soon as we can, most of them look good!

The puppet-announce mailing list is a good place to get this info. It's low volume as the only messages sent out are for product releases:

<https://groups.google.com/g/puppet-announce/c/NJsRPQ10i_A>

Blog posts are in the works and should be showing up over the next few days.

set the channel topic: Puppet Enterprise 2021.7: Empowering automation and compliance simply, safely, and at scale. <https://puppet.com/docs/pe/2021.7/release_notes_pe.html#release_notes_pe_x-7l>
See the Support Knowledge Base
<https://support.puppet.com/hc/en-us>

This could be a bug, it looks like influxdb will be “helpful” and assume a data type on an insert,

and the next time the insert happens if the value doesnt conform, this happ[ens

Could you raise an issue  in github, we may need to be explicit with some datatypes

So from what im reading  in another similar case

```You've previously written that field as a float, but now you're sending an integer. Make sure you continue to send a float.
If you continue with an integer, it will eventually work when the shard rolls over; as type checks are only enforced within a shard. This can lead to longer term problems."```

So the issue should be transient and may just “start working” at some point, but we will nail it to a specific datatype to avoid the issue

I raised <https://github.com/puppetlabs/puppet_operational_dashboards/issues/78>

Thank you! yeah it popped up on my dash a few seconds ago!

hey people, it's me again. PE can provide a shell/bash script that agents can download to install itself. Is there any documentation about it and its parameters online?

<https://puppet.com/docs/pe/2019.8/installing_agents.html#using_install_script-csr-attribute-settings>

it’s a bit weird to me.  Used to be a single curl string, but now they’re doing the URI on a separate line and stuff…

One extra stealth flag that isn’t documented is `--puppet-service-debug` that passes `--debug` to `puppet resource` when controlling the puppet service.

I believe that is due to some increased logging we added to 2021.7 to help diagnose connection issues.  What is the log message that immediate precedes it?

it's in puppetserver, but it doesn't indicate a line in Puppetfile

seems it complains on each single line there

It is related to the r10k process that generates that output, I believe.  There should be a line with a timestamp and other parts that precede that.

<https://tickets.puppetlabs.com/browse/ENTERPRISE-1461> :slightly_smiling_face:

Always good when I'm not the only person raising issues :smile:

I also get
```Failed to authenticate SSH session: Unable to send userauth-publickey request at /opt/puppetlabs/server/data/code-manager/worker-caches/deploy-pool-1-1/```
once in a blue moon, for one branch out of many in control repo

<https://github.com/puppetlabs/r10k/tree/3.15.1>  which is why that issue was closed, I believe.

but this is totally unrelated to the r10k version

it's about the version of rugged not really supporting ruby 2.7

which is why the Gemfile for r10k was updated to pull in rugged 1.x: <https://github.com/puppetlabs/r10k/blob/main/Gemfile#L5> just PE doesn't care about it and vendors an ancient version

ah lol, maybe forget everything I wrote here

I fixed a very similar issue with PDK  for that depreciated message <https://github.com/puppetlabs/pdk/pull/1177>

which they have done in later versions of rugged <https://github.com/libgit2/rugged/commit/a4ad1dff3d6f7418eda6bbbeb24f70b6e0d43237>

TIL: uppercase characters aren't allowed in environment names, but they do work for the puppet agent, just PE plans/tasks don't like it :smile:

hmm, why they don't allowed? have been using them for years?

seems modern requirement <https://puppet.com/docs/puppet/7/lang_reserved.html#lang_acceptable_char-environment-names>

imho, PE should `fix` it when
```puppet_enterprise::master::code_manager::invalid_branches: correct```

it's at least documented for Puppet 6 as well

PE creates environments, not me :slightly_smiling_face:

its the not being able to use - and therefore not having environment names that matches jira tickets properly which kills me :disappointed:

that would be so nice. especially when you create branches out of jira