...
Components | Stack creation date | Docker download date | VM Component Deployment | Docker Image availability | Container Issues | Robot “health-check” | Occurence Date | JIRA | Comments | ||||||||||
AAI1 | 8/9/2017 | 8/24/2017 | Up & Running | images available | 10 up | FAIL | 20170831 |
| Unable to view/edit the service instance created to trigger VNF creation. Model-version-id is not available.AAI is throwing bad requestinreponsetoMSO'srequest. This is working fine in 1.0 ONAP | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AAI2 | 8/9/2017 | UP not running | Not available | 1 of 3 up | ? | 20170828 |
| ||||||||||||
APPC | 8/9/2017 | 8/9/2017 | Up & Running | images available | PASS |
| |||||||||||||
DCAE | 8/9/2017 | 8/9/2017 | Up & Running | images available | FAIL | ||||||||||||||
DCAE CDAP, PSTG, COLL | Missing | not dockerized | n/a | 20170828 |
| The 5 DCAE orchestrated VMs are missing - will verify my heat template | |||||||||||||
DNS | 8/9/2017 | 8/9/2017 | Up & Running | images available | PASS |
| |||||||||||||
VID | 8/9/2017 | 8/23/2017 | Up & Running | images available | PASS | Still tracking
| |||||||||||||
ROBOT | 8/9/2017 | 8/9/2017 | Up & Running | images available | |||||||||||||||
SDC | 8/9/2017 | 8/9/2017 | Up & Running | images available | PASS | ||||||||||||||
MSO | 8/9/2017 | 8/9/2017 | Up & Running | images available | PASS |
| |||||||||||||
PORTAL | 8/9/2017 | 8/9/2017 | Up & Running | images available | PASS | ||||||||||||||
AAI2 | 8/9/2017 | Up & Running | images available | / | |||||||||||||||
POLICY | 8/9/2017 | 8/9/2017 | Up & Running | images available | PASS | ||||||||||||||
SDNC | 8/9/2017 | 8/9/2017 | Up & Running | images available | PASS | ||||||||||||||
ROUTER | 8/9/2017 | 8/9/2017 | / | / | / |
...
Below you can find more details regarding the latest issues:
Bug | Module | Issue | State | Defect Aging | Resolution/Comments |
AAI | Error: model-version-id is not populated in A&AI during view/edit service instance | Open | 1 day | Posted mail to defect assignee James Forsyth seeking his inputs/alternates/re-assignment. Debug is in progress. | |
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. He closed the defect. |