Oh hey, this package debacle is totally true. Confirmed it myself for EL6:
https://gist.github.com/kbarber/b0551d9aaffe2302a8dc
I've raised a bug on this with our release team, thanks.
As far as why there is a 40? I can't come up with another logical
explanation except for, at one point 3.2.3
puppetdb 3.2.3 is not marked as an available update.
# yum install puppetdb-3.2.3
...
No package puppetdb-3.2.3 available.
# yum repolist -v puppetlabs-pc1
...
Repo-updated : Thu Feb 4 22:15:20 2016
Repo-pkgs: 49
And indeed :
# find ...mirrors/puppetlabs/6/PC1/x86_64 -name '*.rpm' | wc -l
Thanks so much everyone. Makes much more sense now!!! :)
On Monday, 22 February 2016 18:12:24 UTC-5, Scott Walker wrote:
>
> I'm slowly getting up to speed on puppet (coming over from chef but
> honestly haven't used either in probably 3 years so I'm relearning the
> learning curve.).
>
> We
I'm running puppetdb on ScientificLinux 6.7 (a RHEL clone).
I upgraded from puppetdb-3.1.0 to puppetdb-3.2.2, but know I'm getting in the
log :
2016-02-24 11:22:58,585 ERROR [p.t.internal] Error during service start!!!
java.lang.IllegalStateException: Your PuppetDB database contains a schema
Migration number 40 is for version 3.2.3, not version 3.2.2. Looks
like someone has previously installed version 3.2.3 and pointed it at
your database.
See:
https://github.com/puppetlabs/puppetdb/blob/3.2.3/src/puppetlabs/puppetdb/scf/migrate.clj#L1553
versus
PDOC-71 Created: https://tickets.puppetlabs.com/browse/PDOC-71
Thanks,
Trevor
On Tue, Feb 23, 2016 at 8:54 PM, Henrik Lindberg <
henrik.lindb...@puppetlabs.com> wrote:
> On 23/02/16 23:54, Trevor Vaughan wrote:
>
>> Thanks for the response Henrik,
>>
>> I was worried that it would be something
it depends on how big your infrastructure is. these are recommended for
larger infra, there is also the new way of using partitioned mcollective
and using hubs, and spokes, it all depends, you can find about hubs, and
spokes in here
https://docs.puppetlabs.com/pe/latest/install_add_activemq.html
I am using puppet 4.3 and it looks like the new function lookup provider is
not working, unless i am missing something.
I am working from this:
https://docs.puppetlabs.com/puppet/latest/reference/lookup_quick_module.html
I am just testing with this simple example.
% puppet status
{
I'm not sure if anyone here will be able to help, but I feel I need to give
it
a shot, so...
My team is in the process of getting ready to use PostgreSQL, but before
that I need to ensure that our Puppet infrastructure can manage the systems
properly, which means making sure replication stays
On 24/02/16 21:57, RG wrote:
I am using puppet 4.3 and it looks like the new function lookup provider
is not working, unless i am missing something.
I am working from this:
https://docs.puppetlabs.com/puppet/latest/reference/lookup_quick_module.html
I am just testing with this simple example.
We've stopped using the rolling release names (stable, testing) for our
Debian packages and instead use the direct codenames. This maps better to
our processes and is more maintainable over time. What this means is that
the stable/testing portions of the apt repos will be removed. All packages
11 matches
Mail list logo
