Project

General

Profile

Bug #7511

"Error: activation_key not found" when trying to update an activation key

Added by David Davis over 4 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Hammer
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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

History

#1 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) set to 14
  • Difficulty set to easy
  • Triaged changed from No to Yes

#2 Updated by Partha Aji over 4 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

#3 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 14 to 23

#4 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 23 to 31

#5 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) deleted (31)

#6 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) set to 86

#7 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 114

Also available in: Atom PDF