Project

General

Profile

Bug #16327

During selection of puppet module - "Use Latest" is incorrectly pointing to lower version than available in the repo

Added by Brad Buckingham almost 6 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Content Views
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1327622

Description of problem:
During selection of puppet module - "Use Latest" is incorrectly pointing to lower version than available in the repo
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 new 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

Associated revisions

Revision 601291e3 (diff)
Added by Kavita Gaikwad over 5 years ago

Fixes #16327 - "Use Latest" is not pointing to latest version

During selection of puppet module - "Use Latest" is
incorrectly pointing to lower version than available
in the repo. Use Latest should point to actual
Latest version available.
With this commit, Use Latest will point to correct latest version.
All 'Use Latest' code logic placed in server-side and
removed from client-side.

History

#1 Updated by Brad Buckingham almost 6 years ago

  • Subject changed from During selection of puppet module - "Use Latest" is incorrectly pointing to lower version than available in the repo to During selection of puppet module - "Use Latest" is incorrectly pointing to lower version than available in the repo
  • Legacy Backlogs Release (now unused) set to 114

#2 Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Legacy Backlogs Release (now unused) deleted (114)
  • Pull request https://github.com/Katello/katello/pull/6451 added

#3 Updated by Justin Sherrill over 5 years ago

  • Legacy Backlogs Release (now unused) set to 197

#4 Updated by Eric Helms over 5 years ago

  • Legacy Backlogs Release (now unused) changed from 197 to 208

#5 Updated by John Mitsch over 5 years ago

  • Legacy Backlogs Release (now unused) changed from 208 to 214

#6 Updated by Kavita Gaikwad over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#7 Updated by Kavita Gaikwad over 5 years ago

  • Assignee set to Kavita Gaikwad
  • Target version set to 158

Also available in: Atom PDF