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:
Bash's printf built-in no longer believes zero is a number.

Version-Release number of selected component (if applicable):
glibc-2.17-322.el7_9.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Type "printf '%0.2f' 0" into a bash prompt or include it in a shell script.
2. Hit enter or run the script.
3. Gaze in wonder as the system declares that a centuries-old mathematical concept does not exist.

Actual results:
Output is 'nan'

Expected results:
Output should be '0.00'

Additional info:
2.17-317 seems fine.  Bash version doesn't appear to be related since the same bash package is installed on both unaffected (7.8.2003) and affected (7.9.2009), and this started happening after a weekly update cycle last night which didn't have a lot of shadowy characters involved.

I can confirm that this is triggered here to after updating glibc to 0:2.17-322.el7_9. If is fixed after downgrading back to 0:2.17-317.el7.

This bug should be related to https://bugzilla.redhat.com/show_bug.cgi?id=1925204

*** This bug has been marked as a duplicate of bug 1925204 ***