Bug: Crash if FMS License not valid , cannot start new deployments

Had an issue recently where the FMS license on our dev server had expired. After trying to run a deployment to a clients staging server, the deployment crashed apparently due to this reason.

After that, OttoFMS was inaccessible via browser on client machine, and a manual restart of the service was required. The error given when starting the deployment was a 500 error saying a deployment was already in progress.

After service restart, it showed the last deployment crashed.
Attached is the detailed log of that deployment.

Also noted we use slack notifications and after restart of service we got the slack notification attached (note just a small bug with the merge data in the post.

Screenshot 2024-05-24 at 12.25.26 PM

Thanks for the report.

That expired license thing is a pain in the butt. It shuts off the admin API. We probably should check if the license is expired before we do anything.

We’ll get that slack bug fixed.



1 Like