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 2137420

Summary: Upgrade failed with "Transaction in progress" in MCO [rhel-8.4.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: rpm-ostreeAssignee: Colin Walters <walters>
Status: CLOSED ERRATA QA Contact: HuijingHei <hhei>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.4CC: aaradhak, agogala, ddelcian, dornelas, hhei, jerzhang, mkrejci, skumari, walters
Target Milestone: rcKeywords: Reopened, Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rpm-ostree-2020.7-4.el8_4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2101379 Environment:
Last Closed: 2023-01-30 14:46:10 UTC Type: ---
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: 2101379    
Bug Blocks:    

Comment 4 Colin Walters 2022-11-01 17:25:56 UTC 
Some tips on verifying: https://bugzilla.redhat.com/show_bug.cgi?id=2057544#c14
Comment 6 HuijingHei 2022-11-07 12:33:08 UTC 
Hi Colin, I am not quite sure how to verify, any guidance? Thanks!

Start 49.84.202211030959-0 image with rpm-ostree-2020.7-3.el8, run `strace -f --fault connect:error=EPERM:when=2 rpm-ostree upgrade`, get "error: Could not connect: Operation not permitted". Maybe my understanding is not correct.

[root@cosa-devsh ~]# rpm -q rpm-ostree
rpm-ostree-2020.7-3.el8.x86_64

[root@cosa-devsh ~]# rpm-ostree status
State: busy
Transaction: 
  Initiator: client(id:cli dbus:1.32 unit:session-1.scope uid:0)
Deployments:
● ostree://9f25fb72db25e5a4457e5eb7a361e6b53b57e468b0455edf17578b70d7da8786
                   Version: 49.84.202211030959-0 (2022-11-03T10:02:16Z)

# strace -f --fault connect:error=EPERM:when=2 rpm-ostree upgrade
.....
error: Could not connect: Operation not permitted
Comment 7 Colin Walters 2022-11-07 13:39:31 UTC 
Right, it's expected for the `strace` command to output an error - it's forcing a failing system call.

In the buggy version, all *further operations* such as another `rpm-ostree upgrade` should (incorrectly) block, waiting for the old client.

The new fixed version will allow retrying the operation.

In other words, the full reproduction scenario is:

strace -f --fault connect:error=EPERM:when=2 rpm-ostree upgrade  # expected failure in both cases
rpm-ostree upgrade   # Should output Pinned to commit; no upgrade available  - but in the broken version, this will stall

You'll also notice a difference in the output of `rpm-ostree status`; the broken version will show an active transaction, the fixed will not.
Comment 8 HuijingHei 2022-11-08 06:42:29 UTC 
Thanks Colin for the detail explanation! Verify passed on 410.84.202211032138-0.

1) Test with unfixed version rpm-ostree-2020.7-3.el8.x86_64, after strace command, exec `rpm-ostree upgrade` is stuck.
==================================================
[root@cosa-devsh ~]# strace -f --fault connect:error=EPERM:when=2 rpm-ostree upgrade
...error: Could not connect: Operation not permitted

[root@cosa-devsh ~]# rpm-ostree upgrade

[core@cosa-devsh ~]$ rpm-ostree status
State: busy
Transaction: 
  Initiator: client(id:cli dbus:1.33 unit:session-4.scope uid:0)
Deployments:
● ostree://8d68051abeecf4991283052b4e6d38a5bad50e3c8e7b678973d5c39d30145ab0
                   Version: 410.84.202211032138-0 (2022-11-03T21:41:00Z)


2) Test with fixed version rpm-ostree-2020.7-4.el8_4.x86_64, after strace command, exec `rpm-ostree upgrade` print "No upgrade available".
==================================================
[root@cosa-devsh ~]# strace -f --fault connect:error=EPERM:when=2 rpm-ostree upgrade
...error: Could not connect: Operation not permitted

[root@cosa-devsh ~]# rpm-ostree upgrade
Checking out tree 8d68051... done
No enabled rpm-md repositories.
Importing rpm-md... done
Resolving dependencies... done
No upgrade available.

[root@cosa-devsh ~]# rpm-ostree status
State: idle
Deployments:
● ostree://8d68051abeecf4991283052b4e6d38a5bad50e3c8e7b678973d5c39d30145ab0
                   Version: 410.84.202211032138-0 (2022-11-03T21:41:00Z)
      ReplacedBasePackages: rpm-ostree rpm-ostree-libs 2020.7-3.el8 -> 2020.7-4.el8_4

  ostree://8d68051abeecf4991283052b4e6d38a5bad50e3c8e7b678973d5c39d30145ab0
                   Version: 410.84.202211032138-0 (2022-11-03T21:41:00Z)
Comment 16 errata-xmlrpc 2023-01-30 14:46:10 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 (rpm-ostree 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/RHBA-2023:0502