Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2155

yum repos without baseurl are broken

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: PUP 3.5.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Linux ardmore.sc.svcolo.com 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

    • Template:

      Description

      Yum repos without a baseurl and with a mirrorlist are broken in 3.5. Here is the syntax for such a yum repo:

      yumrepo { 'epel':
        descr       => 'Extra Packages for Enterprise Linux $releasever - $basearch',
        baseurl     => absent,
        mirrorlist  => 'https://mirrors.fedoraproject.org/metalink?repo=epel-$releasever&arch=$basearch',
        enabled     => 1,
        gpgcheck   => 1,
        gpgkey      => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6',
      }
      

      The error response is:

      Thu Apr 03 18:22:17 -0700 2014 Puppet (err): Failed to apply catalog: Parameter baseurl failed on Yumrepo[epel]: Must be a valid URL
      Wrapped exception:
      Must be a valid URL
      

      Works perfectly in all previous versions. Furthermore, documentation says absent is a valid value:

      http://docs.puppetlabs.com/references/latest/type.html#yumrepo

      baseurl
      (Property: This attribute represents concrete state on the target system.)

      The URL for this repository. Set this to absent to remove it from the file completely.

      Valid values are absent. Values can match /.*/.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jorhett Jo Rhett
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support