Comment 2 for bug 1999640

I've been looking at the issue in #1, where the same error occurs for export-bundle. This is not reproducible under all circumstances, so it'd be helpful to understand could be different here.

It can happen with charmstore charms as well.

The application data in the charmstore case looks like:
{
        "_id" : "xxxx:rabbitmq-server",
        "name" : "rabbitmq-server",
        "model-uuid" : "xxxx",
        "series" : "focal",
        "subordinate" : false,
        "charmurl" : "cs:rabbitmq-server-118",
        "cs-channel" : "stable",
        "charm-origin" : {
                "source" : "charm-store",
                "id" : "",
                "hash" : "",
                "revision" : 118,
                "channel" : {
                        "risk" : "stable"
                },
                "platform" : {
                        "architecture" : "amd64",
                        "series" : "focal",
                        "os" : "ubuntu"
                }
        },
...
}

There is a workaround floating about for the export-bundle issue which has stopped working:
`db.applications.updateOne({"_id" : "<model-uuid>:<application-name>"},{ $set: {"charm-origin.platform.os":"ubuntu"}})`

FYI: Platform in state uses `series`, while core/charm Platform uses `channel`, they are equivalent and are parsed the same.