MySQL targets not working after boundary 0.10.3 upgrade

Boundary
1

Hello,

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.
Errors:

  • 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"

Thanks,

2

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

3

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).

4

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.

5

The problem disappeared while upgrading from 0.9.1 to 0.10.4

Thanks!

6

Awesome! Glad to hear it!