Bug #7511
closed"Error: activation_key not found" when trying to update an activation key
Description
Looks like when trying to update an activation key, the --name parameter doesn't work but the --id does.
<hammer>
$ hammer activation-key info --name key1 --organization-id 1
Name: key1
ID: 1
Description:
Lifecycle Environment: Dev
Content View: View1
Host Collections:
$ hammer activation-key update --name key1 --lifecycle-environment Library --content-view-id 1 --organization-id 1
Could not update the activation key:
Error: activation_key not found
$ hammer activation-key update --id key1 --lifecycle-environment Library --content-view-id 1 --organization-id 1
Activation key updated
Updated by Eric Helms almost 11 years ago
- Translation missing: en.field_release set to 14
- Difficulty set to easy
- Triaged changed from No to Yes
Updated by Partha Aji over 10 years ago
Same issue with gpg keys/puppet-module/lifecycle-envioment/repository-set
I think the fix needs to happen in https://github.com/theforeman/hammer-cli-foreman/blob/master/lib/hammer_cli_foreman/id_resolver.rb#L140
Updated by Eric Helms over 10 years ago
- Translation missing: en.field_release changed from 14 to 23
Updated by Eric Helms over 10 years ago
- Translation missing: en.field_release changed from 23 to 31
Updated by Eric Helms over 10 years ago
- Translation missing: en.field_release deleted (
31)
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release set to 86
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release changed from 86 to 114
Updated by John Mitsch almost 6 years ago
- Status changed from New to Rejected
- Target version deleted (
Katello Backlog)
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.