Re: [onap-discuss] [PORTAL]: cannot log in after install

David Darbinyan Wed, 19 Sep 2018 10:40:20 -0700

hi Hector

here are steps i did.

1. before starting, result of "helm status portal-19s" ......

==> v1/Pod(related)
NAME                                          READY STATUS      RESTARTS AGE
portal-19s-portal-app-84b789fd9d-hvj9g        2/2    Running     0         22m
portal-19s-portal-cassandra-6d47b4888d-j5hfb 1/1    Running     0         22m
portal-19s-portal-db-58d8bcd74-zxzlr          1/1    Running     1         22m
portal-19s-portal-sdk-86cfcb4f7b-nvmkc        2/2    Running     0         22m
portal-19s-portal-widget-556ddbb9dd-zrrvq     1/1    Running     0         22m
portal-19s-portal-zookeeper-5f46f49c47-jcf8k 1/1    Running     0         22m
portal-19s-portal-db-config-vjbwp             0/2    Init:Error 0         22m
portal-19s-portal-db-config-xm7v4             0/2    Completed   0         11m

2. I removed db-config job from rancher's interface. and re-run with upgrade helm as follow

root@srv11# helm upgrade portal-19s local/portal

3. result of "helm status portal-19s"

==> v1/Pod(related)
NAME                                          READY STATUS     RESTARTS AGE
portal-19s-portal-app-84b789fd9d-hvj9g        2/2    Running    0         26m
portal-19s-portal-cassandra-6d47b4888d-j5hfb 1/1    Running    0         26m
portal-19s-portal-db-58d8bcd74-zxzlr          1/1    Running    1         26m
portal-19s-portal-sdk-86cfcb4f7b-nvmkc        2/2    Running    0         26m
portal-19s-portal-widget-556ddbb9dd-zrrvq     1/1    Running    0         26m
portal-19s-portal-zookeeper-5f46f49c47-jcf8k 1/1    Running    0         26m
portal-19s-portal-db-config-84tbf             0/2    Completed 0         1m

-------------------------

4. now result from pod itself

again., there's no "demo" user in db.

=============================

NOTE!!!!

when I look for helm version from ubuntu's CLI i get.....

root@srv11:~/ONAP/oom/kubernetes# helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

.......................

BUT. when i try same command from Rancher's CLI...

# Run kubectl commands inside here
# e.g. kubectl get all
> helm version
Client: &version.Version{SemVer:"v2.6.1", GitCommit:"bbc1f71dc03afc5f00c6ac84b9308f8ecb4f39ac", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

what is wrong????

regards

David

On 9/12/18 12:13 AM, ANAPAN-LAVALLE, HECTOR A wrote:

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: [email protected] <[email protected]> On Behalf Of David Darbinyan
Sent: Tuesday, September 11, 2018 3:29 AM
To: [email protected]
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.

_._,_._,_

Re: [onap-discuss] [PORTAL]: cannot log in after install

Reply via email to