/var/log/installer/initial-status.gz is empty on server installs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
installation-report (Ubuntu) |
Fix Released
|
Undecided
|
Colin Watson | ||
Hardy |
Fix Released
|
Low
|
Colin Watson |
Bug Description
Binary package hint: installation-report
Example:
# ls /var/log/
-rw-r--r-- 1 root root 0 2009-03-02 12:02 /var/log/
I get similar results on Hardy and Intrepid, i386 and amd64.
This is an issue for the installer team because that file exists specifically to help us debug certain kinds of problems; we'd like to get this fixed to increase our odds of getting useful debugging output.
This was fixed in installation-report version 2.38ubuntu2 in Jaunty. http://
TEST CASE: Perform an installation with the alternate or server installer; check whether /var/log/
REGRESSION POTENTIAL: I can't think of any way that this could go wrong, other than the original bug persisting. The command in question is already failing as it stands, and the failure is being ignored, so it isn't going to cause an installation failure or anything.
Changed in installation-report: | |
assignee: | nobody → cjwatson |
importance: | Undecided → Low |
milestone: | none → ubuntu-8.04.3 |
status: | New → Triaged |
assignee: | nobody → cjwatson |
description: | updated |
Changed in installation-report (Ubuntu Hardy): | |
status: | Triaged → In Progress |
This bug was fixed in the package installation-report - 2.38ubuntu2
---------------
installation-report (2.38ubuntu2) jaunty; urgency=low
* Run gzip chrooted to /target rather than in the installer environment,
since busybox-udeb isn't configured with gzip support, only gunzip
(LP: #337276).
-- Colin Watson <email address hidden> Tue, 03 Mar 2009 15:50:36 +0000