Versions Compared

Key

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

...

For stabilizing the ONAP, we are considering vFW use case (Open loop)asa E2E flow. Below are the issues we are facing while we try tosetup trytosetup a stable environment to run thevFW runthevFW use case successfully. Please observe the status info below regarding all ONAP (Heat based) components in (Openstack(float/no-float) or Rackspace?). 

see 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-106

More Useful info Regarding setting the ONAP Env:

Please note that you need to change the privetip into publicip in hosts file & in property file.

Top Blocking Issues for ONAP1.1

...

JIRADescriptionJIRA Reported DateDeployment Platform

ONAP Deployment Date

Comment


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-149

demo.sh init - failed with ONAP 1.12017-09-07K8S2017-09-05

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-59

VID Fails Robot Health Check

2017-09-07Openstack(WindRiver)2017-09-06

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-211

Policyfails Robot PolicyfailsRobot health check

2017-09-07Openstack(WindRiver)2017-09-06

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-103

SO failed to add VNF to service instance2017-08-30Openstack(WindRiver)2017-08-21

...

 Comp

Stack creation dateDocker download date

VM Deploy openstack

(expecting 19)

VM Deploy rackspace

(expecting 19)

Docker Image availability

Dockers open stack

Dockers rack space

Dockers K8S

Robot “health-check”

Occurence

Date

JIRA

Comments

INT / DEMO2017090620170906

All 19 VMs are up. 3 ONAP modules (VID, Policy, DCAE) failed Robot health check.

19 VMs are up






20170906

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-149

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-95

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-98

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-69

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-88

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-89

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-71

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-178

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-59

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-211

