Please read
You'll also have to rebuild the middletier with mtinstaller, not just start it. Before that, check your ifscloud-values.yaml . The DB name of a cloned DB is probably something else, that's why your DB-init is failing.
Thank you for your answer.
i cheched the ifs-values.yaml. it seems to be Okay. in the logs the database connection is successful.
and then i run : .\installer.cmd --set action=mtinstaller --values .config\ifscloud-values.yaml.
it doesn’t work. i still have the pods ifs-db-init and and ifsapp-odata in an error status.
Thank you
What does the installer log say?
You can also fetch pod logs with kubectl, it often tells you what is wrong.
we followed the procedure that you sent :
- on dev env: Backup database
- on staging env : export tables & clone dev database & import the tables
and i tried to re-install .\installer.cmd --set action=mtinstaller --values .config\ifscloud-values.yaml.
i have this error :
Installing ifs-cloud
INFO: Running helm upgrade
SEVERE: UPGRADE FAILED: post-upgrade hooks failed: 1 error occurred:
SEVERE: Failed to install ifs-cloud
INFO: ifs-db-init log:
Container initiated at Fri Jul 26 15:36:42 UTC 2024
SECRETIMAGE_VERSION=Mon Oct 23 04:26:17 UTC 2023 1.0.6
ALPINE_VERSION=Mon Oct 23 04:26:17 UTC 2023 3.18.3
BASEIMAGE_VERSION=Mon Oct 23 04:26:17 UTC 2023 1.0.51
CERTIFICATE_HANDLER_VERSION=Mon Oct 23 04:28:12 UTC 2023 1.0.8
JAVAIMAGE_VERSION=Mon Oct 23 04:28:12 UTC 2023 1.0.61
DRIVER_VERSION=Mon Oct 23 06:24:15 UTC 2023 23.1.7.0.0
DBINITIMAGE_VERSION=Mon Oct 23 06:24:15 UTC 2023 23.1.7.0.0
No certificates are loaded for database-certs ..
No certificates are loaded for ifs-db-init-certs ..
Failed updating database. ORA-28000: The account is locked..
Failing updating, check credentials
thank you.
ORA-28000: The account is locked..
So you'll have to figure out which account (probably ifsapp) and open it from Oracle.
Also, why is helm upgrade failing? Are you blocking outgoing traffic so that it can't get the updates?
we update the ifssys and ifsapp account and open it from oracle. We also unlocked these account.
then i tried :
.\installer.cmd --set action=delete --values ..\..\..\config\ifscloud-values.yaml
and
.\installer.cmd --set action=mtinstaller --values .config\ifscloud-values.yaml.
i have this error :
>debug] creating 172 resource(s)
client.go:478: 7debug] Starting delete for "ifs-db-init" Job
client.go:482: 8debug] Ignoring delete failure for "ifs-db-init" batch/v1, Kind=Job: jobs.batch "ifs-db-init" not found
client.go:134: 3debug] creating 1 resource(s)
client.go:707: 0debug] Watching for changes to Job ifs-db-init with timeout of 15m0s
client.go:735: 3debug] Add/Modify event for ifs-db-init: ADDED
client.go:774: 7debug] ifs-db-init: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:735: 3debug] Add/Modify event for ifs-db-init: MODIFIED
client.go:774: 7debug] ifs-db-init: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:735: 3debug] Add/Modify event for ifs-db-init: MODIFIED
client.go:774: 7debug] ifs-db-init: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:735: 3debug] Add/Modify event for ifs-db-init: MODIFIED
client.go:774: 7debug] ifs-db-init: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:735: 3debug] Add/Modify event for ifs-db-init: MODIFIED
Error: failed post-install: 1 error occurred:
* job failed: BackoffLimitExceeded
helm.go:84: .debug] failed post-install: 1 error occurred:
* job failed: BackoffLimitExceeded
SEVERE: Failed to install ifs-cloud
and during installation, the account IFSYS becomes locked
No we are not blocking outgoing traffic. the installation was done correctly before database clone.
Thank you
my bad, i put a wrong ifssys
it seems to be Okay after ifssys password update.
Thanks for you help
Hello @Samil,
all the pods are running 2 /2 and OK after db clone except this one.
ifsapp-amm 1/2 Running
Have you any ideas?
Thank You,
Bests
hello @SamiL,
the pod ifsapp-amm is healthy and running without any changes.
i think it take time for the depoyment
Thank you