Hi David,

The first rule of thumb to make sure your pods are healthy is to see that all 
the containers inside each pod are in “ready” or “green” state as below:

root@rancher:~# kubectl get pods -a --namespace=onap | grep portal
dev-portal-app-fb6fd5f84-8s49f                 2/2       Running     0          
16m
dev-portal-cassandra-5d6649dfb6-fxngd          1/1       Running     0          
15d
dev-portal-db-56bdf48468-ftwq6                 1/1       Running     0          
33m
dev-portal-db-config-9z5md                     0/2       Completed   0          
6d
dev-portal-sdk-f4d454ddc-h57br                 2/2       Running     0          
15d
dev-portal-widget-55b4d88875-29n28             1/1       Running     0          
15d
dev-portal-zookeeper-f649b6d49-d7dql           1/1       Running     0          
15d

The only pods that are okay to see containers in not ready state are the pods 
triggered by kubernetes jobs. In the case above, it’s the 
“dev-portal-db-config-9z5md” pod which as you can see is in “completed” state. 
This means that the job’s finite set of actions was successfully completed.

If you are meeting the conditions above but still getting the invalid 
username/password error, please check the following:


  *   Login to the portal-db (not the portal-db-config) pod, enter the mysql 
console (“mysql -u root -p” where password is Aa123456), and check if the demo 
user is in the fn_user table (USE portal; SELECT first_name, org_user_id, email 
FROM fn_user) where “org_user_id” is the column that lists the login usernames 
to access the portal GUI.



  *   If demo user is not in the table above, then the job didn’t complete 
correctly. Please delete the job, and re-run the helm release with helm upgrade.



  *   If demo user is already there, then please delete the “portal-app” pod 
and wait for all its pods to be in ready state again.

Please let me know your findings.


From: onap-discuss@lists.onap.org <onap-discuss@lists.onap.org> On Behalf Of 
David Darbinyan
Sent: Tuesday, September 11, 2018 3:29 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [PORTAL]: cannot log in after install


hi list!

using Rancher+Kubernetes

I can successfully reach to ONAP login interface, but demo/demo123456! gives me 
"Invalid username or password. Please try again."

Presently i use only [ portal ], [ multicloud ], [ so ].

with this setup all my Pods are in "green" state except of "portal-db-config"



Should any other pod be installed for logging in ? Or may be the demo user 
reseted manually ???



Thanks

DD




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

View/Reply Online (#12390): https://lists.onap.org/g/onap-discuss/message/12390
Mute This Topic: https://lists.onap.org/mt/25511078/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to