You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.
Great gem, I have tried several features and they are working fine, but I have found one that is not working as expected.
It is the update for a PTR record:
@unclebilly
I have verified the issues opened and I have found a similar one, issue #43, but with Infoblox::Ptr.find
The WAPI version that we are using is 2.0:
[1] pry(main)> Infoblox.wapi_version
=> "2.0"
May you please have a look at this issue also, maybe offer a workaround.
Great gem, I have tried several features and they are working fine, but I have found one that is not working as expected.
It is the update for a PTR record:
connection = Infoblox::Connection.new(username: 'user', password: 'password1', host: '10.1.1.1', ssl_opts: {verify: false}, timeout: 7)
ptr_record = Infoblox::Ptr.find(connection, {ptrdname:"fqdn_host_name.com", ipv4addr: "10.97.161.5"}).first
=> #<Infoblox::Ptr:0x000055b582cefe40
@_ref="record:ptr/ZG5zLmJpbmRfcHRyJC5fZGVmYXVsdC5hcnBhLmluLWFkZHIuMTAuOTcuMTYxLjUuZGUxYXN3OTg3MDJzLTUubmV0LnZvZGFmb25lLmNvbQ:5.161.97.10.in-addr.arpa/default",
@connection=#<Infoblox::Connection:23480 @host="https://10.1.1.1">,
@disable=false,
@extattrs={},
@ipv4addr="10.97.161.5",
@ipv6addr="",
@name="5.161.97.10.in-addr.arpa",
@ptrdname="fqdn_host_name.com",
@view="default",
@zone="161.97.10.in-addr.arpa">
ptr_record.ipv4addr = "10.97.161.6"
Error received:
pry(main)> ptr_record.put
Infoblox::Error: Error: 400 { "Error": "AdmConProtoError: Invalid value for ipv6addr: "": Invalid IPv6 address",
"code": "Client.Ibap.Proto",
"text": "Invalid value for ipv6addr: "": Invalid IPv6 address"
}
I do not understand why is showing error "Invalid value for ipv6addr" when I am actually updating an ipv4 address.
The text was updated successfully, but these errors were encountered: