Bug 2097084 - 'hammer erratum list' Gives 'Error: environment not found' If '--lifecycle-environment' Is Used.
Summary: 'hammer erratum list' Gives 'Error: environment not found' If '--lifecycle-en...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.10.6
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-14 21:35 UTC by Bernie Hoefer
Modified: 2023-07-21 21:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bernie Hoefer 2022-06-14 21:35:30 UTC
Description of problem:
Executing:

  # 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:

  # 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":

  # 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

Comment 1 Brad Buckingham 2023-07-21 21:06:39 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.


Note You need to log in before you can comment on or make changes to this bug.