You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error is: helm upgrade --install \ --atomic --create-namespace --namespace activiti \ -f values.yaml \ activiti charts/activiti-cloud-full-example Release "activiti" does not exist. Installing it now. coalesce.go:220: warning: cannot overwrite table with non table for activiti-cloud-identity.postgresql.ldap.tls (map[]) Error: release activiti failed, and has been uninstalled due to atomic being set: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
Adding debug gets me to this: Deployment is not ready: activiti/activiti-activiti-cloud-connector. 0 out of 1 expected pods are ready
Clearly, there are too many 'activiti' there.
Removing the activiti in the requirements.yaml file fixes the problem.
Where there is: alias: "activiti-, just remove that "activiti-".
The text was updated successfully, but these errors were encountered:
JimBarrows
changed the title
Instructions fail on the install/upgrade step.
Instructions fail on the install/upgrade step due to missing pod.
Feb 23, 2023
JimBarrows
added a commit
to JimBarrows/activiti-cloud-full-chart
that referenced
this issue
Feb 23, 2023
Error is:
helm upgrade --install \ --atomic --create-namespace --namespace activiti \ -f values.yaml \ activiti charts/activiti-cloud-full-example Release "activiti" does not exist. Installing it now. coalesce.go:220: warning: cannot overwrite table with non table for activiti-cloud-identity.postgresql.ldap.tls (map[]) Error: release activiti failed, and has been uninstalled due to atomic being set: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
Adding debug gets me to this:
Deployment is not ready: activiti/activiti-activiti-cloud-connector. 0 out of 1 expected pods are ready
Clearly, there are too many 'activiti' there.
Removing the activiti in the requirements.yaml file fixes the problem.
Where there is:
alias: "activiti-
, just remove that "activiti-".The text was updated successfully, but these errors were encountered: