Bug 2021771

Summary: dnf update message failed to connect to bus
Product: [Fedora] Fedora Reporter: jpbn <jjb>
Component: dnfAssignee: rpm-software-management
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 35CC: daniel.mach, fedora, jh.redhat-2018, jmracek, jose.p.oliveira.oss, jrohel, larouxn, mailings, maxwell, mblaha, mhatina, michael.scheiffler, mnowak, packaging-team-maint, pkratoch, rpm-software-management, sbarcomb, vmukhame
Target Milestone: ---   
Target Release: ---   
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: 2021-11-11 22:13:52 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 jpbn 2021-11-10 07:21:57 UTC 
Description of problem:

in update (dnf) messages :
  Running scriptlet: java-11-openjdk-headless-1:11.0.13.0.8-2.fc35.x8   110/110 
  Running scriptlet: java-11-openjdk-headless-1:11.0.13.0.8-1.fc35.x8   110/110 
Failed to connect to bus: Invalid argument
Failed to connect to bus: Invalid argument

Failed to connect to bus: Invalid argument

Failed to connect to bus: Invalid argument

  Verifying        : bluez-5.62-2.fc35.x86_64   
Version-Release number of selected component (if applicable):
 dnf --version
4.9.0
  Installed: dnf-0:4.9.0-1.fc35.noarch at Wed 29 Sep 2021 05:49:08 AM GMT
  Built    : Fedora Project at Thu 23 Sep 2021 12:18:24 PM GMT

  Installed: rpm-0:4.17.0-1.fc35.x86_64 at Wed 29 Sep 2021 05:48:28 AM GMT
  Built    : Fedora Project at Fri 03 Sep 2021 11:34:28 AM GMT


How reproducible:

dnf update 
Steps to Reproduce:
1.dnf update 
2.
3.

Actual results:
Failed .. messages appear. 

Expected results:


Additional info:
Do not know how to send error info to you.
Comment 1 Michael 2021-11-10 08:24:44 UTC 
Many uses are affected by this.
See also https://ask.fedoraproject.org/t/failed-to-connect-to-bus-invalid-argument/18006
Comment 4 Jakob Hirsch 2021-11-11 08:49:18 UTC 
Happens also with plain rpm:

# rpm -Uvh mta/nullmailer-2.2-0.fc35.x86_64.rpm --force
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:nullmailer-2.2-0.fc35            ################################# [ 50%]
Cleaning up / removing...
   2:nullmailer-2.2-0.fc35            ################################# [100%]
Failed to connect to bus: Invalid argument
Failed to connect to bus: Invalid argument
Failed to connect to bus: Invalid argument
Failed to connect to bus: Invalid argument
Failed to connect to bus: Invalid argument
Failed to connect to bus: Invalid argument

Works on another F35 system without this failure message.
Comment 5 Maxwell G 2021-11-11 22:13:52 UTC 
Hi jpbn,

This is a duplicate of #2020415. It stems from an issue with a systemd rpm scriptlet and not dnf.

Thanks,
Maxwell

*** This bug has been marked as a duplicate of bug 2020415 ***