Uploaded image for project: 'Integration'
  1. Integration
  2. INT-1918

Stability tests: // instantiation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Honolulu Release
    • Honolulu Release
    • None
    • honolulu weekly installed on the 19th of April

      A stability test has been performed

      it consists in 5 basic_vm tests executed in // during 48h.

      The test starts with 2 success tests (among the 5) then reach a SDNC error.

      STATUS: Error Source: SDNC, Error Message: Error from SDNC: java.util.concurrent.ExecutionException: TransactionCommitFailedException{message=canCommit encountered an unexpected failure, errorList=[RpcError [message=canCommit encountered an unexpected failure, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=akka.pattern.AskTimeoutException: Ask timed out on ActorSelection[Anchor(akka://opendaylight-cluster-data/), Path(/user/shardmanager-config/member-1-shard-default-config#1960658406)] after [120000 ms]. Message of type [org.opendaylight.controller.cluster.datastore.messages.ReadyLocalTransaction]. A typical reason for `AskTimeoutException` is that the recipient actor didn't send a reply.]]}

      This error detected few hours later (wake up time) was fixed by a simple delete of the sdnc (kubectl delete pod sdnc-0 -n onap)

      Then the tests are re-run properly until reaching some Infra certificate issues not dealing with ONAP.

      STATUS: Error Source: OPENSTACK, Error Message: Exception occured during vnf adapter: Exception during create VF org.onap.so.openstack.exceptions.MsoIOException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. FLOW STATUS: Execution of AssignVfModuleBB has completed successfully, next invoking CreateVfModuleBB (Execution Path progress: BBs completed = 1; BBs remaining = 2). TASK INFORMATION: Task name is null.

      During the valid windows of test execution, we can see that the success rate is not so good, most of the errors seem to de due to the timeout on SO call. This issue already reported in gate and daily appear here also. It could eb due to SO/SO-SDNC, SO-AAI, SO-DB,..but there is no timeout on SO side, the test remain in Progress. The timeout is reached on the tester side after 30 minutes on a call to SO.

      The success rate moved from ~80% (serie 10 2021-04-20 07:47:08,784 ) to ~70% (serie 170 2021-04-22 05:05:29,649)

      We may also notice that like in Guilin the distribution of the duration of the test is very wide, the same test can be execute in 5 minutes or in 30 minutes.

      test-basic_vm-5-48h.tar.xz

       

        1. bar_mygraph.png
          bar_mygraph.png
          28 kB
        2. histo_mygraph.png
          histo_mygraph.png
          12 kB
        3. mygraph.png
          mygraph.png
          29 kB
        4. success_rate_basic_vm_5_simu_48h_zoom.png
          success_rate_basic_vm_5_simu_48h_zoom.png
          66 kB
        5. success_rate_basic_vm 5_simu_48h_full.png
          success_rate_basic_vm 5_simu_48h_full.png
          63 kB
        6. test-basic_vm-5-48h.tar.xz
          765 kB

            mrichomme mrichomme
            mrichomme mrichomme
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: