In 2 execution tests of dual stack and single stack on 4.14.6 there were flaky failures at:
tests.network.nmstate.test_nncp_maxunavailable.test_create_policy_get_status
These failures are not due to incorrect policies being observed but are instead related to the state of network devices (specifically bridges) being 'Available' sooner than expected or changing state very quickly. This issue is causing a high number of test failures across the module.

Example of test failure:
tests.network.nmstate.test_nncp_maxunavailable.test_create_policy_get_status[maxunavailable_input_for_bridge_creation_10%]

AssertionError: assert ['Available',...g', 'Pending'] == ['Pending', '...'Progressing']
  At index 0 diff: 'Available' != 'Pending'
  Full diff:
  - ['Pending', 'Pending', 'Progressing']
  + ['Available', 'Pending', 'Pending'] 

test_logs.log