Project

General

Profile

Actions
Copy link

Bug #12628

closed

epel enabled after nuke ?

Added by Vasu Kulkarni over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Andrew Schoen
Category:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

I had deleted old repos, but somehow this repo keeps coming back, Possible nuke:true might be enabling it back?

[ubuntu@magna078 yum.repos.d]$ ls
ceph.log epel.repo epel-testing.repo lab-extras.repo redhat.repo rhel-7-fcgi-ceph.repo

[ubuntu@magna078 yum.repos.d]$ cat epel.repo #
  1. This file is managed by ansible, don't make changes here - they will be overwritten. #

[epel]
baseurl=http://dl.fedoraproject.org/pub/epel/7/$basearch
enabled=1
gpgcheck=0
name=Extra Packages for Enterprise Linux

Actions
Copy link
 #1

Updated by Andrew Schoen over 8 years ago

  • Assignee set to Andrew Schoen
Actions
Copy link
 #2

Updated by Andrew Schoen over 8 years ago

  • Status changed from New to Resolved

This was because the copy of the secrets repo which controlled if epel would be enabled or not was out of date on the teuthology machine. Meaning that every time teuthology ran the testnodes playbook against a node it would enable epel.

This was fixed by updating the secrets repo and creating a cron job that updates that repo nightly.

Actions
Copy link

Also available in: Atom PDF