Azure RedHat vm yum update fails with “SSL peer rejected your certificate as expired.”












7















I just started a Standard RedHat 7 VM on Azure.



I login and type:



sudo yum update


and get:



Loaded plugins: langpacks, product-id, search-disabled-repos
https://rhui-3.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7Server/x86_64/dotnet/1/debug/repodata/repomd.xml:
[Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
Trying other mirror.
https://rhui-1.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7Server/x86_64/dotnet/1/debug/repodata/repomd.xml:
[Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
Trying other mirror.
...


I thought that the PAYG license include updates? Or is the current image broken?
Tried the 7.4 image too?










share|improve this question























  • Take a look this. Maybe it's helpful.

    – Charles Xu
    Nov 23 '18 at 1:54











  • Also, you could run the command with root.

    – Charles Xu
    Nov 23 '18 at 2:11











  • This is also affecting me, Azure RHEL VM and it's only started happening in the past few days. I'm going to lodge a support ticket with Microsoft.

    – pickles
    Nov 23 '18 at 8:02
















7















I just started a Standard RedHat 7 VM on Azure.



I login and type:



sudo yum update


and get:



Loaded plugins: langpacks, product-id, search-disabled-repos
https://rhui-3.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7Server/x86_64/dotnet/1/debug/repodata/repomd.xml:
[Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
Trying other mirror.
https://rhui-1.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7Server/x86_64/dotnet/1/debug/repodata/repomd.xml:
[Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
Trying other mirror.
...


I thought that the PAYG license include updates? Or is the current image broken?
Tried the 7.4 image too?










share|improve this question























  • Take a look this. Maybe it's helpful.

    – Charles Xu
    Nov 23 '18 at 1:54











  • Also, you could run the command with root.

    – Charles Xu
    Nov 23 '18 at 2:11











  • This is also affecting me, Azure RHEL VM and it's only started happening in the past few days. I'm going to lodge a support ticket with Microsoft.

    – pickles
    Nov 23 '18 at 8:02














7












7








7


1






I just started a Standard RedHat 7 VM on Azure.



I login and type:



sudo yum update


and get:



Loaded plugins: langpacks, product-id, search-disabled-repos
https://rhui-3.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7Server/x86_64/dotnet/1/debug/repodata/repomd.xml:
[Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
Trying other mirror.
https://rhui-1.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7Server/x86_64/dotnet/1/debug/repodata/repomd.xml:
[Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
Trying other mirror.
...


I thought that the PAYG license include updates? Or is the current image broken?
Tried the 7.4 image too?










share|improve this question














I just started a Standard RedHat 7 VM on Azure.



I login and type:



sudo yum update


and get:



Loaded plugins: langpacks, product-id, search-disabled-repos
https://rhui-3.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7Server/x86_64/dotnet/1/debug/repodata/repomd.xml:
[Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
Trying other mirror.
https://rhui-1.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7Server/x86_64/dotnet/1/debug/repodata/repomd.xml:
[Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
Trying other mirror.
...


I thought that the PAYG license include updates? Or is the current image broken?
Tried the 7.4 image too?







azure redhat yum






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 18:25









Robin OwensRobin Owens

3613




3613













  • Take a look this. Maybe it's helpful.

    – Charles Xu
    Nov 23 '18 at 1:54











  • Also, you could run the command with root.

    – Charles Xu
    Nov 23 '18 at 2:11











  • This is also affecting me, Azure RHEL VM and it's only started happening in the past few days. I'm going to lodge a support ticket with Microsoft.

    – pickles
    Nov 23 '18 at 8:02



















  • Take a look this. Maybe it's helpful.

    – Charles Xu
    Nov 23 '18 at 1:54











  • Also, you could run the command with root.

    – Charles Xu
    Nov 23 '18 at 2:11











  • This is also affecting me, Azure RHEL VM and it's only started happening in the past few days. I'm going to lodge a support ticket with Microsoft.

    – pickles
    Nov 23 '18 at 8:02

















Take a look this. Maybe it's helpful.

– Charles Xu
Nov 23 '18 at 1:54





Take a look this. Maybe it's helpful.

– Charles Xu
Nov 23 '18 at 1:54













Also, you could run the command with root.

– Charles Xu
Nov 23 '18 at 2:11





Also, you could run the command with root.

– Charles Xu
Nov 23 '18 at 2:11













This is also affecting me, Azure RHEL VM and it's only started happening in the past few days. I'm going to lodge a support ticket with Microsoft.

– pickles
Nov 23 '18 at 8:02





This is also affecting me, Azure RHEL VM and it's only started happening in the past few days. I'm going to lodge a support ticket with Microsoft.

– pickles
Nov 23 '18 at 8:02












4 Answers
4






active

oldest

votes


















11














I also faced same issue yesterday. I referred to following links on Redhat Support Portal.





  • https://access.redhat.com/articles/3189332 (for instructions to link Azure account with RH Portal and register for portal,

  • (registration must) https://access.redhat.com/solutions/3167021


Though my problem didn't got resolved from the above post after following instructions as it is, after taking cue from the problem description, following worked for me. In my case, older version of "rhui-azure-rhel7" RPM was installed on VM I had setup few weeks back where I was facing same issue as yours.



curl -o azureclient.rpm https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
rpm -U azureclient.rpm


Hope this helps.






share|improve this answer
























  • This is the correct answer. RHEL machines use client certificates to authenticate to to the Red Hat Update Infrastructure. That cert has expired and needs a manual update via the package rhui-azure-rhel7, and the exact version number gets updated over time.

    – Dave Mulford
    Nov 26 '18 at 16:40






  • 1





    Thanks! A more direct form worked for me too: rpm -Uvh https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm

    – kim0
    Nov 28 '18 at 22:38





















2














I ran into this issue previously and the workaround provided by Azure support was to run the following commands:



wget  https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
sudo rpm -U rhui-azure-rhel7-2.2-74.noarch.rpm
sudo yum clean all
sudo yum repolist





share|improve this answer































    0














    I also encounter this issue from a few days.
    I found this thread:



    https://access.redhat.com/solutions/3167021






    share|improve this answer































      -1














      Try run sudo yum upgrade and then you should be able to have this working






      share|improve this answer























        Your Answer






        StackExchange.ifUsing("editor", function () {
        StackExchange.using("externalEditor", function () {
        StackExchange.using("snippets", function () {
        StackExchange.snippets.init();
        });
        });
        }, "code-snippets");

        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "1"
        };
        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: true,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: 10,
        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%2fstackoverflow.com%2fquestions%2f53436443%2fazure-redhat-vm-yum-update-fails-with-ssl-peer-rejected-your-certificate-as-exp%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        4 Answers
        4






        active

        oldest

        votes








        4 Answers
        4






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        11














        I also faced same issue yesterday. I referred to following links on Redhat Support Portal.





        • https://access.redhat.com/articles/3189332 (for instructions to link Azure account with RH Portal and register for portal,

        • (registration must) https://access.redhat.com/solutions/3167021


        Though my problem didn't got resolved from the above post after following instructions as it is, after taking cue from the problem description, following worked for me. In my case, older version of "rhui-azure-rhel7" RPM was installed on VM I had setup few weeks back where I was facing same issue as yours.



        curl -o azureclient.rpm https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
        rpm -U azureclient.rpm


        Hope this helps.






        share|improve this answer
























        • This is the correct answer. RHEL machines use client certificates to authenticate to to the Red Hat Update Infrastructure. That cert has expired and needs a manual update via the package rhui-azure-rhel7, and the exact version number gets updated over time.

          – Dave Mulford
          Nov 26 '18 at 16:40






        • 1





          Thanks! A more direct form worked for me too: rpm -Uvh https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm

          – kim0
          Nov 28 '18 at 22:38


















        11














        I also faced same issue yesterday. I referred to following links on Redhat Support Portal.





        • https://access.redhat.com/articles/3189332 (for instructions to link Azure account with RH Portal and register for portal,

        • (registration must) https://access.redhat.com/solutions/3167021


        Though my problem didn't got resolved from the above post after following instructions as it is, after taking cue from the problem description, following worked for me. In my case, older version of "rhui-azure-rhel7" RPM was installed on VM I had setup few weeks back where I was facing same issue as yours.



        curl -o azureclient.rpm https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
        rpm -U azureclient.rpm


        Hope this helps.






        share|improve this answer
























        • This is the correct answer. RHEL machines use client certificates to authenticate to to the Red Hat Update Infrastructure. That cert has expired and needs a manual update via the package rhui-azure-rhel7, and the exact version number gets updated over time.

          – Dave Mulford
          Nov 26 '18 at 16:40






        • 1





          Thanks! A more direct form worked for me too: rpm -Uvh https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm

          – kim0
          Nov 28 '18 at 22:38
















        11












        11








        11







        I also faced same issue yesterday. I referred to following links on Redhat Support Portal.





        • https://access.redhat.com/articles/3189332 (for instructions to link Azure account with RH Portal and register for portal,

        • (registration must) https://access.redhat.com/solutions/3167021


        Though my problem didn't got resolved from the above post after following instructions as it is, after taking cue from the problem description, following worked for me. In my case, older version of "rhui-azure-rhel7" RPM was installed on VM I had setup few weeks back where I was facing same issue as yours.



        curl -o azureclient.rpm https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
        rpm -U azureclient.rpm


        Hope this helps.






        share|improve this answer













        I also faced same issue yesterday. I referred to following links on Redhat Support Portal.





        • https://access.redhat.com/articles/3189332 (for instructions to link Azure account with RH Portal and register for portal,

        • (registration must) https://access.redhat.com/solutions/3167021


        Though my problem didn't got resolved from the above post after following instructions as it is, after taking cue from the problem description, following worked for me. In my case, older version of "rhui-azure-rhel7" RPM was installed on VM I had setup few weeks back where I was facing same issue as yours.



        curl -o azureclient.rpm https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
        rpm -U azureclient.rpm


        Hope this helps.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 23 '18 at 11:18









        Kishan ParekhKishan Parekh

        31116




        31116













        • This is the correct answer. RHEL machines use client certificates to authenticate to to the Red Hat Update Infrastructure. That cert has expired and needs a manual update via the package rhui-azure-rhel7, and the exact version number gets updated over time.

          – Dave Mulford
          Nov 26 '18 at 16:40






        • 1





          Thanks! A more direct form worked for me too: rpm -Uvh https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm

          – kim0
          Nov 28 '18 at 22:38





















        • This is the correct answer. RHEL machines use client certificates to authenticate to to the Red Hat Update Infrastructure. That cert has expired and needs a manual update via the package rhui-azure-rhel7, and the exact version number gets updated over time.

          – Dave Mulford
          Nov 26 '18 at 16:40






        • 1





          Thanks! A more direct form worked for me too: rpm -Uvh https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm

          – kim0
          Nov 28 '18 at 22:38



















        This is the correct answer. RHEL machines use client certificates to authenticate to to the Red Hat Update Infrastructure. That cert has expired and needs a manual update via the package rhui-azure-rhel7, and the exact version number gets updated over time.

        – Dave Mulford
        Nov 26 '18 at 16:40





        This is the correct answer. RHEL machines use client certificates to authenticate to to the Red Hat Update Infrastructure. That cert has expired and needs a manual update via the package rhui-azure-rhel7, and the exact version number gets updated over time.

        – Dave Mulford
        Nov 26 '18 at 16:40




        1




        1





        Thanks! A more direct form worked for me too: rpm -Uvh https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm

        – kim0
        Nov 28 '18 at 22:38







        Thanks! A more direct form worked for me too: rpm -Uvh https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm

        – kim0
        Nov 28 '18 at 22:38















        2














        I ran into this issue previously and the workaround provided by Azure support was to run the following commands:



        wget  https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
        sudo rpm -U rhui-azure-rhel7-2.2-74.noarch.rpm
        sudo yum clean all
        sudo yum repolist





        share|improve this answer




























          2














          I ran into this issue previously and the workaround provided by Azure support was to run the following commands:



          wget  https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
          sudo rpm -U rhui-azure-rhel7-2.2-74.noarch.rpm
          sudo yum clean all
          sudo yum repolist





          share|improve this answer


























            2












            2








            2







            I ran into this issue previously and the workaround provided by Azure support was to run the following commands:



            wget  https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
            sudo rpm -U rhui-azure-rhel7-2.2-74.noarch.rpm
            sudo yum clean all
            sudo yum repolist





            share|improve this answer













            I ran into this issue previously and the workaround provided by Azure support was to run the following commands:



            wget  https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm
            sudo rpm -U rhui-azure-rhel7-2.2-74.noarch.rpm
            sudo yum clean all
            sudo yum repolist






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 7 at 1:54









            IcehornIcehorn

            435211




            435211























                0














                I also encounter this issue from a few days.
                I found this thread:



                https://access.redhat.com/solutions/3167021






                share|improve this answer




























                  0














                  I also encounter this issue from a few days.
                  I found this thread:



                  https://access.redhat.com/solutions/3167021






                  share|improve this answer


























                    0












                    0








                    0







                    I also encounter this issue from a few days.
                    I found this thread:



                    https://access.redhat.com/solutions/3167021






                    share|improve this answer













                    I also encounter this issue from a few days.
                    I found this thread:



                    https://access.redhat.com/solutions/3167021







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Nov 23 '18 at 9:51









                    MastroBirraioMastroBirraio

                    1




                    1























                        -1














                        Try run sudo yum upgrade and then you should be able to have this working






                        share|improve this answer




























                          -1














                          Try run sudo yum upgrade and then you should be able to have this working






                          share|improve this answer


























                            -1












                            -1








                            -1







                            Try run sudo yum upgrade and then you should be able to have this working






                            share|improve this answer













                            Try run sudo yum upgrade and then you should be able to have this working







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Nov 22 '18 at 23:43









                            Tim RaynorTim Raynor

                            3271621




                            3271621






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Stack Overflow!


                                • 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%2fstackoverflow.com%2fquestions%2f53436443%2fazure-redhat-vm-yum-update-fails-with-ssl-peer-rejected-your-certificate-as-exp%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

                                If I really need a card on my start hand, how many mulligans make sense? [duplicate]

                                Alcedinidae

                                Can an atomic nucleus contain both particles and antiparticles? [duplicate]