You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using service checks on a session to lock a key/value, the service checks are not rendered correctly in the lock session summary.
Reproduction Steps
Create a session with a service check e.g. curl -X PUT -d '{"Name": "myservice", "ServiceChecks":[{"ID":"myServiceCheck"}]}' http://localhost:8500/v1/session/create
Lock a value using the session that was created e.g. curl -X PUT -d '{"Application": "test", "host":"somehost", "port":1234}' http://localhost:8500/v1/kv/example/key?acquire=933fd1dd-83fd-e3be-dab4-f5dfab2e33eb
View the key value in the UI by navigating to Key/Value -> example -> key and see the service check is rendered as a generic object obscuring the check ID.
Consul info for both Client and Server
Client and server running 1.10.0
The text was updated successfully, but these errors were encountered:
This looks to be due to the UI and tests expecting the response to be formatted as per the incorrect documentation noted in #10752.
It may be sufficient to use the ID field directly when joining on to the list of checks for most use cases, it would also be necessary to update the test data that covers this use case.
Overview of the Issue
When using service checks on a session to lock a key/value, the service checks are not rendered correctly in the lock session summary.
Reproduction Steps
curl -X PUT -d '{"Name": "myservice", "ServiceChecks":[{"ID":"myServiceCheck"}]}' http://localhost:8500/v1/session/create
curl -X PUT -d '{"Application": "test", "host":"somehost", "port":1234}' http://localhost:8500/v1/kv/example/key?acquire=933fd1dd-83fd-e3be-dab4-f5dfab2e33eb
Consul info for both Client and Server
Client and server running 1.10.0
The text was updated successfully, but these errors were encountered: