yum update

yum update

yum -y update
yum -y update --security

Amazon Linux 2

yum update
Loaded plugins: extras_suggestions, langpacks, priorities, update-
             : motd
amzn2-core                                 | 3.7 kB     00:00
216 packages excluded due to repository priority protections
No packages marked for update

Play with K8s

yum update
Loaded plugins: fastestmirror, ovl
Loading mirror speeds from cached hostfile
 * base: mirror.ams1.nl.leaseweb.net
 * extras: mirror.ams1.nl.leaseweb.net
 * updates: mirror.ams1.nl.leaseweb.net
base                                                                                                                                                                                                                           | 3.6 kB  00:00:00     
docker-ce-stable                                                                                                                                                                                                               | 3.5 kB  00:00:00     
extras                                                                                                                                                                                                                         | 2.9 kB  00:00:00     
https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (Kubernetes),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=kubernetes ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable kubernetes
        or
            subscription-manager repos --disable=kubernetes

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true

failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try.
https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

Related

• yum upgrade
• apt update
• history
• How to update Red Hat Enterprise Linux via minor releases and Extended Update Support
• yum-config-manager

See also

• YUM, [ install | update | upgrade | search | repolist | list| updateinfo | utils | config-manager | /etc/yum.conf ], /etc/yum/vars/releasever