Bug #33912: After force deleting a repo, its entry in /etc/yum.repos.d/redhat.repo continues to be populated - Katello - Foreman

Actions

Copy link

Bug #33912

closed

After force deleting a repo, its entry in /etc/yum.repos.d/redhat.repo continues to be populated

Added by Ian Ballou about 3 years ago. Updated almost 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ian Ballou

Category:

Repositories

Target version:

Katello 4.3.0

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

https://github.com/Katello/katello/pull/9781, https://github.com/Katello/katello/pull/9886

Fixed in Releases:

Katello 4.4.0

Found in Releases:

Red Hat JIRA:

Description

I force deleted a repo and noticed that subscription-manager still thought the repository existed, even after running subscription-manager refresh and clean and re-registering.

It looks like this is caused by the ::Katello::Content entry not being properly deleted.

To reproduce, make a yum repo and add it to a content view version. Subscribe a host and ensure the host sees the repo. Then, force delete the repo. After you run sub-man refresh, the repo will still be there.

If this doesn't make Katello 4.3.0 we should put it on 4.3.1 and make a BZ.