Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Test No.

Category

(Stability, Resiliency, Scalability)

Description

Status

(Not Started, In-Progress, Pass, Fail)

Notes
1StabilityExecute Restart Test for 72 hour period

PASS

Single instance of restart test executed successfully from JMX - 5/11

All tests executed successfully 16:50GMT 6/11

72 hour Stability test started 16:52GMT

Stability test abandoned due to DMaaP errors from JMX

Edited JMX to use randomised consumerGroup in DMaaP call to fix DMaaP errors and restarted test at 11:55pm. Test succeeding for first 20 minutes and VMs being start stop rebuild restart succesfully

Test ongoing at 7:30AM GMT 11/9 - still logging successes in JTL file and successfully carrying out start/stop/restart/rebuild operations on VMs as confirmed from Windriver OpenStack GUI.

Test ongoing at 5:00PM GMT 11/9

Test completed at 11:56pm GMT 11/9

View file
namekaraf.log
height250

View file
nameJMX-restartTestLog.txt
height250

View file
nameJMX_log_all_operations_6_11.txt
height250


2StabilityExecute Rebuild Test for 72 hour period

PASS

Test started 11/10 01:10GMT

nohup /home/ubuntu/testing/apache-jmeter-4.0/bin/jmeter.sh -n -t ./infinite_APPC-LCM-Action-V1.jmx -l ./APPC-LCM-Action-V1_run72hr_01:10GMT_11_10.jtl >/dev/null 2>&1 &



3StabilityExecute Start Test for 72 hour period

ABANDONED

Restarted 16:00GMT 11/20 nohup /home/ubuntu/testing/apache-jmeter-4.0/bin/jmeter.sh -n -t ./infinite_APPC-LCM-Action-V1.jmx -l ./APPC-LCM-Action-V1_11_20_16_00.jtl >/dev/null 2>&1 &

10:00GMT 11/21 Tests running successfully against 1.4.3 software

13:00GMT 11/22 Faults in VMs causing outages for tests

1) JMX logging errors connecting to DMaaP

1542892966853,998,Submit request via DMaaP,Non HTTP response code: java.net.ConnectException,Non HTTP response message: Connection refused (Connection refused),Stability-Test-VM3 LCM Group 3-1,text,false,,2058,0,1,3,0,0,998
1542892967741,1002,SYNC(accepted/rejectd) response via DMaaP,Non HTTP response code: java.net.ConnectException,Non HTTP response message: Connection refused (Connection refused),Stability-Test-VM2 LCM Group 2-1,text,false,,2058,0,1,3,0,0,1002
1542892963736,2004,Stop Transaction Controller,,"Number of samples in transaction : 2, number of failing samples : 2",Stability-Test-VM2 LCM Group 2-1,,false,,4116,0,1,3,0,3006,2004
1542892968747,996,Submit request via DMaaP,Non HTTP response code: java.net.ConnectException,Non HTTP response message: Connection refused (Connection refused),Stability-Test-VM2 LCM Group 2-1,text,false,,2058,0,1,3,0,0,996
1542892968889,998,SYNC(accepted/rejectd) response via DMaaP,Non HTTP response code: java.net.ConnectException,Non HTTP response message: Connection refused (Connection refused),Stability-Test-VM1 LCM Group 1-1,text,false,,2058,0,1,3,0,0,998
1542892964886,1998,Restart Transaction Controller,,"Number of samples in transaction : 2, number of failing samples : 2",Stability-Test-VM1 LCM Group 1-1,,false,,4116,0,1,3,0,3006,1998
1542892969891,1000,Submit request via DMaaP,Non HTTP response code: java.net.ConnectException,Non HTTP response message: Connection refused (Connection refused),Stability-Test-VM1 LCM Group 1-1,text,false,,2058,0,1,3,0,0,1000

2) Stablity Test VM errors

3) APPC VM Reboot

4) Cluster problems logging in APPC

2018-11-22 13:37:46,865 | WARN | lt-dispatcher-98 | NettyTransport | 57 - com.typesafe.akka.slf4j - 2.5.11 | Remote connection to [null] failed with java.net.ConnectException: Connection refused: onap-appc-2.appc-cluster.onap/10.42.0.70:2550
2018-11-22 13:37:46,930 | WARN | lt-dispatcher-84 | ReliableDeliverySupervisor | 57 - com.typesafe.akka.slf4j - 2.5.11 | Association with remote system [akka.tcp://opendaylight-cluster-data@onap-appc-2.appc-cluster.onap:2550] has failed, address is now gated for [5000] ms. Reason: [Association failed with [akka.tcp://opendaylight-cluster-data@onap-appc-2.appc-cluster.onap:2550]] Caused by: [Connection refused: onap-appc-2.appc-cluster.onap/10.42.0.70:2550]

Abandoning test 17:00GMT 11/22

APPC deployment has most pods running morning of 11/23 but onap-appc-2 pod is not connectable and is reporting:

onap-appc-2 1/2 Running 0 13h 10.44.0.107 k8s-appc1 <none>



4StabilityExecute Stop Test for 72 hour period

...