Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4641

resource_events partitioning migration failure

    XMLWordPrintable

Details

    • PuppetDB
    • Needs Assessment
    • Bug Fix
    • Hide
      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)
      Show
      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 )
    • Needs Assessment

    Description

      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

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Activity

            People

              austin.blatt Austin Blatt
              vicinus Reinhard Vicinus
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support