The following code is expected to create the following OF actions
actions=set_field:00:1c:73:4e:d3:31->eth_dst,load:0x100->NXM_NX_REG6[],resubmit(,220)

List<ActionInfo> actionList = new ArrayList<>();
actionList.add(new ActionInfo(ActionType.set_field_eth_dest, new String[]

));
List<ActionInfo> egressActionList = NatUtil.getEgressActionsForInterface(interfaceManager, extInterface, null);
actionList.addAll(egressActionList);

Instead, only the egress actions are created and set_field will be discarded due to internal ordering created by OdlInterfaceRpcService.getEgressActionsForInterface()

A workaround for this can be forcing the order using ActionInfo c'tor with order parameter. But why is an ordered collection like List needs an additional ordering?