...
Known Issues
Beijing/master branch
These are current failures for individual ONAP compoents that have workarounds or can be ignored - as a service to everyone who asks - last update 20180314
AAF has a failing container -
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | AAF-170 |
|---|
|
SDC has an internal dependency issue and will need a coordinated restart -
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SDC-739 |
|---|
|
SDNC has a timing issue and will need a restart -
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | OOM-543 |
|---|
|
(vCPE/vVOLTE use case only) VFC has a failing container -
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | VFC-818 |
|---|
|
(vCPE/vVOLTE use case only) VNFSDK has a failing container -
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | VNFSDK-226 |
|---|
|
Details
Installation templates for Kubernetes and deploying ONAP via OOM for the master and amsterdam branches are in the following locations
...
