KV keys created in UI are added one prefix level up

[urog]

Overview of the Issue

When adding new prefixed keys (using the UI) under an existing prefix, the resulting keys are added one level up in the tree

Reproduction Steps

Steps to reproduce this issue, eg:

1. In the UI, create a new key: my/key with a value of 1
2. Navigate to the prefix my/
3. Add a new, prefixed, key: key2/key3 with a value of 1
4. Observe that we now have two top-level keys: my/key and key2/key3. The expected result is my/key and my/key2/key3

Consul info for both Client and Server

Client info

agent:
	check_monitors = 0
	check_ttls = 0
	checks = 3
	services = 3
build:
	prerelease =
	revision = 27de64da
	version = 1.10.0
consul:
	acl = disabled
	bootstrap = false
	known_datacenters = 1
	leader = true
	leader_addr = 10.152.0.10:8300
	server = true
raft:
	applied_index = 7345068
	commit_index = 7345068
	fsm_pending = 0
	last_contact = 0
	last_log_index = 7345068
	last_log_term = 775
	last_snapshot_index = 7336395
	last_snapshot_term = 775
	latest_configuration = [{Suffrage:Voter ID:643b6c47-88d1-7b99-83b8-88f87a9dfeed Address:10.152.0.11:8300} {Suffrage:Voter ID:46047727-5a0f-2df6-15a6-68213aaa086d Address:10.152.0.10:8300} {Suffrage:Voter ID:af50379b-c2a5-9f3d-a295-7f56704c488d Address:10.152.0.7:8300}]
	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 = Leader
	term = 775
runtime:
	arch = amd64
	cpu_count = 2
	goroutines = 1200
	max_procs = 2
	os = linux
	version = go1.16.5
serf_lan:
	coordinate_resets = 0
	encrypted = false
	event_queue = 0
	event_time = 33
	failed = 0
	health_score = 0
	intent_queue = 0
	left = 0
	member_time = 100492
	members = 12
	query_queue = 0
	query_time = 1
serf_wan:
	coordinate_resets = 0
	encrypted = false
	event_queue = 0
	event_time = 1
	failed = 0
	health_score = 0
	intent_queue = 0
	left = 0
	member_time = 29330
	members = 3
	query_queue = 0
	query_time = 1

Server info

agent:
	check_monitors = 0
	check_ttls = 0
	checks = 3
	services = 3
build:
	prerelease =
	revision = 27de64da
	version = 1.10.0
consul:
	acl = disabled
	bootstrap = false
	known_datacenters = 1
	leader = true
	leader_addr = 10.152.0.10:8300
	server = true
raft:
	applied_index = 7345068
	commit_index = 7345068
	fsm_pending = 0
	last_contact = 0
	last_log_index = 7345068
	last_log_term = 775
	last_snapshot_index = 7336395
	last_snapshot_term = 775
	latest_configuration = [{Suffrage:Voter ID:643b6c47-88d1-7b99-83b8-88f87a9dfeed Address:10.152.0.11:8300} {Suffrage:Voter ID:46047727-5a0f-2df6-15a6-68213aaa086d Address:10.152.0.10:8300} {Suffrage:Voter ID:af50379b-c2a5-9f3d-a295-7f56704c488d Address:10.152.0.7:8300}]
	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 = Leader
	term = 775
runtime:
	arch = amd64
	cpu_count = 2
	goroutines = 1200
	max_procs = 2
	os = linux
	version = go1.16.5
serf_lan:
	coordinate_resets = 0
	encrypted = false
	event_queue = 0
	event_time = 33
	failed = 0
	health_score = 0
	intent_queue = 0
	left = 0
	member_time = 100492
	members = 12
	query_queue = 0
	query_time = 1
serf_wan:
	coordinate_resets = 0
	encrypted = false
	event_queue = 0
	event_time = 1
	failed = 0
	health_score = 0
	intent_queue = 0
	left = 0
	member_time = 29330
	members = 3
	query_queue = 0
	query_time = 1

Operating system and Environment details

Ubuntu 18.04.5 LTS

matthew@dev-consul-nomad-servers-1007:~$ uname -a
Linux dev-consul-nomad-servers-1007 5.4.0-1044-gcp #47~18.04.2-Ubuntu SMP Mon May 17 03:48:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux```

[johncowen]

Thanks for the report @urog, much appreciated!

I just had a look to see how far back this went, and it seems to be a problem in the UI with the new 1.10.0 release (earlier than this is fine, so 1.9.x back), I'll see if we can get this fixed up for 1.10.1

Thanks again for the submitting the issue 👍

[shantanugadgil]

This is a very amusing bug to be faced with, especially after the major upgrade and the UI change! 👀
Hope a beta2 (or the next GA) gets released soon with this fixed in! ⚡

[johncowen]

😬 thanks all for reporting this! There's a fix in the works ^ . I'm just staring at it a little harder before I write it up. Fix should be good to go in our next 1.10.x release.

[shantanugadgil]

New release anytime soon? 😀 😁

[blake]

New release anytime soon? 😀 😁

https://github.com/hashicorp/consul/releases/tag/v1.10.1 was just released which contains this fix.

[shantanugadgil]

Awesome!!!