status check does not tolerate ENOENT if ringlefile not yet created
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
swift-proxy (Juju Charms Collection) |
Fix Released
|
Critical
|
Edward Hope-Morley |
Bug Description
Recently added assess_status() causes this by calling has_minimum_zones() which errors if rings do not exist yet. Should be easy enough to fix.
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 INFO swift-storage-
2015-10-28 10:00:45 ERROR juju.worker.
Related branches
- Chris Glass (community): Approve
-
Diff: 12 lines (+2/-0)1 file modifiedlib/swift_utils.py (+2/-0)
Changed in swift-proxy (Juju Charms Collection): | |
milestone: | none → 16.01 |
assignee: | nobody → Edward Hope-Morley (hopem) |
importance: | Undecided → Critical |
status: | New → In Progress |
tags: | added: backport-potential openstack sts |
tags: | added: kanban-cross-team |
Changed in swift-proxy (Juju Charms Collection): | |
status: | Fix Committed → Fix Released |
Seems this has already been fixed in /next - http:// bazaar. launchpad. net/~openstack- charmers/ charms/ trusty/ swift-proxy/ next/revision/ 121. I'll proceed with backporting it.