boundary
boundary copied to clipboard
hashicorp
Client connect error with client 0.15.0
Describe the bug
After upgrading boundary controller and worker to 0.15.0, connections fails when using boundary client 0.15.0, but using boundary client 0.14.3 connections works.
To Reproduce Steps to reproduce the behavior:
- Run
boundary connect -target-id=xx -host-id=xx - Run
nc 127.0.0.1 port_number - See error
Expected behavior Connections work with client version 0.15.0 as they do with client 0.14.3
Additional context
Nothing in either the controller og worker logs
same issue for us as well. so, I'm now running
Controller: 0.15.0 Worker: 0.14.3 Client: 0.15.0
to get this working around
Hey @umglurf ,
I've tried reproducing the issue here but haven't had any luck. Can you please provide some more information about your set up. Your controller is 0.15.0, worker is 0.15.0 & your CLI client is 0.15.0? Also, what OS are you using?
Thank You!
Hey @umglurf ,
Hey
I've tried reproducing the issue here but haven't had any luck. Can you please provide some more information about your set up. Your controller is 0.15.0, worker is 0.15.0 & your CLI client is 0.15.0? Also, what OS are you using?
Controller & worker is 0.15.0. CLI client 0.15.0 fails, CLI client 0.14.3 works. Controller and worker is running in podman using the https://hub.docker.com/r/hashicorp/boundary image, CLI is on Fedora Linux 39 with the packages from the Hashicorp repo
@umglurf Thanks!
What is the error thrown when you attempt to connect to the authorized session nc 127.0.0.1 port_number?
What is the error thrown when you attempt to connect to the authorized session
nc 127.0.0.1 port_number?
I've made a short recording showing what happens Screencast from 2024-02-08 06-12-21.webm
@umglurf Thanks for the video. That helps a lot
What is the maximum number of connections configured for your target?
@umglurf Thanks for the video. That helps a lot
What is the maximum number of connections configured for your target?
Hi, the session max connection limit is set to 1. I tried increasing it to 2, and then it works with 0.15.0, so could it be something has changed in 0.15 that now requires an extra connection?
That should not be happening. We're working on a fix on our end. Thanks for your help!
Hi @elimt
I tested the released 0.15.1 now and it works again with that version. Thanks for the fix