I'm guessing that the work to update the tracker to notice that there are new resources available as well as a new charm revision, ends up putting something into the database such that the 'juju refresh' action then says "oh, I can't do that, you already have it". We'll have to figure out why that is an issue, but it very much seems to be a controller side issue.
I'm guessing that the work to update the tracker to notice that there are new resources available as well as a new charm revision, ends up putting something into the database such that the 'juju refresh' action then says "oh, I can't do that, you already have it". We'll have to figure out why that is an issue, but it very much seems to be a controller side issue.