Bug with re-deployment of nse-composition with kernel-interfaces

[isZams]

Expected Behavior

I would like to change the endpoint composition by adding a new pod in the middle of the chain, by simply modifying the network service definition file.

Actual Behavior

Actually if i add a new pod, there are some problems with the kernel interfaces. Assuming that initially i have this configuration: nsc --> passthrough-4 --> gateway. Then i want to move to this configuration: nsc--> test --> passthrough-4 --> gateway.

The problem with the interfaces is between test and passthrough-4 and then also within passthrough-4. Do you have any idea about the possible reasons? I thought to have a similar behaviour when a client connects to a different service and therefore a new interface is established, as in the example of change-nse-dynamically.

Here there is the zip folder containing all the files that i'm using for this use case. kernel-composition.zip