Description of problem: During selection of puppet module - "Use Latest" is incorrectly pointing to lower version than available in the repo Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Enable and sync Puppet Forge Repo 2. Create new CV 3. Add new Puppet module (for example abiquo) -> Select version * you see Use Latest (currently 0.1.6) 0.1.6 0.1.3 0.1.2 4. Choose 0.1.6 (Not Use Latest (currently 0.1.6)) 5. Select another version of same puppet module * you see Use Latest (currently 0.1.3) 0.1.3 0.1.2 Actual results: Use Latest is pointing to version 0.1.3 (Latest from current displayed list) Expected results: Use Latest should point to 0.1.6 - actual Latest version available. Additional info: Probably 0.1.6 version should appear on a list as well. Then Use Latest will point to correct version
Moving 6.2 bugs out to sat-backlog.
Created redmine issue http://projects.theforeman.org/issues/16327 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16327 has been resolved.
Verified on Satellite 6.3 SNAP 10 : satellite-6.3.0-16.0.beta.el7sat.noarch, tfm-rubygem-katello-3.4.4-1.el7sat.noarch - create a puppet repo - upload modules (e.g. theforeman) for multiple versions (e.g. 2.0.1, 1.3.0..) - create a cv - on the CV, Puppet Modules - Add New Module - 2.0.1 - 'Select new version', verify 'Always Use Latest (2.0.1)' and 1.3.0 listed - 'Select Version' 1.3.0 - 'Select new version', verify 'Always Use Latest (2.0.1)' and 2.0.1 listed - 'Select Version' 2.0.1 - 'Select new version', verify 'Always Use Latest (2.0.1)' and 1.3.0 listed - 'Select Version' 'Always Use Latest' - 'Select new version', verify 'Always Use Latest (2.0.1)', 2.0.1 and 1.3.0 listed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. > > For information on the advisory, and where to find the updated files, follow the link below. > > If the solution does not work for you, open a new bug report. > > https://access.redhat.com/errata/RHSA-2018:0336