mirroring of mirrored branches being left permanently disabled
Bug #684407 reported by
Michael Barnett
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
We ran into a couple mirrored branches that had their "Next Mirror Time" set to "disabled". Preliminary investigation seems to indicate that the branch was pulled properly, but the scanner failed, which means the next_mirror_time variable was never updated.
Any branch left in this state will be broken (mirroring will be disabled) until someone notices and manually intervenes.
We were able to fix these branches by requesting a mirror through the api, which triggered a new scan, and updated the next_mirror_time.
tags: | added: branch-puller branch-scanner |
tags: | removed: lp-code |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
Probably fallout from the xmlrpc incident 2 weeks back.