Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I can reproduce and see that hammer is not working per defined descriptions.
# hammer capsule content --help
available-lifecycle-environments List the lifecycle environments not attached to the capsule
lifecycle-environments List the lifecycle environments attached to the capsule
# hammer capsule content --help
lifecycle-environments List the lifecycle environments attached to the capsule
available-lifecycle-environments List the lifecycle environments not attached to the capsule
Version-Release number of selected component (if applicable):
Satellite 6.2.10
How reproducible:
Login to satellite server and execute hammer cli.
# hammer capsule content lifecycle-environments --id 2
---|---------|-------------
ID | NAME | ORGANIZATION
---|---------|-------------
1 | Library | GSS
---|---------|-------------
# hammer capsule content available-lifecycle-environments --id 2
---|---------|-------------
ID | NAME | ORGANIZATION
---|---------|-------------
1 | Library | GSS <--Attached Library to capsule shouldn't list here
3 | prod | GSS
2 | dev | GSS
# hammer capsule content add-lifecycle-environment --id 2 --environment-id 3
Lifecycle environment successfully added to the capsule
# hammer capsule content lifecycle-environments --id 2
---|---------|-------------
ID | NAME | ORGANIZATION
---|---------|-------------
3 | prod | GSS
1 | Library | GSS
---|---------|-------------
# hammer capsule content available-lifecycle-environments --id 2
---|---------|-------------
ID | NAME | ORGANIZATION
---|---------|-------------
1 | Library | GSS
3 | prod | GSS <--Attached Lib/prod to capsule shouldn't list here
2 | dev | GSS
---|---------|-------------
Expected results:
Once environment-id attached to capsule, it should not list in "available-lifecycle-environments"
Additional info:
# hammer capsule content --help
Usage:
hammer capsule content [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND subcommand
[ARG] ... subcommand arguments
Subcommands:
add-lifecycle-environment Add lifecycle environments to the capsule
available-lifecycle-environments List the lifecycle environments not attached to the capsule
cancel-synchronization Cancel running capsule synchronization.
info Get current capsule synchronization status
lifecycle-environments List the lifecycle environments attached to the capsule
remove-lifecycle-environment Remove lifecycle environments from the capsule
synchronization-status Get current capsule synchronization status
synchronize Synchronize the content to the capsule
Hi,
Is it possible to get any patch or temporary fix for this issue. Customer needs this asap since they have large number of lifecycle environments(LC) ID's and capsules, and to find out all unattached LC envs for each capsule is a very tedious manual tasks.
Thanks.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Description of problem: I can reproduce and see that hammer is not working per defined descriptions. # hammer capsule content --help available-lifecycle-environments List the lifecycle environments not attached to the capsule lifecycle-environments List the lifecycle environments attached to the capsule # hammer capsule content --help lifecycle-environments List the lifecycle environments attached to the capsule available-lifecycle-environments List the lifecycle environments not attached to the capsule Version-Release number of selected component (if applicable): Satellite 6.2.10 How reproducible: Login to satellite server and execute hammer cli. # hammer capsule content lifecycle-environments --id 2 ---|---------|------------- ID | NAME | ORGANIZATION ---|---------|------------- 1 | Library | GSS ---|---------|------------- # hammer capsule content available-lifecycle-environments --id 2 ---|---------|------------- ID | NAME | ORGANIZATION ---|---------|------------- 1 | Library | GSS <--Attached Library to capsule shouldn't list here 3 | prod | GSS 2 | dev | GSS # hammer capsule content add-lifecycle-environment --id 2 --environment-id 3 Lifecycle environment successfully added to the capsule # hammer capsule content lifecycle-environments --id 2 ---|---------|------------- ID | NAME | ORGANIZATION ---|---------|------------- 3 | prod | GSS 1 | Library | GSS ---|---------|------------- # hammer capsule content available-lifecycle-environments --id 2 ---|---------|------------- ID | NAME | ORGANIZATION ---|---------|------------- 1 | Library | GSS 3 | prod | GSS <--Attached Lib/prod to capsule shouldn't list here 2 | dev | GSS ---|---------|------------- Expected results: Once environment-id attached to capsule, it should not list in "available-lifecycle-environments" Additional info: # hammer capsule content --help Usage: hammer capsule content [OPTIONS] SUBCOMMAND [ARG] ... Parameters: SUBCOMMAND subcommand [ARG] ... subcommand arguments Subcommands: add-lifecycle-environment Add lifecycle environments to the capsule available-lifecycle-environments List the lifecycle environments not attached to the capsule cancel-synchronization Cancel running capsule synchronization. info Get current capsule synchronization status lifecycle-environments List the lifecycle environments attached to the capsule remove-lifecycle-environment Remove lifecycle environments from the capsule synchronization-status Get current capsule synchronization status synchronize Synchronize the content to the capsule