Tired of waiting to cache image: sles11rc1-amd64/sles11rc1-amd64.img.manifest.xml giving up

Bug #680626 reported by Brian J. Murrell
This bug report is a duplicate of:  Bug #565043: Walrus unable to decrypt image for NC. Edit Remove
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Eucalyptus
New
Undecided
Neil Soman

Bug Description

After having upgraded to 2.0.1 within the last week or two, my NCs seem to be having trouble fetching one particular image. The CLC reports:

14:04:49 ERROR [WalrusImageManager:Bukkit.13] Tired of waiting to cache image: sles11rc1-amd64/sles11rc1-amd64.img.manifest.xml giving up
14:04:49 DEBUG [ReplyQueue:Bukkit.13] :1290459889591:ReplyQueue:MSG_REPLY:String:NativeMethodAccessorImpl.invoke0.-2
14:04:49 TRACE [ReplyQueue:Bukkit.13] Caught exception while servicing: <?xml version="1.0" encoding="UTF-8"?>
<euca:GetDecryptedImageType xmlns:euca="http://msgs.eucalyptus.com">
<euca:WalrusDataGetRequestType>
<euca:WalrusDataRequestType>
<euca:WalrusRequestType>
<euca:EucalyptusMessage>
<euca:correlationId>db17a588-7b0a-4e61-9915-cfb048a059a4
<euca:userId>admin
<euca:effectiveUserId>eucalyptus
<euca:_return>true
</euca:EucalyptusMessage>
<euca:accessKeyID>W...w
<euca:timeStamp>2010-11-22T19:44:49.419Z
<euca:bucket>sles11rc1-amd64
<euca:key>sles11rc1-amd64.img.manifest.xml
</euca:WalrusRequestType>
</euca:WalrusDataRequestType>
</euca:WalrusDataGetRequestType>
</euca:GetDecryptedImageType>
14:04:49 ERROR [ReplyQueue:Bukkit.13] org.mule.api.service.ServiceException: Component that caused exception is: Bukkit. Message payload is of type: GetDecryptedImageType
org.mule.api.service.ServiceException: Component that caused exception is: Bukkit. Message payload is of type: GetDecryptedImageType
at org.mule.component.DefaultLifecycleAdapter.intercept(DefaultLifecycleAdapter.java:214)
at org.mule.component.AbstractJavaComponent.invokeComponentInstance(AbstractJavaComponent.java:82)
at org.mule.component.AbstractJavaComponent.doOnCall(AbstractJavaComponent.java:73)
at org.mule.component.AbstractComponent.onCall(AbstractComponent.java:87)
at org.mule.model.seda.SedaService$ComponentStageWorker.run(SedaService.java:533)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:636)
Caused by: com.eucalyptus.util.EucalyptusCloudException: caching failure
at edu.ucsb.eucalyptus.cloud.ws.WalrusImageManager.getDecryptedImage(WalrusImageManager.java:1136)
at edu.ucsb.eucalyptus.cloud.ws.WalrusControl.GetDecryptedImage(WalrusControl.java:342)
at sun.reflect.GeneratedMethodAccessor328.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.mule.model.resolvers.AbstractEntryPointResolver.invokeMethod(AbstractEntryPointResolver.java:147)
at org.mule.model.resolvers.ReflectionEntryPointResolver.invoke(ReflectionEntryPointResolver.java:127)
at org.mule.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:50)
at org.mule.component.DefaultLifecycleAdapter.intercept(DefaultLifecycleAdapter.java:202)
... 8 more

The sles11rc1-amd64/sles11rc1-amd64.img.manifest.xml image seems to be the only one with a problem. The dozens of other images we have here seem to transfer to the NC with no issues.

This image worked just fine prior to the upgrade from 1.6.2->2.0.0->2.0.1

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

Here's a cloud-output.log from the CLC of trying to start the sles11sp1 instance through until it complains "Tired of waiting..." and then a bit beyond that.

Changed in eucalyptus:
assignee: nobody → Neil Soman (neilsoman)
Revision history for this message
graziano obertelli (graziano.obertelli) wrote :

This could be another manifestation of bug 565043. The test (and workaround) is at the end of that bug (downloads a new fresh set of credentials, re-bundle the image etc ...).

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.