instance had only post-shutdown console output

[Scott Moser]

An instance started in iso testing for alpha-1 did not have console output available:

RESERVATION r-d87ec0af 950047163771 default
INSTANCE i-78f57d0f ami-53321827 pending ec2-keypair.eu-west-1 0 m1.small 2010-06-02T00:43:58+0000 eu-west-1a aki-c35e74b7 monitoring-disabled ebs

The instance was reachable via ssh, and generally functional (passed tests run on the instance for the ud-simple-01 user data test).

The test waited for 240 seconds trying to collect console output for this instance. That is after other tests have been run, and the other instances have had their console output collected (here 5 other instances)

this was an ebs instance. In the EBS tests:
a.) instance is booted
b.) tests are run
c.) console data is collected (retrying and delaying for up to 240 seconds per instance)
d.) instance is shut down
e.) console data is collected
f.) instance is started
g.) console data is collected

The consoles in both e and g did contain data. What is particularly interesting here, is that 'e' contained only data *after* shutdown was issued. Normally , that would contain all messages to the console for the instance.

I will attach the console logs here.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-ec2 2.6.32.305.6
ProcVersionSignature: User Name 2.6.32-305.9-ec2 2.6.32.11+drm33.2
Uname: Linux 2.6.32-305-ec2 i686
Architecture: i386
Date: Wed Jun 2 13:35:49 2010
Ec2AMI: ami-53321827
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1b
Ec2InstanceType: m1.small
Ec2Kernel: aki-c35e74b7
Ec2Ramdisk: unavailable
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-ec2

related bugs:
  * bug 588725: instance had no console output

[Scott Moser (smoser)]

I've seen this again today testing Maverick release (20101007.1).

[Scott Moser (smoser)]

This still exists in natty (alpha-2) testing.
I really am suspecting a link (or duplicate) between this bug and bug 588725.

[Jeremy Foshee (jeremyfoshee)]

Scott,
    Have you had the chance ti test this against the latest?

Thanks!

~JFo

[Scott Moser (smoser)]

I don't have as good of logs from test as I used to. Hopefully as we move to fully automated nightly test we'll have even better logs of such things.

For the moment, I'll let this time-out to incomplete, but I really don't suspect its fixed. As I've stated elsewhere, I really think its a hypervisor bug.

[Joseph Salisbury (jsalisbury)]

@Scott

Do you happen to know if this is still an issue in Oneiric?

[Scott Moser (smoser)]

As I've stated elsewhere, I really think its a hypervisor bug, something beyond Ubuntu's control.

[Ben Howard (darkmuggle-deactivatedaccount)]

Amazon is asking for users that see this bug report it on the AWS Forums.

Please post instance ID and AMI ID in your forum post.

https://forums.aws.amazon.com/forum.jspa?forumID=30

[Joseph Salisbury (jsalisbury)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[dino99 (9d9)]

https://wiki.ubuntu.com/Releases