Comment 5 for bug 1626334

Andres,

When I tried the manual release, it worked. These are not new systems that we have been using with the CI automated builds and hadn't seen prior to that. We also haven't had a change since moving to release version of maas. But after looking at the timestamps, I am now realizing that there was an issue with the vCenter around the time of these failures last week and we were getting 203 back from trying to access it. The issue went away after restarting the vCenter.

So, this is most likely this scenario that you mentionned "the client cannot actually connect to the vCenterAPI". Here are the power parameters below but you can mark this one as invalid and I'll reopen if I recreate with any data pointing away from the vCenter.

ubuntu@maas2-integration:~$ maas root machines power-parameters id=4y4fma
Success.
Machine-readable output follows:
{
    "4y4fma": {
        "power_uuid": "5007125f-76fe-1e10-a20f-9a9a31b0fa98",
        "power_vm_name": "integrationnedge0",
        "power_protocol": "https+unverified",
        "power_port": null,
        "power_user": "administrator@*******.***",
        "power_pass": "**********",
        "power_address": "10.244.192.131"
    }
}