MySQL targets not working after boundary 0.10.3 upgrade


Yesterday I tried to upgrade our boundary instances (1 controller and 1 worker) from 0.9.1 to 0.10.3 and it dit not go well. Using 0.10.3 and connecting to MySQL targets was not working anymore.

  • MySQL client: ERROR 2013 (HY000): Lost connection to server at 'handshake: reading initial communication packet', system error: 11
  • boundary client: error reading handshake result: failed to read protobuf message: failed to get reader: received close frame: status = StatusInternalError and reason = "refusing to activate session"


Did you run a boundary database migrate with the new version before running it as a controller?

Yes I did. As far as I remember the migration was successful.

Also http targets are working as usual (for example to target k8s eks api server through lens k8s ide).

Quite possibly refusing to activate session errors after upgrading to 0.10.1 · Issue #2362 · hashicorp/boundary · GitHub which will be fixed in 0.10.4, out soon.

The problem disappeared while upgrading from 0.9.1 to 0.10.4


Awesome! Glad to hear it!