Hi Gulsum,

After investigating a similar issue on Integration-SB-05, it looks like the 
issue is not caused by the warning that " IP address '10.42.0.1' could not be 
resolved" and it is possibly that the database was never instantiated correctly.

One way to check this would be to enter the 
'/dockerdata-nfs/dev-dmaap/dmaap/dr-db/data' directory and check if a 
datarouter directory exists here.
If it doesn't, the database was not created so the datarouter-prov container 
could not be created.

A workaround for this would be to 

Enter the dmaap-dr-db pod and run the following commands to create the database:
To enter the mysql server on the pod:
        mysql -u root

Once there run the following SQL statements:

SET PASSWORD FOR 'root'@'localhost' = PASSWORD('datarouter');

GRANT ALL ON *.* TO 'root'@'localhost' WITH GRANT OPTION;

CREATE USER datarouter;

SET PASSWORD FOR 'datarouter' = PASSWORD('datarouter');

CREATE database datarouter;

GRANT ALL ON `datarouter`.* TO 'datarouter';

Regards,
Conor Ward

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14590): https://lists.onap.org/g/onap-discuss/message/14590
Mute This Topic: https://lists.onap.org/mt/27483391/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to