Red Hat Bugzilla – Bug 840988
RFE: Ability to define custom installation repo in recipeset without need to inject custom kickstart
Last modified: 2014-08-12 00:34:57 EDT
Motivation: We need to install RHEL 6.2 directly from the repo containing recent RHEL 6.2.Z build  instead of standard RHEL 6.2 . Otherwise "yum update" takes too long and it significantly prolongs the test time that is needed for the scheduled job. Currently the only bullet-proof way how to reach the desired behavior is to provide custom kickstart with modified "repo" command via <kickstart> tag (providing custom distribution repo URL). As far as the only altered part of the provided kickstart file are the "repo" commands, this solution is adding undesired complexity into our recipesets (and also into the code that is generating the recipeset in our Jenkins job).
Proposal: We propose to improve functionality of the existing <repo> tag, to allow user to specify that the custom repo will not be just added to the /etc/yum.repos.d in the %post section, but it will be also add corresponding "repo" command and thus Anaconda will use custom repo during installation.
For our tests is also essential to add the possibility to replace (or override) the "repo" command that defines distribution repo URL, as far as we want Beaker to use the provided distribution repo URL (e.g. ) instead of .
Note: To be correct, the default kickstart for RHEL 6.2 is actually specifying  in the repo command (to allow Anaconda to access RHEL 6.2 repo via NFS). Nevertheless, using  instead of  reduces our test-time anyway (as described in the motivation section above).
*** This bug has been marked as a duplicate of bug 633369 ***