Bug 2346780 - NetworkManager fails to start with latest version of gnutls
Summary: NetworkManager fails to start with latest version of gnutls
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnutls
Version: 41
Hardware: ppc64le
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Red Hat Crypto Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-20 10:36 UTC by Michal Konecny
Modified: 2025-02-20 14:27 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-20 12:35:22 UTC
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1491 0 None None None 2025-02-20 10:37:40 UTC

Description Michal Konecny 2025-02-20 10:36:51 UTC
After update of gnutls today (20.02.2025) on our builder VM host in Fedora Infrastructure the NetworkManager failed to start with issue when importing gnutls library.

After downgrading to gnutls-3.8.8-3.fc41.ppc64le it started working fine again.

Reproducible: Always

Steps to Reproduce:
1. Update to gnutls-3.8.9-2.fc41.src.rpm
2. Restart machine
Actual Results:  
NetworkManager fails to start

Expected Results:  
NetworkManager is running

Comment 1 Alexander Sosedkin 2025-02-20 10:47:34 UTC
... cannot reproduce on x86_64, will try on ppc64le. What's the error, by the way?

Comment 2 Michal Konecny 2025-02-20 11:03:56 UTC
Forgot to add the actual error:

```
Feb 20 10:13:28 bvmhost-p09-04.iad2.fedoraproject.org NetworkManager[6041]: /usr/sbin/NetworkManager: error while loading shared libraries: /lib64/libgnutls.so.30: file too short
```

We have a dnf automatic script setup on our machines and I noticed only this one ppc64le misbehaving like that.

Comment 3 Alexander Sosedkin 2025-02-20 12:10:19 UTC
That's purely vibes-only analysis at this point, but smells like data corruption to me.
The following diagnostics steps might prove useful in either confirming or denying this:

sha256sum /lib64/libgnutls.so.30
wc -c /lib64/libgnutls.so.30
rpm -V gnutls

Comment 4 Alexander Sosedkin 2025-02-20 12:35:22 UTC
... got a ppc64le, and yes, cannot reproduce:

# rpm -q gnutls
gnutls-3.8.9-2.fc41.ppc64le
# systemctl restart NetworkManager
# sha256sum /lib64/libgnutls.so.30
c82003a1afa8a84d7c8dc5a197b0d4d37f4502111764c5db402b4b78a87eeb49  /lib64/libgnutls.so.30
# wc -c /lib64/libgnutls.so.30
2866664 /lib64/libgnutls.so.30
# rpm -V gnutls && echo OK
OK

unless I manually truncate the shared library:

# :>/lib64/libgnutls.so.30
# sha256sum /lib64/libgnutls.so.30
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855  /lib64/libgnutls.so.30
# wc -c /lib64/libgnutls.so.30
0 /lib64/libgnutls.so.30
# rpm -V gnutls
S.5....T.    /usr/lib64/libgnutls.so.30.40.3
# systemctl restart NetworkManager
Job for NetworkManager.service failed because the control process exited with error code.
See "systemctl status NetworkManager.service" and "journalctl -xeu NetworkManager.service" for details.
[root@ibm-p10-01-lp65 ~]# journalctl -u NetworkManager|grep short
Feb 20 07:30:03 *redacted* NetworkManager[2220]: /usr/sbin/NetworkManager: error while loading shared libraries: /lib64/libgnutls.so.30: file too short
...
# dnf -y reinstall gnutls
# systemctl restart NetworkManager

Sorry to be the bearer of bad news, but please double-check the health of this machines partition and/or disk.

Comment 5 Michal Konecny 2025-02-20 14:27:51 UTC
Disk corruption is possible, we have another ppc63le machine that started to have problems with disks and they are same age as this one. Thanks for your time.


Note You need to log in before you can comment on or make changes to this bug.