Need better error message when referring to a non-existant block

[jfischer]

We get a NameError exception without any arguments. When running from within an engage environment, debugging the install is complicated - the master is calling the deployer, which is calling the config engine. We should do some validation that the name in the topology file maps to a valid block.