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

PMT upgrade command returns an error when trying to upgrade a module with only one release

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: PUP 3.6.2
    • Fix Version/s: PUP 3.7.0
    • Component/s: PMT
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      2014-07-23, 2014-08-06

      Description

      When you use the "puppet module upgrade" command to upgrade a module that has only one published release, it reports that there are no releases available for that module instead of telling you that you already have the latest version.

      $ bin/puppet module install ghoneycutt/sysklogd
      Notice: Preparing to install into /Users/jesse/sandbox/puppet/modules ...
      Notice: Downloading from https://forgeapi.puppetlabs.com ...
      Notice: Installing -- do not interrupt ...
      /Users/jesse/sandbox/puppet/modules
      └── ghoneycutt-sysklogd (v1.0.0)
       
      $ bin/puppet module upgrade ghoneycutt/sysklogd
      Notice: Preparing to upgrade 'ghoneycutt-sysklogd' ...
      Notice: Found 'ghoneycutt-sysklogd' (v1.0.0) in /Users/jesse/sandbox/puppet/modules ...
      Notice: Downloading from https://forgeapi.puppetlabs.com ...
      Error: Could not upgrade 'ghoneycutt-sysklogd' (v1.0.0 -> latest)
        No releases are available from https://forgeapi.puppetlabs.com
          Does 'ghoneycutt-sysklogd' have at least one published release?
      

      (See also: https://groups.google.com/forum/#!msg/puppet-users/9_iiPGyP9ls/-t7LRUdg1T4J)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jesse Jesse Scott
              QA Contact:
              John Duarte
            • Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support