Uploaded image for project: 'Optimization Framework'
  1. Optimization Framework
  2. OPTFRA-498

Policy loading problem

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • High
    • Resolution: Done
    • Dublin Release
    • Dublin Release
    • OSDF
    • None

    • SB-00

    Description

      When Traffic Distribution request is being done OSDF returns and error HTTP 400 with message PE300 - no match found. Attached debug.log from pdp with information that requested policies are being loaded by pdp but because of some reason HTTP 400 is returned.

      Perhaps the problewm is with policy pattern used for policy retrieval "policyName": "OSDF_CASABLANCA..\\d."

      When I invoke such query on OSDF it return 400:

      wget -O - --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST'  https://pdp:8081/pdp/api/getConfig  --post-data '{ "policyName": "OSDF_CASABLANCA.*.[\\d].*"}'

      but when I modify it to:

      wget -O - --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST'  https://pdp:8081/pdp/api/getConfig  --post-data '{ "policyName": "OSDF_CASABLANCA.*"}'

      it returns whole set of policies.

      Moreover, OSDF looks for policies with scope OSDF_CASABLANCA when it should look for OSDF_DUBLIN scope instead.

      Attachments

        1. pdp-debug.txt
          27 kB
        2. request.json
          2 kB
        3. response.json
          0.9 kB

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OPTFRA-424 Extend OOF to support traffic distribution optimization

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed
          mentioned in

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              rajewluk Lukasz Rajewski
              rajewluk Lukasz Rajewski
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: