Precise kernel post-install fails in grub configuration in EC2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Doing a release-upgrade from oneiric on EC2 (ubuntu cloud official images), with an aufs overlay. EC2 instance is a t1.micro.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.0.0-16-virtual i686
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Mar 2 07:53 seq
crw-rw---T 1 root audio 116, 33 Mar 2 07:53 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 1.93-0ubuntu2
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Fri Mar 2 08:02:29 2012
Ec2AMI: ami-08fd4c09
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: t1.micro
Ec2Kernel: aki-ec5df7ed
Ec2Ramdisk: unavailable
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 2
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
ProcKernelCmdLine: root=LABEL=
ProcModules:
acpiphp 23408 0 - Live 0xe772a000
aufs 159860 345 - Live 0xe7795000
iptable_filter 12706 0 - Live 0xe7724000
ip_tables 18106 1 iptable_filter, Live 0xe7731000
x_tables 21975 2 iptable_
SourcePackage: linux
Title: package linux-image-
UpgradeStatus: Upgraded to precise on 2012-03-02 (1 days ago)
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.
We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following commands in a terminal window:
sudo apt-get update
sudo apt-get upgrade
If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.
If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.
Thank you for your help, we really do appreciate it.