Jira (PDB-4680) puppetdb restart failed during HA upgrade in 2018.1.x

10 views
Skip to first unread message

Shaigy Nixon (Jira)

unread,
Mar 31, 2020, 1:11:04 PM3/31/20
to puppe...@googlegroups.com
Shaigy Nixon created an issue
 
PuppetDB / Bug PDB-4680
puppetdb restart failed during HA upgrade in 2018.1.x
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: enterprise_pe-acceptance-tests_integration-system_pe_ha-upgrade_nightly_2018_1_x___279__2020-03-31__sut-files.tgz
Created: 2020/03/31 10:10 AM
Priority: Normal Normal
Reporter: Shaigy Nixon

During HA upgrade in 2018.1.x from 2017.2.5 on redhat7 puppetdb restart failed

      2020-03-31T01:14:26.529+00:00 - [Error]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Service[pe-puppetdb]: Failed to call refresh: Systemd restart for pe-puppetdb failed!
      journalctl log for pe-puppetdb:
      -- Logs begin at Tue 2020-03-31 00:20:42 UTC, end at Tue 2020-03-31 01:14:26 UTC. --
      Mar 31 01:09:48 gothic-materiel systemd[1]: Stopping pe-puppetdb Service...
      Mar 31 01:09:49 gothic-materiel systemd[1]: Stopped pe-puppetdb Service.
      Mar 31 01:13:48 gothic-materiel systemd[1]: Starting pe-puppetdb Service...
      Mar 31 01:14:15 gothic-materiel puppetdb[5864]: The [database] classname setting has been retired and will be ignored.
      Mar 31 01:14:15 gothic-materiel puppetdb[5864]: The [database] subprotocol setting has been retired and will be ignored.
      Mar 31 01:14:19 gothic-materiel puppetdb[5864]: The [database] classname setting has been retired and will be ignored.
      Mar 31 01:14:19 gothic-materiel puppetdb[5864]: The [database] subprotocol setting has been retired and will be ignored.
      Mar 31 01:14:24 gothic-materiel systemd[1]: Started pe-puppetdb Service.
      Mar 31 01:14:25 gothic-materiel systemd[1]: Reloading pe-puppetdb Service.
      Mar 31 01:14:25 gothic-materiel systemd[1]: pe-puppetdb.service: main process exited, code=exited, status=1/FAILURE
      Mar 31 01:14:26 gothic-materiel puppetdb[6220]: Process 5876 exited before reload had completed
      Mar 31 01:14:26 gothic-materiel systemd[1]: pe-puppetdb.service: control process exited, code=exited status=1
      Mar 31 01:14:26 gothic-materiel systemd[1]: Reload failed for pe-puppetdb Service.
      Mar 31 01:14:26 gothic-materiel systemd[1]: Unit pe-puppetdb.service entered failed state.
      Mar 31 01:14:26 gothic-materiel systemd[1]: pe-puppetdb.service failed.
      

puppetdb.log has the following error:

