| 2023-09-04 08:18:22 |
Marian Gasparovic |
description |
Since Aug 31 we started to receive this error when we deploy machines with Terraform MAAS provider
Error: ServerError: 409 Conflict (<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "[http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd](http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd)">
<html xmlns="[http://www.w3.org/1999/xhtml](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 happens only in our long running MAAS which serves six "silos". We have another two silos where we deploy new MAAS every time, we did not encounter this error there.
Both long running and freshly deployed MAAS's are 3.2.9
This seems like an issue which happens after MAAS is up for some time. We did not encounter it before Aug 31 and many times since. I will update with exact number after I triage all.
Typical example is here
https://oil-jenkins.canonical.com/artifacts/d356f7bc-91ad-4a86-a5e8-30d16af4f379/index.html
I will upload MAAS logs later.
I was observing one of the runs when it was happening. It was supposed to deploy six machines using tag as constraint. I could see 6 machines with tags available but during TF run it started to deploy only five4 of them, it did not touch the sixth. |
Since Aug 31 we started to receive this error when we deploy machines with Terraform MAAS provider
Error: ServerError: 409 Conflict (<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "[http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd](http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd)">
<html xmlns="[http://www.w3.org/1999/xhtml](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 happens only in our long running MAAS which serves six "silos". We have another two silos where we deploy new MAAS every time, we did not encounter this error there.
Both long running and freshly deployed MAAS's are 3.2.9
This seems like an issue which happens after MAAS is up for some time. We did not encounter it before Aug 31 and many times since. I will update with exact number after I triage all.
Typical example is here
https://oil-jenkins.canonical.com/artifacts/d356f7bc-91ad-4a86-a5e8-30d16af4f379/index.html
I will upload MAAS logs later.
I was observing one of the runs when it was happening. It was supposed to deploy six machines using tag as constraint. I could see 6 machines with tags available but during TF run it started to deploy only five4 of them, it did not touch the sixth.
We hit this bug 34 times in 81 test runs in four days. |
|
