Issue #3039
closed
Uninstalling pulp-rpm-handlers removes /etc/yum.repos.d/pulp.repo
Description
Uninstalling pulp-rpm-handlers removes /etc/yum.repos.d/pulp.repo. This is concerning, because:
1. This file isn't owned by the pulp-rpm-handlers package, as far as I can tell. A package shouldn't touch files it doesn't own.
2. It's unintuitive. I've never, ever heard of a package that blows away an entire repository file. At most, I would expect an entry from a repository file to be removed.
3. It can break the system. Any number of repositories might be listed in that file, and blowing away that file will make all of them unavailable.
This third point is the one that's most problematic. Whenever a system is provisioned with the Ansible playbooks in the pulp_packaging repository, a repository is created in /etc/yum.repos.d/pulp.repo, where that file lists our nightly builds of Pulp 2.x. Uninstalling pulp-rpm-handlers blows away that file, which breaks the system, which makes it much harder to test pulp-consumer and pulp-agent. Pulp Smash #611 is heavily affected.
- Description updated (diff)
- Description updated (diff)
For what it's worth, pulp-agent will not be very functional without pulp-rpm-handlers. I'm not sure what you would want to test in that case. I think you'd basically be testing gofer by itself.
Note that pulp-agent is what we call goferd when it's running as a service with pulp "handlers" installed. Gofer is pluggable, and like Pulp platform, it has a very limited set of functionality by itself that isn't very useful unless you add plugins/handlers.
For what it's worth, pulp-agent will not be very functional without pulp-rpm-handlers. I'm not sure what you would want to test in that case. I think you'd basically be testing gofer by itself.
Sure. We're not actually testing this case. What we're doing is installing and uninstalling all of the pulp-agent packages from a host during the course of a test, and it just happens that pulp-rpm-handlers is one of those packages.
I should emphasize, again, that /etc/yum.repos.d/pulp.repo is created by the Pulp 2 installer in pulp_packaging. As a result, uninstalling pulp-agent packages (including pulp-rpm-handlers) breaks a Pulp 2 installation.
I see. It looks like we may have a name collision with that file. pulp-agent's yum handler probably makes a file named "pulp.repo" and uses it to manage repositories the consumer gets bound to. And it happens that the same file name is now used when installing pulp itself.
I think you're exactly right, Michael.
- Triaged changed from No to Yes
Note that pulp-agent doesn't overwrite /etc/yum.repos.d/pulp.repo. Instead, it adds and removes entries from the file.
- Status changed from NEW to CLOSED - WONTFIX
Also available in: Atom
PDF
.