Exstream Cloud Native Installation on Kubernetes

IMEX Support

Hi There,

Is there an posts that describes Exstreal Cloud Native Installation with Kubernetes servers.

I got many issues with that

Kasper Rasmussen

I dont think there are any official step-by-step guides other than the installation and configuration guides.
If there are it would be nice to know about.

What environment are you running k8s on?

Ganesh Dhanawde

Hi @IMEX Support / @Kasper Rasmussen ,

We are trying to install Exstream CE 24.2. We are using below command

helm install "exstream" "Path of exstream-24.2.16-55862.tgz" --wait --timeout 30m0s --set otds.bootstrap.license.enabled=true --set-file otds.bootstrap.license.nonprod="Path of lic file"  -f "Path of yaml file" --debug

This installation is getting stopped after a 30 min timeout. Below are debug logs -

client.go:486: 2024-11-13 12:56:20.4128907 +0530 IST m=+2.711765101 [debug] Starting delete for "exstream-dasdb-secret-pre" Secret
client.go:490: 2024-11-13 12:56:20.4278291 +0530 IST m=+2.726703501 [debug] Ignoring delete failure for "exstream-dasdb-secret-pre" /v1, Kind=Secret: secrets "exstream-dasdb-secret-pre" not found
wait.go:104: 2024-11-13 12:56:20.4278291 +0530 IST m=+2.726703501 [debug] beginning wait for 1 resources to be deleted with timeout of 30m0s
client.go:142: 2024-11-13 12:56:20.6382085 +0530 IST m=+2.937082901 [debug] creating 1 resource(s)
client.go:486: 2024-11-13 12:56:20.6638663 +0530 IST m=+2.962740701 [debug] Starting delete for "exstream-design-config-pre" ConfigMap
client.go:490: 2024-11-13 12:56:20.6748583 +0530 IST m=+2.973732701 [debug] Ignoring delete failure for "exstream-design-config-pre" /v1, Kind=ConfigMap: configmaps "exstream-design-config-pre" not found
wait.go:104: 2024-11-13 12:56:20.6758195 +0530 IST m=+2.974693901 [debug] beginning wait for 1 resources to be deleted with timeout of 30m0s
client.go:142: 2024-11-13 12:56:20.9766717 +0530 IST m=+3.275546101 [debug] creating 1 resource(s)
client.go:486: 2024-11-13 12:56:21.0163108 +0530 IST m=+3.315185201 [debug] Starting delete for "exstream-keys-secret-pre" Secret
client.go:490: 2024-11-13 12:56:21.0213113 +0530 IST m=+3.320185701 [debug] Ignoring delete failure for "exstream-keys-secret-pre" /v1, Kind=Secret: secrets "exstream-keys-secret-pre" not found
wait.go:104: 2024-11-13 12:56:21.0213113 +0530 IST m=+3.320185701 [debug] beginning wait for 1 resources to be deleted with timeout of 30m0s
client.go:142: 2024-11-13 12:56:21.1917759 +0530 IST m=+3.490650301 [debug] creating 1 resource(s)
client.go:486: 2024-11-13 12:56:21.2172655 +0530 IST m=+3.516139901 [debug] Starting delete for "exstream-orcdb-secret-pre" Secret
client.go:490: 2024-11-13 12:56:21.2248293 +0530 IST m=+3.523703701 [debug] Ignoring delete failure for "exstream-orcdb-secret-pre" /v1, Kind=Secret: secrets "exstream-orcdb-secret-pre" not found
wait.go:104: 2024-11-13 12:56:21.2248293 +0530 IST m=+3.523703701 [debug] beginning wait for 1 resources to be deleted with timeout of 30m0s
client.go:142: 2024-11-13 12:56:21.5465834 +0530 IST m=+3.845457801 [debug] creating 1 resource(s)
client.go:486: 2024-11-13 12:56:21.5704543 +0530 IST m=+3.869328701 [debug] Starting delete for "exstream-orchestration-config-pre" ConfigMap
client.go:490: 2024-11-13 12:56:21.5872588 +0530 IST m=+3.886133201 [debug] Ignoring delete failure for "exstream-orchestration-config-pre" /v1, Kind=ConfigMap: configmaps "exstream-orchestration-config-pre" not found
wait.go:104: 2024-11-13 12:56:21.5872588 +0530 IST m=+3.886133201 [debug] beginning wait for 1 resources to be deleted with timeout of 30m0s
client.go:142: 2024-11-13 12:56:21.8749755 +0530 IST m=+4.173849901 [debug] creating 1 resource(s)
client.go:486: 2024-11-13 12:56:21.9122096 +0530 IST m=+4.211084001 [debug] Starting delete for "exstream-rabbitmq-ha-pre" Secret
client.go:490: 2024-11-13 12:56:21.923242 +0530 IST m=+4.222116401 [debug] Ignoring delete failure for "exstream-rabbitmq-ha-pre" /v1, Kind=Secret: secrets "exstream-rabbitmq-ha-pre" not found
wait.go:104: 2024-11-13 12:56:21.9262433 +0530 IST m=+4.225117701 [debug] beginning wait for 1 resources to be deleted with timeout of 30m0s
client.go:142: 2024-11-13 12:56:22.2634513 +0530 IST m=+4.562325701 [debug] creating 1 resource(s)
client.go:486: 2024-11-13 12:56:22.2995564 +0530 IST m=+4.598430801 [debug] Starting delete for "exstream-design-schema-job" Job
client.go:490: 2024-11-13 12:56:22.313133 +0530 IST m=+4.612007401 [debug] Ignoring delete failure for "exstream-design-schema-job" batch/v1, Kind=Job: jobs.batch "exstream-design-schema-job" not found
wait.go:104: 2024-11-13 12:56:22.3148139 +0530 IST m=+4.613688301 [debug] beginning wait for 1 resources to be deleted with timeout of 30m0s
client.go:142: 2024-11-13 12:56:22.5098887 +0530 IST m=+4.808763101 [debug] creating 1 resource(s)
client.go:712: 2024-11-13 12:56:22.5388448 +0530 IST m=+4.837719201 [debug] Watching for changes to Job exstream-design-schema-job with timeout of 30m0s
client.go:740: 2024-11-13 12:56:22.5901634 +0530 IST m=+4.889037801 [debug] Add/Modify event for exstream-design-schema-job: ADDED
client.go:779: 2024-11-13 12:56:22.5945832 +0530 IST m=+4.893457601 [debug] exstream-design-schema-job: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:740: 2024-11-13 12:56:22.6484054 +0530 IST m=+4.947279801 [debug] Add/Modify event for exstream-design-schema-job: MODIFIED
client.go:779: 2024-11-13 12:56:22.6494034 +0530 IST m=+4.948277801 [debug] exstream-design-schema-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:740: 2024-11-13 13:05:55.5810075 +0530 IST m=+577.879881901 [debug] Add/Modify event for exstream-design-schema-job: MODIFIED
client.go:779: 2024-11-13 13:05:55.5815701 +0530 IST m=+577.880444501 [debug] exstream-design-schema-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:740: 2024-11-13 13:13:42.9130177 +0530 IST m=+1045.211892101 [debug] Add/Modify event for exstream-design-schema-job: MODIFIED
client.go:779: 2024-11-13 13:13:42.9138134 +0530 IST m=+1045.212687801 [debug] exstream-design-schema-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:740: 2024-11-13 13:16:24.8374896 +0530 IST m=+1207.136364001 [debug] Add/Modify event for exstream-design-schema-job: MODIFIED
client.go:779: 2024-11-13 13:16:24.8375906 +0530 IST m=+1207.136465001 [debug] exstream-design-schema-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:740: 2024-11-13 13:16:24.9013627 +0530 IST m=+1207.200237101 [debug] Add/Modify event for exstream-design-schema-job: MODIFIED
client.go:779: 2024-11-13 13:16:24.9023574 +0530 IST m=+1207.201231801 [debug] exstream-design-schema-job: Jobs active: 1, jobs failed: 1, jobs succeeded: 0
Error: INSTALLATION FAILED: failed pre-install: 1 error occurred:
* timed out waiting for the condition

