ID 423675 - [B] From Avid: Unable to import AAF to Flix due to Source ID for clips not found

Problem summary
Unable to import certain AAFs to Flix due to Source ID for clips not found.

Customer reported version
Flix 6.2.1

Customer reported platform
CentOS 7

Steps to reproduce

Note: This is an intermittent issue dependent on the nature of Avid sequence items; following these steps will not reproduce the issue 100% of the times.

1) Export an AAF from Avid.
2) Import it to Flix. The Sequence will sometimes not import and the Server logs will display the following error:

time="04 Feb 20 15:22 GMT" level=debug msg="runPythonCLICommand: running python" args="[/flix/flix_server_6.2.2_35/thirdparty/python/aaf.py extract_clips /mnt/netshare/flix/katieAssets/assets/3213_removed alcon logo.aaf /tmp/472730554]" cmd=/flix/flix_server_6.2.2_35/thirdparty/python/linux/bin/python
time="04 Feb 20 15:22 GMT" level=error msg="ExtractClips: python returned error code" Error Code=4
time="04 Feb 20 15:22 GMT" level=error msg="JobChain.processJob: job failed, stopping chain" Job="Get AAF clips job" error="the PyAAF2 code returned an error code"

The aaf_python log will also display an error:

01/31/2020 03:48:20 INFO:[aaf.py:360] get_clips_data: params aaf_file: /mnt/netshare/flix/katieAssets/assets/3208_deleted all but first clip.aaf, output_file: /tmp/219864071
01/31/2020 03:48:21 ERROR:[aaf.py:436] get_clips_data: AAF Error: 'SourceID'
01/31/2020 03:48:21 WARNING:[aaf.py:55] output_code: outputing code 4

Expected behaviour
The AAF should import, if some clip IDs are not found Flix should skip those clips rather than not import the AAF at all.

Actual behaviour
The import fails altogether.

Reproduced by support
This bug has been reproduced in:

6.2.2 - CentOS 7

6.2.1 - CentOS 7