Description: metadata service returning 500 error.  In the eucalyptus
 logs, a traceback similar to the following is identified:
 .
 "Internal Error. com.eucalyptus.context.NoSuchContextException: Found 
 channel context ... but no corresponding context."
 .
 It seems that the context is somehow lost, and this patch seems to 
 resolve this, but the rational for the line being added originally
 needs clarification.
Author: Dave Walker (Daviey) <DaveWalker@ubuntu.com>
Bug: https://launchpad.net/bugs/637659
Bug-Ubuntu: https://launchpad.net/bugs/637659
Forwarded: https://launchpad.net/bugs/637659

--- eucalyptus-2.0+bzr1239.orig/clc/modules/wsstack/src/main/java/com/eucalyptus/ws/server/MetadataPipeline.java
+++ eucalyptus-2.0+bzr1239/clc/modules/wsstack/src/main/java/com/eucalyptus/ws/server/MetadataPipeline.java
@@ -69,7 +69,6 @@ public class MetadataPipeline extends Fi
 
       HttpResponse response = null;
       LOG.info( "Trying to get metadata: " + newUri );
-      Contexts.clear( Contexts.lookup( ctx.getChannel( ) ) );
       Object reply = ServiceContext.send( "VmMetadata", newUri );
       if ( !( reply instanceof NullPayload ) ) {
         response = new DefaultHttpResponse(request.getProtocolVersion( ),HttpResponseStatus.OK);