SimplyTest.me is currently throwing an error stating the server is at capacity. This is not accurate and is caused due to the spawning getting stuck at 17%. According to the logs, the instances are actually provisioning properly, it's just not redirecting to the provisioned instances.

The server is clogged because the instances are stuck at "spawned". While the instances are deleted on the infrastructure, deleted instances are not reflected in the web UI and it then thinks its at capacity.

This suggests the state is not being set properly. This can likely be resolved by updating the state within build.sh.

Instances will need manually cleared out (and there seems to be some old servers there we need to clean up). There should also be a Drupal-based patch for CRON that updates any instance to destroyed that has a status of spawned and is after the 12 hour termination.

Comments

nerdstein created an issue. See original summary.

nerdstein’s picture

StatusFileSize
new1.82 KB

Patch for CRON hook that will free up the stalled instances

  • nerdstein committed 17c0869 on 7.x-1.x
    Issue #2951673 by nerdstein: Spawned submissions are clogging SimplyTest...
nerdstein’s picture

SimplyTest spawning should be restored. Fixing the provisioning now.

matsbla’s picture

StatusFileSize
new74.37 KB

It still doesn't work for me, everything stops here;
The submission was spawned.. stop

  • nerdstein committed 9e67cd4 on 7.x-1.x
    Issue #2951673 by nerdstein: Spawned submissions are clogging SimplyTest...
nerdstein’s picture

Status: Active » Needs review

Instances are now spawning. The IP address that was triggering submission state changes was not registered to the server. The commit pushed above fixes this by updating the logic. Instances are now working.

It's not ideal that the IP address is in the commit, so there will be a to do item for this and a force push.

mikemiles86’s picture

The following patch provides a configuration value for setting the IP address for submissions and then uses that while list in the authentication access check for access state from the work server.

I have not tested this patch, but code looks correct.

nerdstein’s picture

Issue tags: +midcamp2018

Reviewed and thank you, Mike!! Merging, rebasing, and force pushing

  • nerdstein committed 987eaa7 on 7.x-1.x authored by mikemiles86
    Issue #2951673 by nerdstein, mikemiles86, matsbla: Spawned submissions...
nerdstein’s picture

Status: Needs review » Fixed

IP address config is now pushed and IP is out of code.

Marking this as fixed - there still needs to be some manual clean up of really old instances that were not destroyed properly, but things are working now.

matsbla’s picture

StatusFileSize
new79.27 KB

It doesn't work when I test with Drupal core, I get an error like this (but it seem to work for other projects);
Drupal core error

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.