I’ve posted a fix for the stx-horizon build issue:
https://review.opendev.org/c/starlingx/root/+/766357
Inclusion of a specific version of Django in our wheels tarball for the loci build resulted in a conflict between the upper-constraints.txt in the tarball and the requirements.txt from openstack/horizon. The
new pip resolver exposed this conflict and causes the stx-horizon image build to fail. Removing the entry from our stable-wheels.cfg avoids the conflict, and I’m able to successfully build the image.
Once the review is approved and merged, we can kick a new image build from cengn.
Cheers,
Don.
From: Penney, Don <Don.Penney@windriver.com>
Sent: Tuesday, December 8, 2020 12:55 PM
To: Little, Scott <Scott.Little@windriver.com>; starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing!
That seems odd. It certainly looks like pypi.org has a wheel that should satisfy the requirement Django<3.0,>=2.2:
https://pypi.org/project/Django/2.2.17/#files
Django-2.2.17-py3-none-any.whl
This is a py3 wheel, and stx-horizon has been updated to python3:
From: Scott Little <scott.little@windriver.com>
Sent: Tuesday, December 8, 2020 12:46 PM
To: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing!
There is second container build failure in the logs.
The stx-horizon docker image can't find a version of Django that it can use.
Can someone volunteer to investigate this one?
Scott
On 2020-12-08 1:08 a.m.,
build.starlingx@gmail.com wrote: