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.
enhancement request:
The customer desires the ability to be able to rollback to a last known good version of an RPM in less than four minutes across many thousands of systems, if a software bug or other deficiency is discovered post installation. To facilitate this requirement previous contents of the last known good version of the RPM must be preserved during installation of the new RPM.
Requirements:
- The rollback must be name value pair specific for the package and version and not rely upon date or time. Rolling back foobar-10.0 will revert the software to foo-9.0.
- The rollback should also rollback one-to-one dependencies if possible. Dependencies used by more than one package should not rollback. If package-a.9.0 and package-b.21.0 are both dependent on package-c.99.0 and a rollback on package-a.9.0 is requested then package-a.9.0 will rollback, package-c.99.0 will remain unchanged, and an error will be logged. If package-c.99.0 has no other linked dependencies other than package-a.9.0 then both packages will rollback.
- Files that do not match the original MD5 signature, configuration files that can be altered post installation, for example should not be excluded from the snapshot due to a failed signature.
Assumptions:
- Command and control software is in place to issue the necessary commands to execute rollback scenarios.
Comment 5RHEL Program Management
2011-12-07 10:05:10 UTC
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.