Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hello @admin245734 and @azaj.ikbal,
So indeed I’ve managed to recreate the issue. This is coming from the fact that when you create a new CentOS Droplet and then try to update it with the dnf or yum update command you are updating the rpm package as well causing differences in the rpm version trying to unpackage rpm files thus coming with an error like :
Problem opening package linux-firmware-20230217-113.git83f1d778.el8.noarch.rpm
I’ve reported this however for the time being what you can do is to update rpm alone and then do the dnf update on all packages;
- dnf update rpm
After that is completed:
- dnf update
Hey @admin245734,
I’ve found a similar bug in this thread :
https://bugzilla.redhat.com/show_bug.cgi?id=1192524
Can you set skip_if_unavailable=True and timeout=400 in etc/dnf/dnf.conf and try again?
Additionally, can you paste the contents of your dnf conf?
Hi @admin245734,
Try adding the following lines to your /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
If it doesn’t work, try adding the following parameter to your update command:
- sudo yum update --nogpgcheck
Let me know how it goes,
Sergio Turpín