Project

General

Profile

Actions

Bug #36773

closed

'hammer erratum list' Gives 'Error: environment not found' If '--lifecycle-environment' Is Used.

Added by Lucy Fu 8 months ago. Updated 8 months ago.

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

Description

Description of problem:
Executing:

  1. hammer erratum list \
    --organization-id=1 \
    --content-view=rhel77_e4s \
    --lifecycle-environment=Development \
    --errata-restrict-installable=yes

...results in this output:

Error: environment not found.

(I get the same error if I specify "Library".) Yet, this slightly different command:

  1. hammer erratum list \
    --organization-id=1 \
    --content-view=rhel77_e4s \
    --lifecycle-environment-id=2 \
    --errata-restrict-installable=yes

...succeeds. FYI, lifecycle environment ID #2 is "Development":

  1. hammer lifecycle-environment list \
    --organization-id=1
    ---|-------------|--------
    ID | NAME | PRIOR
    ---|-------------|--------
    2 | Development | Library
    1 | Library |
    ---|-------------|--------

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-2.5.1-1.el7sat.noarch

Actions

Also available in: Atom PDF