Issue Details (XML | Word | Printable)

Key: ABICLOUD-352
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Xavier Fernandez
Reporter: Diego Parrilla
Votes: 0
Watchers: 0
Operations

Email this issue
Send issue summary in email
If you were logged in you would be able to see more operations.
Abiquo

Unexpected error bundling images: Cannot recover from error.

Created: 30/Nov/09 11:06 PM   Updated: 10/Jun/10 11:08 AM   Resolved: 04/Jan/10 10:14 AM
Component/s: Bundle
Affects Version/s: abicloud-1.0.0-RC2
Fix Version/s: abicloud-1.0.0-RC3

Time Tracking:
Not Specified


 Description  « Hide
A virtual appliance has been created with two images. I want to bundle both images and modify the virtual app to keep the lastest versions of the images. After confiriming the bundle, the error in the trace happens and the bundle fails. It's not possible to recover the images from these error and then the changes in the images are lost because the system does not allow to try again with the bundling.

The status of the images in the infrastructure is 'stopped' and the real status in the hypervisor is 'stopped' for both images. If you start them in the hypervisor manually, then the status in the infrastructure view does not change.

both images are copied back to the /opt/vm_repository, but they don't appear registered in the appliances library.

After changing manually the status of the virtual machines and virtuall app in the database and starting manually the virtual machines in the hypervisor, I tried again to bundle them and it work.

The traces of the error are:

18:50:34.822 [pool-3-thread-3] INFO c.a.v.v.i.VirtualapplianceresourceDeployer
- An attempt was made to get a resource that did not exist called: 1
18:50:38.092 [pool-6-thread-1] ERROR c.a.a.vsm.plugin.esxi.ESXiPoller -
org.apache.axis.AxisFault: (0)null
        at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.j
ava:744) [axis-1.4.jar:na]
        at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
 [axis-1.4.jar:na]
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32) [axis-1.4.jar:na]
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) [axis-1.
4.jar:na]
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) [axis-1.4.jar
:na]
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165) [axis-1
.4.jar:na]
        at org.apache.axis.client.Call.invokeEngine(Call.java:2784) [axis-1.4.ja
r:na]
        at org.apache.axis.client.Call.invoke(Call.java:2767) [axis-1.4.jar:na]
        at org.apache.axis.client.Call.invoke(Call.java:2443) [axis-1.4.jar:na]
        at org.apache.axis.client.Call.invoke(Call.java:2366) [axis-1.4.jar:na]
        at org.apache.axis.client.Call.invoke(Call.java:1812) [axis-1.4.jar:na]
        at com.vmware.vim25.VimBindingStub.createCollectorForEvents(VimBindingSt
ub.java:49026) [vmware-api-1.0.0-SNAPSHOT.jar:na]
        at com.abiquo.abicloud.vsm.plugin.esxi.ESXiPoller.createEventHistoryColl
ector(ESXiPoller.java:160) [ESXiPoller.class:na]
        at com.abiquo.abicloud.vsm.plugin.esxi.ESXiPoller.call(ESXiPoller.java:4
93) [ESXiPoller.class:na]
        at com.abiquo.abicloud.vsm.plugin.esxi.ESXiPoller.call(ESXiPoller.java:4
7) [ESXiPoller.class:na]
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [n
a:1.6.0_17]
        at java.util.concurrent.FutureTask.run(FutureTask.java:138) [na:1.6.0_17
]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886) [na:1.6.0_17]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908) [na:1.6.0_17]
        at java.lang.Thread.run(Thread.java:619) [na:1.6.0_17]
18:50:39.665 ERROR com.abiquo.util.AbiCloudError - Virtual Appliance error: Can
 not bundle the virtual appliance.[Error code:ABI-S009 Timestamp:1259625039]. Vi
rtual Appliance error:

Error Code: ABI-S009
Error ID: 1259625039.


Enric Ruiz added a comment - 01/Dec/09 10:05 AM
I tested it with KVM and it is working correctly. Seems that you are using ESXi plugin. Correct?

Enric Ruiz added a comment - 02/Dec/09 09:52 AM
I can not reproduce this behavior, but during testing I encountered an error related to the OVF manager and the arguments passed to RIMP (resolved now) i can not ensure that the issue resolves the reported error.

Diego Parrilla added a comment - 02/Dec/09 10:18 AM
Please test in a ESXi environment. The error happens with ESXi, no link with RIMP.

It hapeens very often, and after this error the eventing systems for ESXi stops working. Then, only clikcing on refresh button status is updated.

Enric Ruiz added a comment - 02/Dec/09 10:41 AM
ESXi is tested already.

Diego Parrilla added a comment - 02/Dec/09 10:48 AM
Reopened until a fix or workaround it's in place.

Xavier Fernandez added a comment - 04/Jan/10 10:14 AM
Related with eventing issues and other minor errors solved.