I see cases where the build ppas are not cleaned. The API was being called by the lander_ppa_free job calls: Calling via PATCH [http://10.55.32.150:8080/api/v1/ppa/1/]: {'state': 'dirty'}
The ppa-cleaner upstart log showed:
INFO:root:populating ppa model from: https://api.launchpad.net/1.0/~fginther/ppas
ESC[31;1mOperationalError: unable to open database file
Status of service:
$ curl http://10.55.32.150:8080/api/v1/ppa/{"meta": {"limit": 20, "next": null, "offset": 0, "previous": null, "total_count": 2}, "objects": [{"id": 1, "name": "ppa:fginther/ci-pool-001", "resource_uri": "/api/v1/ppa/1/", "state": 20, "ticket_id": 1, "timestamp": "2014-02-26T20:18:58.010577"}, {"id": 2, "name": "ppa:fginther/ci-pool-002", "resource_uri": "/api/v1/ppa/2/", "state": 20, "ticket_id": 1, "timestamp": "2014-02-26T20:44:01.642353"}]}
The upstart job was not running, after starting it with "sudo start ppa-cleaner", the status soon went to:
$ curl http://10.55.32.150:8080/api/v1/ppa/{"meta": {"limit": 20, "next": null, "offset": 0, "previous": null, "total_count": 2}, "objects": [{"id": 1, "name": "ppa:fginther/ci-pool-001", "resource_uri": "/api/v1/ppa/1/", "state": 30, "ticket_id": 1, "timestamp": "2014-02-26T21:48:25.595955"}, {"id": 2, "name": "ppa:fginther/ci-pool-002", "resource_uri": "/api/v1/ppa/2/", "state": 30, "ticket_id": 1, "timestamp": "2014-02-26T21:48:58.883521"}]}f
you can work around this right now, by doing
juju ssh ppa-django/0 sudo restart ppa-cleaner
i need to do some charm debugging