Hence we result in having a 404 response, as the method "DELETE" does not exist for that call, only GET, PUT and PATCH.
{
"message": "No value present",
"statusCode": 404,
"errorCode": 0
}
Resolution
If the Network has been configured as an Input on the Cloud Template then you can use "Update" as Deployment Day-2 option to change the Network configuration, which however may recreate the VM:
If this is not possible or desired, we can unregister the VM from Aria Automation and re-onboard it to a new deployment once the Networks are manually unlinked in vSphere:
In Service Broker, under Consume > Deployments > Virtual Machines > Managed > Three Dots next to Selected VM > Unregister
The chosen VM will go from "Deployed" to "Discovered" Origin and will be found under the "Discovered" tab rather than "Managed" once the Data Collection completes on the vCenter Cloud Account (10 minute cycle), since we have removed the VM from Aria Automation management.
Make your changes, removing Networks manually from the machine etc. while waiting for this Data Collection cycle to start.
Once the Data Collection is completed and the VM is in a "Discovered" state, select the VM using the Checkbox on the left and click "Onboard".
Select the type of Onboarding and give the Deployment a name if you wish.
Click "Onboard".
Once complete the VM should now show in the "Managed" section again.
We can go back to our Deployments from above and find the Deployment with the name we just set.
We can see the VM onboarded with no additional existing vSphere backed Networks.