Project

General

Profile

Actions

Bug #9736

closed

The content-view-version param in the CLI is interfering with commands

Added by Partha Aji about 9 years ago. Updated over 5 years ago.

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

Description

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

Some commands in the CLI are passing content-view-version-id to the API when they shouldn't.

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

All

How reproducible:

Always

Steps to Reproduce:
1. Create a content view with some errata and promote it out of Library into another env (ie Dev)
2. Run the command to list errata for this environment:

hammer erratum list --organization "Default Organization" --environment "Dev"

Actual results:

You either get no results (if you have one cvv in Dev) or 'Error: content_view_version found more than once'

Expected results:

I should see all the errata in Dev.

Additional info:

It appears that the CLI is trying to always look up content-view-version when it see environment. Another command to test is:

hammer erratum list --organization "Default Organization" --environment "Dev" --content-view MyErrataCV

This should show me all the errata in Dev and MyErrataCV.

Actions #1

Updated by Eric Helms about 9 years ago

  • Target version set to 68
  • translation missing: en.field_release set to 31
  • Triaged changed from No to Yes
Actions #2

Updated by Christine Fouant almost 9 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF