Uploaded image for project: 'mod-circulation'
  1. mod-circulation
  2. CIRC-1860

missing permission circulation-storage.circulation-rules.get for mod-circulation_0 timer

    XMLWordPrintable

Details

    • EPAM-Veg Sprint 171
    • 0.5
    • Vega
    • Orchid (R1 2023) Service Patch #5
    • Yes
    • Hide
      As a P1 issue, and is having significant impact on Chalmers - they are unable to check in anything. They are observing this issue in Orchid - SP#3 - mod-circulation-23.5.5. This may affect any institution with this release and a similar set up.

      Workaround - If an institution is able, they could update the module descriptor to include the missing permission

      Impacted areas - Everything that relies on circulation rules (check-in, check-out, requests, renewals etc.) But it should only affect performance, not the ability to perform these actions.

      Fix & effort - A wrong permission was used for circulation rules automated reloading, it was fixed. Both effort and risk are close to zero.

      Testing - we're still working on finding a way to test this that doesn't include retesting everything related to circulation rules, which would take days. We're working with QA.

      Rollback plan - Only revert the code, there are no irreversible changes in the DB.
      Show
      As a P1 issue, and is having significant impact on Chalmers - they are unable to check in anything. They are observing this issue in Orchid - SP#3 - mod-circulation-23.5.5. This may affect any institution with this release and a similar set up. Workaround - If an institution is able, they could update the module descriptor to include the missing permission Impacted areas - Everything that relies on circulation rules (check-in, check-out, requests, renewals etc.) But it should only affect performance, not the ability to perform these actions. Fix & effort - A wrong permission was used for circulation rules automated reloading, it was fixed. Both effort and risk are close to zero. Testing - we're still working on finding a way to test this that doesn't include retesting everything related to circulation rules, which would take days. We're working with QA. Rollback plan - Only revert the code, there are no irreversible changes in the DB.
    • Chalmers
    • Missing module permission
    • Orchid (R1 2023)

    Description

      Overview: mod-circulation-23.3.5 missing permission in module descriptor
      Steps to Reproduce:

      1. Deploy mod-circulation-23.3.5
      2. Watch the okapi log output for 500 responses
      3. See POST request for mod-circulation-23.3.5 /circulation/rules-reload failed with 500

      Expected Results: POST request for mod-circulation-23.3.5 /circulation/rules-reload response is success
      Actual Results:

      2023-07-20T22:13:11,835        INFO        ?        timer mod-circulation_0 handle for tenant sul        

      2023-07-20T22:13:11,838        INFO        ?        timer mod-circulation_0 call start module mod-circulation-23.3.5 for tenant sul        

      2023-07-20T22:13:11,838        INFO        ?        waitTimer mod-circulation_0 delay 180000 for tenant sul        

      2023-07-20T22:13:11,845        INFO        ?        831827/circulation REQ okapiClient sul POST http://mod-authtoken/circulation/rules-reload        

      2023-07-20T22:13:11,846        INFO        ?        831827/circulation RES 202 1153us okapiClient http://mod-authtoken/circulation/rules-reload        

      2023-07-20T22:13:11,846        INFO        ?        authForSystemInterface: mod-circulation-23.3.5 [{"X-Okapi-Url":"http://okapi:9130"},{"X-Okapi-Permissions":"[]"}]        

      2023-07-20T22:13:11,851        INFO        ?        886260/circulation REQ okapiClient sul POST http://mod-circulation/circulation/rules-reload        

      2023-07-20T22:13:11,875        INFO        ?        886260/circulation RES 500 23497us okapiClient http://mod-circulation/circulation/rules-reload        

      2023-07-20T22:13:11,875        WARN        ?        POST request for mod-circulation-23.3.5 /circulation/rules-reload failed with 500: Failed to decode:Unrecognized token 'Access': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') |  at [Source: (String)"Access for user 'UNDEFINED_USER__10.1.72.72:59964__2023-07-20T22:13:11.846+0000' (null) requires permission: circulation-storage.circulation-rules.get"; line: 1, column: 7] | io.vertx.core.json.DecodeException: Failed to decode:Unrecognized token 'Access': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') |  at [Source: (String)"Access for user 'UNDEFINED_USER__10.1.72.72:59964__2023-07-20T22:13:11.846+0000' (null) requires permission: circulation-storage.circulation-rules.get"; line: 1, column: 7] |   at io.vertx.core.json.jackson.DatabindCodec.fromParser(DatabindCodec.java:129) |   a

      *Additional Information: See https://issues.folio.org/browse/CIRC-1783*
      URL:
      Interested parties:

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                OleksandrVidinieiev Oleksandr Vidinieiev
                sdoljack Shelley Doljack
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases