To be clear, this is needed because we get the destination host, and then substitute that into the locally configured URL pattern.
This is largely why the live_migration_uri is now deprecated in favor of several specific configuration options, that makes this all more discoverable.
I don't believe this is new behaviour as such, but I could be very wrong on that. I am curious if it is a change.
Maybe the "fix" here is to warn users in the configuration description?
To be clear, this is needed because we get the destination host, and then substitute that into the locally configured URL pattern.
This is largely why the live_migration_uri is now deprecated in favor of several specific configuration options, that makes this all more discoverable.
I don't believe this is new behaviour as such, but I could be very wrong on that. I am curious if it is a change.
Maybe the "fix" here is to warn users in the configuration description?