console logs should be available after instance is terminated

Bug #563175 reported by Scott Moser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eucalyptus
New
Wishlist
chris grzegorczyk
OpenStack Compute (nova)
Invalid
Undecided
Unassigned
eucalyptus (Ubuntu)
Fix Released
Medium
Dustin Kirkland 

Bug Description

$ euca-run-instances --key mykey emi-4287166D
$ euca-terminate-instances i-51F80895
$ sleep 3
$ euca-describe-instances
RESERVATION r-4B79091F admin default
INSTANCE i-51F80895 emi-4287166D 172.19.1.2 172.19.1.2 terminated mykey 0 m1.small 2010-04-14T16:12:18.264Z
        cluster1 eki-7B8A16F6
$ euca-get-console-output i-51F80895
DefaultJavaComponent: Can't find registered object: i-51F80895 in VmInstances

Above, I started an instance, terminated it, and then tried to get the console log. describe-instances knew about the instance, but get-console-output did not.

In ec2, as long as the instance shows up in describe-images output, get-console-output will succeed.

Eucalyptus loses the console log immediately on termination. Instead, it should hang onto it.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: eucalyptus-common 1.6.2-0ubuntu29
ProcVersionSignature: Ubuntu 2.6.32-21.31~security201004122115-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-server x86_64
.etc.eucalyptus.eucalyptus.cc.conf: CC_NAME="cluster1"
Architecture: amd64
Date: Wed Apr 14 11:23:19 2010
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eucalyptus

Revision history for this message
Scott Moser (smoser) wrote :
Scott Moser (smoser)
Changed in eucalyptus (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in eucalyptus:
importance: Undecided → Wishlist
assignee: nobody → chris grzegorczyk (chris-grze)
Revision history for this message
Scott Moser (smoser) wrote :

Relevant link to amazon ec2 documentation:
http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?instance-console.html
"Only the most recent 64 KB of posted output is stored, which is available for at least 1 hour after the last posting."

Changed in eucalyptus (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Dustin Kirkland (kirkland)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 2.0~bzr1231-0ubuntu1

---------------
eucalyptus (2.0~bzr1231-0ubuntu1) maverick; urgency=low

  * New upstream snapshot, -r1231, bugs fixed by upstream:
    - LP: #566792 - metadata service returns empty data with 200 OK
    - LP: #606243 - euca-describe-availability-zones verbose corrupted
    - LP: #563175 - should hold on to console logs after terminated
    - LP: #613832 - Cannot mark address as allocating
    - LP: #610479 - Instance fails to start
 -- Dustin Kirkland <email address hidden> Tue, 17 Aug 2010 12:49:28 -0400

Changed in eucalyptus (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Scott Moser (smoser) wrote :

I just verified that this is indeed fixed on
eucalyptus-common 2.0~bzr1233-0ubuntu1

(I did have to work around bug 619843 with the suggested /etc/libvirt/qemu.conf changes)

Scott Moser (smoser)
summary: - eucalyptus should hold on to console logs as after instance terminated
+ console logs should be available after instance is terminated
Revision history for this message
Scott Moser (smoser) wrote :

I'm marking this invalid on nova. I'll open other bugs for that.

Changed in nova:
status: New → Invalid
Revision history for this message
Andy Grimm (agrimm) wrote :

This issue is now being tracked upstream at http://eucalyptus.atlassian.net/browse/EUCA-2692

Please watch that issue for further updates.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.