Bug #9520
closed
Changing Release Version on Activation Key Doesn't Change $releasever when Building
Added by Greg Koch about 10 years ago.
Updated over 5 years ago.
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.
- Category set to 83
- Target version set to 67
- Translation missing: en.field_release set to 23
- Triaged changed from No to Yes
- Translation missing: en.field_release changed from 23 to 31
- Target version changed from 67 to 68
- Target version deleted (
68)
- Translation missing: en.field_release changed from 31 to 70
- Translation missing: en.field_release changed from 70 to 86
- Translation missing: en.field_release changed from 86 to 114
- 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.
Also available in: Atom
PDF
Updated by 
Updated by