helm.go:86: 2024-11-13 13:26:22.5944096 +0530 IST m=+1804.893284001 [debug] failed pre-install: 1 error occurred:
* timed out waiting for the condition

INSTALLATION FAILED
main.newInstallCmd.func2
helm.sh/helm/v3/cmd/helm/install.go:158
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.8.1/command.go:985
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.8.1/command.go:1117
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.8.1/command.go:1041
main.main
helm.sh/helm/v3/cmd/helm/helm.go:85
runtime.main
runtime/proc.go:271
runtime.goexit
runtime/asm_amd64.s:1695

Also PFA, YAML file we are trying.

test.txt

Please suggest if anything is wrong here. We are trying to use Auto Schema Management

Kasper Rasmussen

My intuition would be to look at the database connection.
If you are able to access and if you have permissions. Are you using the internal exstreamdb?
If you are hard stuck, then try manual schema management.

Venkata Xpression

i would like to learn open text exstream cloud, please suggest the documents

Ganesh Dhanawde

https://forums.opentext.com/forums/developer/discussion/comment/969870#Comment_969870

Thanks @Kasper Rasmussen for your prompt response! We have checked DB Connection, it is proper. Earlier we have tried using Internal ExstreamDB and no outside DB, that was also getting stucked at same step.

The above error messages which we mentioned, are with 'No Internal DB' & 'Auto Manage 'true'

Then we also tried 'No Internal DB' & 'Auto Manage' - 'false' (Manual Schema)

Here, we are getting stucked with below line -

ready.go:303: 2024-11-19 13:57:11.3639208 +0530 IST m=+1803.093365301 [debug] Deployment is not ready: default/exstream-batch. 0 out of 1 expected pods are ready

(In Manual Schema, we have seen only 2 tables added - databasechangelog, databasechangeloglock - Is this normal?)

Kasper Rasmussen

The database should contain more than just those two tables.
So the auto schema mgmt apparently isn't working. When running the Liquibase scripts it will say what it's adding to the database, and it will make a lot of changes :)

I see you've called your dasdb.externalDb.schema = 'public'. The same for your orcdb.externalDb.schema. You should consider renaming those.

You'd wanna run the liquibase scripts for each of your schemas (exd_system, exd_tenant, exo_system, exo_tenant)
add your exd_system and exo_system in this values.yaml and the exd_tenant and exo_tenant in the bootstrap.

hope that helps

Kasper Rasmussen

But also 24.2 has given me some issues, so be aware that the liquibase scripts are run correctly :)

Ganesh Dhanawde

https://forums.opentext.com/forums/developer/discussion/comment/969886#Comment_969886

Thanks for your response.. let me do this and confirm

Venkata Xpression

I would like to learn exstream cloud native, please help any one, i am open text xpression developer.

+919986546246