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 2229895 - Backport https://github.com/ostreedev/ostree/pull/2969/commits/402e04280b54c058ad47be99fe6a9326caf2ae00
Summary: Backport https://github.com/ostreedev/ostree/pull/2969/commits/402e04280b54c0...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ostree
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Joseph Marrero
QA Contact: HuijingHei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-08 06:47 UTC by Joseph Marrero
Modified: 2023-11-14 17:09 UTC (History)
4 users (show)

Fixed In Version: ostree-2022.2-8.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-14 15:37:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-164791 0 None None None 2023-08-08 06:49:08 UTC
Red Hat Product Errata RHBA-2023:7063 0 None None None 2023-11-14 15:37:25 UTC

Comment 1 HuijingHei 2023-08-23 02:19:58 UTC
Verify passed with ostree-2022.2-8.el8.x86_64, thanks Joseph and Colin for the guidance.

Steps:

Create cluster using OCP 4.12.28 on gcp: 

- reproduce with unfixed ostree: exec steps according to the video of Colin (see https://issues.redhat.com/browse/OCPBUGS-15917?focusedId=22747033&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-22747033), and run `ip link set ens4 down; sleep 5; reboot`, check the node is down, when node is back after waiting about 30min, check that could not get kernel parameter `test=1`

- manually upgrade ostree on the node to ostree-2022.2-8.el8.x86_64 and reboot, exec same steps, check we have kernel parameter `test=1` after the node is back, service still failed as expected.

[root@ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ~]# rpm -q ostree
ostree-2022.2-8.el8.x86_64

[root@ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ~]# cat /proc/cmdline 
... test=1

[root@ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ~]# journalctl -b -1 -u ostree-finalize-staged.service
-- Logs begin at Tue 2023-08-15 13:41:46 UTC, end at Tue 2023-08-15 15:33:07 UTC. --
Aug 15 14:58:09 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: Started OSTree Finalize Staged Deployment.
Aug 15 15:03:00 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: Stopping OSTree Finalize Staged Deployment...
Aug 15 15:03:00 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ostree[29496]: Finalizing staged deployment
Aug 15 15:03:02 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ostree[29496]: Copying /etc changes: 14 modified, 0 removed, 133 added
Aug 15 15:03:02 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ostree[29496]: Copying /etc changes: 14 modified, 0 removed, 133 added
Aug 15 15:03:10 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ostree[29496]: Timed out waiting for global sync()
Aug 15 15:03:11 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ostree[29496]: Bootloader updated; bootconfig swap: yes; bootversion: boot.0.1, deployment count chan>
Aug 15 15:03:11 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn ostree[29496]: Bootloader updated; bootconfig swap: yes; bootversion: boot.0.1, deployment count chan>
Aug 15 15:08:00 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: Stopping timed out. Terminating.
Aug 15 15:13:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: State 'stop-sigterm' timed out. Killing.
Aug 15 15:13:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: Killing process 29496 (ostree) with signal SIGKILL.
Aug 15 15:18:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: Processes still around after SIGKILL. Ignoring.
Aug 15 15:23:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: State 'stop-final-sigterm' timed out. Killing.
Aug 15 15:23:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: Killing process 29496 (ostree) with signal SIGKILL.
Aug 15 15:28:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: Processes still around after final SIGKILL. Entering fail>
Aug 15 15:28:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: Failed with result 'timeout'.
Aug 15 15:28:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: Stopped OSTree Finalize Staged Deployment.
Aug 15 15:28:01 ci-ln-22pq4y2-72292-9h7tq-worker-a-wd9mn systemd[1]: ostree-finalize-staged.service: Consumed 3.458s CPU time

Comment 4 HuijingHei 2023-08-24 08:35:59 UTC
Change status to verified according to result in Comment 1

Comment 6 errata-xmlrpc 2023-11-14 15:37:15 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 (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:7063


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