Description of change
Creating 2 offers off the one app was failing when relations were processed. To fix, change the token generated on the offer side to be based on the offer name, not the app name.
Also, fix the offer status watcher so that status changes to an offering app's units also trigger a status update in the consuming model.
Note: existing single app offers will continue to work with this fix (it's backwards compatible). But multi-offers on the same app will need to be redeployed.
QA steps
juju bootstrap lxd test juju switch controller juju model-config logging-juju switch default juju deploy memcached juju deploy mariadb juju add-model foo juju deploy mediawiki juju offer mediawiki:cache mw-cache juju offer mediawiki:db mw-db juju switch default juju consume foo.mw-db juju consume foo.mw-cache juju relate mw-db mariadb:db juju relate mw-cache memcached
Check controller logs for cmr relation errors. Check workloads
juju remove-relation mariadb:db mw-db
Check SAAS status
Upgrade a 2.5.0 cmr deployment and check operations.
Bug reference
https://bugs.launchpad.net/juju/+bug/1813151 https://bugs.launchpad.net/juju/+bug/1815179
该提问来源于开源项目：juju/juju
