siamaksade / openshift-jenkins-demo

CI/CD Demo on OpenShift
http://www.openshift.com
531 stars 930 forks source link

ERROR: role "user1ca2ol5m" does not exist #123

Open nickschuetz opened 5 years ago

nickschuetz commented 5 years ago

On OCP v3.11.88

$ oc get pods
NAME                        READY     STATUS             RESTARTS   AGE
che-2-w5b7w                 1/1       Running            0          7m
cicd-demo-installer-qxbff   0/1       Completed          0          2m
gogs-1-678jk                1/1       Running            5          8m
gogs-postgresql-1-knlgv     1/1       Running            0          8m
jenkins-2-pxfx6             1/1       Running            0          8m
nexus-2-wtvtz               1/1       Running            0          7m
sonardb-1-deploy            1/1       Running            0          8m
sonardb-1-wt4ml             0/1       CrashLoopBackOff   6          8m
sonarqube-1-2d97x           0/1       CrashLoopBackOff   5          7m
sonarqube-1-deploy          1/1       Running            0          8m
$ oc logs sonardb-1-wt4ml
pg_ctl: another server might be running; trying to start server anyway
waiting for server to start....LOG:  redirecting log output to logging collector process
HINT:  Future log output will appear in directory "pg_log".
........... done
server started
=> sourcing /usr/share/container-scripts/postgresql/start/set_passwords.sh ...
ERROR:  role "user1ca2ol5m" does not exist
rbo commented 5 years ago

This work-a-round solved the problem on my env.:

$ oc debug sonardb-2-n9dw8
Defaulting container name to postgresql.
Use 'oc describe pod/sonardb-2-n9dw8-debug -n cicd-rbohne' to see all of the containers in this pod.

Debugging with pod/sonardb-2-n9dw8-debug, original command: container-entrypoint run-postgresql
Waiting for pod to start ...
If you don't see a command prompt, try pressing enter.
sh-4.2$ rm -rf /var/lib/pgsql/data/userdata/^C
sh-4.2$ exit
exit

Removing debug pod ...
$ oc delete pod sonardb-2-n9dw8
pod "sonardb-2-n9dw8" deleted
jairojunior commented 5 years ago

Also had this issue with 3.11.98, but was able to deploy with the workaround above.