Bug 2097084

Summary:	'hammer erratum list' Gives 'Error: environment not found' If '--lifecycle-environment' Is Used.
Product:	Red Hat Satellite	Reporter:	Bernie Hoefer <bhoefer>
Component:	Errata Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.10.6	CC:	addubey, apatel, kgaikwad, ofedoren, rabajaj
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.