@natemccurdy would you happen to know the binary file name I want to call for r10k on windows? I've installed it via gem and I'm not finding a r10k.exe|r10k.bat Reinstall fixed.

This message was deleted.

Tried this but seems to be wrong,

Vagrant.configure('2') { |config| 
    config.vm.boot_timeout = 600
    config.vagrant.plugins = 'oscar' 
}

I got it, I think it was timing out on ssh but reporting that I needed to adjust the boot value. did the trick for me

Vagrant.configure('2') { |config| 
    config.vm.boot_timeout = 300
    config.ssh.connect_timeout = 30
    config.vagrant.plugins = 'oscar' 
}

This message was deleted.

```- lost a level. (Karma: -88)

This message was deleted.

Hello! Our group has been working on upgrading from the old LTS to the current LTS (2021.7). The server and compiler seems okay, but we are getting some nodes failing with the puppet agent with the following message:

Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Unable to parse The incoming YAML document exceeds the limit: 3145728 code points. on node <http://node.name.fqdn.org|node.name.fqdn.org>

Anyone else experience that? We are still working on having the agents upgraded but this worked fine with the old LTS (2019.8). Slack Conversation

This message was deleted.

standard approach is arrange your profiles properly

This message was deleted.

I just spun up a brand new VM based on that, and it works:

[root@agent7 ~]# puppet agent -t
Info: Creating a new RSA SSL key for agent7.vagrant
Info: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for agent7.vagrant
Info: Certificate Request fingerprint (SHA256): A9:FB:3D:CE:02:47:04:BE:D1:F9:E1:00:CF:25:B7:0D:2E:BE:C8:4B:21:39:97:EE:14:30:6A:25:EE:CF:9E:73
Info: Downloaded certificate for agent7.vagrant from <https://server7.vagrant:8140/puppet-ca/v1>
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for agent7.vagrant
Info: Applying configuration version '1668713619'
Info: Creating state file /opt/puppetlabs/puppet/cache/state/state.yaml
Notice: Applied catalog in 0.01 seconds

message has been deleted

Yeah, you can put that in the roles.yaml, make a new line 33 here: https://github.com/natemccurdy/vagrant-puppetserver/blob/control_repo/vagrant-configs/roles.yaml#L32

Is puppet forge down?

seems that way

sure looks it

I assume someone pager is going off already

if it wasn't it is now 😄

This is one of those times I wish I had a mirror of it.

☕ 🧑‍🏫PE Console is about to start up in #CFD8Z9A4T

@natemccurdy I figured it out, had to do with the text formatting of the file, dos2unix fixed config_version.sh , although some providers (mainly related to the archive module) aren't being recognized unless I install them over the top using r10k

something more bizarre then just that file appears to be going on, puppet manifests being applied to the vagrant system are also corrupting files such as /etc/sudoers , /etc/sshd_config, etc as puppet touches them. Trying to run sudo commands will throw errors due to syntax issues in /etc/sudoers. dos2unix fixes the file. I'm going to go back to my original plan of building the host system with Ubuntu Desktop opposed to Windows

something more bizarre then just that file appears to be going on, puppet manifests being applied to the vagrant system are also corrupting files such as /etc/sudoers , /etc/sshd_config, etc with invalid line ends as puppet touches them. Trying to run sudo commands will throw errors due to syntax issues in /etc/sudoers. dos2unix fixes the file. I'm going to go back to my original plan of building the host system with Ubuntu Desktop opposed to Windows

This message was deleted.

This message was deleted.

I don't have a huge experience with the foreman but I know they changed to the plugin system and have https://github.com/theforeman/puppetdb_foreman for Puppetdb

Is there a way to set all *.sh files recursively in a dir, to execute, without using an exec with find? Can it be done natively?

if you are managing the files yes, they would just be file resources, but otherwise no, because puppet doesn't know about managing the files

I am managing the files, but at the directory level recursively