IPv6 object update error
Hello! I'm trying to update an IPv6 object in RIPE databease via API and I'm getting an error: <errormessages> <errormessage severity="Error" text=""%s:" attribute not allowed for resources with "%s:" status"> <args value="mnt-lower"/> <args value="ASSIGNED"/> </errormessage> <errormessage severity="Info" text="Value %s converted to %s"> <attribute name="source" value="RIPE"/> <args value="ripe"/> <args value="RIPE"/> </errormessage> </errormessages> I started getting this error about a month ago. Regards Jure
On 4 Jul 2024, at 12:36, Jure Knez via db-wg <db-wg@ripe.net> wrote:
Hello!
I'm trying to update an IPv6 object in RIPE databease via API and I'm getting an error:
<errormessages> <errormessage severity="Error" text=""%s:" attribute not allowed for resources with "%s:" status"> <args value="mnt-lower"/> <args value="ASSIGNED"/> </errormessage> <errormessage severity="Info" text="Value %s converted to %s"> <attribute name="source" value="RIPE"/> <args value="ripe"/> <args value="RIPE"/> </errormessage> </errormessages>
I started getting this error about a month ago.
Does the existing object have: inet6num: 2001:db8::1 status: ASSIGNED and the new object: inet6num: 2001:db8::1 status: ASSIGNED mnt-lower: XYZ-MNT as the error says that one cannot have a mnt-lower when status == ASSIGNED. Showing your actual object, before and after can be helpful if you need more details. Greets, Jeroen
The existing object have: inet6num: 2001:1470:xxx:/48 status: ASSIGNED mnt-by: xxx-MNT mnt-lower: xxx-MNT mnt-routes: xxx-MNT created: 2021-04-22T06:28:57Z last-modified: 2021-04-22T06:28:57Z source: RIPE The new: <object type="inet6num"> <link xlink:type="locator" xlink:href=["https://rest.db.ripe.net/ripe/inet6num/2001:1470:xxx::/48"](https://rest.db.ripe.net/ripe/inet6num/2001:1470:xxx::/48)/> <source id="ripe"/> <primary-key> <attribute name="inet6num" value="2001:1470:xxx::/48"/> </primary-key> <attributes> <attribute name="inet6num" value="2001:1470:xxx::/48"/> <attribute name="status" value="ASSIGNED"/> <attribute name="mnt-by" value=“xxx-MNT" referenced-type="mntner"> <link xlink:type="locator" xlink:href=["https://rest.db.ripe.net/ripe/mntner/xxx-MNT"](https://rest.db.ripe.net/ripe/mntner/xxx-MNT)/> </attribute> <attribute name="mnt-lower" value=“xxx-MNT" referenced-type="mntner"> <link xlink:type="locator" xlink:href=["https://rest.db.ripe.net/ripe/mntner/xxx-MNT"](https://rest.db.ripe.net/ripe/mntner/xxx-MNT)/> </attribute> <attribute name="mnt-routes" value=“xxx-MNT" referenced-type="mntner"> <link xlink:type="locator" xlink:href=["https://rest.db.ripe.net/ripe/mntner/xxx-MNT"](https://rest.db.ripe.net/ripe/mntner/xxx-MNT)/> </attribute> <attribute name="source" value="RIPE"/> </attributes> </object> Regards
On 4 Jul 2024, at 13:13, Jeroen Massar <jeroen@massar.ch> wrote:
On 4 Jul 2024, at 12:36, Jure Knez via db-wg <db-wg@ripe.net> wrote:
Hello!
I'm trying to update an IPv6 object in RIPE databease via API and I'm getting an error:
<errormessages> <errormessage severity="Error" text=""%s:" attribute not allowed for resources with "%s:" status"> <args value="mnt-lower"/> <args value="ASSIGNED"/> </errormessage> <errormessage severity="Info" text="Value %s converted to %s"> <attribute name="source" value="RIPE"/> <args value="ripe"/> <args value="RIPE"/> </errormessage> </errormessages>
I started getting this error about a month ago.
Does the existing object have: inet6num: 2001:db8::1 status: ASSIGNED
and the new object: inet6num: 2001:db8::1 status: ASSIGNED mnt-lower: XYZ-MNT
as the error says that one cannot have a mnt-lower when status == ASSIGNED.
Showing your actual object, before and after can be helpful if you need more details.
Greets, Jeroen
Hi Jure,
On 4 Jul 2024, at 12:36, Jure Knez via db-wg <db-wg@ripe.net> wrote:
... I started getting this error about a month ago.
This change was introduced in the Whois 1.112 release on 16th May: "Don't allow "mnt-lower" on assignments" https://apps.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-112 Because there is only one level of assignments allowed in the RIPE database (i.e. nothing more specific below an assignment), the "mnt-lower:" attribute is not necessary and has no effect. Regards Ed Shryane RIPE NCC
Hello Edward Thank you for this information. Regards Jure
On 4 Jul 2024, at 14:14, Edward Shryane <eshryane@ripe.net> wrote:
Hi Jure,
On 4 Jul 2024, at 12:36, Jure Knez via db-wg <db-wg@ripe.net> wrote:
... I started getting this error about a month ago.
This change was introduced in the Whois 1.112 release on 16th May: "Don't allow "mnt-lower" on assignments" https://apps.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-112
Because there is only one level of assignments allowed in the RIPE database (i.e. nothing more specific below an assignment), the "mnt-lower:" attribute is not necessary and has no effect.
Regards Ed Shryane RIPE NCC
participants (3)
-
Edward Shryane -
Jeroen Massar -
Jure Knez