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

Ensuring latest does not use upgrade command in DNF

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.8.0
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Agent
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Fixed an issue where ensuring latest did not use the upgrade command in DNF.

      Description

      tl;dr using ensure latest with a previous install will use the install command in dnf, which does not upgrade the package:

      Debug: /Stage[main]/Main/Package[cockpit]/ensure: cockpit "0.55-1.fc22" is installed, latest is "0:0.67-2.fc22"
        Debug: Package[cockpit](provider=dnf_update): Ensuring => latest
        Debug: Executing: '/usr/bin/dnf -d 0 -e 1 -y install cockpit'
        Notice: /Stage[main]/Main/Package[cockpit]/ensure: ensure changed '0.55-1.fc22' to '0:0.67-2.fc22'
        Debug: /Stage[main]/Main/Package[cockpit]: The container Class[Main] will propagate my refresh event
      

      The original issue of failing to update when a new version is specified was fixed in https://tickets.puppetlabs.com/browse/PUP-6324, but the code doesn't cover the case of a package that is installed, then later attempted to update with ensure => latest.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  peter.souter Peter Souter
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: