Mirror jobs should not copy new packages if installation fails.

Bug #1203198 reported by Clark Boylan
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Won't Fix

Bug Description

http://logs.openstack.org/periodic/periodic-mirror-python27/140/console.html shows a mirror job run that attempted to install xattr 0.7.0. This failed because xattr depends on cffi which depends on the system libffi-dev package being present (it was not). Despite failing to properly install xattr 0.7.0 was copied to the mirror and broke testing for all projects that depend on xattr.

Revision history for this message
Clark Boylan (cboylan) wrote :

There has been some confusion on what the failure mode of the mirror jobs should be. We will have a summit session to talk openstack/requirements and the mirror to sort out what has worked, what hasn't and how we can make it better. This particular bug should be brought up there.

Changed in openstack-ci:
milestone: havana → icehouse
Revision history for this message
Jeremy Stanley (fungi) wrote :

This was only minimally touched on at the summit sessions on requirements. The takeaway though is that our mirror should, whenever possible, reflect any of the same breakage exposed upstream in PyPI and not try to shield our CI processes from it... proposals were floated to perform some sort of notification of breakage during mirror builds and then fall back on safe/working behavior instead, but the primary concern there is visibility. The compromise with the most support was if we had some process to automagically open bugs when this happens, and include the list of packages added when that happened.

There was also a related proposals for preemptive testing of upstream dependencies to provide feedback for us (and possibly them depending on openness to it and proximity of our communities) as an early warning system for these sorts of issues.

Revision history for this message
James E. Blair (corvus) wrote :

We now use bandersnatch so most of this bug is no longer relevant.

Changed in openstack-ci:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.