metadata service returns 500 error

Bug #637659 reported by Dave Walker
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eucalyptus
Fix Released
Undecided
Unassigned
eucalyptus (Ubuntu)
Fix Released
High
Dave Walker
Maverick
Fix Released
High
Dave Walker

Bug Description

Starting an instance, trnasitions to running state - but ssh fails to work. Seems metadata service is returning 500.

Extract from log, that seems pertinent:
==> cloud-error.log <==
00:12:34 ERROR [NioServerHandler:New I/O server worker #1-10] Internal Error.
com.eucalyptus.context.NoSuchContextException: Found channel context [id: 0x77dc7e18, /172.19.1.2:49179 => /169.254.169.254:8773] but no corresponding context.
        at com.eucalyptus.context.Contexts.lookup(Contexts.java:29)
        at com.eucalyptus.ws.server.MetadataPipeline.handleUpstream(MetadataPipeline.java:72)
        at com.eucalyptus.ws.server.NioServerHandler.messageReceived(NioServerHandler.java:127)
        at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:114)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:385)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndfireMessageReceived(ReplayingDecoder.java:459)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:443)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:381)
        at com.eucalyptus.ws.handlers.http.NioSslHandler.handleUpstream(NioSslHandler.java:31)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:342)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:329)
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:330)
        at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:203)
        at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:53)
        at org.jboss.netty.handler.execution.MemoryAwareThreadPoolExecutor$MemoryAwareRunnable.run(MemoryAwareThreadPoolExecutor.java:502)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:636)

Full logs, as reproduced by hggdh2:
 lp:~hggdh2/+junk/uec-qa (r55)

Dave Walker (davewalker)
Changed in eucalyptus (Ubuntu):
milestone: none → ubuntu-10.10
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
C de-Avillez (hggdh2) wrote :

logs showing this are at lp:~hggdh2/+junk/uec-qa, revision 55

Dave Walker (davewalker)
Changed in eucalyptus (Ubuntu Maverick):
importance: Critical → High
assignee: nobody → Dave Walker (davewalker)
Revision history for this message
Dave Walker (davewalker) wrote :
Thierry Carrez (ttx)
tags: added: server-mrs
tags: added: patch
Revision history for this message
Neil Soman (neilsoman) wrote :

Fixed in revno 1240.

Changed in eucalyptus:
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 2.0+bzr1241-0ubuntu1

---------------
eucalyptus (2.0+bzr1241-0ubuntu1) maverick; urgency=low

  * New upstream bug fix snapshot, -r1241
    - Fixes euca-* commands stop responding. (LP: #639639
    - Fixes metadata service returning 500 error. (LP: #637659)
  * debian/patches/06-UEC-webinterface.patch: Improved cross
    browser compatability, particularly on the login screen.
 -- Dave Walker (Daviey) <email address hidden> Thu, 16 Sep 2010 17:10:38 +0100

Changed in eucalyptus (Ubuntu Maverick):
status: Confirmed → Fix Released
Changed in eucalyptus:
status: Fix Committed → Fix Released
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.