We had a 404 error across multiple source mirrors trying to access one of the repodata files on one repo. There are a couple of theories. 1) The fastest mirror plugin appears to open the window for the various files that make up a repodata to come from various sources. Those sources might be inconsistent as they aren't updating in unison. Disabling the fast mirror plugin isn't my first choice. No obvious config option to make all repodata come from a single source. Am I missing something? 2) stale cached content locally, requireing an explicit yum cleanup comand Failure to reproduce on the next run suggests this isn't the issue. 3) stale cached content in an upstream server Solution: add http_caching=packages to yum.conf Yum will ask upstream for non-cached repodata. I will test this and see if we get a recurrence over the next few weeks. Scott On 2019-03-06 1:07 a.m., build.starlingx@gmail.com wrote:
Project: STX_build_master_master Build #: 7 Status: Failure Timestamp: 20190306T060000Z
Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060... -------------------------------------------------------------------------------- Parameters
BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss