-
Notifications
You must be signed in to change notification settings - Fork 51
Description
Is your feature request related to a problem? Please describe.
We had a partner recently that was running into an issue setting up some repos and installing packages on a machine they had provisioned with DCI/Beaker. We traced the issue back to the beaker-tasks repo that is on the machine after Beaker is done. The partner ran a "yum clean all" and then attempted to perform some more yum commands, but ran into problems with the system not being able to get the repomd.xml for the beaker-tasks repo since it is deleted from the Beaker server from which it was served and the clean command removed the cache for it.
We understand removing the repo from the Beaker server makes sense, but our ask would be that the repo either be disabled by Beaker on the provisioned system or be skipped if it can't be found.