Opened at 2013-02-26T02:48:21Z
Closed at 2020-10-30T12:35:44Z
#1923 closed defect (wontfix)
cloud backend OpenStack: crawlers are not working correctly with HP Cloud Object Storage
| Reported by: | davidsarah | Owned by: | davidsarah |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.15.0 |
| Component: | code-storage | Version: | cloud-branch |
| Keywords: | cloud-backend openstack hp-cloud accounting crawlers leasedb | Cc: | |
| Launchpad Bug: |
Description (last modified by daira)
The smoke-testing I did to confirm that the OpenStack code was working with HP Cloud Object Storage, only covered basic upload/download. It appears that list queries done by the accounting crawler are not finding any existing shares, causing the accounting crawler to treat all shares in the leasedb as "disappeared". This doesn't happen with Rackspace Cloud Files.
List queries done in order to find specific shares for download are working, so it's probably something to do with the prefix handling (unless I'm misinterpreting the logs).
Change History (9)
comment:1 Changed at 2013-02-26T02:49:14Z by davidsarah
- Description modified (diff)
- Status changed from new to assigned
comment:2 Changed at 2013-02-26T03:04:09Z by davidsarah
comment:3 Changed at 2013-02-27T23:52:46Z by zooko
- Keywords leasedb added
comment:4 Changed at 2013-03-01T01:42:35Z by davidsarah
This appears to be unrelated to #1921, even though it has superficially similar symptoms.
comment:5 Changed at 2014-12-06T15:44:38Z by daira
- Description modified (diff)
- Milestone changed from undecided to 1.12.0
comment:6 Changed at 2016-03-22T05:02:25Z by warner
- Milestone changed from 1.12.0 to 1.13.0
Milestone renamed
comment:7 Changed at 2016-06-28T18:17:14Z by warner
- Milestone changed from 1.13.0 to 1.14.0
renaming milestone
comment:8 Changed at 2020-06-30T14:45:13Z by exarkun
- Milestone changed from 1.14.0 to 1.15.0
Moving open issues out of closed milestones.
comment:9 Changed at 2020-10-30T12:35:44Z by exarkun
- Resolution set to wontfix
- Status changed from assigned to closed
The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.
If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).
If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.
Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.
Hmm, the ability to run tests against an actual cloud storage service rather than mock_cloud (as suggested by itamar) would help here.