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:
log_* & solution_file functions provided by API don't support use with multiple arguments, which could be useful in case you want to print longer text. For example this construction is useful for printing in bash:
$ echo "long text" \
       "enother text"

and this should work with log_functions too, e.g.
log_info "Some text" \
         "continue."

In addition, function log_info uses "$@" when processing input, however function
_log (which is called by func log_info) doesn't, so these two functions are not uniform in expected input.

Note:
This is only for bash, because it is usual use in this language. However Python
expect just one parameter and it make sense, because python has diffent constructions for format of longer texts.

After discussion it was decided that this funcionality will not be accepted
as it make differences between API for Python and Bash. So I am closing this rfe.