librarian failures cause poimport to mark imports as failed (rather than waiting a while and retrying)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
When librarian is down, poimport script fails with a backtrace like:
2008-04-28 13:22:07 ERROR Got an unexpected exception while importing Lao (lo) translation of sw-frmdlg in Ubuntu Hardy package "openoffice.org"
Traceback (most recent call last):
File "/srv/launchpad
(mail_subject, mail_body) = (
File "/srv/launchpad
import_file = librarian_
File "/srv/launchpad
return _File(urllib2.
File "/usr/lib/
return _opener.open(url, data)
File "/usr/lib/
response = meth(req, response)
File "/usr/lib/
response = self.parent.error(
File "/usr/lib/
return self._call_
File "/usr/lib/
result = func(*args)
File "/usr/lib/
raise HTTPError(
HTTPError: HTTP Error 502: Bad Gateway
This produces that we set the status of that import to 'FAILED'. Instead, given that no imports will success with Librarian being down, we should stop the script so it can resume its work in a future execution once Librarian is back to normality.
Changed in rosetta: | |
status: | New → Confirmed |
Changed in rosetta: | |
importance: | Undecided → Medium |
visibility: | private → public |
Changed in launchpad: | |
importance: | Medium → High |
summary: |
- Don't set imports as FAILED if librarian is unavailable + librarian failures cause poimport to mark imports as failed (rather than + waiting a while and retrying) |