Jira (PDB-4709) PuppetDB 6.10 schema migration failed

[Iain Buclaw (Jira)]

Iain Buclaw commented on PDB-4709

Re: PuppetDB 6.10 schema migration failed Full report: {:clojure.main/message "Execution error (IllegalStateException) at jdk.internal.reflect.NativeConstructorAccessorImpl/newInstance0 (NativeConstructorAccessorImpl.java:-2).\nYour PuppetDB database contains a schema migration numbered 1, but this version of PuppetDB does not recognize that version.\n", :clojure.main/triage {:clojure.error/class java.lang.IllegalStateException, :clojure.error/line -2, :clojure.error/cause "Your PuppetDB database contains a schema migration numbered 1, but this version of PuppetDB does not recognize that version.", :clojure.error/symbol jdk.internal.reflect.NativeConstructorAccessorImpl/newInstance0, :clojure.error/source "NativeConstructorAccessorImpl.java", :clojure.error/phase :execution}, :clojure.main/trace {:via [{:type java.lang.IllegalStateException, :message "Your PuppetDB database contains a schema migration numbered 1, but this version of PuppetDB does not recognize that version.", :at [jdk.internal.reflect.NativeConstructorAccessorImpl newInstance0 "NativeConstructorAccessorImpl.java" -2]}], :trace [[jdk.internal.reflect.NativeConstructorAccessorImpl newInstance0 "NativeConstructorAccessorImpl.java" -2] [jdk.internal.reflect.NativeConstructorAccessorImpl newInstance "NativeConstructorAccessorImpl.java" 62] [jdk.internal.reflect.DelegatingConstructorAccessorImpl newInstance "DelegatingConstructorAccessorImpl.java" 45] [java.lang.reflect.Constructor newInstance "Constructor.java" 490] [clojure.lang.Reflector invokeConstructor "Reflector.java" 305] [puppetlabs.puppetdb.scf.migrate$require_valid_schema invokeStatic "migrate.clj" 2085] [puppetlabs.puppetdb.scf.migrate$require_valid_schema invoke "migrate.clj" 2066] [puppetlabs.puppetdb.scf.migrate$update_schema$fn__35940 invoke "migrate.clj" 2225] [clojure.java.jdbc$db_transaction_STAR_ invokeStatic "jdbc.clj" 771] [clojure.java.jdbc$db_transaction_STAR_ invoke "jdbc.clj" 741] [puppetlabs.puppetdb.scf.migrate$update_schema invokeStatic "migrate.clj" 2220] [puppetlabs.puppetdb.scf.migrate$update_schema invoke "migrate.clj" 2186] [puppetlabs.puppetdb.scf.migrate$initialize_schema invokeStatic "migrate.clj" 2258] [puppetlabs.puppetdb.scf.migrate$initialize_schema invoke "migrate.clj" 2251] [puppetlabs.puppetdb.scf.migrate$initialize_schema invokeStatic "migrate.clj" 2255] [puppetlabs.puppetdb.scf.migrate$initialize_schema invoke "migrate.clj" 2251] [puppetlabs.puppetdb.cli.services$prep_db invokeStatic "services.clj" 423] [puppetlabs.puppetdb.cli.services$prep_db invoke "services.clj" 416] [puppetlabs.puppetdb.cli.services$init_with_db$fn__36211 invoke "services.clj" 475] [puppetlabs.puppetdb.cli.services$init_with_db invokeStatic "services.clj" 472] [puppetlabs.puppetdb.cli.services$init_with_db invoke "services.clj" 439] [puppetlabs.puppetdb.cli.services$start_puppetdb invokeStatic "services.clj" 599] [puppetlabs.puppetdb.cli.services$start_puppetdb invoke "services.clj" 576] [puppetlabs.puppetdb.cli.services$start_puppetdb_or_shutdown$fn__36262 invoke "services.clj" 695] [puppetlabs.puppetdb.cli.services$start_puppetdb_or_shutdown invokeStatic "services.clj" 693] [puppetlabs.puppetdb.cli.services$start_puppetdb_or_shutdown invoke "services.clj" 688] [puppetlabs.puppetdb.cli.services$reify__36374$service_fnk__19145__auto___positional$reify__36385 start "services.clj" 790] [puppetlabs.trapperkeeper.services$fn__18982$G__18963__18985 invoke "services.clj" 9] [puppetlabs.trapperkeeper.services$fn__18982$G__18962__18989 invoke "services.clj" 9] [puppetlabs.trapperkeeper.internal$fn__19477$run_lifecycle_fn_BANG___19484$fn__19485 invoke "internal.clj" 196] [puppetlabs.trapperkeeper.internal$fn__19477$run_lifecycle_fn_BANG___19484 invoke "internal.clj" 179] [puppetlabs.trapperkeeper.internal$fn__19506$run_lifecycle_fns__19511$fn__19512 invoke "internal.clj" 229] [puppetlabs.trapperkeeper.internal$fn__19506$run_lifecycle_fns__19511 invoke "internal.clj" 206] [puppetlabs.trapperkeeper.internal$fn__20122$build_app_STAR___20131$fn$reify__20143 start "internal.clj" 605] [puppetlabs.trapperkeeper.internal$fn__20170$boot_services_for_app_STAR__STAR___20177$fn__20178$fn__20180 invoke "internal.clj" 631] [puppetlabs.trapperkeeper.internal$fn__20170$boot_services_for_app_STAR__STAR___20177$fn__20178 invoke "internal.clj" 629] [puppetlabs.trapperkeeper.internal$fn__20170$boot_services_for_app_STAR__STAR___20177 invoke "internal.clj" 623] [clojure.core$partial$fn__5841 invoke "core.clj" 2630] [puppetlabs.trapperkeeper.internal$fn__19551$initialize_lifecycle_worker__19562$fn__19563$fn__19713$state_machine__12280__auto____19738$fn__19741 invoke "internal.clj" 249] [puppetlabs.trapperkeeper.internal$fn__19551$initialize_lifecycle_worker__19562$fn__19563$fn__19713$state_machine__12280__auto____19738 invoke "internal.clj" 249] [clojure.core.async.impl.ioc_macros$run_state_machine invokeStatic "ioc_macros.clj" 973] [clojure.core.async.impl.ioc_macros$run_state_machine invoke "ioc_macros.clj" 972] [clojure.core.async.impl.ioc_macros$run_state_machine_wrapped invokeStatic "ioc_macros.clj" 977] [clojure.core.async.impl.ioc_macros$run_state_machine_wrapped invoke "ioc_macros.clj" 975] [clojure.core.async$ioc_alts_BANG_$fn__12495 invoke "async.clj" 384] [clojure.core.async$do_alts$fn__12435$fn__12438 invoke "async.clj" 253] [clojure.core.async.impl.channels.ManyToManyChannel$fn__7099$fn__7100 invoke "channels.clj" 95] [clojure.lang.AFn run "AFn.java" 22] [java.util.concurrent.ThreadPoolExecutor runWorker "ThreadPoolExecutor.java" 1128] [java.util.concurrent.ThreadPoolExecutor$Worker run "ThreadPoolExecutor.java" 628] [java.lang.Thread run "Thread.java" 834]], :cause "Your PuppetDB database contains a schema migration numbered 1, but this version of PuppetDB does not recognize that version."}} Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Iain Buclaw (Jira)]

