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 wa
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
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
https://github.com/puppetlabs/puppetd
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
mi
