This Page will show the Daily status of the ONAP master branch with info such as issues/WA/relevant info regarding the ONAP components.
In this way we will be able to track the progress of all the Projects under ONAP, and to be able to solve issues faster while everyone is familiar with the latest issues and get info how to solve them with the info below.
Please observe the status info below regarding all ONAP (Heat based) components.
Components | VM Component Deployment | Docker Image availability | Container Issues | Robot “health-check” | Occurence Date | JIRA | Comments |
AAI1 | Up & Running | images available | 10 up | FAIL | AAI-226 - Getting issue details... STATUS | AAI is throwing bad requestinreponsetoMSO'srequest. This is working fine in 1.0 ONAP | |
|---|---|---|---|---|---|---|---|
AAI2 | UP not running | Not available | 1 of 3 up | ? | 20170828 | AAI-237 - Getting issue details... STATUS | |
APPC | Up & Running | Not available | PASS | CIMAN-32 - Getting issue details... STATUS | |||
DCAE | Up & Running | images available | FAIL | ||||
| DCAE CDAP, PSTG, COLL | Missing | not dockerized | n/a | 20170828 | DCAEGEN2-88 - Getting issue details... STATUS | The 5 DCAE orchestrated VMs are missing | |
DNS | Up & Running | Not available | PASS | CIMAN-32 - Getting issue details... STATUS | |||
VID | Up & Running | images available | PASS | Still tracking VID-38 - Getting issue details... STATUS | |||
ROBOT | Up & Running | images available | 1 up missing/opt content | / | 20170824 | INT-113 - Getting issue details... STATUS | |
SDC | Up & Running | images available | PASS | ||||
MSO | Up & Running | Not available | PASS | CIMAN-32 - Getting issue details... STATUS | |||
PORTAL | Up & Running | images available | PASS | ||||
AAI2 | Up & Running | images available | / | ||||
POLICY | Up & Running | images available | PASS | ||||
SDNC | Up & Running | images available | PASS | ||||
ROUTER | / | / | / |
Below you can find more details regarding the latest issues:
| Bug | Module | Issue | State | Defect Aging | Resolution/Comments |
| AAI-226 | AAI | AAIthrowsBadRequesterrortoMSO during service instance creation | Open | 1 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 | 3 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 | Re-open | 13 days | Reopened by community as the build was failing with the fix. Ofir's work is in progress. |