Bug 1794864

Summary:	Error message while using microdnf with Ubisofts-minimal
Product:	Red Hat Enterprise Linux 8	Reporter:	Veer Muchandi <veer>
Component:	microdnf	Assignee:	Jaroslav Rohel <jrohel>
Status:	CLOSED ERRATA	QA Contact:	Luca Berton <lberton>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	8.4	CC:	amatej, jrohel, lberton, mblaha
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libdnf-0.47.0-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 01:52:04 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:

Description Veer Muchandi 2020-01-24 22:34:38 UTC

Description of problem:
When I build using microdnf with ubi8/ubi-minimal I see the following error message `(process:620): libdnf-WARNING **: 21:45:54.627: Loading "/etc/dnf/dnf.conf": IniParser: Can't open file`

Version-Release number of selected component (if applicable):


How reproducible:
It can be

Steps to Reproduce:
1.RUn a build using https://github.com/VeerMuchandi/openshiftcli-inabox/blob/4.3/Dockerfile
2.You will see the warnings. The build goes ok. It is just this warning.


Actual results:

warning message `(process:620): libdnf-WARNING **: 21:45:54.627: Loading "/etc/dnf/dnf.conf": IniParser: Can't open file`

Expected results:
 
NO warning message

Additional info:

Comment 1 Jaroslav Rohel 2020-02-05 11:03:46 UTC

PR: https://github.com/rpm-software-management/libdnf/pull/888

Comment 2 Jaroslav Rohel 2020-04-01 05:34:12 UTC

Merged to upstream PR: https://github.com/rpm-software-management/libdnf/pull/888

Changes:
- It will always generate an error if the main configuration file exists
but can't be opened (eg. Permission denied).

- It will always generate an error if the main configuration file was
requested by user (using "dnf_context_set_config_file_path") and it
can't be opened.

- It will not generate error nor warning if the main config file
(/etc/dnf/dnf.conf) does not exists and was not explicitly requested
by user.

Comment 10 errata-xmlrpc 2020-11-04 01:52:04 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (microdnf bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4507