ORD Pod Crash looping about oracle-database-operator HOT 10 OPEN

Right, this is the correct link

from oracle-database-operator.

Based on the log output you provided above, you are using ORDS 22.2:
.
ORDS: Release 22.2 Production on Thu Sep 08 19:43:10 2022
.
and not the required/supported 21.4.3

from oracle-database-operator.

Gotcha! How would I get/use 21.4.3? I have the zip file for 21.4.3 (downloaded from here: https://www.oracle.com/tools/ords/ords-downloads-2143.html ) in my ords directory and the dockerfile is using that zip. Here is the output of running ls on my ords dir
cdbadmin.properties.tmpl '#Dockerfile#' Dockerfile ords-21.4.3.117.0405.zip ords_params.properties.tmpl runOrds.sh setupwebuser.sh standalone.properties.tmpl

Output from Running kubectl get events -n oracle-database-operator-system
LAST SEEN TYPE REASON OBJECT MESSAGE 34m Normal Pulling pod/cdb-dev-ords-rs-dsk72 Pulling image "__omitted/oracle/ords:21.4.3" 4m11s Warning BackOff pod/cdb-dev-ords-rs-dsk72 Back-off restarting failed container

from oracle-database-operator.

It seems that you have downloaded the wrong ORDS version. DBoperator supports ords 21.4.3 the ; DBoperator with ords 22.2 is on the way

from oracle-database-operator.

Gotcha, I downloaded the ords service from here: https://www.oracle.com/tools/ords/ords-downloads-2143.html . Is there anything else that corresponds to version 21.4.3 ?

from oracle-database-operator.

So thats the ords version I am using with the pod crashlooping. Is there anything else I need to configure.

from oracle-database-operator.

here
You can follow the steps output on making ORDS 21.4.3. I wonder if you see anything different from what you have done?
.
You could drop ords pod: "kubectl delete -f cdb.yaml" and in case retry building the new image as above url

from oracle-database-operator.

So I removed all of my local docker images and re ran all of the steps.
When I run the command
kubectl apply -f config/samples/onpremdb/cdb.yaml
and then
kubectl get cdb.database.oracle.com -A
The output is
NAMESPACE NAME CDB NAME DB SERVER DB PORT SCAN NAME REPLICAS STATUS MESSAGE oracle-database-operator-system cdb-dev devcdb [omitted] 1521 devdb 1 Failed Check DB connection parameters
And the cdb-dev-ords pod terminates pretty quickly.

from oracle-database-operator.

What should the 'Database Server Name' , 'Database Service Name' and 'Scan Name ' be set to. I was also wondering what the difference between the yaml file here and here

from oracle-database-operator.

Make sure to set dbServer: equal to your hostname or scan name if you are using RAC , The parameter scanName: is redundant and is bound to be removed.
To debug this kind of connection issue during installation you can try to get pod log information before it dies
/usr/bin/kubectl logs /usr/bin/kubectl get pods -n oracle-database-operator-system|grep ords|cut -d ' ' -f 1 -n oracle-database-operator-system
or otherwise you can run the ords installation manually by recreating the ords image in this way
sed -i 's/$ORDS_HOME/$RUN_FILE/["/usr/sbin/init"]/g' Dockerfile && docker build -t oracle/ords-dboper:latest .
once you have reloaded the ords image in your registry and redeployed the ords pod connect to the pod and execute the installation script /opt/oracle/ords/runOrds.sh

from oracle-database-operator.