Truststores can be exposed as a message sources to clients for the purposes of public key distribution for end-to-end message encryption.
If a truststore is exposed, by default the truststore is exposed to all virtualhosts. The user can opt to make this more restrictive by opting to include or exclude virtualhosts.
The inclusion/exclusion based on virtualhost is problematic in the HA case, as the virtualhost may be elsewhere in the group. This would prevent the Truststore from starting (it would go into error).
The Truststore implementations must change to have inclusion/exclusion based on virtualhostnode.
The configuration upgrader will need to guess that the virtualhostnode name is the same as the virtualhost. This will work with default configuration in the non-HA case (where virtualhostnode name = virtualhost name), but will fail in the HA case.