`juju export-bundle` fails when an ingress integrator is deployed on microk8s

[Nick Moffitt]

On a microk8s model that has two applications deployed: one is a local charm I am developing, and the other is the charmhub nginx-ingress-integrator (since juju cannot yet control ingress by itself, and there is no integrator for API Gateways):

```ShellSession
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
site24x7 microk8s-localhost microk8s/localhost 2.9.0 unsupported 11:44:58+01:00

App Version Status Scale Charm Store Channel Rev OS Address Message
nginx-ingress-integrator active 1 nginx-ingress-integrator charmhub stable 10 kubernetes Ingress with service IP(s): 10.152.183.68
site24x7-exporter active 1 site24x7-exporter local 7 kubernetes

Unit Workload Agent Address Ports Message
nginx-ingress-integrator/0* active idle 10.1.27.215 Ingress with service IP(s): 10.152.183.68
site24x7-exporter/0* active idle 10.1.27.214

$ juju export-bundle
ERROR operator image metadata for application "nginx-ingress-integrator" not found (not found)
```

[Yang Kelvin Liu (kelvin.liu)]

hi Nick

I was not able to reproduce this issue.
Here are my testing steps: https://pastebin.ubuntu.com/p/tYvnXkpXmD/

Would you give more details for us to reproduce?

thanks

[Launchpad Janitor (janitor)]

[Expired for Canonical Juju because there has been no activity for 60 days.]