Github user bvbharatk commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-43971
### ACS CI BVT Run
**Sumarry:**
Build Number 67
Hypervisor xenserver
NetworkType Advanced
Passed=68
Failed=4
Skipped=3
_
Github user rhtyd commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-216219596
@anshul1886 rebase against latest master, thanks
Do you think a cleanup action of some sort be performed, as this will only
delete the snapshot in database
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-215460320
@anshul1886 I see in some other places in that file when
`snapshotDao.remove(snapshotId);` is called there is a `return true` right
after it. Can you help me underst
Github user anshul1886 commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-215375588
@koushik-das All hypervisor uses XenServerSnapshotStrategy so it should be
applicable on all hypervisors.
---
If your project is set up for it, you can reply to
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-215350146
@anshul1886 The fix is only for XS snapshots. What about other HVs?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user Slair1 commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-214804222
Thanks! I had the same issue, retention settings for snapshots were
failing because it couldn't delete two snapshots that were stuck in "allocated'
state.
---
If
Github user bvbharatk commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-202495572
### ACS CI BVT Run
**Sumarry:**
Build Number 140
Hypervisor xenserver
NetworkType Advanced
Passed=104
Failed=1
Skipped=4
Github user anshul1886 commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-167040721
@pdube Snapshot can be in Allocated state for a split second only in normal
scenarios. If it is in Allocated state for more than that time, then it simply
means
Github user pdube commented on the pull request:
https://github.com/apache/cloudstack/pull/1282#issuecomment-166910265
How do you know if there are no jobs associated with it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
GitHub user anshul1886 opened a pull request:
https://github.com/apache/cloudstack/pull/1282
CLOUDSTACK-9200: Fixed failed to delete snapshot if snapshot is stuck in
Allocated state without any job associated with it
https://issues.apache.org/jira/browse/CLOUDSTACK-9200
Thi
10 matches
Mail list logo