check-sync, sync-from, sync-to is failing on L3VPN service when device is OOS: Hi All,Steps I followed:1. Deployed a L3 VPN service on device-4 and device-6. Service got deployed successfully2. manually made changes to device-6 to make it out-of-sync3. Verified that device shows out-of-sync4. Edited the L3 VPN service, it failed as expected with error Device-6 out-of-sync5. from the error shown on CNC UI, tried to do a sync-from for the device-6, it didn't go throughBehavior observed: Changes got pulled from device-6(validated taht RFS node is in-sync with device-6) , but still L3VPN service is showing device out-of-sync message.expected: L3 VPN should show in-sync trueCW: admin/Ovatest123@CFS:admin/Ovatest123@RFS-62:admin/Ovatest123@RFS-63:admin/Ovatest123@Thanks,Kanchan
Hi Kanchan,When you bring the device back in-sync, did you do a service re-deploy for your L3 service?Thanks,Isaac KimHi Isaac,I did perform a sync-from or sync-to operation, commands performed are attached.Question here is: once my device is in-sync state, is it mandatory to perform re-deploy? if yes, then what sync-from or sync-to does?Also, when I perform re-deploy dry-run, I get following outputadmin@ncs# l3vpn-ntw vpn-services vpn-service L3VPN_NM-IGP-IPV4 re-deploy dry-runcli {  lsa-node {    name rfs-63    data devices {          device xrv9k-PE6 {            config {              route-policy PASS_ALL {       -        value " passr       ";       +        value pass;              }            }          }        }  }}But I didn't change anything about route-policy, I changed the loopback address. expected?Hi Kanchan,Seems like UI bug, you can see from the text box: CLI command is : l3vpn-ntw vpn-servicesvpn-service L3VPN-NM-IGP-IPV4 error-recovery sync-direction sync-fromThis is error recovery action, not a device sync action.After doing sync-from on device, I would re-deploy the service to bring the "failed" service plan back into "success" state.Thanks,Isaac KimThanks Isaac.So on UI, it should not say "pushing to the device" as it it error-recovery action, right?also, is there a doc that explains what error recovery action is?Hi Isaac, I performed re-deploy and service came back to success state. Before re-deploying I checked re-deploy dry-run to verify what will be re-deployed, screenshot attached. But when I was editing the service, I changed loopback address on one device but CLI shows different thing.Hi Kanchan,I apologize for the very delayed response.For more details on error recovery you can look here : For the redeploy issue, this seems unrelated to the current issue described on the ticket. Please feel free to open a new JSD ticket for this!Thanks,Isaac KimPlease open new JSD if you encounter this again. Thank you!