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 2041848

Summary: [RFE] - allow configuration of number of greenboot boot attempts
Product: Red Hat Enterprise Linux 9 Reporter: Peter Robinson <perobins>
Component: greenbootAssignee: Peter Robinson <perobins>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: atomic-bugs, bbreard, briasmit, dornelas, xiaofwan, yih
Target Milestone: rcKeywords: FutureFeature, Rebase, Triaged
Target Release: 9.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: greenboot-0.14.0-3.el9 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1920063 Environment:
Last Closed: 2022-05-17 13:51:19 UTC Type: Enhancement
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: 1920063    
Bug Blocks:    

Description Peter Robinson 2022-01-18 11:21:16 UTC
+++ This bug was initially created as a clone of Bug #1920063 +++

Description of problem:
In RHEL for Edge 8.3, greenboot will attempt 3 boots if the health check script fails.  This is a request to make the number of boot attempts configurable.  


Version-Release number of selected component (if applicable): RHEL for Edge 8.3, greenboot-0.11-1.el8.x86_64


How reproducible: Every time


Steps to Reproduce:
1.  Configure greenboot on RHEL for Edge system
2.  Upgrade RHEL for Edge
3.  If greenboot health check script fails, 3 boot attempts are completed before rollback.  

Actual results:
- Number of greenboot boot attempts does not appear to be configurable. 

Expected results:
- Able to configure number of greenboot boot attempts


Additional info:
It appears that the number of boot attempts is set in /etc/systemd/system/ostree-finalize-staged.service.requires/greenboot-grub2-set-counter.service  However, this file is a symbolic link to a file under /usr, which on RHEL for Edge, is mounted read-only.

Comment 7 Xiaofeng Wang 2022-03-04 03:30:54 UTC
Verified on:
greenboot-0.14.0-3.el9.x86_64
greenboot-default-health-checks-0.14.0-3.el9.x86_64

Comment 9 errata-xmlrpc 2022-05-17 13:51:19 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 (new packages: greenboot), 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-2022:2601