fedora-infrastructure

#12413 Latest update of gnutls causing NetworkManager to fail to start on ppc64le machines
Closed: Fixed by zlopez. Opened by zlopez.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

Today bvmhost-p09-04 was reported by Nagios as DOWN. I restarted the machine but it was not reachable by ssh, but still available through ipmitool. After some investigation of the journal I found out that the NetworkManager failed to start, which was caused by trying to import latest version of gnutls library (gnutls-3.8.9-2.fc41). I checked the dnf history and the latest update did updated gnutls. So I undone the update and rebooted the machine again. After that the NetworkManager started without issue.

I already opened ticket on bugzilla about this issue.

I'm opening this ticket more for discussion what to do about it and to track it here.

When do you need this to be done by? (YYYY/MM/DD)

@kevin Should we just add gnutls to dnf ignore list for now. Till the situation is resolved? I saw this only on the one ppc64le host, but it could probably happen to others.

According to the bugzilla discussion, it seems that the issue is probably with the machine. Maybe faulty disk on bvmhost-p09-04. They are probably the same age as bvmhost-p09-03 which is having disk issues as well :-/

And one of the VMs seems to be stuck on start, so that is another thing pointing on faulty disk.

After trying to reapply the updates the NetworkManager started without issue. Not sure what messed up the library, but it was probably a one-time issue.

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata

medium-gain medium-trouble ops

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.