Comment 29 for bug 1993836

"As far as fixing the issue from MAAS, it seems a bit odd that we could receive a status for modules-final and other requests will follow, but if we were to fix it on the MAAS side, would returning a 409 for the modules-final request result in retries from cloud-init?"

To answer your specific question, yes, "raise_for_status()" from requests is used, which will raise on http responses 400-599. We'll catch this and then retry until time/tries is up.

I'm not sure I follow though. How would this be used to help the situation? Do you know which message specifically is the problematic one? Why is it not expected to be received as soon as it is?