Comment 1 for bug 1168093

I was able to resolve the majority of the 500 errors by changing the way <revno> was picked up from the URL. Instead of using the <charm>-<revno> format I switched my branch to use <charm>:<revno>. Subordinates also throw a 500 error but this is probably to be expected given their nature. A few other charms that don't meet those two criteria which are still producing 500 errors are listed below:

glance
drupal6
mumble-server
nagios
nova-cloud-controller
nova-compute
postgresql
tomcat7

I'm not worried about the OpenStack charms, as graph testing those are burdensome for charmtester, but the rest should be able to generate plans. I'll dig deeper to see if I can find a common reason why these fail to build test plans.