Bug 920813 - Kickstart tree not automatically updated when new kickstart tree available
Summary: Kickstart tree not automatically updated when new kickstart tree available
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stephen Herr
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2013-03-12 20:09 UTC by Stephen Herr
Modified: 2017-09-28 18:10 UTC (History)
0 users

Fixed In Version: [spacewalk-java-1.9.84-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-15 18:43:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Stephen Herr 2013-03-12 20:09:54 UTC
Description of problem:
Spacewalk 1.9 has new functionality that allows a kickstart profile to stay attached to the newest tree available. Currently however the kickstart profile will attach itself to the kickstart tree with the last alphabetical label, not the most recent last_modified date. 

How reproducible:
always


Steps to Reproduce:
1. create a kickstart profile that is set to stay updated to the latest kickstart tree (distribution)
2. create or modify a kickstart tree
  
Actual results:
The kickstart profile attaches itself to the kickstart tree with the last alphabetically-ranked label

Expected results:
The kickstart profile attaches itself to the newest kickstart tree.

Comment 1 Stephen Herr 2013-03-15 18:43:38 UTC
Committed to Spacewalk master: e453fa5540ebd9d59679234e9a93cb3c65da21ff

Spacewalk 1.9 has been updated.

Comment 2 Eric Herget 2017-09-28 18:10:57 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.


Note You need to log in before you can comment on or make changes to this bug.