Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1512457 - when you feed "-c" option with nonexistent file, dnf still returns 0
Summary: when you feed "-c" option with nonexistent file, dnf still returns 0
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-13 09:44 UTC by Jan Hutař
Modified: 2018-09-30 21:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Jan Hutař 2017-11-13 09:44:34 UTC
Description of problem:
When you feed "-c" option in `dnf -c /etc/does-not-exist.conf` with nonexistent file, dnf still returns 0


Version-Release number of selected component (if applicable):
dnf-2.7.5-1.fc26.noarch


How reproducible:
always


Steps to Reproduce:
1. Non-existing file:
   # dnf -c /etc/yum-c-that-does-not-exists.conf repolist; echo $?
2. Parameter missing at all:
   # dnf -c repolist; echo $?


Actual results:
Return code is 0 in both cases. E.g. in first case dnf says:

    Can not read configuration: /etc/yum-c-that-does-not-exists.conf , ignoring

but returns 0.


Expected results:
This is difference when compared to yum. IMO should be consistent (in case you are automating something, it is better to fail fast.

Comment 1 Fedora End Of Life 2018-05-03 08:53:18 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Jan Kurik 2018-08-14 11:00:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.


Note You need to log in before you can comment on or make changes to this bug.