Project

Profile

Help

Story #1875

closed

As a user, I can manage consumers that use DNF package manager

Added by dkliban@redhat.com over 6 years ago. Updated over 3 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 33
Quarter:

Description

With Pulp3 so far underway, and not including consumers at all, adding this to Pulp2 is unlikely. I think we should do two things:

1. Create a blog post describing an alternate set of tooling (like ansible) to manage consumers via.
2. In the docs announce that dnf support is not planned and link to the blog post as a workaround.
3. Close this after as WONTFIX

Actions #1

Updated by dkliban@redhat.com almost 6 years ago

  • Sprint Candidate changed from No to Yes
Actions #2

Updated by amacdona@redhat.com over 5 years ago

  • Sprint Candidate changed from Yes to No
Actions #3

Updated by bmbouter almost 5 years ago

I think this feature request should be closed as WONTFIX unless someone from the community wants to send a PR for it. Consumers have been removed entirely from Pulp3, so users are going to need to switch off of Pulp code for consumer management anyway.

We should announce a deprecation of consumer management features if it hasn't been done already. We should additionally state that dnf based consumer actions won't be added. We should give some other options as alternatives such as Ansible. You can easily maintain an Ansible inventory to perform consumer actions with Ansible like you did with Pulp.

Actions #4

Updated by bmbouter almost 5 years ago

I filed an issue in the katello tracker for them to take the Pulp code into Katello and port it to also support dnf. That issue is here: http://projects.theforeman.org/issues/21904

Actions #5

Updated by jsherril@redhat.com almost 5 years ago

This makes sense from the katello side as long as projects.theforeman.org/issues/21904 is handled appropriately .

Actions #6

Updated by bmbouter almost 5 years ago

  • Description updated (diff)

I added some content to the description.

Actions #7

Updated by ttereshc almost 5 years ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes
Actions #8

Updated by rchan almost 5 years ago

  • Sprint/Milestone set to 56
Actions #9

Updated by daviddavis almost 5 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to daviddavis

Added by daviddavis over 4 years ago

Revision 576dbc03

Add section about DNF to consumer docs

closes #1875 https://pulp.plan.io/issues/1875

Actions #11

Updated by daviddavis over 4 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #12

Updated by bmbouter over 4 years ago

  • Sprint set to Sprint 33
Actions #13

Updated by bmbouter over 4 years ago

  • Sprint/Milestone deleted (56)
Actions #14

Updated by ttereshc over 4 years ago

Do we want to close this one as a WONTFIX? so it will be clear that we didn't add support for DNF. Is it ok from rel-eng standpoint?

I get that the docs and blog post were created and the docs should go into release. But for users it can be confusing that status of the story is "closed-current release", though it's only docs which say that it won't be fixed.

Actions #15

Updated by daviddavis over 4 years ago

  • Status changed from MODIFIED to CLOSED - WONTFIX
Actions #16

Updated by bmbouter over 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF