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

yumrepo resource completely broken with 3.5 release

    XMLWordPrintable

    Details

    • Template:
    • Story Points:
      1
    • Sprint:
      Week 2014-4-09 to 2014-4-16

      Description

      1. Any attribute that can take 'absent' as a value, either complains about it being invalid or puts the actual text value 'absent' in to the produced repo file.

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

      for example:
      exclude => absent

      ends up looking like
      exclude=absent

      in the .repo file.

      2. yumrepo resource title should become the repo id, and the attribute name should become the name value in the .repo file. If you manage to produce a repo file by not specifying any attribute with absent you will be greeted by this error when running yum..

      Repository 'local-base' is missing name in configuration, using id
      Repository 'local-centosplus' is missing name in configuration, using id
      Repository 'local-extras' is missing name in configuration, using id
      Repository 'local-updates' is missing name in configuration, using id
      

      3. When using ensure => absent on an existing repository id of say 'base' for centos/rhel it removes the entire CentOS-Base.repo file which contains more than just the base repo. It should edit the repo in place.

      4. The name attribute becomes the repo filename, where as the title (repository id) attribute should really be used as the file name. Because usually repository name's are long winded and contain lots of spaces..

      As it stands I'll have to rollback our puppet clients and servers to the previous release until this is fixed/sane.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              aaron.whiteside@outspoken.com Aaron Whiteside
              QA Contact:
              Kurt Wall
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support