We can proceed as far as creating a service for thevFirewallforthevFirewall(the VF and VF-Module creation will need a fix.

./demo.shinitnot working shinitnotworking in all deployment environments

AAI1

2017080920170824

Up

Up  images available

10/10 20170907

10/10

(zookeeper,dmaap,kafkato be kafkatobe removed 20170908 to be 7/7)

PASS

20170831

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-249

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-237

AAI-79 is 6 weeks old

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-79

Unable to view/edit the service instance created to trigger VNF creation. Model-version-id is not available.

Rackspace missing traversal, data-router, service, search-data-service, model-loader-service - fixed 20170907

Gremlinis being Gremlinisbeing retired

AAI2

2017080920170809

Up

Up
  1 image verified
3/3 201709073/3

PASS

20170828

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-237

basedon the basedonthe fact aai2 used to have 3 containers and aai1 had 10 - OOM is currently bringing up all 13 together as a reference - fixed 20170907

Overall Deployment Architecture#Version1.1.0/R1

APPC

2017080920170809

Up &
Running

Up &
Running

images

available



3/3

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCIMAN-32


CLAMP20170903

UP not functional?
0/2

pendingOOM-12


healthcheckneedsupdate20170903

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-115

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-12

(added20170829) - missingmariadband clamp missingmariadbandclamp containers - it is possible CLAMP is still a WIP?

DCAE-CONT

ROLLER

2017080920170809

Up &
Running

UP not functional images available
0/2 20170903n/a

FAIL


Health check failed {u'service': u'cdap-helloworld', u'instance': u'iad4', u'status': u'UNDEPLOYED', u'healthTestStatus': u'YELLOW', u'healthTestMessageCode': u'Cluster not deployed'}

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-71

20170903


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-88

The groovy process runs for 45 then exists with orchestration running

DCAE zldc<dc> vi cdap(3), pstg, coll20170828
5/5 Up &
Running
5/4 Up &
Running
not all dockerized

n/an/a20170903

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-131

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-95

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-98

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-69

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-89

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-71

5 of 5 DCAEvmsup as of 20170907

DNS -SERVER

2017080920170809

Up &
Running

Up &
Running
 not dockerized

notrequired

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCIMAN-32


LOG

notin heat notinheat yet







pendingmerge

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-110

VID

2017080920170823

Up &
Running

Up &
Running
 images available

2/2

FAIL

500 != 200


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-57

Still tracking

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-38


ROBOT

20170809
20170809

Up &
Running

Up &
Running
images available



1/1





SDC

20170809
20170809

Up


 images available
5/55/5

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-268

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-280

OOM workaround:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-282

ON RS I get a 503

healthcheckshows 500healthcheckshows500

forOOM fix forOOMfix will be in

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-276

MSB

notin heat notinheat yet



4/4

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-113

containershave nexus3 containershavenexus3 security secret issues

heattemplate pendingheattemplatepending

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-115

MSO

20170809
20170809

Up &
Running

Up &
Running
images available

2/2

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCIMAN-32


PORTAL

20170809
20170809

Up &
Running

Up &
Running
 images available

3/3

PASS




POLICY

20170809
20170809

Up &
Running

Up &
Running
 images available

7/7

FAIL



Policyis not Policyisnot coming up from Portal in RS - verifying in K8S before a JIRA arrives

SDNC

20170809
20170809

Up & Running

Up &
Running
 images available

4/4

PASS


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-78
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-77

These two issues are related. BAD request response from SDNC. And SDNC databasedoesnthaverequired tablecreatedSDNCdatabasedoesnthaverequiredtablecreated.

MESSAGE -ROUTER

20170809
20170809
//images available

3/3

   /




...

BugModuleIssueStateDefect AgingWork Around

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-98

DCAE

Until 20170907 the 5dcaeVMs were not up - fixed todayClosed

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-79

AAISincejuly28 simple gets are returning 404 for v8Open6 weeks

AAI-249

AAIError: model-version-id is not populated in A&AI during view/edit service instanceClosedNA
Closed since it was working with v11 UTF version.
AAI-226AAIAAIthrowsBadRequesterrortoMSO  during service instance creationOpen3 dayThis is working fine in 1.0 ONAP but not working in 1.1 ONAP.
-AAIUnable   to deploy model loader docker in AAIClosedNAUpdate   the port numbers and restart the dockers
AAI-190AAIAAI-190   AAI was not able to communicate with ASDC.
    Unable to deploy model loader docker in AAI.
ClosedNA1.Stop   and remove the old dockers,placenewdockersandupdatethejava.security file like   above.
   2.Update the port numbers and restart the dockers.

CIMAN-32

 - Dockers are not present in the VMs after ONAP 1.1 deployment Open 4 days It was working till last Wednesday 8/23/2017 (when we last checked.)
-SOUnable   to connect to AAI due to SSLClosedNA1.   Comment the certificate partinjava.security file resides in   /etc/java-8-openjdk/security
   2.Updatemso.asdc.json located in /etc/mso/config.d path.
VID-38VIDDeploy   button is not working in VID to distribute ModelClosedNAOfir's work is completed. But it still persists. I tried to see this on Saturday's build and it is still an issue.

VID-57

VIDUnable to create a VNF in VID since Add VNF button is unresponsive in GUI.Open5 days

Ofir Sonsino is working on this issue. Issue is reported with highest priority.

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-178

DemoDNS zone configuration errorcauses BIND errorcausesBIND can't resolve DNS queriesChange has been merged2017/09/06thechangehttps://gerrit.onap.org/r/#/c/10713/

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-59

VIDVID fails Robot health check. There is Java ClassNotFoundException inlogClassNotFoundExceptioninlogOpen2017/09/06Reported with highest priority

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-211

POLICYPOLICY fails Robot health checkOpen2017/09/06Reported with highest priority

...

OpenstackDeploymentRackspace DeploymentOOM DeploymentVagrant Deployment

20170906 All VMs are up

3 ONAP modules (VID, Policy and DCAE) fail onRobot failonRobot health check

20170903 with latest Clamp VM addition

20170902 All up except in-review DCAE

Console: http://test.onap.info:8880/ | vnc-portal: http://test.onap.info:30211/

SDC 404 issue - JIRA pending when I retestrackspaceas wellIretestrackspaceaswell



Historical Docker Deployment Status

...