-
Notifications
You must be signed in to change notification settings - Fork 29
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Probably not a scenario that happens in production but during development this is something I do routinely. Seems like it might be a bug
- make a config for tunneller to dial a service by identity"
- make a service using the config from above
- create 2 service policies - one for an identity to dial the service, one for an identity to host the service
- start a golang program which binds the service
- make a request via the tunneller - see it 'work'...
- delete the service and the config
- recreate the service and the config (without restarting the golang program)
Observe this over and over:
time="2022-03-28T22:50:10Z" level=warning msg="failure creating Bind session to service my.svc" error="unable to find resource. http status code: 404, msg: {\"error\":{\"cause\":{\"code\":\"UNHANDLED\",\"message\":\"service with id FsKqVJu6H not found\"},\"code\":\"NOT_FOUND\",\"message\":\"The resource requested was not found or is no longer available\",\"requestId\":\"J.8mVLu8y\"},\"meta\":{\"apiEnrollmentVersion\":\"0.0.1\",\"apiVersion\":\"0.0.1\"}}\n"
service never rebinds.... restart the process and things work as expected
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working