Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-12328

Postgres upgrade from 9.5 to 9.6 won't use the old data dir

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • None
    • fuse-7.5-GA
    • Fuse Online
    • None
    • Fuse 7.6 - Sprint 56 (2/4)

    Description

      Between 7.4 and 7.5 we changed postgres 9.5 to 9.6 and during the upgrade a new deployment of database is rolled out. however the deployment ends with:

      Exec lifecycle hook ([/bin/sh -c /var/lib/pgsql/sampledb/postStart.sh]) for Container "postgresql" in Pod "syndesis-db-2-7t7mb_avano-syndesis(f8c5f29e-102c-11ea-8dae-fa163e2bfff4)" failed - error: command '/bin/sh -c /var/lib/pgsql/sampledb/postStart.sh' exited with 137: , message: ""

      I assume that this is the culprit:

      sh-4.2$ container-entrypoint run-postgresql
Incompatible data directory.  This container image provides
PostgreSQL '9.6', but data directory is of
version '9.5'.

This image supports automatic data directory upgrade from
'9.5', please _carefully_ consult image documentation
about how to use the '$POSTGRESQL_UPGRADE' startup option.

      Attachments

        Issue Links

          is incorporated by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ENTESB-12359 Fuse Online 7.5.1

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Sub-task - The sub-task of the issue ENTESB-12917 Add upgrade steps that can perform the Postgres dataDir conversion if needed

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-12534 Sort out upgrade cases related to postgres

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Done

          Activity

            People

              lgarciaac Luis García Acosta
              avano@redhat.com Andrej Vano
              Michael Cada Michael Cada
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: