Project

General

Profile

Actions
Copy link

Bug #25145

closed

Hammer command with content view version --order is not working as expected.

Added by Stephen Benjamin over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Stephen Benjamin
Category:
Hammer
Target version:
Katello 3.9.0
Difficulty:
Triaged:
Yes
Bugzilla link:
1624416
Pull request:
https://github.com/Katello/katello/pull/7741
Fixed in Releases:
Katello 3.9.0
Found in Releases:
Red Hat JIRA:

Description

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

Description of problem:

After upgrading Satellite 6.2 to 6.3 hammer content view version --order parameter not functioning as expected.

Version-Release number of selected component (if applicable):

tfm-rubygem-hammer_cli-0.11.0.1-1.el7sat.noarch

How reproducible:

Steps to Reproduce:

1. Publish multiple version of a content view.

2. Run # hammer --output csv content-view version list --content-view client --organization redhat --order 'version DESC'

Actual results:

  1. hammer --output csv content-view version list --content-view client --organization redhat --order 'version DESC'
    ID,Name,Version,Lifecycle Environments

Expected results:

  1. hammer --output csv content-view version list --content-view client --organization redhat --order 'version DESC'
    ID,Name,Version,Lifecycle Environments
    4,client 2.0,2.0,Library
    3,client 1.0,1.0,"Dev, Prod"

Additional info:

This parameter is working well in Satellite 6.2.

Actions
Copy link

Also available in: Atom PDF