Bug 537491 - Cloned kickstart profile loses package information
Summary: Cloned kickstart profile loses package information
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 530
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
Assignee: Justin Sherrill
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks: sat531-blockers
TreeView+ depends on / blocked
 
Reported: 2009-11-13 20:29 UTC by Scott Croft
Modified: 2018-10-27 15:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-08 10:02:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0021 0 normal SHIPPED_LIVE Red Hat Network Satellite bug fix update 2010-01-08 10:02:22 UTC

Description Scott Croft 2009-11-13 20:29:11 UTC
Description of problem: When cloning a kickstart profile, the packages in the original profile do not get cloned over to the new profile


Version-Release number of selected component (if applicable):

5.3.0


How reproducible:

Everytime a profile is cloned

Steps to Reproduce:
1. Select a kickstart profile
2. Choose the clone option
3. View the packages window under the software tab for the new profile
  
Actual results: The pakcages section is empty


Expected results: The packages section should have the packages from the original profile being cloned


Additional info:

Comment 1 Justin Sherrill 2009-11-16 23:14:56 UTC
This was caused by:

https://bugzilla.redhat.com/show_bug.cgi?id=527724

fixed in spacewalk master: 5a8c271358b4da0f355d333c86a0739420488067

Comment 2 Justin Sherrill 2009-11-17 18:14:10 UTC
this fix also requires 0d51f52919e5c66d8c87ae4d315e2e4c7ae54432 from spacewalk master

Comment 7 Petr Sklenar 2009-12-17 10:27:00 UTC
reproduced with sat530

Verified with sat531, spacewalk-java-0.5.44-60.el4sat

Comment 9 errata-xmlrpc 2010-01-08 10:02:25 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0021.html


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