The cases were I can't find a problem, the db does have a platform in the charm-origin for local charms. So this is different.
Is the model running 2.9.42 also?
Do you know if this was a long running model starting before 2.9? If so, do you know if it was migrated to a 2.9 controller? Or just upgraded?
You should be able to update the application charm-origin in the db as a workaround. Though that does will not help fixing it.
Provided the machine running turnip-api is on an AMD platform, updating the charm-origin's platform to: "platform" : { "architecture" : "amd64", "series" : "bionic", "os" : "ubuntu"
}
The cases were I can't find a problem, the db does have a platform in the charm-origin for local charms. So this is different.
Is the model running 2.9.42 also?
Do you know if this was a long running model starting before 2.9? If so, do you know if it was migrated to a 2.9 controller? Or just upgraded?
You should be able to update the application charm-origin in the db as a workaround. Though that does will not help fixing it.
Provided the machine running turnip-api is on an AMD platform, updating the charm-origin's platform to:
"platform" : {
"architectur e" : "amd64",
"series" : "bionic",
"os" : "ubuntu"
}
should work.