Project

General

Profile

Actions
Copy link

Bug #9520

closed

Changing Release Version on Activation Key Doesn't Change $releasever when Building

Added by Greg Koch about 9 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

If an activation key is updated and the release version is changed/removed it does not save correctly and the host will build with the previous value set.

Actions
Copy link
 #1

Updated by Eric Helms about 9 years ago

  • Category set to 83
  • Target version set to 67
  • translation missing: en.field_release set to 23
  • Triaged changed from No to Yes
Actions
Copy link
 #2

Updated by Eric Helms about 9 years ago

  • translation missing: en.field_release changed from 23 to 31
Actions
Copy link
 #3

Updated by Eric Helms about 9 years ago

  • Target version changed from 67 to 68
Actions
Copy link
 #4

Updated by Eric Helms about 9 years ago

  • Target version deleted (68)
Actions
Copy link
 #5

Updated by Eric Helms almost 9 years ago

  • translation missing: en.field_release changed from 31 to 70
Actions
Copy link
 #6

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release changed from 70 to 86
Actions
Copy link
 #7

Updated by Eric Helms about 8 years ago

  • translation missing: en.field_release changed from 86 to 114
Actions
Copy link
 #8

Updated by John Mitsch over 4 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.

Actions
Copy link

Also available in: Atom PDF