Re: [Puppet Users] Re: Upgrade to puppet-agent 5.3.5 report failure

On Fri, Nov 30, 2018 at 7:39 AM Darragh Bailey wrote: > > > On Thursday, November 29, 2018 at 11:27:13 AM UTC, Darragh Bailey wrote: >> >> >> >> On Wednesday, November 28, 2018 at 6:32:44 PM UTC, Eric Sorenson wrote: >>> >>> Hi Darragh, the fact that the error message contains a '400' error >>> s

[Puppet Users] Bolt 1.4.0 now available

Greetings! We're happy to announce the release of Bolt 1.4.0. Highlights in this release include: - Using Bolt `apply` with orchestrator - Adding targets to an inventory group during plan execution - Additional plan test helpers For more information, check out the release notes: https:/

Re: [Puppet Users] error signing certs

Thanks for the pointer! That fixed the problem. Kay > > On 30. Nov 2018, at 16:35, Kay Nettle wrote: > > > > I updated the puppetserver on a bionic machine to 6.0.2-1bionic and I > > can no longer sign certs. I get this error: > > > > Error: > >code: 403 > >body: Forbidden request: /p

Re: [Puppet Users] Re: Puppet Certificate Issues

Hi Rohit, I don't have great ideas about what's going on in your environment. Are you using custom built containers or the puppet namespaced containers from hub.docker.com. You could try applying this patch ( https://github.com/puppetlabs/puppetdb/commit/a1ab2f50598f12ac51acb21f256232143891dbc1) a

Re: [Puppet Users] error signing certs

> On 30. Nov 2018, at 16:35, Kay Nettle wrote: > > I updated the puppetserver on a bionic machine to 6.0.2-1bionic and I > can no longer sign certs. I get this error: > > Error: >code: 403 >body: Forbidden request: /puppet-ca/v1/certificate_statuses/any_key > (method :get). Please see

[Puppet Users] Re: Upgrade to puppet-agent 5.3.5 report failure

On Thursday, November 29, 2018 at 11:27:13 AM UTC, Darragh Bailey wrote: > > > > On Wednesday, November 28, 2018 at 6:32:44 PM UTC, Eric Sorenson wrote: >> >> Hi Darragh, the fact that the error message contains a '400' error >> suggests the problem happens on the server when it receives the rep

[Puppet Users] error signing certs

I updated the puppetserver on a bionic machine to 6.0.2-1bionic and I can no longer sign certs. I get this error: Error: code: 403 body: Forbidden request: /puppet-ca/v1/certificate_statuses/any_key (method :get). Please see the server logs for details. The logfile says: 2018-11-30T09:01

[Puppet Users] Re: Problem starting with cisco_ios

Hi Angel, I'm having a look at this now. The manifest you supplied looks to be device_manager setup, which is executed either by an agent (if set in an environment) or 'puppet apply' rather than 'puppet device'. This sets up the device.conf ready for puppet device. Can you tell me if you get

Re: [Puppet Users] Problem starting with cisco_ios

El 30/11/18 a las 14:29, Ángel L. Mateo escribió: In _manifests/site.pp_ I have: node default {   device_manager {'switch_cisco_pruebas':     type => 'cisco_ios',     credentials => {   address => '1.2.3.4',   port => '22',   username => 'test',   password => 'password',

[Puppet Users] Problem starting with cisco_ios

I'm beginning with puppetlabs/cisco_ios module. For the moment, just a proof of concept. These are the modules I have installed: /etc/puppetlabs/code/environments/ciscotest/modules ├── puppetlabs-cisco_ios (v0.6.1) ├── puppetlabs-concat (v5.1.0) ├── puppetlabs-device_manager (v2.7.0) ├── puppet

Re: [Puppet Users] Re: Puppet.agent with path

Hi, Thanks! Em qui, 29 de nov de 2018 às 14:29, Ben Ford escreveu: > Rafael, if you're trying to execute scripts with a certain path, you'd > provide that at the resource declaration level, like so: > > exec { 'tar -xf /Volumes/nfs02/important.tar': cwd => '/var/tmp', creates > => '/var/tmp/myf