Comment 2 for bug 1958696

Comparing two builds
 - a previous build which failed differently
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220120T050921Z/logs/jenkins-STX_build_docker_flock_images-484.log.html

and the one this bug is raised for:
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20220121T145521Z/logs/jenkins-STX_build_docker_flock_images-485.log.html

The Jan 20 fail does not report the 'conflicts' but clones a much older version of loci.
See this in the logs:
Cloning into 'loci'...
Note: checking out 'f022ecba553903df3df72d3668e143e9eb9ceded'.

that version of loci is a commit dated April 2020
https://github.com/openstack/loci/commit/f022ecba553903df3df72d3668e143e9eb9ceded

The load this is tagged against has the 'conflicts' and uses a newer loci.
Cloning into 'loci'...
Note: checking out 'efccd0a853879ac6af6066eda09792d0d3afe9c0'.

that loci is dated Jan 12 2022
https://github.com/openstack/loci/commit/efccd0a853879ac6af6066eda09792d0d3afe9c0

I do not know why loci is now moved to 'HEAD' instead of whatever that old version was locked to.
There are supposed to be fixes for virtualenv, pip, setuptools already locked in loci, but apparently we stayed locked to the old version up until now.