CNR: I think I messed something up

[tlimoncelli]

CC @KaiSchwarz-cnic @AsifNawaz-cnic

Hi CNR folks!

Sorry to be a bother!

While doing some testing I accidentally created a large number of records in the CNR test domain. Now I can't remove them.

I get this message:

    integration_test.go:308: Error while updating zone "dnscontroltest-cnr.com". [549 Command failed; error adding record: record (dnscontroltest-cnr.com,NS,ns1.rrpproxy.net,300) exists (locked=0)]

Integration tests are failing as a result:

https://github.com/StackExchange/dnscontrol/actions/runs/12816559874/job/35741863939

Would you please take a look and see if you can unlock this domain? Feel free to delete any records in that zone... the test framework will fix things on the next run.

Thanks and my apologies!

Tom

[tlimoncelli]

Welp....

I waited 2 hours and tried again. The integration tests deleted the records and things started to work again.

Never mind!

[KaiSchwarz-cnic]

@tlimoncelli no problem, but in case we notice that happening more frequently, we'll have to further analyze the situation. You might want then to run our tests with the debugmode flag defined.

{
  "CNR": {
    "TYPE": "CNR",
    "apilogin": "your-cnr-account-id",
    "apipassword": "your-cnr-account-password",
    "apientity": "LIVE", // for the LIVE system; use "OTE" for the OT&E system
    "debugmode": "0", // set it to "1" to get debug output of the communication with our Backend System API
  }
}

We recommend setting it then to value "2" to have a very verbose output of the API communication. That would allows us to identify the error message of the respective API Calls.

-> CNR_DEBUGMODE is the env var related to that obviously (just for reference).