[Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing!

Bailey, Henry Albert (Al) Al.Bailey at windriver.com
Tue Dec 8 20:32:23 UTC 2020


This is because of the new pip
https://discuss.python.org/t/announcement-pip-20-3-release/5948

In python3 it uses a diff resolver.  Which seems to fail for any component ending in a number (Django2, iso8601, etc..)

virtualenv on Dec7 was also updated to use that version of pip by default, which is what is affecting some tox jobs.

there is supposed to be a way to add --use-deprecated=legacy-resolver  to the pip command, which is what I am trying to do to get sysinv zuul to pass,
I havent had much luck yet.

Al

________________________________
From: Penney, Don <Don.Penney at windriver.com>
Sent: Tuesday, December 8, 2020 12:54 PM
To: Little, Scott <Scott.Little at windriver.com>; starlingx-discuss at lists.starlingx.io <starlingx-discuss at 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 <https://files.pythonhosted.org/packages/82/2b/75f2909ba02a3b0e343e560863101aa3d43f58357e7c053596aa29d1cce7/Django-2.2.17-py3-none-any.whl>



This is a py3 wheel, and stx-horizon has been updated to python3:

https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-horizon/centos/stx-horizon.stable_docker_image#L16





From: Scott Little <scott.little at windriver.com>
Sent: Tuesday, December 8, 2020 12:46 PM
To: starlingx-discuss at 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.



https://bugs.launchpad.net/starlingx/+bug/1907290



Can someone volunteer to investigate this one?



Scott





On 2020-12-08 1:08 a.m., build.starlingx at gmail.com<mailto:build.starlingx at gmail.com> wrote:

[Please note this e-mail is from an EXTERNAL e-mail address]



Project: STX_build_layer_containers_master_master

Build #: 90

Status: Still Failing

Timestamp: 20201208T014249Z

Branch: master



Check logs at:

http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs

--------------------------------------------------------------------------------

Parameters



BUILD_CONTAINERS_DEV: false

BUILD_CONTAINERS_STABLE: true

FORCE_BUILD: false



_______________________________________________

Starlingx-discuss mailing list

Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>

http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20201208/8f0287a2/attachment.html>


More information about the Starlingx-discuss mailing list