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.

log_*() functions in bash API (for Preupgrade Assistant modules) accept multiple parameters ($@), however main _log() function, that is subsequently called, ignores all but the first parameter.
In python the log_*() functions correctly accept only one parameter.

Replace $@ by $1 in log_*() functions in bash API. They will be then synced with API for Python.

Version-Release number of selected component (if applicable):
preupgrade-assistant-2.2.0-1.el6

Fixed in upstream: https://github.com/upgrades-migrations/preupgrade-assistant/commit/34cb3c10fa368900e892f51e21d333dcb5a207a1

pstodulk, do you need a bugzilla for modules so they are updated accordingly to the change described above?

NOpe. Behaviour is not changed and original troubles are already fixed in devel repository. Patches will be applied in next build.

Test suite works. Nothing broken.

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