Yum in Amazon Linux 2 still asks for GPG key even after “rpm --import” when adding Kubernetes repogpg asks for password even with --passphraseBash 4.3 yum repository for Amazon LinuxCron on Amazon EC2 centos still executes even after deleteHow can i fix “ ”Failed to connect to 2001:19f0:0:2a:225:90ff:fe08:f840: Network is unreachable“”yum install in fedora 20 [Google chrome]How to import key that signs a repository for dnf/yumyum install and update fail - GPG keys listed for the “CentOS-7 - Updates” repository are already installed but they are not correctIssue with elrepo-kernel: packages are not availableHow to resolve Transaction check error while installing xrdp?explanation of RHEL/CentOS 7 yum repo gpg key

Number of states in taxi environment (Dietterich 2000)

Optimization models for portfolio optimization

Moving millions of files to a different directory with specfic name patterns

Four ships at the ocean with the same distance

I make billions (#6)

What factors could lead to bishops establishing monastic armies?

What is the problem here?(all integers are irrational proof...i think so)

Intern not wearing safety equipment; how could I have handled this differently?

A sequence that changes sign finally at infinity?

Was it ever illegal to name a pig "Napoleon" in France?

US citizen traveling with Peruvian passport

What are the consequences for a developed nation to not accept any refugees?

Write a function

Performance issue in code for reading line and testing for palindrome

Strong Password Detection in Python

What was this character's plan?

First Entry Member State schengen visa

VHF 50 Ω Antenna Over 75 Ω TV Coax

Non-Chromatic Orchestral Instruments?

My previous employer committed a severe violation of the law and is also being sued by me. How do I explain the situation to future employers?

Quoridor rules when faced the opponent

Correct notation for guitar fingerstyle

Did depressed people far more accurately estimate how many monsters they killed in a video game?

What does the multimeter dial do internally?



Yum in Amazon Linux 2 still asks for GPG key even after “rpm --import” when adding Kubernetes repo


gpg asks for password even with --passphraseBash 4.3 yum repository for Amazon LinuxCron on Amazon EC2 centos still executes even after deleteHow can i fix “ ”Failed to connect to 2001:19f0:0:2a:225:90ff:fe08:f840: Network is unreachable“”yum install in fedora 20 [Google chrome]How to import key that signs a repository for dnf/yumyum install and update fail - GPG keys listed for the “CentOS-7 - Updates” repository are already installed but they are not correctIssue with elrepo-kernel: packages are not availableHow to resolve Transaction check error while installing xrdp?explanation of RHEL/CentOS 7 yum repo gpg key






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








5















I'm trying to add a kubernetes repo to my Amazon Linux 2 instance and struggle with automatically adding GPG keys.



This is my /etc/yum.repos.d/kubernetes.repo...



[kubernetes]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg


I then try to import the GPG keys:




~ # wget https://packages.cloud.google.com/yum/doc/yum-key.gpg
https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

~ # rpm --import *.gpg


However when I run any yum command it still doesn't know the keys:



# yum upgrade -y
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
kubernetes/signature | 454 B 00:00:00
Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
Importing GPG key 0xA7317B0F:
Userid : "Google Cloud Packages Automatic Signing Key <gc-team@google.com>"
Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
kubernetes/signature | 1.4 kB 00:00:00 !!!
https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for kubernetes
Trying other mirror.
No packages marked for update


Even if I try to accept them manually it still doesn't work.



# yum upgrade
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
kubernetes/signature | 454 B 00:00:00
Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
Importing GPG key 0xA7317B0F:
Userid : "Google Cloud Packages Automatic Signing Key <gc-team@google.com>"
Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
Is this ok [y/N]: y <<<<< Yes, I accept it!
Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
kubernetes/signature | 1.4 kB 00:00:01 !!!
https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for kubernetes
Trying other mirror.
No packages marked for update


How can I add the key so that YUM accepts it?










share|improve this question






























    5















    I'm trying to add a kubernetes repo to my Amazon Linux 2 instance and struggle with automatically adding GPG keys.



    This is my /etc/yum.repos.d/kubernetes.repo...



    [kubernetes]
    name=Kubernetes
    baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
    enabled=1
    gpgcheck=1
    repo_gpgcheck=1
    gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
    https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg


    I then try to import the GPG keys:




    ~ # wget https://packages.cloud.google.com/yum/doc/yum-key.gpg
    https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

    ~ # rpm --import *.gpg


    However when I run any yum command it still doesn't know the keys:



    # yum upgrade -y
    Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
    kubernetes/signature | 454 B 00:00:00
    Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
    Importing GPG key 0xA7317B0F:
    Userid : "Google Cloud Packages Automatic Signing Key <gc-team@google.com>"
    Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
    From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
    Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
    kubernetes/signature | 1.4 kB 00:00:00 !!!
    https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for kubernetes
    Trying other mirror.
    No packages marked for update


    Even if I try to accept them manually it still doesn't work.



    # yum upgrade
    Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
    kubernetes/signature | 454 B 00:00:00
    Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
    Importing GPG key 0xA7317B0F:
    Userid : "Google Cloud Packages Automatic Signing Key <gc-team@google.com>"
    Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
    From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
    Is this ok [y/N]: y <<<<< Yes, I accept it!
    Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
    kubernetes/signature | 1.4 kB 00:00:01 !!!
    https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for kubernetes
    Trying other mirror.
    No packages marked for update


    How can I add the key so that YUM accepts it?










    share|improve this question


























      5












      5








      5








      I'm trying to add a kubernetes repo to my Amazon Linux 2 instance and struggle with automatically adding GPG keys.



      This is my /etc/yum.repos.d/kubernetes.repo...



      [kubernetes]
      name=Kubernetes
      baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
      enabled=1
      gpgcheck=1
      repo_gpgcheck=1
      gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
      https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg


      I then try to import the GPG keys:




      ~ # wget https://packages.cloud.google.com/yum/doc/yum-key.gpg
      https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

      ~ # rpm --import *.gpg


      However when I run any yum command it still doesn't know the keys:



      # yum upgrade -y
      Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
      kubernetes/signature | 454 B 00:00:00
      Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
      Importing GPG key 0xA7317B0F:
      Userid : "Google Cloud Packages Automatic Signing Key <gc-team@google.com>"
      Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
      From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
      Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
      kubernetes/signature | 1.4 kB 00:00:00 !!!
      https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for kubernetes
      Trying other mirror.
      No packages marked for update


      Even if I try to accept them manually it still doesn't work.



      # yum upgrade
      Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
      kubernetes/signature | 454 B 00:00:00
      Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
      Importing GPG key 0xA7317B0F:
      Userid : "Google Cloud Packages Automatic Signing Key <gc-team@google.com>"
      Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
      From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
      Is this ok [y/N]: y <<<<< Yes, I accept it!
      Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
      kubernetes/signature | 1.4 kB 00:00:01 !!!
      https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for kubernetes
      Trying other mirror.
      No packages marked for update


      How can I add the key so that YUM accepts it?










      share|improve this question
















      I'm trying to add a kubernetes repo to my Amazon Linux 2 instance and struggle with automatically adding GPG keys.



      This is my /etc/yum.repos.d/kubernetes.repo...



      [kubernetes]
      name=Kubernetes
      baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
      enabled=1
      gpgcheck=1
      repo_gpgcheck=1
      gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
      https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg


      I then try to import the GPG keys:




      ~ # wget https://packages.cloud.google.com/yum/doc/yum-key.gpg
      https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

      ~ # rpm --import *.gpg


      However when I run any yum command it still doesn't know the keys:



      # yum upgrade -y
      Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
      kubernetes/signature | 454 B 00:00:00
      Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
      Importing GPG key 0xA7317B0F:
      Userid : "Google Cloud Packages Automatic Signing Key <gc-team@google.com>"
      Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
      From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
      Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
      kubernetes/signature | 1.4 kB 00:00:00 !!!
      https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for kubernetes
      Trying other mirror.
      No packages marked for update


      Even if I try to accept them manually it still doesn't work.



      # yum upgrade
      Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
      kubernetes/signature | 454 B 00:00:00
      Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
      Importing GPG key 0xA7317B0F:
      Userid : "Google Cloud Packages Automatic Signing Key <gc-team@google.com>"
      Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
      From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
      Is this ok [y/N]: y <<<<< Yes, I accept it!
      Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
      kubernetes/signature | 1.4 kB 00:00:01 !!!
      https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for kubernetes
      Trying other mirror.
      No packages marked for update


      How can I add the key so that YUM accepts it?







      yum rpm gpg amazon-ec2 kubernetes






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 30 at 8:17









      Edward

      8375 silver badges16 bronze badges




      8375 silver badges16 bronze badges










      asked Jun 30 at 7:00









      KeepLearningKeepLearning

      504 bronze badges




      504 bronze badges




















          1 Answer
          1






          active

          oldest

          votes


















          5














          This is a known issue (see https://github.com/kubernetes/kubernetes/issues/60134).
          Work around it by disabling GPG checks: set repo_gpgcheck=0 in /etc/yum.repos.d/kubernetes.repo.



          Credits to drakedevel, who writes:




          I think this is due to Amazon Linux 2 shipping an old version of GnuPG, and something about the repomd.xml.asc signature requires a newer version.



          GnuPG 2.0.22 outright rejects the signature on the repository metadata with assuming bad signature from key BA07F4FB due to an unknown critical bit. I haven't been able to figure out what critical bit it's referring to -- there don't appear to be any on the signature or key -- but whatever GnuPG 2.0.22 is upset about is most likely the root cause.



          This only affects the repomd signature, so there's zero reason to disable gpgcheck as several others have suggested. Disabling repo_gpgcheck is sufficient and preserves package signature verification (although it's still not an ideal workaround...)







          share|improve this answer



























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f527707%2fyum-in-amazon-linux-2-still-asks-for-gpg-key-even-after-rpm-import-when-addi%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            5














            This is a known issue (see https://github.com/kubernetes/kubernetes/issues/60134).
            Work around it by disabling GPG checks: set repo_gpgcheck=0 in /etc/yum.repos.d/kubernetes.repo.



            Credits to drakedevel, who writes:




            I think this is due to Amazon Linux 2 shipping an old version of GnuPG, and something about the repomd.xml.asc signature requires a newer version.



            GnuPG 2.0.22 outright rejects the signature on the repository metadata with assuming bad signature from key BA07F4FB due to an unknown critical bit. I haven't been able to figure out what critical bit it's referring to -- there don't appear to be any on the signature or key -- but whatever GnuPG 2.0.22 is upset about is most likely the root cause.



            This only affects the repomd signature, so there's zero reason to disable gpgcheck as several others have suggested. Disabling repo_gpgcheck is sufficient and preserves package signature verification (although it's still not an ideal workaround...)







            share|improve this answer





























              5














              This is a known issue (see https://github.com/kubernetes/kubernetes/issues/60134).
              Work around it by disabling GPG checks: set repo_gpgcheck=0 in /etc/yum.repos.d/kubernetes.repo.



              Credits to drakedevel, who writes:




              I think this is due to Amazon Linux 2 shipping an old version of GnuPG, and something about the repomd.xml.asc signature requires a newer version.



              GnuPG 2.0.22 outright rejects the signature on the repository metadata with assuming bad signature from key BA07F4FB due to an unknown critical bit. I haven't been able to figure out what critical bit it's referring to -- there don't appear to be any on the signature or key -- but whatever GnuPG 2.0.22 is upset about is most likely the root cause.



              This only affects the repomd signature, so there's zero reason to disable gpgcheck as several others have suggested. Disabling repo_gpgcheck is sufficient and preserves package signature verification (although it's still not an ideal workaround...)







              share|improve this answer



























                5












                5








                5







                This is a known issue (see https://github.com/kubernetes/kubernetes/issues/60134).
                Work around it by disabling GPG checks: set repo_gpgcheck=0 in /etc/yum.repos.d/kubernetes.repo.



                Credits to drakedevel, who writes:




                I think this is due to Amazon Linux 2 shipping an old version of GnuPG, and something about the repomd.xml.asc signature requires a newer version.



                GnuPG 2.0.22 outright rejects the signature on the repository metadata with assuming bad signature from key BA07F4FB due to an unknown critical bit. I haven't been able to figure out what critical bit it's referring to -- there don't appear to be any on the signature or key -- but whatever GnuPG 2.0.22 is upset about is most likely the root cause.



                This only affects the repomd signature, so there's zero reason to disable gpgcheck as several others have suggested. Disabling repo_gpgcheck is sufficient and preserves package signature verification (although it's still not an ideal workaround...)







                share|improve this answer















                This is a known issue (see https://github.com/kubernetes/kubernetes/issues/60134).
                Work around it by disabling GPG checks: set repo_gpgcheck=0 in /etc/yum.repos.d/kubernetes.repo.



                Credits to drakedevel, who writes:




                I think this is due to Amazon Linux 2 shipping an old version of GnuPG, and something about the repomd.xml.asc signature requires a newer version.



                GnuPG 2.0.22 outright rejects the signature on the repository metadata with assuming bad signature from key BA07F4FB due to an unknown critical bit. I haven't been able to figure out what critical bit it's referring to -- there don't appear to be any on the signature or key -- but whatever GnuPG 2.0.22 is upset about is most likely the root cause.



                This only affects the repomd signature, so there's zero reason to disable gpgcheck as several others have suggested. Disabling repo_gpgcheck is sufficient and preserves package signature verification (although it's still not an ideal workaround...)








                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jun 30 at 7:21

























                answered Jun 30 at 7:16









                EdwardEdward

                8375 silver badges16 bronze badges




                8375 silver badges16 bronze badges



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f527707%2fyum-in-amazon-linux-2-still-asks-for-gpg-key-even-after-rpm-import-when-addi%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Category:9 (number) SubcategoriesMedia in category "9 (number)"Navigation menuUpload mediaGND ID: 4485639-8Library of Congress authority ID: sh85091979ReasonatorScholiaStatistics

                    Circuit construction for execution of conditional statements using least significant bitHow are two different registers being used as “control”?How exactly is the stated composite state of the two registers being produced using the $R_zz$ controlled rotations?Efficiently performing controlled rotations in HHLWould this quantum algorithm implementation work?How to prepare a superposed states of odd integers from $1$ to $sqrtN$?Why is this implementation of the order finding algorithm not working?Circuit construction for Hamiltonian simulationHow can I invert the least significant bit of a certain term of a superposed state?Implementing an oracleImplementing a controlled sum operation

                    Magento 2 “No Payment Methods” in Admin New OrderHow to integrate Paypal Express Checkout with the Magento APIMagento 1.5 - Sales > Order > edit order and shipping methods disappearAuto Invoice Check/Money Order Payment methodAdd more simple payment methods?Shipping methods not showingWhat should I do to change payment methods if changing the configuration has no effects?1.9 - No Payment Methods showing upMy Payment Methods not Showing for downloadable/virtual product when checkout?Magento2 API to access internal payment methodHow to call an existing payment methods in the registration form?