I found this bug in Redmine that sounds like it could be your problem.
http://projects.puppetlabs.com/issues/3234
It looks like a long standing issue, but that Nick L is possibly on to a
solution. Could you review the ticket to see if this is what is affecting
you and if so post your newest info
Have you tried su-ing to the peadmin user on the master node and trying
`mco ping`?
Live Management is basically a front end for actions the peadmin user can
do. Dropping down to that level may let you debug the issue easier.
Other things to check are that activemq is working and correctly
I've used PE with cucumber-puppet before
I put cucumber/cucumber-puppet in the same ruby as PE (which I *think* is a
requirement for cucumber-puppet),
which required manually setting up the dependencies for, and installing
pe-ruby-devel then using /opt/puppet/bin/gem.
Installing the ruby
So, this is an Awesomely un-helpful error message.
First there's two (possibly three) things that happen between the Setting
up puppet agent... message and whatever message comes next (the next
message depends on if you're installing the console or not).
First the installer runs puppet agent -t
On Thu, Apr 5, 2012 at 8:22 AM, Nan Liu n...@puppetlabs.com wrote:
On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz mfgl...@gmail.com wrote:
Removing the default group worked for the most part but I am still
running into some issues
It cataloged correctly and even ran the test class I
On Fri, Jun 15, 2012 at 3:07 PM, hulk15 btholc...@gmail.com wrote:
Hey guys,
Trying to install PE for a PoC and have run into the following: Has
anyone seen this?
Starting puppet: [ OK ]
** chkconfig pe-puppet on
** cp -a
they will conflict
you should definitely look into puppetdb as a more scalable solution
than the active_record terminus for both inventory service and
storeconfigs
storedconfigs stores resources from your puppet manifests and
inventory service stores facts.
- Justin
sorry for the top post
(inventory
service) and puppet resources (storedconfigs) are different however
and even if the tables exist they all won't be populated until you
enable both.
does that make sense?
On Wed, Jul 25, 2012 at 10:46 AM, Justin Stoller jus...@puppetlabs.com
wrote:
they will conflict
you should
On Fri, Aug 10, 2012 at 6:08 AM, Patrick McCarty
patrick.mcca...@gmail.com wrote:
All,
I am evaluating Puppet for a client. It has not been a smooth evaluation. :-)
Sorry to hear that. It's a great tool, but its still got a few edges
that if you fall on can be mighty sharp.
I have four
On Sun, Aug 12, 2012 at 1:35 AM, Samuel José Martín faus...@gmail.com wrote:
Hi,
I am using puppet to generate ipsec tunnels configuration on OpenBSDs
gateways.
Having a bunch of offices, I did something like this:
$enc = $office ?
{
paris =
{
On Tue, Aug 14, 2012 at 7:49 AM, Jen Patrick jenafl...@gmail.com wrote:
It's barfing on this:
Is this in relation to a previous thread?
Error 400 on SERVER: Could not parse for environment production: Syntax
error at '{'; expected '}'
is there a line number?
Here's the node.pp
Does this
On Fri, Aug 17, 2012 at 8:42 AM, llowder llowde...@gmail.com wrote:
I am using puppet 2.7.14 on Ubuntu 10.04 LTS. I have the following gems:
*** LOCAL GEMS ***
diff-lcs (1.1.3)
hiera (0.3.0)
hiera-puppet (0.3.0)
metaclass (0.0.1)
mocha (0.12.1)
puppet-lint (0.1.13)
Hey Jo,
Do you have any debugging information about this issue? Stack traces,
systems, versions, ruby, custom facts, etc would all be helpful. It
certainly seems from what you said that the version of Facter had
something to do with this error, but I'm not exactly sure how Facter
would affect
On Wed, Aug 22, 2012 at 1:34 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Wed, Aug 22, 2012 at 11:08 AM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Aug 21, 2012 at 11:51 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Aug 21, 2012 at 11:44 PM, Douglas
On Sat, Aug 25, 2012 at 6:14 AM, Choon Ming Goh choonming2...@gmail.com wrote:
Hi,
I'm in the middle of setting up jenkins for testing and building our puppet
modules. I'm quite new at this and been trying to make it work the way i
wanted but in reality it doesnt. There are a few
On Sat, Aug 25, 2012 at 3:45 AM, Sandra Schlichting
littlesandr...@gmail.com wrote:
Does there exist a tracker bug of blocking bugs for final release?
Redmine supports filtering tickets by their target version. You can
filter based on which are still open and targeted at 3.0.0. This link
might
On Tue, Sep 25, 2012 at 8:57 AM, Philip Brown p...@bolthole.com wrote:
I tried a few google searches on this, and attempted to look through
docs.puppetlabs.com, but couldnt find anything...
how do you make a module throw an error for an unrecognized parameter?
ie:
class setitup($machtype)
I know that yours was more a question for the community but have you
checked out:
http://docs.puppetlabs.com/puppet/#hacking-and-extending
If those aren't super helpful we'd love to make them better.
HTH,
Justin
On Tue, Sep 25, 2012 at 10:47 AM, Jakov Sosic jso...@srce.hr wrote:
On
On Mon, Oct 1, 2012 at 4:28 PM, Matthaus Owens matth...@puppetlabs.com wrote:
The puppet 3 gem requires hiera, whose latest version requires json,
which can be either json (a c extension), or json_pure (a ruby
implementation). If it is the c extension, make and gcc are required
to build the c
Are you using +ExportCertData in your configuration?
Have a look at: http://projects.puppetlabs.com/issues/16769
and let us know if you think this is what is affecting you.
HTH,
Justin
On Thu, Oct 4, 2012 at 9:47 AM, Jeff McCune j...@puppetlabs.com wrote:
On Thu, Oct 4, 2012 at 2:00 AM,
Try su-ing to the peadmin account and issuing `mco ping`. What kind of
time are you seeing there? Live Management is a GUI front end to using
mcollective and the peadmin account has all of the mco subcommands
added to its path. If there's a reason mcollective is running slowly
it will bog down
On Tue, Dec 18, 2012 at 9:03 PM, lalit jangra lalit.j.jan...@gmail.comwrote:
Hi,
I have an amazon ec2 instance where i have installed puppet from
http://info.puppetlabs.com/download-pe.html. Installation is successful
without any issue as per
There's a completely undocumented (outside of the Pickaxe book) Ruby STDLIB
module called 'expect' that you could use in 1.8.7, open up irb and give it
a whirl. You can find other expect like gems (or at least crib how they're
using the pty)[1]. I think you'll want something like expect4r[2]
On Thu, Feb 7, 2013 at 2:04 PM, Dan McManus mothbitt...@gmail.com wrote:
Hello all!
I am using open source puppet 3.0.1 on both the client and master. The
issue I am having is that I cannot get a simple custom fact to be
recognized in my manifest. Hopefully I am missing something.
I am
On Thu, Feb 14, 2013 at 7:29 AM, jim stra...@gmail.com wrote:
Hello all,
I'm currently running 2.7.19 (Puppet Enterprise 2.7.0)
I want to use puppet to add / amend or delete windows firewall rules, is
there a tidy way of doing this
exec { Check_MK_Firewall_Rule_create:
command =
On Sun, Apr 7, 2013 at 4:16 PM, Joaquin Menchaca joaquin...@gmail.comwrote:
I was wondering what experiences (or how to get started) with configuring
features and roles (some of which may require reboot) on Windows 2008R2
(and other versions) that others might have had.
Manually, I have
This only works in Facter 1.7, what do you get when you run `facter
--version`?
Have you double checked
http://docs.puppetlabs.com/guides/custom_facts.html#enabling-powershell-scriptsto
ensure that the powershell scripts are enabled?
- Justin
On Tue, Apr 9, 2013 at 8:44 AM, Grant Trevor
On Tue, Apr 16, 2013 at 1:29 PM, Gary Park gep...@gmail.com wrote:
Hello,
Thanks for getting back to me.
I think I forgot to mention, I am using this:
http://forge.puppetlabs.com/joshcooper/powershell
Does this change how the onlyif parameter interprets what it is provided?
yes it
On Thu, Apr 18, 2013 at 1:09 PM, Erik Dalén erik.gustav.da...@gmail.comwrote:
Would the reboot_pending fact return true on Unix after a newer kernel
version has been installed but the system isn't rebooted yet?
If I understand the armature correctly the fact example is simply something
that
On Thu, Jun 20, 2013 at 2:39 PM, Dan White y...@comcast.net wrote:
But I'd rather be certain of the answer than guess or try it and go down
in flames:
The question: Can one integrate VMWare with Open Source Puppet ? Or is
this a Puppet-Enterprise-only thing ?
You can integrate anything
It's been a while since I jumped into this code and it's late, forgive me
if I say something naive inline.
On Wed, Jun 26, 2013 at 8:14 PM, Nan Liu nan@gmail.com wrote:
On Wed, Jun 26, 2013 at 7:23 PM, Amos Shapira amos.shap...@gmail.comwrote:
I'm writing my first puppet function rspec
On Wed, Jul 10, 2013 at 2:15 AM, Wen Andes ylyy1...@gmail.com wrote:
Hi, all,
I use puppet enterprise VM (pe 3.0) with dashboard (version 2.0 built-in)
to set up my very simple env. but in the master node, when I want to check
the 'rake' API, I failed with '-bash: rake: command not found'.
On Wed, Jul 17, 2013 at 4:23 PM, shivaraj mathrubai
me.shiva...@gmail.comwrote:
I'm using CentOS
On Thursday, 18 July 2013 00:21:52 UTC+1, shivaraj mathrubai wrote:
Hi Guys,
I'm unable to load the module cloud provisioner, when I try to run
node_aws it gives me the below errors:
On Thu, Jul 18, 2013 at 12:44 AM, Ripunjay Godhani ripunj...@gmail.comwrote:
getting error change from stopped to running failed: Could not start
Service[pe-activemq]: Execution of '/sbin/service pe-activemq start'
returned 1: at
SUSE Linux Enterprise 11 is a supported PE platform. You can download a
demo for it here: http://info.puppetlabs.com/download (good up to 10 nodes)
Puppet Enterprise contains an installer that will guide you through setting
up Puppet, Facter, MCollective and the Enterprise Console. For more info
On Thu, Jan 2, 2014 at 1:23 PM, Colin Cullinan cculli...@gmail.com wrote:
Hello,
I am attempting to manage EC2 instances using Puppet's node_aws but
everytime I run
*~$ sudo puppet node_aws list*
I get the following response
*Error: undefined method `reject' for
On Wed, Jan 8, 2014 at 12:21 PM, expouser churi...@gmail.com wrote:
Hi All,
Does anyone know how to install PE (3.1 latest) on OpenSuse (13.1 x64)
Linux.
Unfortunately, you can't as it's not a supported platform (SLES is though!)
I'm getting:
!! ERROR: Unknown platform
On Mon, Oct 6, 2014 at 6:44 PM, Ken Barber k...@puppetlabs.com wrote:
I was just testing the host config file from puppetdb coupled with the
documentation on the beaker documentation.
Those docs honestly look old, they are still mentioning blimpy which I
effectively deprecated/superseded
On Tue, Oct 20, 2015 at 12:49 AM, Alex Harvey wrote:
> Hi all,
>
> I am investigating whether or not I can use Beaker to do acceptance
> testing on roles and profiles.
>
> I've had a look at Liam Bennett's excellent blog posts -
>
>
On Tue, Feb 16, 2016 at 11:00 AM, Brett Swift wrote:
> It's the spec_prep that is failing, so even bundle exec spec won't work.
>
Just an FYI: the spec* rake tasks are controlling and setting up lower
level unit tests using "rspec-puppet"[1] while the task to run
On Thu, Nov 3, 2016 at 2:52 AM, Jonathan Gazeley <
jonathan.gaze...@bristol.ac.uk> wrote:
> Hi folks,
>
> I've been running open-source Puppet 3.x for years but this week I'm
> dabbling with a new installation of PE 2016.4. I installed from the
> pointy-clicky installer and so far the PE server
We’re happy to announce the 2.7.2 release of Puppet Server. This is a
backward compatible bug fix release.
The release contains packaging related fixes:
* Remove unneeded RPM dependencies, including system ruby <--- Regression
in 2.7.x that precipitated this release
* Improvements to service
On Thu, Aug 23, 2018 at 1:42 AM Peter Meier wrote:
> On 08/22/2018 08:42 PM, Molly Waggett wrote:
> > Puppet Platform 5.5.6 is a bug-fix, feature, and deprecations release
> > that includes updates for Puppet 5.5.6, Facter 3.11.4, and Puppet agent
> > 5.5.6. For details, see the Puppet
> >
Hello!
We recently released a new version of the Puppet Platform that contained
many CA related deprecations and we wanted to reach out and clarify a few
things.
Currently in Puppet 5 there are two(!) mostly identical CA implementations,
which can cause race conditions in signing and revoking,
Thanks for feedback, Gabriel!
On Fri, Aug 24, 2018 at 5:49 AM Gabriel Filion wrote:
> Hi there,
>
> On 2018-08-23 2:35 p.m., Maggie Dreyer wrote:
> > In the 5.5.5 release of the Puppet Platform, we released a new
> experimental
> > command line tool for interacting with the Puppet CA.
> >
> >
On Thu, Sep 27, 2018 at 9:12 AM wrote:
> Hi again,
>
> I also tried to set allow-unauthenticated: true for rule "puppetlabs cert
> status" and that worked.
> Now I was able to sign the csr.
>
Be aware, this is a very dangerous way to solve the problem. This will
allow anyone with http access to
What happens on the agent that is running on the master?
When running any agent here's a flag, `--http_debug` I think, that will
show you exactly what Puppet's requesting.
Seeing the output from curling the CA endpoints from the agent in question
might be helpful (both from curl's side and the
On Tue, Oct 30, 2018 at 2:34 PM Matt Zagrabelny wrote:
> Greetings,
>
> I'm running puppet 5.5.6 (Debian testing.)
>
> I'm seeing some curious and inconsistent results from where I put config
> settings in /etc/puppet/puppet.conf. When I use the [master] heading, the
> "external_nodes" setting
We're happy to announce the R10K 3.1.0 has been released to Rubygems.org.
R10K provides the ability to reference environments acted upon in a
deploy's postrun script. This should help users integrate the creation of
Puppet's type generation into your code deployment. See this FAQ topic[1]
for
Hi Jesus,
On Thu, Nov 22, 2018 at 6:44 AM Jesús Oliván
wrote:
> Hi!
>
> i'm experimenting a weird issue at random times when some clients are
> trying to sign his certificate in their puppet masters. Here's the log
> lines where error is visible:
>
> Info: Creating a new SSL key for
On Wed, Jan 9, 2019 at 9:06 AM Peter Berghold
wrote:
> Hi folks,
>
> I know... I know... get off of Puppet 3. I'll be getting there soon.
>
> Right now I have Puppet 3 in our production environment where I work.
> Long political story as to why we are still on 3 that I won't get into. I
>
which it's
> talking about.
>
> On Monday, March 4, 2019 at 4:56:49 PM UTC-5, Justin Stoller wrote:
>>
>> The new ca tool (which is one of the things node clean is calling under
>> the hood) uses the CA's http api in most cases and requires special
>> permissions. By default, the
The new ca tool (which is one of the things node clean is calling under the
hood) uses the CA's http api in most cases and requires special
permissions. By default, the api now only allows access to most certificate
endpoints by clients that contain a special cert extension. You can create
a cert
On Mon, Feb 11, 2019 at 5:42 AM Mike Sharpton wrote:
> Hey all,
>
> We have recently upgraded our environment from Puppetserver 4.2.2 to
> Puppetserver 6.0.2. We are running a mix of Puppet 4 and Puppet 6 agents
> until we can get them all upgraded to 6. We have around 6000 nodes, and we
> had
That's not an error from Puppet Server's HTTP auth.conf, it's an error from
Puppet's old auth.conf or its fileserver.conf. Note the "Not authorized to
call *find* on ..." Puppet Server's auth handles HTTP verbs like GET,
Puppet's indirector auth translates those to verbs like FIND or SEARCH.
On Thu, May 9, 2019 at 12:00 PM Zama wrote:
> HI All ,
>
> I had a working puppetserver. But after yesterday's OS reboot , the
> service is not coming up . Below errors can be seen in log
>
>
> Version are as follows:
>
> rpm -q puppetserver
>
> puppetserver-2.3.1-1.el6.noarch
>
> rpm -q
On Wed, Sep 4, 2019 at 12:16 PM 'Prentice Bisbal' via Puppet Users <
puppet-users@googlegroups.com> wrote:
> I'm doing a fresh install of Puppet6 on CentOS 7.6:
>
> # rpm -qa | grep puppet
> puppetserver-6.4.0-1.el7.noarch
> puppetdb-termini-6.3.4-1.el7.noarch
> puppet-bolt-1.26.0-1.el7.x86_64
>
Depending on your security inclinations you might try turning crl checking
off on your 5.5 agent (iirc, that was the biggest issue - if not the only
issue). You might have to also copy the signed cert over to the agent too).
Otherwise, you may be able to turn off your master, delete your ssldir
Hello!
I noticed that the way we were computing the "Puppet" stack (ie the files
and line numbers from function calls within Puppet code like `fqdn_rand()`)
had become slow and was likely to become slower. In my attempt to improve
the situation I focused on ensuring backwards compatibility with
inline
On Fri, Oct 11, 2019 at 8:53 AM Sander de Boer wrote:
> I have a problem with a with Foreman and Puppet server (6.2.1) on a KVM VM
> with Ubuntu 18.04.
> After a crash of the VM Foreman starts without a problem (no errors in
> it's logs) but puppetserver refuses with this JRuby java
(but if more
folks are concerned about this having been a breaking change I can put the
solitary `--trace` output back to having them interleaved).
On Thu, Nov 21, 2019 at 10:41 AM Justin Stoller wrote:
> Hello!
>
> I noticed that the way we were computing the "Puppet" stack (ie t
re for demo purposes, but it's not
actively maintained.
Again, there's probably a better way w/in PE to distribute the certs once
you've regen them for the CA/master to the console/pdb, but I don't know
it. You might want to try #puppet-enterprise in the community slack channel.
hth,
Justin
&g
The Puppet Server and Puppet Agent brought in a dependency on the
concurrent gem in versions 6.7.0 & 6.9.0 respectively (the server and agent
are unfortunately versioned slightly differently).
On the master, the Agent and the Server also share Ruby code. So if you
have a Server >= 6.7 with an
On Sun, Mar 1, 2020 at 4:38 PM Simon Tideswell wrote:
> Hello
>
> In case someone else gets tripped up by this, when upgrading from 6.8.0-1
> to 6.9.0-1 on Ubuntu 18 (and possibly other platforms) the sense of
> *strict_hostname_checking* changes. Previously it appears it was set to
> *false* by
Yvan your issue sounds like https://tickets.puppetlabs.com/browse/PUP-3647,
do you know if that is fixed now, or has regressed since then?
Your issue does sound like a CodeCache or Metaspace issue.
One tunable you didn't mention was "max-active-instances" I've found a
bunch of folks that turned
On Mon, Feb 10, 2020 at 1:44 AM Martijn Grendelman
wrote:
> Hi Kevin and others who have responded,
>
> Thanks all for your tips. Unfortunately, no breakthroughs yet.
>
> The current state is this:
>
>- Both Puppetservers typically run at the latest version, currently
>both 6.8.0.
>-
I believe a config value was added at:
metrics.metrics-webservice.mbeans.enabled
to match the jolokia one that controls v2.
However the default for the mbeans / v1 endpoint is now `false`.
Note that this is now the case for Puppet Server as well and can be
re-enabled with the same config value in
On Tue, Apr 28, 2020 at 4:46 PM comport3 wrote:
> Thanks for the update Gabriel, appreciated. Do you know when v6.15.0 is
> expected to be release, even approximately?
>
Hopefully tomorrow ( :
We're double checking things now for the release and unless we find a
blocker that's when it will
ile.rb. I
>> quadruple checked the puppet module directory on the prod server and the
>> code does have the quick_check parm. For some reason it is just not
>> refreshing the server cache. Both domains have a value of 0 for
>> environment_timeout for each environment.
>>
>&
> why wouldn't puppet just do this automatically when a module changes?
Some background. Puppet's type and provider system modifies the running
Puppet instance when they're _loaded_. This causes issues when you try to
load multiple conflicting versions of a type in different environments. To
work
y manage a symlink. If you
are using environment caching as well it should be even safer because types
will only be read from disk on the first compilation that uses them and
then cached in memory after that.
hth,
justin
1.
https://puppet.com/docs/puppet/6.17/environment_isolation.html#env_generat
This is a draft of a new 6.x tuning guide we're working on, it may be of
some help to you
https://tickets.puppetlabs.com/browse/SERVER-2771
The big things are a need for increased codecache and a very negative
effect of low max-requests-per-instance values.
hth,
Justin
On Thu, Sep 17, 2020 at
I'd expect errors from the service framework/java level to go into the
journal and/or /var/log/{messages,syslog}.
If the service framework says it's up and running and there's nothing in
the above logs there should be _something_ in
/var/log/puppetlabs/puppetserver.log
you might also want to
Let us know if they aren't easily findable from google or through the docs
page. fwiw, they're linked by service/product like:
db: https://puppet.com/docs/puppetdb/latest/api/index.html
server: https://puppet.com/docs/puppetserver/latest/http_api_index.html
and pe:
On Wed, Aug 5, 2020 at 9:10 AM alexey@gmail.com <
alexey.potyo...@gmail.com> wrote:
> Is it possible to configure the automatic signing of certificates in such
> a way that verification takes place according to a parameter in the config
> on the client. For example, the client config will
In Puppet 6 and the latest Puppet 5 releases we shipped a subcommand with
Puppet Server `puppetserver ca` and an agent local subcommand `puppet ssl`
that can remotely manage the CA or manage an agent's local certificate info
respectively. These tools exist in Puppet 5 and and replaces the several
We shipped agent support for Focal but did not have plans to support it as
a master platform. I believe product was trying to gauge community interest
before committing to it and taking requests in
https://tickets.puppetlabs.com/browse/SERVER-2820.
>From an internal note it looks like they have
t; On Friday, June 19, 2020 at 1:45:24 AM UTC+5:30, Justin Stoller wrote:
>>
>> providing the erb template would be valuable, if possible.
>>
>> The error looks like someone defined new constants w/in a custom function
>> file.
>> Is your erb file calling a custom
providing the erb template would be valuable, if possible.
The error looks like someone defined new constants w/in a custom function
file.
Is your erb file calling a custom function?
On Thu, Jun 18, 2020 at 8:08 AM Aditya Gupta wrote:
> Hello All,
>
> Recently i have updated from puppet-5 to
You might want to have a target for memory per worker that you tune for.
In Puppet 5, if you are using the default JRuby 1.7 implementation, you
might start at 1/2G per JRuby on a small test box and go up in 1/4G
increments seeing how your average catalog performance changes. I want to
say most
On Fri, Jul 17, 2020 at 7:41 AM Peter Krawetzky
wrote:
> Ok I figured out the curl command but I get this error:
>
> [root@mypuppetserver private_keys]# curl -v --header "Content-Type:
> application/json" --cert
> /etc/puppetlabs/puppet/ssl/certs/mypuppetserver.mydomain.com.pem
> --key
>
It maybe because of a long environment timeout:
https://puppet.com/docs/puppet/5.5/environments_creating.html#task-3930
In PE this is set to unlimited by default when using code management. The
code manager will then manually evict the cache after a code deployment to
ensure that new code is
We needed to upgrade Jetty but they changed their defaults and started
warning about weak ciphers. To avoid breaking folks we added back the
ciphers that had been allowed at the start of the 6.x series but that
causes a lot of warnings. If you don't have connections that rely on the
older ciphers
Just to pile on. If you want the content updated whenever the package is
updated and you are managing the package with puppet you can "subscribe" to
the package resource to have the file resource only applied when the
package changes.
On Fri, Jan 29, 2021 at 11:47 AM Ben Ford wrote:
> I do have
On Tue, Jun 15, 2021 at 9:40 AM Jarod Schoen
wrote:
> Hi all,
> I've been practicing getting Puppet Server (Master) up and running on a
> whole variety of distros. CentOS, Ubuntu, Debian... and the more
> instructions I read, the more its impossible to understand how Puppet works
> and should be
Hello!
I don't have a favorite tutorial for making the certificate, but for steps
two and three that you mentioned you should be able to run `puppetserver ca
import` to help import your certs and get them to the correct location on
disk.
HTH,
Justin
On Fri, Jul 2, 2021 at 12:11 PM Jarod Schoen
te to the approach there if you want, otherwise I'll
reply to this thread when it's sorted out.
> -Original message-----
> *From:* Justin Stoller
> *Sent:* Friday 5th March 2021 20:35
> *To:* puppet-users@googlegroups.com
> *Subject:* Re: [Puppet Users] Puppetserver ca mi
On Tue, Mar 2, 2021 at 9:05 AM Mark Dixon wrote:
> Hi Nick,
>
> That's great news, for a moment there I was worried :)
>
> It's a new deployment so I'm fairly relaxed about puppet 6 vs. 7, but
> specifically I'm feeling the lack of any version at all for rhel8.
>
That's a weird thing with the
Hi!
If you've mounted external volumes for your cadir like:
--mount source=ca-volume,destination=/etc/puppetlabs/puppet/ssl/ca
You should instead mount the destination as /etc/puppetlabs/puppetserver/ca
If you have a Dockerfile that pre-populates your cadir you'll need to
update your script
:
That "Generation succeeded. Find your files in
/etc/puppetlabs/puppetserver/ca" line should be coming from the
"puppetserver ca" cli generating the CA files in the new location
>
> -Original message-
> *From:* Justin Stoller
> *Sent:* Thursday 4t
90 matches
Mail list logo