2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
The script is probably using the EC2 Instance Meta Data Service to find the region it is in. Was IMDS turned off or set to only support V2 of the IMDS?
0
For me, this was resolived by installing the rh-amazon-rhui-client rpm. Because I could not do anything with dnf (yum), I could not install it with "dnf install rh-amazon-rhui-client". I had to go to a working server, run "dnf download rh-amazon-rhui-client", which downloaded the file rh-amazon-rhui-client-4.0.14-1.el8.noarch.rpm. I copied that file to the broken server and ran "rpm -Uvh rh-amazon-rhui-client-4.0.14-1.el8.noarch.rpm" to install it. Then, when I ran "dnf update", it reconfigured itself and began working.
répondu il y a un mois
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 8 mois
- AWS OFFICIELA mis à jour il y a 10 mois
- AWS OFFICIELA mis à jour il y a 4 mois
It wasn't IMDS directly, but when I looked into what IMDS was, I realized that the host based firewall (I know it seems redundant but it's a requirement) was blocking access to 169.254.169.254 which IMDS uses. Thanks!