From 6a6ab3e12b4fe0f3fc402a6b99932640fabccc32 Mon Sep 17 00:00:00 2001
From: Marek Blaha <mblaha@redhat.com>
Date: Wed, 3 Jul 2019 10:49:20 +0200
Subject: [PATCH 1/2] Method to get catched rpm errors from RPMTransaction
 (RhBug:1677199)

This method enables iterating through messages logged by underlaying
rpm. The messages could be then logged by dnf, printed to user...
---
 dnf/yum/rpmtrans.py | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/dnf/yum/rpmtrans.py b/dnf/yum/rpmtrans.py
index 8a5bd4731..b0fd9b6eb 100644
--- a/dnf/yum/rpmtrans.py
+++ b/dnf/yum/rpmtrans.py
@@ -210,6 +210,12 @@ class RPMTransaction(object):
         except IOError:
             pass
 
+    def messages(self):
+        messages = self._scriptOutput()
+        if messages:
+            for line in messages.splitlines():
+                yield ucd(line)
+
     def _scriptout(self):
         msgs = self._scriptOutput()
         for display in self.displays:
-- 
2.21.0


From 61e0b7c553fe0c04dfeb3b6d4c16fa36e4eb26f4 Mon Sep 17 00:00:00 2001
From: Marek Blaha <mblaha@redhat.com>
Date: Wed, 3 Jul 2019 10:54:42 +0200
Subject: [PATCH 2/2] Print rpm error messages during transaction
 (RhBug:1677199)

This patch lets the rpm error messages to be passed on to the user.
Original code basically considered all rpm errors as "Failed to obtain
the transaction lock", which is obviously not always the case. Now dnf
prints out original rpm messages so that user could find out what the
real problem is.

https://bugzilla.redhat.com/show_bug.cgi?id=1677199
---
 dnf/base.py | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/dnf/base.py b/dnf/base.py
index 237ad397d..2c5d17e8b 100644
--- a/dnf/base.py
+++ b/dnf/base.py
@@ -983,16 +983,16 @@ class Base(object):
         if errors is None:
             pass
         elif len(errors) == 0:
-            # this is a particularly tricky case happening also when rpm failed
-            # to obtain the transaction lock. We can only try to see if a
-            # particular element failed and if not, decide that is the
-            # case.
+            # If there is no failing element it means that some "global" error
+            # occured (like rpm failed to obtain the transaction lock). Just pass
+            # the rpm logs on to the user and raise an Error.
+            # If there are failing elements the problem is related to those
+            # elements and the Error is raised later, after saving the failure
+            # to the history and printing out the transaction table to user.
             failed = [el for el in self._ts if el.Failed()]
             if not failed:
-                login = dnf.util.get_effective_login()
-                msg = _("Failed to obtain the transaction lock "
-                        "(logged in as: %s).")
-                logger.critical(msg, login)
+                for msg in cb.messages():
+                    logger.critical(_('RPM: {}').format(msg))
                 msg = _('Could not run transaction.')
                 raise dnf.exceptions.Error(msg)
         else:
-- 
2.21.0