Albert Puig added a comment - 18/Aug/10 03:08 PM

Albert Puig added a comment - 18/Aug/10 03:08 PM The concrete case is when the AM module is abnormally finished while downloading some packages. This can be observed on the repository filesystem leaving the *.deploying* file mark on the package directory (each referenced file have its own XXX.downloading file). So, when AM starts check for packages on DOWNLOADING state to delete it. Also deletes all its format conversions and bundles images. NOTES: multiple AM running on the same repository filesystem (thats a nonsense for me): If a second instance of AM is started it will delete the packages being download any another AM.

Valerie Kalusinski added a comment - 25/Aug/10 05:01 PM

Valerie Kalusinski added a comment - 25/Aug/10 05:01 PM This problem still happen. Reopened on build 3353.

Valerie Kalusinski added a comment - 13/Sep/10 04:52 PM

Valerie Kalusinski added a comment - 13/Sep/10 04:52 PM reopen if occur again. Closed on release 1.6.5 build 3412

Valerie Kalusinski added a comment - 14/Sep/10 12:17 PM - edited

Valerie Kalusinski added a comment - 14/Sep/10 12:17 PM - edited This occurred again after adding/removing OVFPackageList with API but maybe this is not relevant. Reopened on build 3412.

Valerie Kalusinski added a comment - 09/Nov/10 12:23 PM

Valerie Kalusinski added a comment - 09/Nov/10 12:23 PM This has been reproduced if 2 datacenters have the same AM (but this is not allowed now).

Albert Puig added a comment - 17/Dec/10 10:21 AM

Albert Puig added a comment - 17/Dec/10 10:21 AM the eventing mechanism has moved from jms to amqp. On the revised implementation the issue can not be reproduced.

Valerie Kalusinski added a comment - 08/Mar/11 10:07 AM

Valerie Kalusinski added a comment - 08/Mar/11 10:07 AM This has not been reproduced. Closed on 1.7.5 master.