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:

  Content View and Lifecycle Environment are not required to create an Activation Key.  Once set, however, they cannot be removed from an activation key.

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

  Red Hat Satellite 6.3.1


How reproducible:


Steps to Reproduce:
1.   Create activation key without Lifecycle Environment or Content View
2.   After creation, set LE and CV
3.   WebUI provides no mechanism to remove CV. And LE stays checked.

Actual results:

  No mechanism to completely remove Lifecycle Environment or Content View from Activation Key

Expected results:

  If Lifecycle Environment and Content View are mandatory, then they should be required at creation time.  If they are not mandatory, then a mechanism to remove the Lifecycle Environment and Content View should be provided.


Additional info:

Verified:
@satellite 6.4.0 snap 22

steps:
1. Create activation key without Lifecycle Environment or Content View
2. After creation, set LE and CV
3. once activation key is successfully updated, remove Lifecycle Environment or Content View

observation:
Lifecycle Environment or Content View removed successfully

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927