...
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 | ||||||
---|---|---|---|---|---|---|
|
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
...
JIRA | Description | JIRA Reported Date | Deployment Platform | ONAP Deployment Date | Comment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| demo.sh init - failed with ONAP 1.1 | 2017-09-07 | K8S | 2017-09-05 | |||||||||
| VID Fails Robot Health Check | 2017-09-07 | Openstack(WindRiver) | 2017-09-06 | |||||||||
| Policyfails Robot PolicyfailsRobot health check | 2017-09-07 | Openstack(WindRiver) | 2017-09-06 | |||||||||
| SO failed to add VNF to service instance | 2017-08-30 | Openstack(WindRiver) | 2017-08-21 |
...
Comp | Stack creation date | Docker 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 / DEMO | 20170906 | 20170906 | All 19 VMs are up. 3 ONAP modules (VID, Policy, DCAE) failed Robot health check. | 19 VMs are up | 20170906 |
| 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 | 20170809 | 20170824 | Up | Up | images available | 10/10 20170907 | 10/10 (zookeeper,dmaap,kafkato be kafkatobe removed 20170908 to be 7/7) | PASS | 20170831 |
AAI-79 is 6 weeks old
| 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 | 20170809 | 20170809 | Up | Up | 1 image verified | 3/3 20170907 | 3/3 | PASS | 20170828 |
| 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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
APPC | 20170809 | 20170809 | Up & | Up & Running | images available | 3/3 | PASS |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CLAMP | 20170903 | UP not functional | ? | 0/2 | pendingOOM-12 | healthcheckneedsupdate | 20170903 |
| (added20170829) - missingmariadband clamp missingmariadbandclamp containers - it is possible CLAMP is still a WIP? | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DCAE-CONT ROLLER | 20170809 | 20170809 | Up & | UP not functional | images available | 0/2 20170903 | n/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'}
| 20170903 |
| The groovy process runs for 45 then exists with orchestration running | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DCAE zldc<dc> vi cdap(3), pstg, coll | 20170828 | 5/5 Up & Running | 5/4 Up & Running | not all dockerized | n/a | n/a | 20170903 |
| 5 of 5 DCAEvmsup as of 20170907 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DNS -SERVER | 20170809 | 20170809 | Up & | Up & Running | not dockerized | notrequired | PASS |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
LOG | notin heat notinheat yet | pendingmerge
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
VID | 20170809 | 20170823 | Up & | Up & Running | images available | 2/2 | FAIL 500 != 200 |
Still tracking
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ROBOT | 20170809 | 20170809 | Up & | Up & Running | images available | 1/1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SDC | 20170809 | 20170809 | Up | images available | 5/5 | 5/5 | PASS |
| OOM workaround:
ON RS I get a 503 healthcheckshows 500healthcheckshows500 forOOM fix forOOMfix will be in
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MSB | notin heat notinheat yet | 4/4 |
| containershave nexus3 containershavenexus3 security secret issues heattemplate pendingheattemplatepending
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MSO | 20170809 | 20170809 | Up & | Up & Running | images available | 2/2 | PASS |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PORTAL | 20170809 | 20170809 | Up & | Up & Running | images available | 3/3 | PASS | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
POLICY | 20170809 | 20170809 | Up & | 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 |
| These two issues are related. BAD request response from SDNC. And SDNC databasedoesnthaverequired tablecreatedSDNCdatabasedoesnthaverequiredtablecreated. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MESSAGE -ROUTER | 20170809 | 20170809 | / | / | images available | 3/3 | / |
...
Bug | Module | Issue | State | Defect Aging | Work Around | ||||||||
| DCAE | Until 20170907 the 5dcaeVMs were not up - fixed today | Closed | ||||||||||
| AAI | Sincejuly28 simple gets are returning 404 for v8 | Open | 6 weeks | |||||||||
AAI | Error: model-version-id is not populated in A&AI during view/edit service instance | Closed | NA | Closed since it was working with v11 UTF version. | |||||||||
AAI-226 | AAI | AAIthrowsBadRequesterrortoMSO during service instance creation | Open | 3 day | This is working fine in 1.0 ONAP but not working in 1.1 ONAP. | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
- | AAI | Unable to deploy model loader docker in AAI | Closed | NA | Update the port numbers and restart the dockers | ||||||||
AAI-190 | AAI | AAI-190 AAI was not able to communicate with ASDC. Unable to deploy model loader docker in AAI. | Closed | NA | 1.Stop and remove the old dockers,placenewdockersandupdatethejava.security file like above. 2.Update the port numbers and restart the dockers. | ||||||||
- | 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.) | |||||||||
- | SO | Unable to connect to AAI due to SSL | Closed | NA | 1. 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-38 | VID | Deploy button is not working in VID to distribute Model | Closed | NA | Ofir's work is completed. But it still persists. I tried to see this on Saturday's build and it is still an issue. | ||||||||
VID | Unable to create a VNF in VID since Add VNF button is unresponsive in GUI. | Open | 5 days | Ofir Sonsino is working on this issue. Issue is reported with highest priority. | |||||||||
| Demo | DNS zone configuration errorcauses BIND errorcausesBIND can't resolve DNS queries | Change has been merged | 2017/09/06 | thechangehttps://gerrit.onap.org/r/#/c/10713/ | ||||||||
| VID | VID fails Robot health check. There is Java ClassNotFoundException inlogClassNotFoundExceptioninlog | Open | 2017/09/06 | Reported with highest priority | ||||||||
| POLICY | POLICY fails Robot health check | Open | 2017/09/06 | Reported with highest priority |
...
OpenstackDeployment | Rackspace Deployment | OOM Deployment | Vagrant 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
...