Re: [Puppet Users] Need help with puppet device and cisco_ios - AGENTLESS PROXY

2019-05-24 Thread Will Meek
Hi Thorben, Did you use device_manager to set up your credentials? Can you confirm that you can ping / access the address specified from your proxy host? Thanks Will On Thu, May 23, 2019 at 9:13 PM 'Thorben Brakel' via Puppet Users < puppet-users@googlegroups.com> wrote: > Hello, I want to use

[Puppet Users] SRV-Records and puppetserver

2019-05-24 Thread Karsten Heymann
Hi everyone, I have a question: Is the puppetserver expected to honor the srv records to find the puppet ca server? We have the problem that since switching our puppet server detection from explicit settings in the puppet.conf-File to srv records, we cannot remove certificates from puppetserver an

[Puppet Users] Re: SRV-Records and puppetserver

2019-05-24 Thread Karsten Heymann
Addition: 'puppet cert clean ' still works. So this looks very much like a regression introduced by the switch from puppet to puppetserver for certificate handling. @Puppetlabs people: Should I open a jira ticket for this? Best regards Karsten Am Freitag, 24. Mai 2019 14:29:31 UTC+2 schrieb

Re: [Puppet Users] Re: SRV-Records and puppetserver

2019-05-24 Thread Maggie Dreyer
Yes, this is a known bug, and we do already have a ticket for it, https://tickets.puppetlabs.com/browse/SERVER-2451. We are planning a round of improvements and bug fixes for the `puppetserver ca` CLI, and this is high on the list. I'm glad you found a workaround. Since the CLI tool is shipped as

[Puppet Users] Server Error: Data Provider type mismatch: Got String when a hash-like object was expected

2019-05-24 Thread Vivek kulkarni
we got an error as per subject in which we are just created one file name as version.yaml in which we can define node specific application related rpms are stored and that could we access by creating an alias in node.yaml file and ran puppet then it gives below error Error: Could not retrieve

[Puppet Users] Re: Updates to CA command line interaction in Puppet 6

2019-05-24 Thread Evgenii Fedosov
Hi Maggie, I'm curretly trying to use puppetserver ca commands on m puppetserver but getting the following error message: puppetserver: 'ca' is not a puppetserver command. See 'puppetserver --help' I've dug through a ton of information but none of it references this exact message. I'm using pup

Re: [Puppet Users] Re: Updates to CA command line interaction in Puppet 6

2019-05-24 Thread Maggie Dreyer
Hi Evgenii, The `puppetserver ca` command is only available starting in version 5.3.5 of Puppet Server, released last August. Puppet Server 2.8.1 is EOL (along with all of Platform 4) and is not receiving feature updates like this one. You should probably try to use the `puppet cert` command inste

Re: [Puppet Users] Re: [ACTION] Changes to release package links

2019-05-24 Thread Molly Waggett
Hi Yosuke, We will likely remove the release packages from the subdirectories *before* the archives are ready. I'll send an update next week when we have a better sense of the timeline. Let us know if you have any concerns. Thanks! On Thu, May 23, 2019 at 1:13 PM Yosuke Adachi wrote: > Hi Mol

Re: [Puppet Users] Re: SRV-Records and puppetserver

2019-05-24 Thread Karsten Heymann
Hi Maggie, thanks for the confirmation, I will certainly keep an eye on that jira issue. In the meantime I'm fine with using the old cli interface. As our puppet master has no access to the internet and only uses an internal mirror of the puppetlabs apt repo, installing gems is usually not wort

Re: [Puppet Users] Re: Updates to CA command line interaction in Puppet 6

2019-05-24 Thread Evgenii Fedosov
Hi Maggie, I realized what the issue was once I posted it of course =) Thank you for your suggestion but unfortunately I've tried using puppet cert but the system says "This command is no longer functional, please use 'puppetserver ca' instead", that's why I was trying the latter initially. I f

[Puppet Users] SSL peer had some unspecified issue with the certificate it received

2019-05-24 Thread Gaurav Bajaj
Hi there, We upgraded to puppet 5.5.0 recently, so far it's working fine but we see lots of issue with SSL certs. Currently, we are using self-signed certs ( I know that's not the best way to handle certs and we do have plans to move away from self-signed certs) We using below API's to delete/