API & Integration

Reply
Accepted Solution

Extensible attribute '<EA>' is not allowed for this operation

[ Edited ]
bonhxh
Techie
Posts: 4
548     0

Hello,

 

I am new to the community and we are working on leveraging WAPI for automated network allocation.

I have searched across the forum but couldn't find an answer (apologies if I missed the information).

 

I am getting this error when trying to allocate a network using WAPI (2.6.1)

 

"json": {

"Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Extensible at

tribute 'Application' is not allowed for this operation)",

"code": "Client.Ibap.Data.Conflict",

"text": "Extensible attribute 'Application' is not allowed for this operation"

}

 

I have provided all the mandatory fields in the POST body and 'Application' is not a mandatory field.

 

data: |

 

{

  "network": "func:nextavailablenetwork:10.251.251.224/28,29",

  "network_view": "default",

  "extattrs": {

    "Created By": {

      "value": "Test"

    },

    "Creation Date": {

      "value": "2018-11-05T13:19:00Z"

    },

    "Customer": {

      "value": "Test"

    },

    "Env": {

      "value": "Prod"

    },

    "Site": {

      "value": "WAN"

    },

  }

}

uri:

  url: "{{ infoblox_url }}network?_return_fields%2B=network,extattrs&_return_as_object=1"

  method: POST

  headers:

 

    Accept: "application/json;odata=verbose"

  body: "{{ data }}"

 

Can you please assist? any help will be much appreciated Smiley Happy

 

Thank you.

 

 

 

Re: Extensible attribute '<EA>' is not allowed for this operation

Adviser
Posts: 63
548     0

Can you check the settings on the "Application"EA, and verify that it it's "Restricted to Objects" either is empty, or the list contains IPv4 Network.

 

Highlighted

Re: Extensible attribute '<EA>' is not allowed for this operation

bonhxh
Techie
Posts: 4
548     0

Hi MRichard

 

Thanks for the reply.

 

Yes the list contains IPv4 Network

 

Application
List
 
No
IPv4 Network,IPv4 Network Container,IPv6 Network,IPv6 Network Container
Yes

Re: Extensible attribute '<EA>' is not allowed for this operation

bonhxh
Techie
Posts: 4
549     0

The EA 'Application' is inherited.

 

I have tried the following but still getting the same error

"extattrs": {

  "Application": {

    "inheritance_operation": "INHERIT",

    "descendants_action": {

      "option_with_ea": "RETAIN",

      "option_without_ea": "NOT_INHERIT"

    },

    "value": "AD"

  },

  "Creation Date": {

    "value": "2018-11-05T13:19:00Z" 

  },

  ...

}

 

If I specify "inheritance_operation": "DELETE" (although I want the EA value to be inherited)

"extattrs": {

  "Application": {

    "inheritance_operation": "DELETE",

    "descendants_action": {

      "option_with_ea": "RETAIN",

      "option_without_ea": "NOT_INHERIT"

    },

    "value": "AD"

  },

  "Creation Date": {

    "value": "2018-11-05T13:19:00Z" 

  },

  ...

}

then the error messages changes to

"json": {

"Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Extensible attribute 'Creation Date' is not allowed for this operation)",

"code": "Client.Ibap.Data.Conflict",

"text": "Extensible attribute 'Creation Date' is not allowed for this operation"

},

which is odd because EA 'Creation Date' is mandatory, it is not inherited and corresponding 'Restricted to Objects' is empty.

 

 

Re: Extensible attribute '<EA>' is not allowed for this operation

bonhxh
Techie
Posts: 4
549     0

Our Infoblox admin made a mistake in the permission settings...

The fix for us was to select API(WAPI/PAPI only) (instead of Cloud API) in the user group permissions

Permissions.png

 

Terrible experience with Infoblox support who could not find the issue after four weeks...

We did escalate several times and eventually got the Systems Engineering Manager involved who found the root cause very quickly.

 

 

 

Showing results for 
Search instead for 
Do you mean 

Recommended for You