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.
TLS certs seem to be backed up on dirtyconf:
$ tree dirtyconf/etc/openldap/certs/
dirtyconf/etc/openldap/certs/
├── cert8.db
├── key3.db
├── password
└── secmod.db
...but the module behavior is a bit strange:
* there's a medium risk, but result is 'informational'. I don't think
it's valid
* the risk message has three lines; this basically means there's risk with
colon at the end and then two stray lines
* the messages are a bit confusing. The risk speaks about new dir structure,
the first stray line shows how to migrate it, then the next line shows
how to do DAC but it's not consistent with solution text.
I think that a nicer way would be to print just a brief log_info (or risk, but then we should have other result), then append fuller explanation(s) (including commands) to solution text.
Note: Some parts of above behavior might be actually shipped; in that case it's OK from our POV to keep it (ie. avoid touching legacy code), just the new message should be probably conforming...
Testing with preupgrade-assistant-el6toel7-0.6.59-5.el6:
* The result is now needs_inspection.
* Risk is brief, one-line.
* Further info is in solution text.
Thank you!
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, 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://rhn.redhat.com/errata/RHEA-2016-2618.html