Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-967

OpenSUSE repository redirects https -> http

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: etc, www
    • Environment:
    • Similar Issues:

      Description

      Retrieving the jenkins rpm package for OpenSUSE fails when you run "zypper update" or "zypper install".

      Retrieving package jenkins-2.28-1.2.noarch                                                                                                    (1/15),  66.7 MiB ( 66.9 MiB unpacked)
      Retrieving: jenkins-2.28-1.2.noarch.rpm .....................................................................................................................................[error]
      Download (curl) error for 'https://pkg.jenkins.io/opensuse/jenkins-2.28-1.2.noarch.rpm':
      Error code:  Bad URL
      Error message: Protocol "http" not supported or disabled in libcurl
      

      We're using the official repository (taken from https://pkg.jenkins.io/opensuse/):

      # | Alias   |  Name    | Enabled | GPG Check | Refresh | URI                                                             
      3 | jenkins |  jenkins | Yes     | (r ) Yes  | Yes     | https://pkg.jenkins.io/opensuse/                                 
      

      The easiest way to reproduce/test this would be to execute:

      jenkins:~ # zypper in "https://pkg.jenkins.io/opensuse/jenkins-2.28-1.2.noarch.rpm"
      

      This will return the same error.

      P.S. Watchout for zypper cache - run "zypper clean" every now and then.

        Attachments

          Issue Links

            Activity

            Hide
            rtyler R. Tyler Croy added a comment -

            Thanks for filing this. Daniel Beck, how long do you think I should wait for the Debian-based repositories to "soak test" before I start switching more repositories to sent HTTPs traffic to Azure?

            Show
            rtyler R. Tyler Croy added a comment - Thanks for filing this. Daniel Beck , how long do you think I should wait for the Debian-based repositories to "soak test" before I start switching more repositories to sent HTTPs traffic to Azure?
            Hide
            danielbeck Daniel Beck added a comment -

            Depends on what data you're expecting from the experiment. Are you concerned about stability, bandwidth, etc? Are you concerned about traffic / cost?

            I mean, nothing really prevents you from switching everything now…?

            Show
            danielbeck Daniel Beck added a comment - Depends on what data you're expecting from the experiment. Are you concerned about stability, bandwidth, etc? Are you concerned about traffic / cost? I mean, nothing really prevents you from switching everything now…?
            Hide
            rtyler R. Tyler Croy added a comment -

            Depends on what data you're expecting from the experiment. Are you concerned about stability, bandwidth, etc? Are you concerned about traffic / cost?

            I'm less concerned with the cost and more concerned with the stability. I don't think there should be any, but I figure if anybody else were to notice complaints or issues it would be you

            If there's nothing fishy or concerning to you about turning on more repositories, then I'll start working through them when I have time.

            Show
            rtyler R. Tyler Croy added a comment - Depends on what data you're expecting from the experiment. Are you concerned about stability, bandwidth, etc? Are you concerned about traffic / cost? I'm less concerned with the cost and more concerned with the stability. I don't think there should be any, but I figure if anybody else were to notice complaints or issues it would be you If there's nothing fishy or concerning to you about turning on more repositories, then I'll start working through them when I have time.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: R. Tyler Croy
            Path:
            dist/profile/manifests/opensuse_repo.pp
            dist/profile/manifests/redhat_repo.pp
            dist/profile/templates/pkgrepo/redhat_htaccess.erb
            spec/classes/profile/pkgrepo_spec.rb
            spec/server/mirrorbrain/mirrorbrain_spec.rb
            http://jenkins-ci.org/commit/jenkins-infra/b925b70c7a95feeeb6c007cd10f617edb875d0df
            Log:
            Migrate opensuse and redhat repositories to redirect https://pkg.jenkins.io to Azure

            Generally, any Linux package request we get over HTTPs will now redirect over
            HTTPs to Azure blob storage.

            Fixes INFRA-967

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: R. Tyler Croy Path: dist/profile/manifests/opensuse_repo.pp dist/profile/manifests/redhat_repo.pp dist/profile/templates/pkgrepo/redhat_htaccess.erb spec/classes/profile/pkgrepo_spec.rb spec/server/mirrorbrain/mirrorbrain_spec.rb http://jenkins-ci.org/commit/jenkins-infra/b925b70c7a95feeeb6c007cd10f617edb875d0df Log: Migrate opensuse and redhat repositories to redirect https://pkg.jenkins.io to Azure Generally, any Linux package request we get over HTTPs will now redirect over HTTPs to Azure blob storage. Fixes INFRA-967

              People

              • Assignee:
                rtyler R. Tyler Croy
                Reporter:
                stodorov Steve Todorov
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: