Uh, Houston, we've had a problem:

One or more blueprints promised a new resource, but failed when allocating: [PhutilAggregateException] All blueprints failed to allocate a suitable new resource when trying to allocate lease ("PHID-DRYL-7bvtnllfkursoigqa4ea").
- PhutilAggregateException: Unable to allocate any binding as a resource.
- DrydockSlotLockException: Unable to acquire slot locks: "almanac.host.binding(PHID-ABND-d546gmbq7ajyidyi6hcf)" (owned by "PHID-DRYR-f4guzy2xnotw6thi67mf").

https://gitpull.it/drydock/lease/140/

Uhm. It seems that my PhutilAggregateException (Unable to allocate any binding as a resource.) means that you cannot have two Host Blueprints pointing to the same Almanac Service.

And the Google search for that raises 7 results:

This Task is one of these results, and the others are mirrors of the official source-code related to the AlmanacService, so I'm officially the first human exploring this cute exception.

Having said that.

This is somehow confusing to me because the credentials are something Blueprint-related and so it may have sense to have different Blueprints using the same resources (for example to initialize different separate SSH connections).

I've made a cute schema to explain my concerns:

Original Dia file:

SVG:

Let's share some thoughts with upstream to learn more about this interesting part.