PuppetDB 1.6.2 final Now available

[Ryan Senior]

PuppetDB 1.6.2 final - February 6th, 2014.


PuppetDB 1.6.2 Downloads

------------------------


Available in native package format in the release repositories at:

http://yum.puppetlabs.com and http://apt.puppetlabs.com


For information on how to enable the Puppet Labs repos, see:

http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#open-source-repositories


Binary tarball: http://downloads.puppetlabs.com/puppetdb/


Source: http://github.com/puppetlabs/puppetdb


Please report feedback via the Puppet Labs tickets site, using an

affected PuppetDB version of 1.6.2:

https://tickets.puppetlabs.com/browse/PDB


Documentation: http://docs.puppetlabs.com/puppetdb/1.6


Puppet module:

http://forge.puppetlabs.com/puppetlabs/puppetdb


PuppetDB 1.6.2 Release Notes

----------------------------


PuppetDB 1.6.2 is a bugfix release.


Things to take note of before upgrading:


* There is a known issue in Puppet 3.4.0, 3.4.1 and 3.4.2 with
duplicate failed events being tracked here:
https://tickets.puppetlabs.com/browse/PUP-1524. This is being fixed in
an upcoming release of Puppet. Since 1.6.0 this error will become more
obvious as we are now raising full stack traces, so you may notice it
more readily after the upgrade.


* If upgrading from 1.5.2 or earlier, there are a number of database
migrations performed upon first startup. This will require extra free
disk space on your PostgreSQL server while we rebuild some tables, so
make sure you have enough free space _before_ you start the upgrade.
Since a full table migration takes a copy of the old table, a good
rule of thumb would be to check your current database usage (using du
-sh on the database directory for example) and ensure you have as much
free space on that partition. While all migrations are protected by an
atomic database transaction, it never hurts to backup your database
beforehand just in case.


* Also due to the migrations that will take place (when upgrading from
1.5.2 or before), it might take several minutes (depending on the size
of your database) before PuppetDB can respond to requests again. Give
the migration ample time to complete and you should be fine.


* Make sure all your PuppetDB instances are shutdown and only upgrade
one at a time.


* As usual, don't forget to upgrade your puppetdb-terminus package
also (on the host where your Puppet Master lives), and restart your
master service.


Notable improvements and fixes:


* Provided an early release RPM SPEC for RHEL 7, no automated builds yet.


* (PDB-377) - Fixed a Fedora RPM packaging issue preventing PuppetDB
from starting by disabling JAR repacking


* (PDB-341) - Fixed a naming issue when using subqueries for resource
metadata like file and line with v3 of the API


* (PDB-128) - Add support for Oracle Java 7 packages on Debian. This
means that users who have older Debian based distros but do not have
native JDK 7 packages can build their own Oracle Java 7 package (see
https://wiki.debian.org/JavaPackage) and we will pull it in as a
dependency.

* (PDB-106) - Added an explicit log message upon a failed agent run
(previously would fail with "undefined method `[]' for nil:NilClass")


* Change the order that filters are applied for events


When using the `distinct-resources` flag of an event query, the

previous behavior was that we would do the filtering of the events

*before* we would eliminate duplicate resources. This was not

the expected behavior in many cases in the UI; for example,

when filtering events based on event status, the desired behavior

was to find all of the most recent events for each resource *first*,

and then apply the filter to that set of resources. If we did the

status filtering first, then we might end up in a state where we

found the most recent 'failed' event and showed it in the UI even

if there were 'success' events on that resource afterwards.


This commit changes the order that the filtering happens in. We

now do the `distinct` portion of the query before we do the filtering.


However, in order to achieve reasonable performance, we need to

at least include timestamp filtering in the `distinct` query; otherwise

that portion of the query has to work against the entire table,

and becomes prohibitively expensive.


Since the existing timestamp filtering can be nested arbitrarily

inside of the query (inside of boolean logic, etc.), it was not

going to be possible to re-use that to handle the timestamp filtering

for the `distinct` part of the query; thus, we had to introduce

two new query parameters to go along with `distinct-resources`:

`distinct-start-time` and `distinct-end-time`. These are now

required when using `distinct-resources`.


* (PDB-407) - Add Fedora 20 acceptance tests


* (PDB-425) - Fix issues upgrading from 1.5.2 to 1.6.2 on Fedora.
1.5.2 used System V scripts while 1.6.x used SystemD which caused
failures.


PuppetDB 1.6.2 Contributors

---------------------------


Chris Price, Daniele Sluijters, Jason Antman, Ken Barber, Matthaus
Owens, Moses Mendoza, Melissa Stone, Ryan McKern and Ryan Senior


PuppetDB 1.6.2 Changlog

-----------------------


Chris Price (3):

a3ef183 (PE-2675) Change the order that filters are applied for events

435ca1a Add documentation for `distinct-resources` query parameter

12d2e2f Refactor `validate-distinct-options` into common events http ns


Daniele Sluijters (1):

88c6423 PDB-128: Support Oracle Java distribution.


Jason Antman (3):

6df3ae3 PDB-106 add unit test for processing of reports with
empty metrics hash (failed reports)

2bea939 PDB-106: return 0 run_duration for failed runs, rather
than hitting an exception

ab2f85f PDB-106 instead of setting run_duration to 0 on reports
with no metrics (failed run), raise an error


Ken Barber (14):

350dd7b Update supported packages for distros

be48a62 PDB-306 Switch to using new el5 imgages to fix DNS
resolution hassles

b28c2ec PDB-127 Remove references to reports being 'experimental'

e01140a PDB-106 Reword error message

cdf065b PDB-341 Fix some API version crossover issues

2b20a3e PDB-341 Remove extra get-response and fix ordering issues in tests

9abb8b4 PDB-341 Ensure body of response is drained after query

ae1e74c Document repl 'host' setting

846b273 Invalid namespaces for tests http/nodes|fact_names masking failures

3c05242 PDB-407 Fedora 20 Acceptance Testing

f747fb5 PDB-407 Fix bug in init script for fedora

11eb5f0 PDB-407 Change gemfile reference for beaker to point to upstream

a9189d1 PDB-407 Make sure we add suffix for fedora packages

4ce359c PDB-407 Fix dev repo retrieval for fedora


Matthaus Owens (2):

ae2689e (PDB-425) Move daemon-reload out of install-only

2a253a8 (PDB-425) Try SysV and SystemD on upgrades


Moses Mendoza (1):

1d93409 (packaging) correct path to libexec files for PE


Ryan McKern (2):

890df7d (maint) Update RPM spec for RHEL 7

8282fc6 (maint) Remove Sid from package build defaults


Ryan Senior (2):

d10b437 Fixes an issue when using spyscope as a lein user profile

c29a13b (PDB-377) Disabling JAR repacking when creating RPMS