Iain Buclaw created an issue

PuppetDB / PDB-4709

PuppetDB 6.10 schema migration failed

Issue Type: Bug Affects Versions: PDB 6.10.0 Assignee: Unassigned Components: PuppetDB Created: 2020/05/04 1:35 AM Priority: High Reporter: Iain Buclaw Service fails to start after 6.9.1 -> 6.10.0 upgrade. WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by dynapath.defaults$fn__20897$fn__20898 (file:/opt/puppetlabs/server/apps/puppetdb/puppetdb.jar) to method java.net.URLClassLoader.addURL(java.net.URL) WARNING: Please consider reporting this to the maintainers of dynapath.defaults$fn__20897$fn__20898 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release The [database] classname config option has been retired and will be ignored. The [database] conn-keep-alive config option has been retired and will be ignored. The [database] log-slow-statements config option has been retired and will be ignored. The [database] subprotocol config option has been retired and will be ignored. The [read-database] classname config option has been retired and will be ignored. The [read-database] conn-keep-alive config option has been retired and will be ignored. The [read-database] log-slow-statements config option has been retired and will be ignored. The [read-database] subprotocol config option has been retired and will be ignored. The [database] classname config option has been retired and will be ignored. The [database] conn-keep-alive config option has been retired and will be ignored. The [database] log-slow-statements config option has been retired and will be ignored. The [database] subprotocol config option has been retired and will be ignored. The [read-database] classname config option has been retired and will be ignored. The [read-database] conn-keep-alive config option has been retired and will be ignored. The [read-database] log-slow-statements config option has been retired and will be ignored. The [read-database] subprotocol config option has been retired and will be ignored.

Execution error (IllegalStateException) at jdk.internal.reflect.NativeConstructorAccessorImpl/newInstance0 (NativeConstructorAccessorImpl.java:-2).

Your PuppetDB database contains a schema migration numbered 1, but this version of PuppetDB does not recognize that version. Full report at: /tmp/clojure-14479181673949144443.edn

Add Comment

[Matt Dainty (Jira)]

Matt Dainty commented on PDB-4709

Re: PuppetDB 6.10 schema migration failed I noticed a similar error when PuppetDB was upgraded from 5.2.13 to 5.2.14 over the weekend, I saw the same "Your PuppetDB database contains a schema migration numbered 1, but..." error message and PuppetDB wouldn't start. Downgrading back to 5.2.13 got things working again. I am going to investigate and see if I can see anything in the logs.

Add Comment

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4709

PuppetDB 6.10 schema migration failed

Change By: Austin Blatt Affects Version/s: PDB 5.2.14

Add Comment

[Austin Blatt (Jira)]

Austin Blatt assigned an issue to Rob Browning

PuppetDB / PDB-4709 PuppetDB 6.10 schema migration failed

Change By: Austin Blatt Assignee: Rob Browning

Add Comment

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4709 PuppetDB 6.10 schema migration failed

Change By: Austin Blatt Fix Version/s: PDB 6.10.1 Fix Version/s: PDB 5.2.15

Add Comment

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4709 PuppetDB 6.10 schema migration failed

Change By: Austin Blatt Release Notes: Bug Fix Release Notes Summary: Fixed an issue that would cause PuppetDB to fail to start on a database that had migrations from before PuppetDB 4.0.0.

Add Comment

[Austin Blatt (Jira)]

Austin Blatt commented on PDB-4709

Re: PuppetDB 6.10 schema migration failed The issue you're running into is a recent change made PuppetDB not recognize migrations from before PuppetDB 4.0.0, so if you've been running this PuppetDB server since before 4.0.0 it will think there's something wrong with the schema_migrations table and fail to start. We are working on a fix and aim to release versions 5.2.15 and 6.10.1 to fix this as soon as possible.

Add Comment