Problems/Issues encountered or steps required when using ONAP Dublin after a fresh installation

1 Portal HTTP 500
2 DMaaP message router pods in ContainerConfigError
3 Policy PODs in CrashLoopBackOff
4 Most of SO PODs in CrashLoopBackOff
5 Remove duplicate objects from A&AI

Portal HTTP 500

PORTAL-571: Can't access Portal UIClosed

DMaaP message router pods in ContainerConfigError

Restart kubelet container in affected hosts

Policy PODs in CrashLoopBackOff

POLICY-1640: Three Policy pods are in CrashLoopBackOff after ONAP deploymentClosed

Most of SO PODs in CrashLoopBackOff

See SO-1674: SO pods failed to come up in ONAP deploymentClosed and https://lists.onap.org/g/onap-discuss/message/16509

workaround

1. Connect to MariaDB container
2. mysql -uroot
3. use mysql;
4. SET PASSWORD FOR 'root'@'localhost' = PASSWORD('password');

5. cd docker-entrypoint-initdb.d
6. Run scripts 01-… to 05-…


Wait for SO PODs to become in Running state

Remove duplicate objects from A&AI

Context of issue is described here

For instance, we had many duplicate Logical-links and we could not fetch/delete them.

So, we have to first get their Vertex IDs so that we can manually delete them from Graph database.

Fetching Vertex IDs

curl -X GET \
'https://172.30.0.90:30233/aai/v16/network/logical-links?format=id' \
-H 'Accept: application/json' \
-H 'Authorization: Basic QUFJOkFBSQ==' \
-H 'Content-Type: application/json' \
-H 'Postman-Token: 5f14e474-f704-4f48-859e-ac1977e7243c' \
-H 'X-FromAppId: Postman Application' \
-H 'X-TransactionId: Postman REST Transaction' \
-H 'cache-control: no-cache'

An example of an output is shown the official documentation

Upon fetching all the vertex IDs that need to be manually removed, for each one of them we execute the following command (replace the graph-admin POD and VERTEX_ID placeholders as per your environment)

Manually Remove Objects from A&AI

For example, here is one of the executions to delete a duplicate entry of a logical-link

ONAP Wiki

ONAP Dublin Troubleshooting