Thank you Ed for understanding. And the practice to deploy prod releases makes total sense and definitely a good practice to follow.
Just an FYI we have recently deployed prod that should have created a prod release that you can use for deploy.
1 Like
Hi Amit, I deployed again and am still experiencing similar issues to before unfortunately. I deployed 8dd3e5b. The first deploy produced this error during the DB migrations:
"elasticsearch5.exceptions.ConnectionTimeout: ConnectionTimeout caused by - ReadTimeoutError(HTTPConnectionPool(host='10.3.0.4', port=9200): Read timed out. (read timeout=30))"]}"
As with previous attempts, the ES service health was red after the initial deploy attempt. A restart, fixes that, then a follow-up deploy of the same produced this error:
"elasticsearch5.exceptions.RequestError: TransportError(400, 'index_already_exists_exception', 'index [apps-2024-05-09/AjntXg-CSPy-JLHs4v-Y3Q] already exists')"
Thanks