...
JIRA | Description | JIRA Reported Date | Deployment Platform | ONAP Deployment Date | Comment
|
---|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key |
---|
|
| INT | 149 | VF_MODULE_MODEL table is not present in SDNC database.demo.sh init - failed with ONAP 1.1 | 2017-09-0709 | K8SOpenstack | 2017-09- | 0509 | Blocker |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VID- |
---|
|
| 59 | Unable to create a VNF in VID since Add VNF button is unresponsive in GUI.VID Fails Robot Health Check | 2017-09-0706 | Openstack | (WindRiver) | 2017-09- | 0609 | Blocker |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | POLICYINT-211149 |
---|
|
| demo.sh init - failed with ONAP 1.1PolicyfailsRobothealth check | 2017-09-07 | Openstack(WindRiver)K8S | 2017-09-0605 |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SOVID-10359 |
---|
|
| VID Fails Robot Health Check SO failed to add VNF to service instance | 2017-09-07 | Openstack(WindRiver) | 2017-09-06 |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | POLICY-211 |
---|
|
| PolicyfailsRobothealth check | 2017-09-07 | Openstack(WindRiver) | 2017-09-06 |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-103 |
---|
|
| SO failed to add VNF to service instance | 2017-08-08-30 | Openstack(WindRiver) | 2017-08-21 |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | INT-197 |
---|
|
| demo.sh init failed on Openstack ONAP1.1 | 2017-09-12 | Openstack(WindRiver) | 2017-09-06 | |
...
- Please update the below issues, organized according to A-Z.
Bug | Module | Issue | State | Defect Aging | Work Around |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-79 |
---|
|
| AAI | Sincejuly28 simple gets are returning 404 for v8 | Open | 6 weeks |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-249 |
---|
|
| 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 | Closed
| NA |
|
---|
- | 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-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. |
---|
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 This is still an issue. AAI doesn't have all the Docker imagesWe see that AAI and Robot dockers are not coming up. Work around for AAI: - Manually update the aai_instance file from aa1 to aai2 and run the VM_init script and AAI1 VM will have allthe dockers and we can start using it.
- And revert the change to aai1 and run the init script again and all the AAI1 dockers are also present.
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-98 |
---|
|
| DCAE | Until 20170907 the 5dcaeVMs were not up - fixed today | Closed | NA |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-77 |
---|
|
| SDNC | VF |
_MODULE_MODEL table is not present in SDNC database.Open | 3 days | _MODULE_MODEL table is not present in SDNC database. | Open | 5 days | Raised with highest priority. This is a blocker because this functionality doesnt seem to be implemented so far. This blocks the use case progression. |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-80 |
---|
|
| SDNC | Username and Password are wrongly configured in SDNC_controller_Container. | Open | 1 day | Work around: penecomp/sdnc/data/properties in docker sdnc_controller_container Open aaiclient.properties Change Username and password as: AAI |
Raised with highest priority. |
- | 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 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-82 |
---|
|
| SO | SDC model is not getting distributed into MSO and MSO is throwing an error | Open | 28 days |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-100 |
---|
|
| SO | org.communda.bpm throws null value exception while creating service instance through VID | Open | 20 days | Go to testlab_mariadb_1 docker Open DB using mysql -uroot –ppassword And populate the tables with data. |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-122 |
---|
|
|
SO | Model-version-id is not populated in A&AI during view/edit service instance due to version mismatch (v11) | Open | | SO | Model-version-id is not populated in A&AI during view/edit service instance due to version mismatch (v11) | Open |
| In MSO-server docker go to /etc/mso/config.d/mso.bpmn.urn.properties And change below aai version from v8 to v11 everywhere |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-123 |
---|
|
| SO | Bad request response from SDNC during VF module creation | Open | 1 day | in /etc/mso/config.d/mso.sdnc.properties, update the public IPs. |
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 |
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 |
6 7 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 | VID-61 |
---|
|
| VID | Model-version-id is not populated in AAI during view/edit service instance due to version mismatch (v11) | Open |
1 day2 day | Update the verrsion from 8 to 11 in /tmp/vid/stage/WEB-INF/conf/ directory. |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | INT-178 |
---|
|
| Demo | DNS zone configurationerrorcausesBINDcan'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 |
Testing Environment
Rackspace
...