Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1706384

Summary: "dnf config-manager" with no arguments should default to --dump
Product: Red Hat Enterprise Linux 8 Reporter: Michal Domonkos <mdomonko>
Component: dnf-plugins-coreAssignee: Pavla Kratochvilova <pkratoch>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: low    
Version: 8.0CC: dmach, james.antill, ksrot, pkratoch, tbowling
Target Milestone: rcKeywords: Triaged
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 12:39:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1681085    
Bug Blocks:    

Description Michal Domonkos 2019-05-04 14:32:49 UTC
SSIA.

This is also important to maintain YUM3 compatibility (yum-config-manager defaulted to --dump also).

Comment 1 Michal Domonkos 2019-05-06 11:49:18 UTC
Original docs bug: https://bugzilla.redhat.com/show_bug.cgi?id=1701874

Comment 2 Karel Srot 2019-05-15 12:56:48 UTC
I believe yum-config-manager for yum v3 is always providing the output, not just when no arguments are provided.. So to make it really compatible we should actually make --dump always default, not just with no arguments.

Comment 4 Daniel Mach 2019-12-12 12:39:17 UTC
We have decided to close this issue and keep the existing behavior.

The command name ("config-manager") doesn't indicated any action, dumping configuration
a quite unexpected result.
We prefer users to explicitly specify an action (--dump in this case).