Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy Not Completing #986

Open
davidsmejia opened this issue Mar 6, 2023 · 3 comments
Open

Deploy Not Completing #986

davidsmejia opened this issue Mar 6, 2023 · 3 comments
Assignees

Comments

@davidsmejia
Copy link
Contributor

Context

Recently ran a deploy to production to verify if cron jobs were being correctly initiated on deploy and confirmed they are not.
This is most likely due to the api-server-instance-user-data.tpl.sh script not completing or errorring out at some point during execution. Additionally the api docker image did not start on deploy.

In order to manually fix:

  • sudo docker remove resources_portal_api
  • sudo ./start_api_with_migrations.sh
  • manually add back the cron jobs defined at the bottom of api-server-instance-user-data.sh

Solution or next step

  • Determine if the api-server-instance-user-data script is indeed erroring out and where
  • apply a fix and redeploy
@davidsmejia
Copy link
Contributor Author

This issue is currently happening on staging though now it is erroring out at around apt update.

@arkid15r
Copy link
Contributor

arkid15r commented Jun 7, 2023

After inspecting the logs I came to a conclusion that the issue could be caused by a transient network error (Network is unreachable) or/and deb package mirrors error (Connection refused, Service Unavailable). This resulted in an incomplete package installation making awscli and certbot unavailable.

I ran the following commands to return the box into a usable state:

rm /var/log/cloud-init.log \
&& rm -rf /var/lib/cloud/* \
&& cloud-init -d init \
&& cloud-init -d modules --mode final

@arkid15r
Copy link
Contributor

arkid15r commented Jun 8, 2023

In order to get this closed we need to make sure the deploy process works fine. To do that the 1password issue needs to be resolved first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants