Project

Profile

Help

Issue #3040

closed

When a consumer is unbound from an RPM repository, that repository should be deleted from /etc/yum.repos.d/...

Added by Ichimonji10 over 4 years ago. Updated about 3 years ago.

Status:
CLOSED - WORKSFORME
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

When a consumer is bound to an RPM repository, a new entry is added into /etc/yum.repos.d/pulp.repo. Intuitively, I expect that when that same consumer is unbound from that same RPM repository, that entry will be removed from /etc/yum.repos.d/pulp.repo. Unfortunately, that doesn't happen. Instead, the repository entry is left in place.

This behaviour is unintuitive. It is my expectation that the following two actions produce a functionally identical system:

  • Do nothing.
  • Bind a consumer to a repository, and unbind that same consumer from that same repository.

The current behaviour makes it harder to implement tests such as Pulp Smash #611.

Actions #1

Updated by mhrivnak over 4 years ago

After being unbound from a repo, does that repo's entry in the .repo file at least get disabled?

Actions #2

Updated by Ichimonji10 over 4 years ago

  • Status changed from NEW to CLOSED - WORKSFORME

Sorry. This bug was reported in error. Whan a consumer is unbound from an RPM repository, it is correctly deleted from /etc/yum.repos.d/pulp.repo.

Actions #3

Updated by bmbouter about 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF