At 16:15 07/08/2015 +0200, denis wrote: Thanks! Good workaround. -Hank
HI Hank
Just a note for the future. If you find yourself in this situation again you can try doing an update on the object first to remove the problematic "remarks:" attribute and then delete the object in a second step. This work around often helps in these situations. It gets around the problems of weird behaviour of mail clients.
cheers denis
On 07/08/2015 11:01, Hank Nussbacher wrote:
At 10:32 07/08/2015 +0200, Edward Shryane wrote:
Was finally able to delete it from a 3rd mail client - Outlook (Office 365 in the cloud).
Feel free to try from Gmail to recreate the bug.
-Hank
Good morning Hank,
it appears that your mail client is wrapping the remarks line when it reaches the URL. This produces an invalid RPSL object, and doesn't match the version in the database.
Can you check your mail client settings?
A workaround is to use another update mechanism (Syncupdates, webupdates or the REST API).
Regards
Ed Shryane RIPE NCC
On 7 Aug 2015, at 10:16, Hank Nussbacher <hank@efes.iucc.ac.il> wrote:
On Fri, Aug 07, 2015 at 10:56:17AM +0300, Hank Nussbacher wrote:
> Are you absolutely sure that this is not due to some other reasons? > I have "reproduced" your object under my ip space just a minute ago and > was able to delete it without any problems via email interface. The only > important difference is that it doesn't have LEGACY status. I have > created it one more time - take a look at 83.230.58.0/24. Just let me > know if you see any meaningful differences to 192.114.48.0/20.
Indeed your object looks correct and has the proper remarks
At 10:05 07/08/2015 +0200, Piotr Strzyzewski wrote: line. Someone
else encountered the same issue with a legacy object so the bug might be specific to LEGACY objects only.
I have created similar object under LEGACY space. Take a look at the 157.158.200.0/24. I was also able to delete it with email interface. Will keep them both for one day.
Try deleting the 192.114.48.0/20 object (in correct pw). I get:
Delete FAILED: [inetnum] 192.114.48.0 - 192.114.63.255
inetnum: 192.114.48.0 - 192.114.63.255 netname: ISRAEL-SMALL-BLOCK10 descr: Israel Inter-University Computation Center country: IL admin-c: HN293-RIPE tech-c: HN293-RIPE org: ORG-IIIC1-RIPE status: LEGACY remarks: For information on "status:" attribute read https: //www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources mnt-by: AS378-MNT mnt-lower: AS378-MNT changed: hank@mail.iucc.ac.il 20050515 created: 1970-01-01T00:00:00Z last-modified: 2014-05-27T13:18:49Z source: RIPE
***Error: Authorisation for [inetnum] 192.114.48.0 - 192.114.63.255 failed using "mnt-by:" not authenticated by: AS378-MNT
***Error: Authorisation for [inetnum] 192.0.0.0 - 192.255.255.255 failed using "mnt-lower:" not authenticated by: RIPE-NCC-HM-MNT
***Error: Authorisation for [inetnum] 192.0.0.0 - 192.255.255.255 failed using "mnt-by:" not authenticated by: RIPE-NCC-HM-MNT
***Error: Object [inetnum] 192.114.48.0 - 192.114.63.255 doesn't match version in database
See last error.
I also get:
DELETE REQUESTED FOR:
inetnum: 192.114.48.0 - 192.114.63.255 netname: ISRAEL-SMALL-BLOCK10 descr: Israel Inter-University Computation Center country: IL admin-c: HN293-RIPE tech-c: HN293-RIPE org: ORG-IIIC1-RIPE status: LEGACY remarks: For information on "status:" attribute read https://www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources mnt-by: AS378-MNT mnt-lower: AS378-MNT changed: hank@mail.iucc.ac.il 20050515 created: 1970-01-01T00:00:00Z last-modified: 2014-05-27T13:18:49Z source: RIPE
--- OBJECT MODIFICATION REQUESTED:
@@ -8,3 +8,4 @@ status: LEGACY -remarks: For information on "status:" attribute read https://www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources +remarks: For information on "status:" attribute read +https: //www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources mnt-by: AS378-MNT
-Hank