Bug 219485 - Cannot unset package profile sync in kickstart profile
Summary: Cannot unset package profile sync in kickstart profile
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Partha Aji
QA Contact: Steve Salevan
URL:
Whiteboard:
Depends On:
Blocks: 248643
TreeView+ depends on / blocked
 
Reported: 2006-12-13 15:08 UTC by Matthew Davis
Modified: 2008-04-02 21:07 UTC (History)
0 users

Fixed In Version: sat510
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-02 21:07:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matthew Davis 2006-12-13 15:08:10 UTC 
Description of problem:

In the details of a kickstart, there is no way to not sync to a package profile
after one is selected.

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

How reproducible:
Evertime

Steps to Reproduce:
1. Systems -> Kickstart -> profiles -> <someprofile> -> Software -> Package Profiles
2. Select a package profile
3. Update kickstart profile
4. Try to unselect a profile
  
Actual results:
Only 1 package profile must be selected

Expected results:
1 or none package profiles can be selected

Additional info:
Maybe adding a 'none' bullet?1
Comment 1 Mike McCune 2007-01-03 19:49:23 UTC 
re-assigning to partha
Comment 2 Red Hat Bugzilla 2007-04-12 02:05:45 UTC 
User bnackash's account has been closed
Comment 3 Partha Aji 2007-10-12 18:57:29 UTC 
Looks like this has been already resolved in the current push with the addition of a "Unassociate Profile" 
button.. Moving it to ON_QA
Comment 4 Steve Salevan 2007-10-16 16:26:25 UTC 
This "Unassociate Profile" button seems to work as it should, so I'm moving this
over to VERIFIED.
Comment 6 Corey Welton 2008-03-25 18:57:50 UTC 
release_pending
Comment 7 Brandon Perkins 2008-04-02 21:07:23 UTC 
UI Enhancements for 5.1 Sat GA so Closed for Current Release.
Note You need to log in before you can comment on or make changes to this bug.