Hi Ivan,
Thanks for the guide, good workaround for someone hitting the same issue. I
must respectfully disagree with your sentiment though. As you have mentioned in
your article issues like this tend to have a root cause –
network outage, hypervisor issues etc. – and these issues vary from environment
to environment and should be investigated on a case by case basis. Your
suggested long term solution is just a workaround – error trapping and
subsequent housekeeping should be improved in the CloudStack code, so the best
thing to do is investigate, find root cause and log a Jira ticket such that it
can be improved going forward.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 31/08/2017, 06:33, "Ivan Kudryavtsev" <kudryavtsev...@bw-sw.com> wrote:
Hello, community.
Today we (again) met snapshots stuck in exotic states and I decided to
create small guide how to fix it. AFAIK, somebody tried to manage KB in
GitHub about useful tools, cases, etc. It might be that small article can
be included. I wrote it because short googling didn't give positive results
about the problem. Also, all comments are welcome.
https://bitworks.software/blog/en/2017-08-31-cloudstack-removing-snapshots-stuck-in-allocated-backingup-states.html
Also, the same for Russian-speaking people:
https://bitworks.software/blog/2017-08-31-cloudstack-removing-snapshots-stuck-in-allocated-backingup-states.html
--
With best regards, Ivan Kudryavtsev
Bitworks Software, Ltd.
Cell: +7-923-414-1515
WWW: http://bitworks.software/ <http://bw-sw.com/>
dag.sonst...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
