Bug 802450 - sync_plan seems not working
Summary: sync_plan seems not working
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-12 15:04 UTC by Garik Khachikyan
Modified: 2015-01-04 21:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-14 11:58:01 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Garik Khachikyan 2012-03-12 15:04:38 UTC
Description of problem:
making sync plan to be launched right two minutes after its creation seems does not do the things.

Version-Release number of selected component (if applicable):
latest CFSE Beta4 (as well as Katello recent/latest)

How reproducible:
always

Steps to Reproduce:
1.create separate org
2.make prov. prod. repo (http://repos.fedorapeople.org/repos/pulp/pulp/v1/stable/6Server/x86_64/)
3.through cli do: sync_plan create --name sync_pulp --date 2012-03-12 --time 15:49:00
(just replace with your recent time on that system to be executed in next 2-3 min.)
4. wait for next 4 min.
5. nothing.

Actual results:
no pulp repo getting synchronized

Expected results:
all recent repos should be synchronizing.


Additional info:

Comment 2 Garik Khachikyan 2012-03-14 11:58:01 UTC
well, actually there is a call that one should know: `product set_plan`

doing that I confirm: sync was done in time.. no complains here :)

but: there is no way so far (seems) to list what products are associated with this plan or what sync plans have assigned the particular product.

Closing this issue now with opening another RFE for implementing `product list_plan` call.

Comment 3 Mike McCune 2013-08-16 18:06:38 UTC
getting rid of 6.0.0 version since that doesn't exist


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