Bug #35236
closedHammer Allows Invalid Release Version to be Set on Activation Key
Description
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:
Updated by The Foreman Bot over 2 years ago
- Status changed from New to Ready For Testing
- Assignee set to Lucy Fu
- Pull request https://github.com/Katello/katello/pull/10200 added
Updated by The Foreman Bot over 2 years ago
- Fixed in Releases Katello 4.6.0 added
Updated by Lucy Fu over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|8b478a0a3a2b35e44556241bdbe954a15b73e6ee.
Updated by Jeremy Lenz over 2 years ago
- Subject changed from Hammer Allows Invalid Release Version to be Set on Activation Key to Hammer Allows Invalid Release Version to be Set on Activation Key
- Target version set to Katello 4.6.0
- Triaged changed from No to Yes
Updated by The Foreman Bot almost 2 years ago
- Pull request https://github.com/Katello/katello/pull/10414 added
Updated by Ian Ballou almost 2 years ago
- Has duplicate Bug #36031: Can't set Release Version in Activation Key added