Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-9298

Command to restore zync-database must points zync_production database

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • 2.13.0 GA, 2.14.0 GA
    • Documentation
    • API CCS Sprint 38 (3Scale), API CCS Sprint 39 (3Scale), API CCS Sprint 40 (3Scale)

    Description

      The current restoring command for zync-database restores data to a wrong database ( to the default postgres database ). The command must point zync_production database.

      Step 4 of 9.5.4.1. Template-based deployments

      oc rsh $(oc get pods -l 'deploymentConfig=zync-database' -o json | jq -r '.items[0].metadata.name') bash -c 'psql -f ${HOME}/zync-database-backup'

      should be:

      oc rsh $(oc get pods -l 'deploymentConfig=zync-database' -o json | jq -r '.items[0].metadata.name') bash -c 'psql zync_production -f ${HOME}/zync-database-backup'

      And step 5 of 9.5.4.2. Operator-based deployments

      oc rsh $(oc get pods -l 'deploymentConfig=zync-database' -o json | jq -r '.items[0].metadata.name') bash -c 'psql -f ${HOME}/zync-database-backup'

      should be:

      oc rsh $(oc get pods -l 'deploymentConfig=zync-database' -o json | jq -r '.items[0].metadata.name') bash -c 'psql zync_production -f ${HOME}/zync-database-backup'

      Attachments

        Issue Links

          duplicates

          Feature Request - Feature requests from customers and/or users THREESCALE-7550 Add documentation about how to scale down pods and then how to scale up after system restoration

          • 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

          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) THREESCALE-8575 Rename the section for "3scale Backup and Restore using templates"

          • Critical - To be worked on immediately following BLOCKER issues.
          • Documenting

          Activity

            People

              Unassigned Unassigned
              rhn-support-tkonishi Takayuki Konishi
              Darren Fennessy Darren Fennessy
              Marian Ganisin Marian Ganisin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: