)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":38059,"name":"Anoop Kumar Shukla","display_name":"Anoop Shukla","email":"anoop.shukla@netapp.com","username":"anoop2","status":"NetApp"},"change_message_id":"863f30395602bf9f1b8fb723d00c3f7f3f1a05eb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f6702695_77ffa11e","updated":"2026-06-11 17:08:05.000000000","message":"Couple of comments.","commit_id":"d9257ddef232bf15aed7dc700fa2fa39ffc20116"}],"specs/release_independent/service-startup-reconciliation.rst":[{"author":{"_account_id":38059,"name":"Anoop Kumar Shukla","display_name":"Anoop Shukla","email":"anoop.shukla@netapp.com","username":"anoop2","status":"NetApp"},"change_message_id":"863f30395602bf9f1b8fb723d00c3f7f3f1a05eb","unresolved":true,"context_lines":[{"line_number":141,"context_line":"share instances), the reconciler retries the corresponding driver"},{"line_number":142,"context_line":"delete call. Delete operations are expected to be idempotent: if the"},{"line_number":143,"context_line":"resource was already removed, the driver should succeed or indicate"},{"line_number":144,"context_line":"the resource is gone. On success, mark ``deleted``. On failure, set"},{"line_number":145,"context_line":"``error_deleting`` (or ``error`` for share servers)."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"**Mark error (all resource types)**"},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"cdc3b5fc_4909e4d1","line":145,"range":{"start_line":144,"start_character":52,"end_line":145,"end_character":52},"updated":"2026-06-11 17:08:05.000000000","message":"So this will not be force deleted? but the attempt to redelete on every cycle and still fail if something goes wrong on driver side?","commit_id":"d9257ddef232bf15aed7dc700fa2fa39ffc20116"},{"author":{"_account_id":38059,"name":"Anoop Kumar Shukla","display_name":"Anoop Shukla","email":"anoop.shukla@netapp.com","username":"anoop2","status":"NetApp"},"change_message_id":"863f30395602bf9f1b8fb723d00c3f7f3f1a05eb","unresolved":true,"context_lines":[{"line_number":200,"context_line":"``ensuring`` status; this reconciliation processes shares in"},{"line_number":201,"context_line":"transient statuses. Neither will act on a resource the other is"},{"line_number":202,"context_line":"handling. The reconciliation thread starts after"},{"line_number":203,"context_line":"``ensure_driver_resources()`` completes, but the two can also run"},{"line_number":204,"context_line":"independently (e.g., if the ensure shares API is invoked later)"},{"line_number":205,"context_line":"without interference."},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"Active/Active HA coordination"}],"source_content_type":"text/x-rst","patch_set":1,"id":"468d6314_66ebc6a8","line":204,"range":{"start_line":203,"start_character":41,"end_line":204,"end_character":13},"updated":"2026-06-11 17:08:05.000000000","message":"Will this create race conditions between the ensure share using states that are being updated by reconciliation thread?","commit_id":"d9257ddef232bf15aed7dc700fa2fa39ffc20116"}]}