Project

General

Profile

Bug #9520

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

Added by Greg Koch over 5 years ago. Updated 9 months ago.

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

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.

History

#1 Updated by Eric Helms over 5 years ago

  • Category set to 83
  • Target version set to 67
  • Legacy Backlogs Release (now unused) set to 23
  • Triaged changed from No to Yes

#2 Updated by Eric Helms about 5 years ago

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

#3 Updated by Eric Helms about 5 years ago

  • Target version changed from 67 to 68

#4 Updated by Eric Helms about 5 years ago

  • Target version deleted (68)

#5 Updated by Eric Helms almost 5 years ago

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

#6 Updated by Eric Helms over 4 years ago

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

#7 Updated by Eric Helms over 4 years ago

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

#8 Updated by John Mitsch 9 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from New to Rejected

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.

Also available in: Atom PDF