[Starlingx-discuss] [build]: py2 starlingx images locked to python modules from June build?

Saul Wold sgw at linux.intel.com
Thu Aug 13 20:18:47 UTC 2020


Another important question is does this affect the 4.0.1 release?  If we 
are using a static tarball from mid-June and we released in early 
August, are there changes that were missed?

Sau!


On 8/13/20 1:07 PM, Miller, Frank wrote:
> Zhipeng:
> 
> Please suggest a solution to this issue.  One option is to back out the 
> commit that introduced this issue.  Can you identify a solution that 
> doesn’t require you to back out your commit?
> 
> Frank
> 
> *From:* Khalil, Ghada <Ghada.Khalil at windriver.com>
> *Sent:* Wednesday, August 12, 2020 10:06 PM
> *To:* Penney, Don <Don.Penney at windriver.com>; 
> 'starlingx-discuss at lists.starlingx.io' 
> <starlingx-discuss at lists.starlingx.io>; Liu, ZhipengS 
> (zhipengs.liu at intel.com) <zhipengs.liu at intel.com>; Miller, Frank 
> <Frank.Miller at windriver.com>
> *Subject:* RE: [build]: py2 starlingx images locked to python modules 
> from June build?
> 
> The launchpad is: https://bugs.launchpad.net/starlingx/+bug/1891416
> 
> *From:* Penney, Don <Don.Penney at windriver.com 
> <mailto:Don.Penney at windriver.com>>
> *Sent:* Wednesday, August 12, 2020 9:21 PM
> *To:* 'starlingx-discuss at lists.starlingx.io' 
> <starlingx-discuss at lists.starlingx.io 
> <mailto:starlingx-discuss at lists.starlingx.io>>; Liu, ZhipengS 
> (zhipengs.liu at intel.com <mailto:zhipengs.liu at intel.com>) 
> <zhipengs.liu at intel.com <mailto:zhipengs.liu at intel.com>>; Miller, Frank 
> <Frank.Miller at windriver.com <mailto:Frank.Miller at windriver.com>>
> *Subject:* [Starlingx-discuss] [build]: py2 starlingx images locked to 
> python modules from June build?
> 
> Hi folks,
> 
> It was discovered that the recent stx-platformclients image was not 
> picking up recent changes made to the distributedcloud-client package (I 
> believe a Launchpad will be raised shortly). Tracing back through the 
> CENGN build logs, the problem appears to stem from the changes 
> introduced by:
> 
> https://review.opendev.org/#/c/737456/11/build-tools/build-docker-images/docker-image-build.cfg
> 
> So for specific images, including stx-platformclients, the image build 
> is now using a reference to a presumably static tarball:
> 
> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/stx-centos-py2_stable-wheels.tar
> 
> Looking at the dir listing, we can see this tarball is dated June 23^rd :
> 
> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/
> 
> What this means is that these particular images will be using this 
> locked tarball for installing python modules from the wheels (ie. The 
> PIP_PACKAGES list)… which means that an image like stx-platformclients, 
> which is getting various starlingx clients from wheels, will only ever 
> have content from that June 23^rd build.
> 
> Was this the intended behavior? Instead of this “alternate wheels 
> tarball”, shouldn’t we be generating a wheels tarball with both py2 and 
> py3 support, as long as we’re building any py2 images?
> 
> Thanks,
> 
> Don.
> 
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> 



More information about the Starlingx-discuss mailing list