Thanks Justin/Josh. Josh, I did come across this during my recent searches
on trying to resolve my original issue.
On Tuesday, September 15, 2020 at 1:48:47 PM UTC-4 Josh Cooper wrote:
>
>
> On Tue, Sep 15, 2020 at 5:25 AM pkraw...@gmail.com
> wrote:
>
>> So I've done some research on the
On Tue, Sep 15, 2020 at 5:25 AM pkraw...@gmail.com
wrote:
> So I've done some research on the puppet generate types command. I'm
> seeing many different results from not having issues to causing issues with
> puppet apply and puppet agent executions.
We fixed an issue in 6.18.0
On Tue, Sep 15, 2020 at 5:25 AM pkraw...@gmail.com
wrote:
> So I've done some research on the puppet generate types command. I'm
> seeing many different results from not having issues to causing issues with
> puppet apply and puppet agent executions.
If I was to run this command and things go
So I've done some research on the puppet generate types command. I'm
seeing many different results from not having issues to causing issues with
puppet apply and puppet agent executions. If I was to run this command and
things go wrong, how do you reverse it? Remove the .resource_types
Justin, yes it's happening in all environments which leads me to believe
it's related to an old copy
in /opt/puppetlabs/puppet/cache/lib/puppet/type. Still trying to wrap my
head around why one domain installation is fine and the other domain
installation is not.
Here is the contents of that
On Fri, Aug 28, 2020 at 10:14 AM pkraw...@gmail.com
wrote:
> Great info but I think I might have found the issue.
>
> So we don't use r10k to deploy code we use a different tool. But what I
> found is on the puppet server (master) the httpfile.rb in
>
Great info but I think I might have found the issue.
So we don't use r10k to deploy code we use a different tool. But what I
found is on the puppet server (master) the httpfile.rb in
/opt/puppetlabs/puppet/cache/lib/puppet/type is the older version. I
didn't find any ./resource_types
> 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
So a followup to the original question.
As a test we created a simple module on the node which is failing when
puppet agent executes. Running puppet apply, the parameter quick_check is
found and the module completes successfully. So why would puppet apply
work and not puppet agent?
Code:
Dirk, why wouldn't puppet just do this automatically when a module
changes? Is there a bug somewhere?
On Tuesday, August 25, 2020 at 2:43:03 AM UTC-4 Dirk Heinrichs wrote:
> Am Montag, den 24.08.2020, 11:06 -0700 schrieb pkraw...@gmail.com:
>
> Justin, I implemented the suggestion you made
Am Montag, den 24.08.2020, 11:06 -0700 schrieb pkraw...@gmail.com:
> Justin, I implemented the suggestion you made however after running
> the curl command against the 2 environments having the issue and
> receiving the 204 response, the puppet module is still getting the
> 500 error. Do you or
Justin, I implemented the suggestion you made however after running the
curl command against the 2 environments having the issue and receiving the
204 response, the puppet module is still getting the 500 error. Do you or
anyone else have any other suggestions? Is it possible it's related to
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
>
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
/etc/puppetlabs/puppet/ssl/private_keys/mypuppetserver.mydomain.com.pem
Does this work for Open Source or PE? My installation is using Open Source.
Also can you provide an example of the actual curl command? I can't seem
to get the exact syntax down for it to work.
Thanks for the advice.
On Thursday, July 16, 2020 at 7:55:51 PM UTC-4, Justin Stoller wrote:
>
>
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
I've reviewed sever 500 error posts in here but the answers seem to differ
based on the situation.
One of our developers modified code to include a parameter available in
httpfile 0.1.9 called quick_check.
We have two installation of puppetserver one in lab domain and one in
production
17 matches
Mail list logo