Comment 16 for bug 1999640

So in all cases I've seen, the relevant bit of dump-db looks like this:

- _id: be99df74-4f14-4b16-841b-502092a160cb:turnip-api
  charm-origin:
    hash: ""
    id: ""
    platform: {}
    revision: 2
    source: local
  charmmodifiedversion: 1
  charmurl: local:bionic/turnip-api-2
  cs-channel: ""
  exposed: false
  forcecharm: false
  life: 0
  metric-credentials: ""
  minunits: 0
  model-uuid: be99df74-4f14-4b16-841b-502092a160cb
  name: turnip-api
  passwordhash: ""
  relationcount: 4
  scale: 0
  series: bionic
  subordinate: false
  txn-queue: []
  txn-revno: 26
  unitcount: 2

i.e. a charm-origin exists, but it has an empty platform. I'm not sure that calling `createCharmOrigin` would be correct in this case since we do know some parts of the origin (in particular the revision), but perhaps it would make sense to create a platform based on the request data, in the same way that `createCharmOrigin` does?

(I know nothing about how things could have got into this state though, beyond observing that it's happened in a couple of different places that I know of.)