[Starlingx-discuss] Kata containers update breaking build - failure to download RPMs

Scott Little scott.little at windriver.com
Fri Jan 17 21:24:37 UTC 2020

Looks like the current serial mirror sync job is taking aprox 24 hours 
to sync all our repos.

In the short term, the zul trigger won't help much.

Need to look into a parallel implementation!!!


On 2020-01-14 8:35 p.m., Saul Wold wrote:
> On 1/14/20 12:49 PM, Scott Little wrote:
>> The new upstream repo should be introduced 24 hours before any lst 
>> files that reference content from that repo.
> What do you think of creating a new Zuul process to fetch or cause 
> Cengn to fetch a current copy when the review is started via the Check 
> gate?
> Sau!
>> That should give CENGN to mirror the new repo.  Once cengn has a copy 
>> of the version we want, it no longer matters if upstream changes the 
>> version.
>> Scott
>> On 2020-01-14 3:22 p.m., Miller, Frank wrote:
>>> 2)Identify how we can prevent a build failure in the future when 
>>> kata puts out a new version and deletes the 1.9.3-8.1 version.  Is 
>>> there a way the StarlingX build or CENGN mirror can cache this 
>>> version so we can control when we move to a new version?
>> _______________________________________________
>> 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