Open Stack

On Tue, Apr 11, 2017 at 06:48:52PM -0400, Paul Belanger wrote:
> On Tue, Apr 04, 2017 at 01:02:59PM -0400, Paul Belanger wrote:
> > Greetings,
> > 
> > Recently we've been running into some issues keeping our EPEL mirror properly
> > sync'd. We are working to fix this, however we'd also like to do the following:
> > 
> >   Stop enabling EPEL mirror by default
> >   https://review.openstack.org/#/c/453222/
> > 
> > For the most part, we enable EPEL for our image build process, this to install
> > haveged.  However, it is also likely the majority of centos-7 projects don't
> > actually need EPEL.  I know specifically both RDO and TripleO avoid using the
> > EPEL repository because of how unstable it is.
> > 
> > Since it is possible this could be a breaking change, jobs will still be able to
> > use EPEL, but it will be an opt-in process. Your jobs will need to be updated to
> > do:
> > 
> >   $ sudo yum-config-manager --enable epel
> > 
> > Feel free to join us in openstack-infra if you have any questions or concerns.
> > 
> > -PB
> > 
> Just a heads up, I believe we'll be landing this change tomorrow. It's been a
> week so far and no major outrage. :)
> 
> As always, you can find us in #openstack-infra if you have problems / questions.
> 
Another (final?) update. We are seeing issues with jobs that have bindep.txt
requirements for python34 from epel. In this case, you'll need to propose a
patch to project-config, specifically your JJB. And enable epel before running
our install-distro-packages macro.

Additionally, we have now removed python34 from bindep-fallback.txt. If you
still depend on it, you'll need to add it to your project bindep.txt file.

-PB