UI: Key / Value search is stuck on subsequent screens

[mochery]

Overview of the Issue

In the key / value search, when you search for a term then click on found key the search is stuck on the next screen.

Reproduction Steps

Steps to reproduce this issue, eg:

1. Browse to Key/Value
2. Search for a Key
3. Click on Key
4. Observe the Search is still filtering on the previous search
   
   

Consul info for both Client and Server

Client info

agent:
        check_monitors = 0
        check_ttls = 0
        checks = 1
        services = 1
build:
        prerelease =
        revision = 2308c75e
        version = 1.12.3
        version_metadata =
consul:
        acl = enabled
        known_servers = 3
        server = false
runtime:
        arch = amd64
        cpu_count = 2
        goroutines = 76
        max_procs = 2
        os = linux
        version = go1.18.1
serf_lan:
        coordinate_resets = 0
        encrypted = true
        event_queue = 0
        event_time = 11173
        failed = 1
        health_score = 0
        intent_queue = 0
        left = 0
        member_time = 135306
        members = 314
        query_queue = 0
        query_time = 15

Server info

agent:
        check_monitors = 1
        check_ttls = 0
        checks = 2
        services = 2
build:
        prerelease =
        revision = 2308c75e
        version = 1.12.3
        version_metadata =
consul:
        acl = enabled
        bootstrap = false
        known_datacenters = 3
        leader = false
        leader_addr = ...
        server = true
raft:
        applied_index = 228784916
        commit_index = 228784916
        fsm_pending = 0
        last_contact = 26.026247ms
        last_log_index = 228784916
        last_log_term = 2414
        last_snapshot_index = 228774823
        last_snapshot_term = 2414
        latest_configuration = ...
        latest_configuration_index = 0
        num_peers = 2
        protocol_version = 3
        protocol_version_max = 3
        protocol_version_min = 0
        snapshot_version_max = 1
        snapshot_version_min = 0
        state = Follower
        term = 2414
runtime:
        arch = amd64
        cpu_count = 4
        goroutines = 1295
        max_procs = 4
        os = linux
        version = go1.18.1
serf_lan:
        coordinate_resets = 0
        encrypted = true
        event_queue = 0
        event_time = 11173
        failed = 1
        health_score = 0
        intent_queue = 0
        left = 0
        member_time = 135306
        members = 314
        query_queue = 0
        query_time = 15
serf_wan:
        coordinate_resets = 0
        encrypted = true
        event_queue = 0
        event_time = 1
        failed = 0
        health_score = 0
        intent_queue = 0
        left = 0
        member_time = 6421
        members = 9
        query_queue = 0
        query_time = 1

Operating system and Environment details

Client and Server on 1.12.3. Have another cluster with enterprise with the same issue.

[mugen6]

This bug was introduced in Consul v1.20. We are running Consul v1.11.11 to avoid it.

I'm surprised this issue doesn't have more comments because it is quite annoying.

[samcarpentier]

We are also experiencing this bug with Consul OSS v1.14.4. Extremely annoying when you have a log of folders in the hierarchy... This deserves more attention.

[mugen6]

Any update on this please? I just tested the latest version and it's still there.