Uploaded image for project: 'mod-remote-storage'
  1. mod-remote-storage
  2. MODRS-79

mod-remote-storage unavailable in snapshot environments

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Firebird Sprint 119
    • Story Points:
      3
    • Development Team:
      Firebird

      Description

      Ann-Marie Breaux and Owen Stephens reported this morning that the snapshot environment is unavailable.

      Symptoms

      The latest build reports the following error:

      fatal: [10.36.1.36]: FAILED! => {"changed": false, "connection": "close", "content": "POST request for mod-remote-storage-1.1.0-SNAPSHOT.49 /_/tenant failed with 500: {\"timestamp\":\"2021-02-01T01:44:25.267+00:00\",\"status\":500,\"error\":\"Internal Server Error\",\"message\":\"\",\"path\":\"/_/tenant\"}", "content_length": "203", "content_type": "text/plain", "elapsed": 117, "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.36.1.36:9130/_/proxy/tenants/diku/install?deploy=true&tenantParameters=loadSample%3Dtrue%2CloadReference%3Dtrue", "vary": "origin"}
      

      This suggests that mod-remote-storage fails to be enabled for the diku tenant.

      Open Questions

      Why does the folio-testing build succeed with the same version of mod-remote-storage?

      Other Affected Environments

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Charniak Siarhei Charniak
                Reporter:
                marcjohnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases