Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-3968

Timeout when so queries oof for NST Selection

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • Jakarta Release

    • oom Jakarta

      I am using oom Jakatar to test the Network Slicing use case.

      I have noticed, when so-bpmn-infra triggers oof for NST selection, it always get timeout after 5-6 mins. But normally it takes about 8-9 mins for oof be able to identify the good NST and reply to so-bpmn-infra. Due to this mismatch, it is not able to getting the correct NST.

      PS: so is triggered from UUI.

        1. oof.log
          16 kB
        2. screenshot-1.png
          screenshot-1.png
          157 kB
        3. screenshot-2.png
          screenshot-2.png
          120 kB
        4. so_bpmn_inra.log
          26 kB

            malar malar
            xuegao xuegao
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: