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:
Using the hammer command to create or update an activation key, users can input invalid release versions (any string is accepted). This causes issues when hosts try and register. It can be difficult to spot if an admin uses "7server" instead of "7Server" in a script. The "7server" will be used in the pathway for the repository url on the content host, and will give 404 errors.
Version-Release number of selected component (if applicable):
Satellite 6.8.0
How reproducible:
always
Steps to Reproduce:
1. Create an activation key with hammer command:
# hammer activation-key create --name=testing --release-version="thisshouldntwork" --organization-id=1 --lifecycle-environment-id=1 --content-view-id=1
2. Or update with hammer:
# hammer activation-key update --id=1 --release-version="butitdoes" --organization-id=1
Actual results:
Activation key is created with an invalid release version.
Expected results:
The API should verify if the release version is valid.
Additional info:
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 (Important: Satellite 6.13 Release), 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-2023:2097