Bug | Module | Issue | State | Defect Aging | Work Around |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key |
---|
|
| DCAEGEN2 | 98DCAE | Until 20170907 the 5dcaeVMs were not up - fixed today | Closed | AAI | Sincejuly28 simple gets are returning 404 for v8 | Open | 6 weeks |
|
6 weeks Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key |
---|
|
AAI-79 | | AAI | Sincejuly28 simple gets are returning 404 for v8 | Open | | AAI | Error: model-version-id is not populated in A&AI during view/edit service instance | Closed | NA | Closed since it was working with API v11 UTF version. |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | 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 |
---|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI- |
---|
|
AAI- | 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. |
---|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | 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.) |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-98 |
---|
|
| DCAE | Until 20170907 the 5dcaeVMs were not up - fixed today | Closed |
|
|
- | 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. |
---|
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | 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. |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VID-57 |
---|
|
| 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. |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | INT-178 |
---|
|
| Demo | DNS zone configuration errorcausesBIND can't resolve DNS queries | Change has been merged | 2017/09/06 | thechangehttps://gerrit.onap.org/r/#/c/10713/ |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VID-59 |
---|
|
| VID | VID fails Robot health check. There is Java ClassNotFoundExceptioninlog | Open | 2017/09/06 | Reported with highest priority |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | POLICY-211 |
---|
|
| POLICY | POLICY fails Robot health check | Open | 2017/09/06 | Reported with highest priority |