2020-03-31T01:14:25.618Z ERROR [p.t.logging] Uncaught exception
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: No matching clause: :puppetlabs.pe-puppetdb-extensions.sync.core/remote-host-error
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at clojure.core$deref_future.invokeStatic(core.clj:2208)
	at clojure.core$future_call$reify__6962.deref(core.clj:6688)
	at clojure.core$deref.invokeStatic(core.clj:2228)
	at clojure.core$deref.invoke(core.clj:2214)
	at puppetlabs.pe_puppetdb_extensions.sync.services$reify__52735$service_fnk__13710__auto___positional$reify__52748.stop(services.clj:536)
	at puppetlabs.trapperkeeper.services$eval13512$fn__13539$G__13504__13542.invoke(services.clj:9)
	at puppetlabs.trapperkeeper.services$eval13512$fn__13539$G__13503__13546.invoke(services.clj:9)
	at puppetlabs.trapperkeeper.internal$eval26182$run_lifecycle_fn_BANG___26189$fn__26190.invoke(internal.clj:198)
	at puppetlabs.trapperkeeper.internal$eval26182$run_lifecycle_fn_BANG___26189.invoke(internal.clj:181)
	at puppetlabs.trapperkeeper.internal$eval26211$run_lifecycle_fns__26216$fn__26217.invoke(internal.clj:231)
	at puppetlabs.trapperkeeper.internal$eval26211$run_lifecycle_fns__26216.invoke(internal.clj:208)
	at puppetlabs.trapperkeeper.internal$eval26693$build_app_STAR___26702$fn$reify__26712.restart(internal.clj:594)
	at puppetlabs.trapperkeeper.internal$restart_tk_apps$restart_fn__26446.invoke(internal.clj:308)
	at puppetlabs.trapperkeeper.internal$eval26252$initialize_lifecycle_worker__26263$fn__26264$fn__26360$state_machine__18333__auto____26361$fn__26363.invoke(internal.clj:251)
	at puppetlabs.trapperkeeper.internal$eval26252$initialize_lifecycle_worker__26263$fn__26264$fn__26360$state_machine__18333__auto____26361.invoke(internal.clj:251)
	at clojure.core.async.impl.ioc_macros$run_state_machine.invokeStatic(ioc_macros.clj:1012)
	at clojure.core.async.impl.ioc_macros$run_state_machine.invoke(ioc_macros.clj:1011)
	at clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invokeStatic(ioc_macros.clj:1016)
	at clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invoke(ioc_macros.clj:1014)
	at clojure.core.async$ioc_alts_BANG_$fn__18501.invoke(async.clj:383)
	at clojure.core.async$do_alts$fn__18447$fn__18450.invoke(async.clj:252)
	at clojure.core.async.impl.channels.ManyToManyChannel$fn__17059$fn__17060.invoke(channels.clj:95)
	at clojure.lang.AFn.run(AFn.java:22)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: No matching clause: :puppetlabs.pe-puppetdb-extensions.sync.core/remote-host-error
	at puppetlabs.pe_puppetdb_extensions.sync.services$attempt_initial_sync.invokeStatic(services.clj:389)
	at puppetlabs.pe_puppetdb_extensions.sync.services$attempt_initial_sync.invoke(services.clj:362)
	at puppetlabs.pe_puppetdb_extensions.sync.services$reify__52735$service_fnk__13710__auto___positional$reify__52748$fn__52756$fn__52757.invoke(services.clj:496)
	at clojure.core$some.invokeStatic(core.clj:2592)
	at clojure.core$some.invoke(core.clj:2583)
	at puppetlabs.pe_puppetdb_extensions.sync.services$reify__52735$service_fnk__13710__auto___positional$reify__52748$fn__52756.invoke(services.clj:496)
	at clojure.core$binding_conveyor_fn$fn__4676.invoke(core.clj:1938)
	at clojure.lang.AFn.call(AFn.java:18)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	... 3 common frames omitted

joblink

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

Austin Blatt (Jira)

unread,
Mar 31, 2020, 1:37:04 PM3/31/20
to puppe...@googlegroups.com
Austin Blatt commented on Bug PDB-4680
 
Re: puppetdb restart failed during HA upgrade in 2018.1.x

The error was thrown from a case statement that appears to have had a misplaced parenthesis.

https://github.com/puppetlabs/pe-puppetdb-extensions/pull/531

Austin Blatt (Jira)

unread,
Apr 1, 2020, 12:30:03 PM4/1/20
to puppe...@googlegroups.com
Austin Blatt commented on Bug PDB-4680

Shaigy Nixon this was promoted into 2018.1 last night, so future runs of CI shouldn't hit this error. It's probably still present on master, but that'll be fixed when we merge up.

Austin Blatt (Jira)

unread,
Apr 13, 2020, 12:44:03 PM4/13/20
to puppe...@googlegroups.com

Austin Blatt (Jira)

unread,
Apr 13, 2020, 12:53:04 PM4/13/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Sprint: HA Team 2020-04-22 (SS 4/15)
Reply all
Reply to author
Forward
0 new messages