Hi, everyone!
Yesterday morning (around 11AM - Brazil) we started the installation of the following deliveries:
- ‘initial’ delivery (1.0.0) for customer XXX (running on server XXX)
- customization delivery 4.12.0 for customer YYY (running on server YYY)
NOTE: Both customers use IFS Cloud 26R1 (26.1.1)
At the very first execution for customer XXX (delivery 1.0.0) the error below was shown:
[Mon Jul 20 11:46:20 BRT 2026][INSTALLER] - INFO: Installer Action: install
[Mon Jul 20 11:46:20 BRT 2026][INSTALLER] - INFO: Installer Deploy Step: all
[Mon Jul 20 11:46:20 BRT 2026][INSTALLER] - INFO: Installer version: 26.1.1
[Mon Jul 20 11:46:20 BRT 2026][INSTALLER] - INFO: Java: build 11.0.29+7-LTS
[Mon Jul 20 11:46:21 BRT 2026][INSTALLER] - INFO: k8s (client): v1.34.1
[Mon Jul 20 11:46:21 BRT 2026][INSTALLER] - INFO: k8s cluster: https://XXXXX.XXXX.com.br:16443
[Mon Jul 20 11:46:22 BRT 2026][INSTALLER] - INFO: k8s (server): v1.34.1
[Mon Jul 20 11:46:22 BRT 2026][INSTALLER] - INFO: auto scaler: 2.18.0
[Mon Jul 20 11:46:22 BRT 2026][INSTALLER] - INFO: helm: v3.19.0
[Mon Jul 20 11:46:25 BRT 2026][INSTALLER] - SEVERE: Internal error occurred: unable to upgrade connection: pod does not exist
[Mon Jul 20 11:46:26 BRT 2026][INSTALLER] - INFO: No Baseline Delivery ID defined for delivery ifs-cloud-26.1.1-XXXX-1.0.0-20260618T141705Z. Delivery will be installed.
….
[Mon Jul 20 11:47:33 BRT 2026][MTINSTALL] - SEVERE: Failed waiting for helm-job to complete
[Mon Jul 20 11:47:56 BRT 2026][MTINSTALL] - SEVERE: timed out waiting for the condition
[Mon Jul 20 11:47:56 BRT 2026][MTINSTALL] - SEVERE: Failed to install ifs-cloud. Collected logs from command:
INFO: Chart file ifs-cloud-261.1.0.tgz already exists, skipping download
INFO: Using chart ifscloud/ifs-cloud version 261.1.0
INFO: Installing ifs-cloud middle tier
INFO: Deleting job ifs-db-init...
job.batch "ifs-db-init" deleted from XXX01tst namespace
INFO: Deleting job ifsapp-am-scheduler-29742605...
job.batch "ifsapp-am-scheduler-29742605" deleted from XXX01tst namespace
INFO: Running helm upgrade with helm pod enabled: true
INFO: Setting up helm pod environment
Error from server (NotFound): configmaps "ifscloudcharts" not found
Error from server (NotFound): secrets "helmjobvalues" not found
Error from server (NotFound): secrets "tmpregistersecret" not found
Error from server (NotFound): jobs.batch "helm-job" not found
configmap/ifscloudcharts created
secret/helmjobvalues created
secret/tmpregistersecret created
INFO: Running helm pod version 1.1.0.0.0
networkpolicy.networking.k8s.io/egress-helm-job-k8s-api configured
serviceaccount/helm-job unchanged
role.rbac.authorization.k8s.io/helm-job-admin unchanged
rolebinding.rbac.authorization.k8s.io/helm-job-admin unchanged
clusterrole.rbac.authorization.k8s.io/helm-job-cluster-access unchanged
clusterrolebinding.rbac.authorization.k8s.io/helm-job-cluster-access unchanged
job.batch/helm-job created
Error from server (NotFound): jobs.batch "helm-job" not found
SEVERE: Failed waiting for helm-job to complete
error: timed out waiting for the condition
Meanwhile, at the execution of delivery 4.12.0, we got the same error:
[Mon Jul 20 11:54:45 BRT 2026][INSTALLER] - INFO: Installer Action: install
[Mon Jul 20 11:54:45 BRT 2026][INSTALLER] - INFO: Installer Deploy Step: all
[Mon Jul 20 11:54:45 BRT 2026][INSTALLER] - INFO: Installer version: 26.1.1
[Mon Jul 20 11:54:45 BRT 2026][INSTALLER] - INFO: Java: build 11.0.29+7-LTS
[Mon Jul 20 11:54:47 BRT 2026][INSTALLER] - INFO: k8s (client): v1.34.1
[Mon Jul 20 11:54:47 BRT 2026][INSTALLER] - INFO: k8s cluster: https://XXXXXX.com.br:16443
[Mon Jul 20 11:54:48 BRT 2026][INSTALLER] - INFO: k8s (server): v1.34.1
[Mon Jul 20 11:54:48 BRT 2026][INSTALLER] - INFO: helm: v3.19.0
[Mon Jul 20 11:54:48 BRT 2026][INSTALLER] - INFO: auto scaler: 2.16.1
[Mon Jul 20 11:54:51 BRT 2026][INSTALLER] - SEVERE: Internal error occurred: unable to upgrade connection: pod does not exist
[Mon Jul 20 11:54:53 BRT 2026][INSTALLER] - INFO: Delivery ifs-cloud-26.1.1-XXXXXX-4.12.0-20260719T211827Z will be re-installed.
…
[Mon Jul 20 11:56:49 BRT 2026][MTINSTALL] - SEVERE: Failed waiting for helm-job to complete
[Mon Jul 20 11:57:12 BRT 2026][MTINSTALL] - SEVERE: timed out waiting for the condition
[Mon Jul 20 11:57:12 BRT 2026][MTINSTALL] - SEVERE: Failed to install ifs-cloud. Collected logs from command:
INFO: Chart file ifs-cloud-261.1.0.tgz already exists, skipping download
INFO: Using chart ifscloud/ifs-cloud version 261.1.0
INFO: Installing ifs-cloud middle tier
INFO: Deleting job ifs-db-init...
job.batch "ifs-db-init" deleted from XXX02tst namespace
INFO: Deleting job ifsapp-am-scheduler-29742605...
job.batch "ifsapp-am-scheduler-29742605" deleted from XXX02tst namespace
INFO: Running helm upgrade with helm pod enabled: true
INFO: Setting up helm pod environment
Error from server (NotFound): configmaps "ifscloudcharts" not found
Error from server (NotFound): secrets "helmjobvalues" not found
Error from server (NotFound): secrets "tmpregistersecret" not found
Error from server (NotFound): jobs.batch "helm-job" not found
configmap/ifscloudcharts created
secret/helmjobvalues created
secret/tmpregistersecret created
INFO: Running helm pod version 1.1.0.0.0
networkpolicy.networking.k8s.io/egress-helm-job-k8s-api configured
serviceaccount/helm-job unchanged
role.rbac.authorization.k8s.io/helm-job-admin unchanged
rolebinding.rbac.authorization.k8s.io/helm-job-admin unchanged
clusterrole.rbac.authorization.k8s.io/helm-job-cluster-access unchanged
clusterrolebinding.rbac.authorization.k8s.io/helm-job-cluster-access unchanged
job.batch/helm-job created
Error from server (NotFound): jobs.batch "helm-job" not found
SEVERE: Failed waiting for helm-job to complete
error: timed out waiting for the condition
After these errors, the only pods remaining was db-init and am-scheduler, but we couldn’t describe or access the log from neither of them. Both systems were broken and we’re unable to fix it… We even tried to delete de namespace so we could try to create them again, but the operation got stuck.…
Today, we decided to restore the previous image of each IFS server (from when they were OK) and executed the same deliveries again… and it worked. :\
I believe it had something to do with the repository or something like that, but I’m not sure… Can anyone tell me what happened? As I’ve said above, each IFS runs in a completely separated infrastructure, the delivery was completely different besides IFS version…
Regards,
Elaine Berenguer
