not okForStorage error when deploying local charm
Bug #1308146 reported by
Matthew Williams
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Unassigned | ||
1.18 |
Fix Released
|
Low
|
Unassigned | ||
1.20 |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Only happens on some local charms, not all.
from debug log:
ERROR error uploading charm: cannot update uploaded charm in state: not okForStorage
machine-0: no kvm containers possible
and forever after:
machine-0: 2014-04-15 16:31:04 ERROR juju resumer.go:68 worker/resumer: cannot resume transactions: not okForStorage
machine-0: 2014-04-15 16:32:04 ERROR juju resumer.go:68 worker/resumer: cannot resume transactions: not okForStorage
machine-0: 2014-04-15 16:33:04 ERROR juju resumer.go:68 worker/resumer: cannot resume transactions: not okForStorage
juju version: 1.18.1-
Happening on aws
Related branches
lp://staging/~dimitern/juju-core/lp-1308146-1.18-backport
- Martin Packman (community): Approve
-
Diff: 108 lines (+66/-1)3 files modifiedstate/charm.go (+11/-0)
state/state.go (+10/-1)
state/state_test.go (+45/-0)
Superseded
for merging
into
lp://staging/~go-bot/juju-core/trunk
- Juju Engineering: Pending requested
-
Diff: 290 lines (+165/-1) (has conflicts)8 files modifiedagent/mongo/mongo.go (+25/-0)
environs/cloudinit/cloudinit_test.go (+51/-0)
provider/ec2/image_test.go (+11/-0)
scripts/win-installer/setup.iss (+4/-0)
state/charm.go (+11/-0)
state/state.go (+10/-1)
state/state_test.go (+49/-0)
version/version.go (+4/-0)
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: charms deploy |
Changed in juju-core: | |
importance: | High → Critical |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | next-stable → 1.21-alpha2 |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core: | |
assignee: | Dimiter Naydenov (dimitern) → nobody |
To post a comment you must log in.
not okForStorage seems to be MongoDB's way of telling you it doesn't accept the syntax of your document.
The ones that come up while googling are having either "." or "$" in your field names (they are allowed in values).