Jira (PDB-3743) ensure PDB 4.4.x can be run with puppetserver 5.x

[Wyatt Alt (JIRA)]

Wyatt Alt created an issue

PuppetDB / PDB-3743 ensure PDB 4.4.x can be run with puppetserver 5.x Issue Type: Bug Assignee: Unassigned Created: 2017/11/02 9:30 AM Priority: Normal Reporter: Wyatt Alt User devicenull on freenode reports that PDB 4.4 does not run with puppetserver 5, even with a v5 terminus, due to a schema violation: 09:21 <devicenull> clojure.lang.ExceptionInfo: Value does not match schema: {:job_id disallowed-key} We should release a fix to 4.4.x that relaxes the schema so that we have an upgrade path, since this means that currently users must upgrade puppetserver and PDB at the same time. Add Comment

This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)

[Brian Rak (JIRA)]

Brian Rak commented on PDB-3743

Re: ensure PDB 4.4.x can be run with puppetserver 5.x FWIW, the masters were running v5.1.0 here. I did not check if upgrading them all to 5.3.2 would have fixed it.

Add Comment

[Roman Pertl (JIRA)]

Roman Pertl commented on PDB-3743

Re: ensure PDB 4.4.x can be run with puppetserver 5.x

I'm having the same Issues: my puppetdb server has the following packages: ii puppet-agent 1.10.9-1jessie ii puppetdb 4.4.0-1puppetlabs1 ii puppetdb-termini 5.1.3-1jessie ii puppetserver 2.8.0-1puppetlabs1 mypuppetmaster has the following packages: ii puppet-agent 5.3.3-1stretch ii puppetdb-termini 5.1.3-1stretch ii puppetserver 5.1.4-1stretch the full error is: 2017-12-14 12:29:29,923 ERROR [p.p.threadpool] Error processing command on thread cmd-proc-thread-2706

clojure.lang.ExceptionInfo: Value does not match schema: {:job_id disallowed-key}

at schema.core$validator$fn__2894.invoke(core.clj:155) at schema.core$validate.invokeStatic(core.clj:164) at schema.core$validate.invoke(core.clj:159) at puppetlabs.puppetdb.command$store_report$fn__32755.invoke(command.clj:355) at puppetlabs.puppetdb.command$store_report.invokeStatic(command.clj:354) at puppetlabs.puppetdb.command$store_report.invoke(command.clj:353) at puppetlabs.puppetdb.command$process_command_BANG_.invokeStatic(command.clj:389) at puppetlabs.puppetdb.command$process_command_BANG_.invoke(command.clj:380) at puppetlabs.puppetdb.command$process_command_and_respond_BANG_$fn__32863.invoke(command.clj:442) at puppetlabs.puppetdb.command$call_with_quick_retry$fn__32856.invoke(command.clj:424) at puppetlabs.puppetdb.command$call_with_quick_retry.invokeStatic(command.clj:423) at puppetlabs.puppetdb.command$call_with_quick_retry.invoke(command.clj:421) at puppetlabs.puppetdb.command$process_command_and_respond_BANG_.invokeStatic(command.clj:440) at puppetlabs.puppetdb.command$process_command_and_respond_BANG_.invoke(command.clj:438) at puppetlabs.puppetdb.command$process_cmdref$fn__32873.invoke(command.clj:505) at puppetlabs.puppetdb.utils.metrics$multitime_BANG__STAR_$fn__30651$fn__30652$fn__30653.invoke(metrics.clj:14) at puppetlabs.puppetdb.utils.metrics.proxy$java.lang.Object$Callable$7da976d4.call(Unknown Source) at com.codahale.metrics.Timer.time(Timer.java:101) at puppetlabs.puppetdb.utils.metrics$multitime_BANG__STAR_$fn__30651$fn__30652.invoke(metrics.clj:14) at puppetlabs.puppetdb.utils.metrics$multitime_BANG__STAR_$fn__30651$fn__30652$fn__30653.invoke(metrics.clj:14) at puppetlabs.puppetdb.utils.metrics.proxy$java.lang.Object$Callable$7da976d4.call(Unknown Source) at com.codahale.metrics.Timer.time(Timer.java:101) at puppetlabs.puppetdb.utils.metrics$multitime_BANG__STAR_$fn__30651$fn__30652.invoke(metrics.clj:14) at puppetlabs.puppetdb.utils.metrics$multitime_BANG__STAR_.invokeStatic(metrics.clj:17) at puppetlabs.puppetdb.utils.metrics$multitime_BANG__STAR_.invoke(metrics.clj:6) at puppetlabs.puppetdb.command$process_cmdref.invokeStatic(command.clj:501) at puppetlabs.puppetdb.command$process_cmdref.invoke(command.clj:480) at puppetlabs.puppetdb.command$message_handler$fn__32881.invoke(command.clj:551) at puppetlabs.puppetdb.threadpool$dochan$fn__32634$fn__32635.invoke(threadpool.clj:117) at puppetlabs.puppetdb.threadpool$call_on_threadpool$fn__32629.invoke(threadpool.clj:95) at clojure.lang.AFn.run(AFn.java:22) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622) at java.lang.Thread.run(Thread.java:748) catalog, facts and exported ressources are working without problems thou, what does not work is the storage of the reports

Add Comment

[Shi Yan (JIRA)]

Shi Yan commented on PDB-3743

Re: ensure PDB 4.4.x can be run with puppetserver 5.x

I have the same issue as well.   puppetserver is 5.3.1 puppetdb-termini is 5.2.2 puppetdb is 4.4.0

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[john (JIRA)]

john commented on PDB-3743

Re: ensure PDB 4.4.x can be run with puppetserver 5.x

Late to the party but same issue ii puppet 5.5.10-4 all configuration management system ii puppet-master 5.5.10-4 all configuration management system, master service ii puppet-master-passenger 5.5.10-4 all configuration management system, scalable master service ii puppet-terminus-puppetdb 6.2.0-3 all Puppet data warehouse ii puppetdb 4.4.0-1 all Puppet Labs puppetdb   Reading the related issues seems the advice from the developers are just upgrade everything all at once

Add Comment