Bug 1925306

Summary: Glibc update appears to break bash built-in for printf
Product: Red Hat Enterprise Linux 7 Reporter: Dagmar <paul.f.roberts.jr>
Component: glibcAssignee: glibc team <glibc-bugzilla>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.9CC: ashankar, codonell, dj, fweimer, jrd-rhbz, mails.bugzilla.redhat.com, mnewsome, pfrankli, sipoyare
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-05 02:10:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dagmar 2021-02-04 20:10:12 UTC 
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.
Comment 2 Matthias Hensler 2021-02-04 22:35:48 UTC 
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
Comment 3 Siddhesh Poyarekar 2021-02-05 02:10:16 UTC 

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