Bug 1072433 - [RFE] new call scheduleSyncPackagesWithProfile
Summary: [RFE] new call scheduleSyncPackagesWithProfile
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API
Version: 560
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat560-triage
TreeView+ depends on / blocked
 
Reported: 2014-03-04 15:03 UTC by Lukas Pramuk
Modified: 2014-10-06 14:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-06 14:09:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Pramuk 2014-03-04 15:03:14 UTC
Description of problem:
We have two api call for package comparison, one call compares two systems, the other call compares a system with a profile: 
- comparePackages ( systemid + systemid )
- comparePackageProfile ( systemid + profile )

For a subsequent sync we have only one option, one call to sync packages between two systems, the other logical option a call to sync a system to a profile is missing.
- scheduleSyncPackagesWithSystem ( systemid + systemid )
- scheduleSyncPackagesWithProfile ( systemid + profile ) <- MISSING


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


Steps to Reproduce:
1. call system.comparePackageProfile
2. call system.scheduleSyncPackagesWithProfile

Actual results:
there is no such api call

Expected results:
new api call for syncing a sytem to a profile, currently there is only compare call implemented.

Comment 1 Tomas Lestach 2014-03-05 12:46:39 UTC
Right, the API is missing, however you have an option to schedule the package installation/upgrade/removal manually according to the system.comparePackageProfile API results.

Comment 2 Lukas Pramuk 2014-03-05 13:52:39 UTC
Sure, unless it is an extra package and I want to schedule its removal.
Currently there's no call for this, therefore filed yet another RFE bz #1072416


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