Better log reporting in distro upgrade activities
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Server |
Fix Released
|
Medium
|
Free Ekanayaka | ||
landscape-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When a distro upgrade activity fails, the logs that are sent back to landscape don't help much.
For example, this is what I got back when such an activity failed for me:
fetched gpgv:/var/
fetched gpgv:/var/
fetched http://
(...)
fetched bzip2:/
fetched bzip2:/
fetched bzip2:/
Only the /var/log/
root@ip-
2010-01-05 14:07:02,483 INFO Using config files '['./DistUpgrad
2010-01-05 14:07:02,483 INFO release-upgrader version '0.111.8' started
2010-01-05 14:07:23,571 WARNING mirror check skipped, *overriden* via config
2010-01-05 14:07:23,616 INFO fixing components inconsistency from 'deb http://
2010-01-05 14:07:23,617 INFO to new entry 'deb http://
2010-01-05 14:07:23,617 INFO fixing components inconsistency from 'deb http://
2010-01-05 14:07:23,617 INFO to new entry 'deb http://
2010-01-05 14:07:51,161 WARNING No kernel: 'linux-image-xen'
2010-01-05 14:07:51,234 INFO no old nvidia driver installed, installing no new
2010-01-05 14:07:54,812 ERROR Unauthenticated packages found: 'landscape-client landscape-common'
2010-01-05 14:07:54,813 ERROR Error authenticating some packages It was not possible to authenticate some packages. This may be a transient network problem. You may want to try again later. See below for a list of unauthenticated packages. (landscape-client
landscape-common)
2010-01-05 14:07:54,814 ERROR view.abort called
Related branches
- Sidnei da Silva (community): Approve
- Jamu Kakar (community): Approve
-
Diff: 352 lines (+203/-10)5 files modifieddebian/changelog (+6/-0)
landscape/lib/fs.py (+22/-0)
landscape/lib/tests/test_fs.py (+36/-0)
landscape/package/releaseupgrader.py (+40/-3)
landscape/package/tests/test_releaseupgrader.py (+99/-7)
Changed in landscape: | |
milestone: | none → 1.4.5 |
importance: | Undecided → Low |
Changed in landscape: | |
assignee: | nobody → Free Ekanayaka (free.ekanayaka) |
status: | New → In Progress |
milestone: | 1.4.5 → 1.5.0 |
Changed in landscape: | |
status: | In Progress → Fix Committed |
tags: | added: testing |
tags: | removed: testing |
tags: | added: needs-testing |
Changed in landscape: | |
status: | Fix Committed → Fix Released |
visibility: | private → public |
affects: | Ubuntu Jaunty → landscape-client (Ubuntu Jaunty) |
Changed in landscape-client (Ubuntu Lucid): | |
status: | New → Fix Released |
Changed in landscape-client (Ubuntu): | |
status: | New → Fix Released |
tags: | removed: verification-needed |
I just tried another upgrade and it failed. The log attached to the landscape activity doesn't show any problem, but the /var/log/ dist-upgrade/ main.log file on the computer nails it down pretty well:
2010-03-12 15:53:57,631 ERROR Not enough free disk space The upgrade is now aborted. The upgrade needs a total of 37.7M free space on disk '/boot'. Please free at least an additional 19.3M of disk space on '/boot'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'. (None)
I'm raising this to Medium because really, without that main.log output, there is no way to even identify the problem using Landscape.