Infoblox IPAM Integration fails with HTTP 404 and "Instance matched a schema it should not have" in Aria Automation

Products

• VCF Automation

Issue/Introduction

When attempting to provision resources or test Cloud Templates using the external Infoblox IPAM integration, users may experience the following issues:

• Deployments fail during the IP allocation phase with the following error surfaced by the extensibility action: IP ALLOCATE_SPECIFIC_IP failed: Action run failed with the following error: "('Error allocating in network or range: Infoblox HTTP request failed with: 404 Client Error: Not Found for url: [URL]"

• When iterating on a blueprint and clicking Test in Assembler, the UI returns a generic validation error: "Instance matched a schema it should not have"

Environment

 

• Aria Automation 8.18

• Infoblox IPAM Plugin version 1.5.4

• Cloud Templates utilizing external IPAM range assignments

 

Cause

There are two distinct configuration issues triggering this sequence of errors:

1. HTTP 404 WAPI URL Error: The Aria Automation appliance is successfully reaching the Infoblox Grid Master, but the constructed REST API endpoint path is invalid. The Infoblox plugin dynamically concatenates the "Hostname" and "WAPI Version" provided in the integration settings. If the Hostname input contains a protocol prefix (e.g., https://) or a trailing slash, the script generates a malformed URL (e.g., https://https://[HOSTNAME]/wapi/...), resulting in a 404 rejection from the Infoblox server.

2. Schema Validation Error: The Cloud Template (blueprint) contains a structural configuration conflict. The Assembler engine translates the YAML canvas into a JSON payload and validates it against strict internal schemas before deployment. If the YAML defines mutually exclusive or forbidden network properties simultaneously (e.g., passing unsupported properties like macAddress alongside a specific IPAM assignment type on Cloud.Machine or Cloud.vSphere.Network resources), the backend explicitly rejects the payload.

Resolution

To resolve these issues, sanitize the integration inputs and isolate the YAML schema conflict.

Part 1: Correct the Infoblox Integration Configuration

1. In Aria Automation, navigate to Assembler > Infrastructure > Connections > Integrations.

2. Open the Infoblox integration configuration.

3. Ensure the Hostname field contains only the FQDN or IP address (remove any https:// prefixes or / suffixes).

4. Verify the WAPI Version exactly matches the version running on your Infoblox Grid Master.

5. Click Validate to ensure connectivity, then Save.

Part 2: Isolate and Correct the Blueprint Schema Conflict Because the UI error is generic, you must use browser tools to identify the exact line causing the failure.

1. Open your web browser's Developer Tools (usually F12) and navigate to the Network tab.

2. In the Aria Automation Assembler UI, click Test on the failing Cloud Template.

3. Locate the failed API POST request (often directed to /blueprint/api/blueprint-requests) in the Network tab.

4. Inspect the Response body. Expand the errors array.

5. Look for the jsonPointer or path value (e.g., /resources/Cloud_Machine_1/properties/networks/0/assignment). This explicit path identifies the exact property in your YAML causing the schema violation.

6. Remove or correct the conflicting property in the Cloud Template YAML and re-test.