search

heroku / heroku-releases-retry

CLI plugin to allow retrying the latest release-phase command
81 stars 7 forks source link

retry does not reflect any state change between actively running and completed #9

Closed SampsonCrowley closed 5 years ago

SampsonCrowley commented 5 years ago

I have two rails based apps that share a common code base and database. Both apps had a commit pushed at the same time. The first app had migrations to run. this puts a lock on the database. second app failed release due to db lock. no big deal, just run a retry when first app is done migrating

upon running heroku releases:retry the release is just stuck doing nothing even though there's not actually anything it needs to do to finish the release. viewing the live log shows "release finished" after loading, but the activity log still shows as retrying

Screenshot from 2019-05-07 15-58-19 Screenshot from 2019-05-07 15-58-32 Screenshot from 2019-05-07 15-58-48

dmathieu commented 5 years ago

This isn't an issue with the buildpack, but rather with your release dyno. Please open a support ticket at help.heroku.com instead.

SampsonCrowley commented 5 years ago

While I did in fact misinterpret what should be present in the activity log, as there is nothing wrong with my dyno; the release completed just fine, this buildpack doesn't reflect that state when it reaches it. I honestly don't know how I'm the first person to find this to be ambiguous