Comment 5 for bug 1860992

Ok, I've worked out what's happening here - it's because the offer name and application name are different. The code that registers the relation exports the offer name, but in WatchRelationChanges we incorrectly use the application name to find the token, this succeeds when they happen to be named the same but not in this case.

I'm fixing that now, but in the meantime the workaround is to rename the offer to keystone in the two overlays.