staging update left bzr tree out of date with branch
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
launchpad@
9738
launchpad@
#!/usr/bin/env python
"""This file is automatically generated by generate_
It uses the current working tree to determine the revision.
So don't edit it. :)
"""
version_info = {'branch_nick': u'launchpad',
'build_date': '2010-09-02 23:29:04 +0000',
'clean': None,
'date': '2010-08-27 19:49:22 +0100',
'revision_id': '<email address hidden>',
'revno': 9710}
revisions = {}
file_revisions = {}
if __name__ == '__main__':
print 'revision: %(revno)d' % version_info
print 'nick: %(branch_nick)s' % version_info
print 'revision id: %(revision_id)s' % version_info
=========
$ bzr --version
Bazaar (bzr) 2.2.0
Python interpreter: /usr/bin/python 2.6.5
Python standard library: /usr/lib/python2.6
Platform: Linux-2.
bzrlib: /usr/lib/
Bazaar configuration: /home/launchpad
Bazaar log file: /home/launchpad
=========
launchpad@
Skipping bzr-version-info.py update; already at revno 9710
| Changed in launchpad-foundations: | |
| importance: | Undecided → Critical |
| tags: | added: canonical-losa-lp |
| Robert Collins (lifeless) wrote | #1 |
| summary: |
- staging update is showing incorrect version in the html/page footer + staging update left bzr tree out of date with branch |
| Changed in launchpad-foundations: | |
| importance: | Critical → High |
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | High → Low |
| Changed in launchpad: | |
| status: | Triaged → Fix Released |
So, sodium's master tree that gets rsynced from A to B,C,D etc had this issue:
14:47 < spm> launchpad@
14:47 < spm> bzr: ERROR: This tree contains left-over files from a failed operation.
14:47 < spm> Please examine /srv/staging.
14:47 < spm> keep, and delete it when you are done.
1
There are some issues here:
- sodium, el crasho
- the staging update process did not detect that this issue existed.
- there is so much cronspam noise that the issue (if reported in cron errors) was not observed by anyone (and I would be getting those mails too: this isn't a criticism of anyone).
Dropping to high as we've figured the problem and can resolve. I will update the RT about sodium too, pointing out that it can break prod and staging rollouts.