https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/IEC-31 Integrated Edge Cloud <p>On the newer SEBA version which we are trying to update to, we have already built the necessary images and are tracking the remaining issues.</p> <p>The first obvious error happens in the XOS GUI (port 30001), showing error notifications in the form of red boxes with the message "Synchronization Failed for ONU Device" and "Synchronization Failed for SwitchPort". </p> IEC-31

[IEC][SEBA] Synchronization failed for ONU Device and SwitchPort in xos-gui

Bug Medium Done Done Catalin Iova Ciprian Barbu Thu, 19 Mar 2020 13:52:55 +0000 Mon, 30 Mar 2020 12:40:10 +0000 Mon, 30 Mar 2020 12:40:10 +0000 0 2 <p>The issue is caused by an error reported by seba-services-volt for an http post request to voltha core through voltha envoy. <font color="#172b4d">seba-services-volt</font> synchronizer is trying to synchronize ONU device by enabling it while is already enabled and voltha core respond back to envoy with grpc error that device cannot be enabled while enabled but also with Bad Request http 400 error. <font color="#172b4d">Using envoy commit </font><font color="#172b4d">29361deae91575a1d46c7a21e913f19e75622ebe or early, the http post request error is not passing through envoy for voltha core response.</font> This may be an issue on opencord version too but not sure thought. With a newer envoy than the current used one (cachengo/envoy:29361deae91575a1d46c7a21e913f19e75622ebe) seems that http 1.0 is implemented and also grpc responses for grpc requests making the error passing through envoy leading to this synchronization issue.</p> <p>SwithcPort is synchronizing later.</p> <p>The fix consist in using <font color="#172b4d">cachengo/envoy:29361deae91575a1d46c7a21e913f19e75622ebe</font> version for voltha-envoy image (iecedge/voltha-envoy_arm64:1.7.0).</p> Development Rank 0|i003no: