Waypoint Context Will Not Reset After Setting New Default

Waypoint
1

Waypoint cache doesn’t appear to reset after changing context. I have removed the waypoint context file with .hcl in an attempt to clear cache, but that didn’t work. Additionally, we have deleted the .waypoint directory in an attempt to clear cache. But, nothing seems to reset the mismatch that waypoint is using to connect to the remote waypoint server vs what’s in the default context.

Information below is redacted somewhat but the mismatch can be seen between the context insepct and connection info when connecting to Waypoint.

We understand they should be the same, but they are not. How can we reset it?

user@Users-MacBook-Pro-2 cicdtestproject % waypoint context list
| NAME | PLATFORM | SERVER ADDRESS
----±-----------------±---------±----------------------------------------------------------

  • | UsersNewContext | n/a | DNS-URL-FOR-AWS.compute.amazonaws.com:9701
    user@Users-MacBook-Pro-2 cicdtestproject % waypoint context inspect UsersNewContext
    » Context Info:
    ** address: DNS-URL-FOR-AWS.compute.amazonaws.com:9701**
    ** tls: true**
    ** tls skip verify: true**
    ** require auth: true**
    ** platform: n/a**
    » Workspace Info:
    ** Name: default**
    user@Users-MacBook-Pro-2 cicdtestproject % waypoint token new -vvv
    2022-08-23T10:37:08.211-0400 [INFO] waypoint: waypoint version: full_string=“v0.9.0 (2a7b89036)” version=v0.9.0 prerelease=“” metadata=“” revision=2a7b89036
    2022-08-23T10:37:08.211-0400 [TRACE] waypoint: starting interrupt listener for context cancellation
    2022-08-23T10:37:08.211-0400 [TRACE] waypoint: interrupt listener goroutine started
    2022-08-23T10:37:08.211-0400 [DEBUG] waypoint: home configuration directory: path=/Users/user/Library/Preferences/waypoint
    2022-08-23T10:37:08.212-0400 [TRACE] waypoint: no API client provided, initializing connection if possible
    2022-08-23T10:37:08.212-0400 [TRACE] waypoint.server: Local server may be created later - server credentials optional
    2022-08-23T10:37:08.212-0400 [INFO] waypoint.server: attempting to source credentials and connect
    2022-08-23T10:37:08.214-0400 [DEBUG] waypoint.serverclient: connection information: address=IP.ADDR.FOR.WAYPOINT:9701 tls=false tls_skip_verify=false send_auth=true has_token=true
    2022-08-23T10:37:18.214-0400 [ERROR] waypoint: failed to create client: error=“context deadline exceeded”
    ! failed to create client: context deadline exceeded
    2022-08-23T10:37:18.214-0400 [TRACE] waypoint: stopping signal listeners and cancelling the context
    user@Users-MacBook-Pro-2 cicdtestproject %
2

Hi wjfrelo,

Do you mean that you’re expecting it to attempt to connect to DNS-URL-FOR-AWS.compute.amazonaws.com:9701, and it’s actually connecting to IP.ADDR.FOR.WAYPOINT:9701?

Is UsersNewContext the only context that you have have configured? Also, is IP.ADDR.FOR.WAYPOINT:9701 the loopback address, or is that the IP of one of your previously-configured servers?

We’ll also consider adding some debug logging to make it more clear which context is currently being used.

3

Thanks for the response @izaaklauer,

Do you mean that you’re expecting it to attempt to connect to DNS-URL-FOR-AWS.compute.amazonaws.com:9701 , and it’s actually connecting to IP.ADDR.FOR.WAYPOINT:9701 ? Correct

Is UsersNewContext the only context that you have have configured? Yes. But, we deleted all other contexts that were there prior and ensured it was the only context and default context.

Also, is IP.ADDR.FOR.WAYPOINT:9701 the loopback address, or is that the IP of one of your previously-configured servers? That is the IP of the remote Waypoint Server and it is the Advertise IP (i.e., waypoint server config-set).

@izaaklauer it appears that the context settings that we have set in the previous iterations of the default context is not changing properly.

You see the waypoint is trying this:

  • address=IP.ADDR.FOR.WAYPOINT:9701
  • tls=false. # This is different than the context
  • tls_skip_verify=false. # This is different than the context
  • send_auth=true
  • has_token=true

But, it should be this: