500 error during TPAAS for some charms
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charmrunner |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I can't seem to find anything in common with the requests at the moment, wanted to start this bug to track the issue.
INFO:werkzeug:
ERROR:werkzeug:
Traceback (most recent call last):
File "/usr/local/
execute(app)
File "/usr/local/
application
File "/home/
return self.wsgi_
File "/home/
response = self.dispatch_
File "/home/
result = getattr(self, "on_%s" % endpoint)(request, **values)
File "/home/
plan = next(plan_iter)
StopIteration
This has been checked against upstream lp:charmrunner, though the branch producing these errors is lp:~marcoceppi/charmrunner/add-server
Related branches
- Juju-Jitsu Hackers: Pending requested
-
Diff: 42 lines (+4/-3)2 files modifiedcharmrunner/graph.py (+2/-2)
charmrunner/server.py (+2/-1)
Changed in charmrunner: | |
status: | New → Fix Released |
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 controller
drupal6
mumble-server
nagios
nova-cloud-
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.