Day 2 action form rendering from Virtual machines list fails with "404 NOT_FOUND" error whereas the same from the deployment is success.
search cancel

Day 2 action form rendering from Virtual machines list fails with "404 NOT_FOUND" error whereas the same from the deployment is success.

book

Article ID: 376003

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Day 2 action form rendering fails with 404 NOT_FOUND error for non admin user and renders fine from the deployment.

1) Go to assembler
2) Go to Resources and then Virtual machines
3) Click on actions for Virtual machines and it throws "404 NOT_FOUND" error.

Environment

Aria Automation 8.17.x

Cause

  • This call most likely caused the issue:

https://{{host}}/form-service/api/forms/renderer/model?formType=requestForm&isUpdateAction=false&formId=&projectId={{projectID}}&resourceId={{resourceID}}&deploymentId=&sourceType=resource.action&sourceId=Cloud.vSphere.Machine.Compute.Disk.Resize

  • When this call is made from the machines datagrid, the parameter deploymentId is provided empty. When it is done from the deployment, the parameter deploymentId is not empty but the actual deployment ID is provided.

    From the har file provided it can clearly be seen that this request is the problem:

    https://<FQDN>/form-service/api/forms/renderer/model?formType=requestForm&isUpdateAction=false&formId=&projectId=<uuid>&resourceId=<uuid>&deploymentId=&sourceType=resource.action&sourceId=Cloud.vSphere.Machine.Compute.Disk.Resize
    {
        "timestamp": "2024-06-14T21:54:13.461+0000",
        "path": "/form-service/api/forms/renderer/model",
        "status": 404,
        "error": "Not Found",
        "message": "404 NOT_FOUND \"Failed to validate form source due to: \"; nested exception is org.springframework.web.server.ResponseStatusException: 404 NOT_FOUND",
        "requestId": "5715439f-129224",
        "@type": "org.springframework.web.server.ResponseStatusException",
        "cause": {
            "message": "404 NOT_FOUND",
            "@type": "org.springframework.web.server.ResponseStatusException"
        }
    }

 

Resolution

  • As a workaround, execute the day 2 operations in a deployment.
  • The problem is that the deployment id is null and our check fails. 
  • This is a known bug and it is fixed in 8.18.1 version

Additional Information