Jira (PDB-4641) resource_events partitioning migration failure

20 views
Skip to first unread message

Reinhard Vicinus (JIRA)

unread,
Feb 3, 2020, 2:56:04 PM2/3/20
to puppe...@googlegroups.com
Reinhard Vicinus created an issue
 
PuppetDB / Bug PDB-4641
resource_events partitioning migration failure
Issue Type: Bug Bug
Affects Versions: PDB 6.8.1
Assignee: Unassigned
Created: 2020/02/03 11:55 AM
Priority: Normal Normal
Reporter: Reinhard Vicinus

Trying to upgrade from puppetdb 6.7.3 to puppetdb 6.8.1 and as far as I can tell I still get the same error as described in PDB-4626:

ERROR [p.p.s.migrate] Caught SQLException during migration
java.sql.BatchUpdateException: Batch entry 0 INSERT INTO resource_events_20200124Z ( event_hash, report_id, certname_id, status, timestamp, resource_type, resource_title, property, new_value, old_value, message, file, line, containment_path, containing_class, corrective_change, name ) VALUES (...) was aborted: ERROR: relation "resource_events_20200124z" does not exist

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

Zachary Kent (JIRA)

unread,
Feb 13, 2020, 1:40:05 PM2/13/20
to puppe...@googlegroups.com
Zachary Kent updated an issue
Change By: Zachary Kent
Fix Version/s: PDB 6.9.0

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 12:35:04 PM2/14/20
to puppe...@googlegroups.com

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 12:49:04 PM2/14/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Release Notes: Bug Fix

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 12:57:04 PM2/14/20
to puppe...@googlegroups.com
Austin Blatt updated an issue

Database migrations could fail if there were long periods of inactivity in the resource_events table and a client's server wasn't using UTC.

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 12:57:04 PM2/14/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Comment:
Database migrations could fail if there were long periods of inactivity in the resource_events table and a client's server wasn't using UTC.

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 12:57:04 PM2/14/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Release Notes Summary:
Database migrations could fail if there were long periods of inactivity in the resource_events table and a client's server wasn't using UTC.

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 12:58:04 PM2/14/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Release Notes Summary: Database migrations could fail if there were long periods of inactivity in the resource_events table and a client's server wasn't using UTC. [PDB-4641|https://tickets.puppetlabs.com/browse/PDB-4641 ]

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 12:58:04 PM2/14/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Release Notes Summary: Database migrations could fail if there were long periods of inactivity in the resource_events table and a client's server wasn't using UTC. [PDB-4641|https://tickets.puppetlabs.com/browse/PDB-4641 ?jql=project%20%3D%20PDB%20AND%20fixVersion%20%3D%20%22PDB%206.9.0%22]

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 12:59:03 PM2/14/20
to puppe...@googlegroups.com

Zachary Kent (JIRA)

unread,
Feb 14, 2020, 1:00:04 PM2/14/20
to puppe...@googlegroups.com
Zachary Kent updated an issue
Change By: Zachary Kent
Release Notes Summary: Database migrations could fail if there were long periods of inactivity in the resource_events table and a client's server wasn't using UTC. [ ( PDB-4641 |https://tickets.puppetlabs.com/browse/PDB-4641] )

Austin Blatt (JIRA)

unread,
Feb 14, 2020, 1:00:05 PM2/14/20
to puppe...@googlegroups.com
Austin Blatt commented on Bug PDB-4641
 
Re: resource_events partitioning migration failure

Copying the workaround from the duplicate ticket for visibility, Open Source users will have a puppetdb service instead.

# On RedHat 6: service pe-puppetdb stop
 
systemctl stop pe-puppetdb
 
 
 
/usr/bin/env TZ=utc /opt/puppetlabs/server/bin/puppetdb foreground
 
 
 
# Use Ctrl-C to stop PuppetDB after "PDBMigrationsPool - Shutdown completed" is logged
 
 
 
# On RedHat 6: service pe-puppetdb start
 
systemctl start pe-puppetdb

Heston Hoffman (JIRA)

unread,
Feb 18, 2020, 2:01:03 PM2/18/20
to puppe...@googlegroups.com
Heston Hoffman updated an issue
Change By: Heston Hoffman
Labels: resolved-issue-added
Reply all
Reply to author
Forward
0 new messages