Bug 1397921

Summary: Older version of ansible rpms are removed as soon as a newer version is released
Product: [Fedora] Fedora EPEL Reporter: Preethi <preethi.ms34>
Component: ansibleAssignee: Kevin Fenzi <kevin>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: el6CC: a.badger, athmanem, kevin, kupo, mark, maxim, preethi.ms34, toromoti
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-23 15:10:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Preethi 2016-11-23 14:57:05 UTC 
Description of problem:
When a newer version of anisble is released, the older versions are removed from epel repo. Epel repo always contain only one version of anisble at a time. Since our scripts stick to a specific version of anisble, removing the rpms from epel repo fails our scripts and forces us to always stick to the latest version.

For example: When ansible-2.2 is released, anisble-2.1 is removed from the epel repo.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Kevin Fenzi 2016-11-23 15:10:09 UTC 
Yes, this is the case. It's due to the way our compose tools work. Changing this is difficult for a number of reasons: 

* would require tooling changes in mash and bodhi
* would mean sometimes we are keeping known insecure versions easily available to users, which they could be tricked into installing to be exploited. 
* would mean a increase in disk space for all mirrors, as well as a increase in updates production time moving around a bunch more rpms. 

You have several options: 

* You can make a local repo of packages you use and keep as many versions as you like there. 
* You can get old versions from https://koji.fedoraproject.org. It has all versions of all packages ever made. 
* You could use something like spacewalk to keep all rpms you use in local repos as well. 

Sorry theres nothing more we can do for you...