I noticed in the engine report (one that John shared https://pastebin.canonical.com/p/BGXRjzYvNF/) that the in-peer field for one of the relations for the unit is true. So I'm wondering if we have a stale peer relation for that unit that hasn't been cleaned up during redeploy. Maybe that's something we could take a look at the db during the meeting.
I noticed in the engine report (one that John shared https:/ /pastebin. canonical. com/p/BGXRjzYvN F/) that the in-peer field for one of the relations for the unit is true. So I'm wondering if we have a stale peer relation for that unit that hasn't been cleaned up during redeploy. Maybe that's something we could take a look at the db during the meeting.
```
application- members:
httpreques t-lego- provider: 1 lego-provider: secret- storage
relations:
"7":
dying: false
endpoint: secret-storage
is-peer: true
members: {}
relation: httprequest-
```
https:/ /github. com/juju/ juju/blob/ de682d4a80a1d0c 104b2cfd31e58e1 49aaede9a1/ state/applicati on.go#L1387 should've cleaned it up.