Failed service with OSS Device allowing service update changes on other Service node: Hi Team,Please help to check and confirm that the following behavior of the corefp is expected.Steps to reproduce:1. Create a failed L3VPN service with one of the service node as OOS with commit-async.2. Edit the service field of an another service node that is up and online3. Perform commit-changes (no commit-queues)4. User get the update successfull message from the CNC5. The update is also able to be seen in the node that is up and online.
 NCS Version : 5.5.2.3Device Model and Version: XRV9K - 7.1.2The behavior has been found the same for both L3VPN and L2VPNHi Dinesh,I was unable to reproduce the issue directly on NSO. Can you please share the plan details on NSO itself to confirm plan is still failed? If its reached and one of the nodes is still unreachable, then can you also share the exact steps for reproduction.Thanks,RegiHi Regi,Please do find the plan status of the service - L2VPN:admin@ncs% run show l2vpn-ntw vpn-services vpn-service-plan L2VPN plan | tab                                                                            POST                       BACK                                                    ACTIONTYPE                  NAME TRACK GOAL STATUS CODE   STATE                   STATUS  WHEN         ref STATUS----------------------------------------------------------------------------------------------------------------------------------------------------------------self                  self false -   -        init                    reached 2021-08-10T16:46:29 -  -                                     ready                   failed  2021-08-10T16:46:42 -  -ietf-l2vpn-ntw-nano-services:vpn-node PE-A false -   TSDN-L2VPN-302 init                    reached 2021-08-10T16:46:29 -  -                                     ietf-l2vpn-ntw-nano-services:config-apply reached 2021-08-10T16:46:29 -  -                                     ready                   failed  2021-08-10T16:46:35 -  -ietf-l2vpn-ntw-nano-services:vpn-node PE-C false -   -        init                    reached 2021-08-10T16:46:29 -  -                                     ietf-l2vpn-ntw-nano-services:config-apply reached 2021-08-10T16:46:29 -  -                                     ready                   reached 2021-08-10T16:46:41 -  -plan failedplan error-info message "Network Element Driver: device PE-A: out of sync"                                                      IMPACTEDTYPE    NAME CODE      SEVERITY RECOMMENDED ACTION                       DEVICE  CONTEXT NAME    CONTEXT MSG--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------local-site PE-A TSDN-L2VPN-302 ERROR   Check sync between device and NSO, and perform recovery steps. PE-A   Device out of sync Network Element Driver: device PE-A: out of syncadmin@ncs%The reproducing steps are the same as exactly mentioned as follows. Kindly have a check.Thanks,DineshHi Dinesh,The plan is failed on NSO. Are we sure the issue isn't with CNC UI itself since you meantioned "4. User get the update successfull message from the CNC"?Hi Regi,The issue is also with CNC UI since Corefp behaves in the same way as CNC just replicates how corefp behaves.User get the update successful message from both CNC and NSO.The device config also get updated with the edit changes. Hence this is a definite corefp issue.Thanks,DineshPlease confirm if you could able to reproduce the issue with the provided info.Thanks,DineshHi Dinesh,I was able to reproduce the issue and was able to confirm that this was expected behavior. If the user decides to push configuration to a failed service a service then the service will not restrict the users intent; however, the correct procedure would be that the user would fix the failed service before pushing more configs.Thanks,RegiThank you for the confirmation Regi. Assuming that this is an expected design of the COREFP.