Project

General

Custom queries

Profile

Actions

Bug #6828

closed

UI shows wrong latest version of puppet module

Added by Walden Raines almost 11 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web UI
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1104636
Description of problem:

when adding puppet module to content view, UI shows wrong latest version number

see screenshot, there is Use Latest (currently 0.0.2), but should be 0.1.0

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140529.0

How reproducible:
always

Steps to Reproduce:
1. create puppet repository and upload several versions of one puppet module (latest version first, )
2. create content view and add uploaded module

Added by Walden Raines almost 11 years ago

Revision ca5bb041 (diff)

Fixes #6828/BZ1104636: show correct version of puppet module. …

The latest version of puppet modules was being incorrectly
calculated, based on an incorrect assumption that the last
item in the array was the latest version. This commit
explicitly sorts the puppet modules by the version such that
the latest version is correct.

http://projects.theforeman.org/issues/6828
https://bugzilla.redhat.com/show_bug.cgi?id=1104636

Added by Walden Raines over 10 years ago

Revision 14befa08

Merge pull request #4501 from waldenraines/6828

Fixes #6828/BZ1104636: show correct version of puppet module.

Actions

Also available in: Atom PDF