| FTR, a customer of mine is also affected by this: mika@puppet ~ % sudo zless /var/log/puppetlabs/puppetdb/puppetdb-2020-01-15.0.log.gz[...]2020-01-15T06:55:45.426+01:00 ERROR [p.p.s.migrate] Caught SQLException during migration
java.sql.BatchUpdateException: Batch entry 0 INSERT INTO resource_events_20200103Z ( 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 ( '\x501aa8aa6d7d2a66d7b93ca07a8fbe63e36c8d77', 429028, 14, 'skipped', '2020-01-03 06:58:06.805+01', 'Exec', '/usr/bin/gitlab-ctl reconfigure', NULL, 'null', 'null', NULL, '/etc/puppetlabs/code/environments/production/site/gitlab/manifests/server.pp', 13, '{Stage[main],Gitlab::Server,"Exec[/usr/bin/gitlab-ctl reconfigure]"}', 'Gitlab::Server', NULL, NULL ),( '\x403832e909d515158843a61847ea20ae92468e1a', 429028, 14, 'skipped', '2020-01-03 06:58:06.801+01', 'File', '/etc/gitlab/gitlab.rb', NULL, 'null', 'null', NULL, '/etc/puppetlabs/code/environments/production/site/gitlab/manifests/server.pp', 7, '{Stage[main],Gitlab::Server,File[/etc/gitlab/gitlab.rb]}', 'Gitlab::Server', NULL, NULL ) was aborted: ERROR: relation "resource_events_20200103z" does not exist
{{ Position: 13 Call getNextException to see other errors in the batch.}} Downgrading puppetdb from 6.8.0-1stretch to puppetdb 6.7.3-1stretch fixed this for us in the meanwhile. Environment:
- Debian stretch
- Postgres 9.6
|
