During deployment we call vm-host update to set overcommit racios. It works the first time but fails second time when VMs are defined.
2022-05-07-08:38:21 root DEBUG [localhost]: maas root vm-hosts read
2022-05-07-08:38:25 root DEBUG [localhost]: maas root version read
2022-05-07-08:38:28 root DEBUG [localhost]: maas root rack-controllers read hostname=infra1
2022-05-07-08:38:32 root DEBUG [localhost]: maas root vm-host update 1 memory_over_commit_ratio=10 cpu_over_commit_ratio=10
2022-05-07-08:39:22 root ERROR [localhost] Command failed: maas root vm-host update 1 memory_over_commit_ratio=10 cpu_over_commit_ratio=10
2022-05-07-08:39:22 root ERROR [localhost] STDOUT follows:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Error: Conflict Error</title>
</head>
<body>
<h2 class="p-heading--four">
Conflict error. Try your request again, as it will most likely succeed.
</h2>
</body>
</html>
It works fine in 3.1/stable
2022-05-07-08:07:03 root DEBUG [localhost]: maas root vm-hosts read
2022-05-07-08:07:07 root DEBUG [localhost]: maas root version read
2022-05-07-08:07:11 root DEBUG [localhost]: maas root rack-controllers read hostname=infra1
2022-05-07-08:07:14 root DEBUG [localhost]: maas root vm-host update 1 memory_over_commit_ratio=10 cpu_over_commit_ratio=10
2022-05-07-08:07:22 root DEBUG [localhost]: maas root machines read
2022-05-07-08:07:33 foundationcloudengine.layers.configuremaas INFO Machine juju-1 already exists in infra1
2022-05-07-08:07:33 root DEBUG [localhost]: maas root tags create name=juju
2022-05-07-08:07:36 root ERROR [localhost] Command failed: maas root tags create name=juju
2022-05-07-08:07:36 root ERROR [localhost] STDOUT follows:
{"name": ["Tag with this Name already exists."]}
2022-05-07-08:07:36 root ERROR [localhost] STDERR follows:
b''
2022-05-07-08:07:36 root DEBUG [localhost]: maas root tag update-nodes juju add=chnm3f
2022-05-07-08:07:40 foundationcloudengine.layers.configuremaas INFO Machine microk8s1-1 already exists in infra1
...
Could you please provide the complete list of CLI calls that lead to this?
Also, is anything else interacting with maas at the same time?
I can't reproduce the issue locally simply by issuing repeated `maas $profile vm-host $id update` calls