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.
Description of problem
======================
In some cases, `preupg` ends with 255, even though everything else seems
to be OK.
I found this when running mysql module test, which runs all 4 database
modules in loop with varying presence of incompatible options or mysql
packages.
There seems to be corelation with results:
notapplicable notapplicable notapplicable notapplicable FAIL
notapplicable pass informational informational FAIL
notapplicable notapplicable notapplicable needs_action PASS
notapplicable pass informational needs_action PASS
notapplicable pass informational needs_inspection PASS
It seems as if only cases containing at leasr "needs_inspection" or
"needs_action" behave normally.
The exact command run in the test is:
preupg --force --select-rules 'xccdf_preupg_rule_databases_postgresql_pre,xccdf_preupg_rule_databases_mysql_data_migration_migration,xccdf_preupg_rule_databases_mysql_configuration_changes_configuration,xccdf_preupg_rule_databases_mysql_general_changes_general'
Version-Release number of selected component
============================================
preupgrade-assistant-2.1.8-2.el6
preupgrade-assistant-el6toel7-0.6.52-1.el6
How reproducible
================
Always (with this test)
Steps to Reproduce
==================
Schedule test /CoreOS/preupgrade-assistant/6to7/contents/mysql-configuration_changes:
ipu sched -B -t /CoreOS/preupgrade-assistant/6to7/contents/mysql-configuration_changes | bash
Actual results
==============
Some subtests report failure due to exit status 255
Expected results
================
Exit status should be 0, 1 or 2 in all sub-tests (i.e. the preupg wrapper
should always report PASS)
(In reply to Petr Hracek from comment #4)
> OK, I will look on it.
> It is a pretty hard to test it, though.
It's probably hard to test the failure cases, but the "normal" cases (various result combinations, 0-3) should be relatively straightforward, and those are currently hurting us most.
(I'm planning to write test focused on the "normal" cases; and more in future cycles...)
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/RHBA-2017-0819.html
Description of problem ====================== In some cases, `preupg` ends with 255, even though everything else seems to be OK. I found this when running mysql module test, which runs all 4 database modules in loop with varying presence of incompatible options or mysql packages. There seems to be corelation with results: notapplicable notapplicable notapplicable notapplicable FAIL notapplicable pass informational informational FAIL notapplicable notapplicable notapplicable needs_action PASS notapplicable pass informational needs_action PASS notapplicable pass informational needs_inspection PASS It seems as if only cases containing at leasr "needs_inspection" or "needs_action" behave normally. The exact command run in the test is: preupg --force --select-rules 'xccdf_preupg_rule_databases_postgresql_pre,xccdf_preupg_rule_databases_mysql_data_migration_migration,xccdf_preupg_rule_databases_mysql_configuration_changes_configuration,xccdf_preupg_rule_databases_mysql_general_changes_general' Version-Release number of selected component ============================================ preupgrade-assistant-2.1.8-2.el6 preupgrade-assistant-el6toel7-0.6.52-1.el6 How reproducible ================ Always (with this test) Steps to Reproduce ================== Schedule test /CoreOS/preupgrade-assistant/6to7/contents/mysql-configuration_changes: ipu sched -B -t /CoreOS/preupgrade-assistant/6to7/contents/mysql-configuration_changes | bash Actual results ============== Some subtests report failure due to exit status 255 Expected results ================ Exit status should be 0, 1 or 2 in all sub-tests (i.e. the preupg wrapper should always report PASS)