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

RPM package provider blind to the package revision

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 3.8.7
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Environment:

      Amazon Linux rolling distro, latest upgdates
      tested with both Puppet 3.7.4 (repo RPMs) and 3.8.7 (Gem installed)

    • Template:
    • QA Risk Assessment:
      Needs Assessment

      Description

      Error: Could not update: Failed to update to version 2.0.14.1, got version 2.0.14.1-1.29.amzn1 instead
      Error: /Stage[main]/Ruby/Package[rubygems]/ensure: change from 2.0.14.1-1.29.amzn1 to 2.0.14.1 failed: Could not update: Failed to update to version 2.0.14.1, got version 2.0.14.1-1.29.amzn1 instead
      

      It would seem that this is not a bug in the puppetlabs/ruby module but instead an issue with the yum provider itself, the package name is right (rubygems20) and the version is right, but the extra dash and revision name don't fit, produce an error, and stop all the dependencies from installing.

      Also, not sure if it's only an Amazon Linux issue or a general one with packages that have revision strings. This is the only configuration I have bumped into this.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            seefood Ira Abramov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support