Bug 1480347 - Sync Plans not fully executing
Summary: Sync Plans not fully executing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.2.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-10 19:45 UTC by Satellite Program
Modified: 2021-04-06 17:51 UTC (History)
18 users (show)

Fixed In Version: pulp-2.13.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1466919
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
[Verification] Screenshot Attached (104.83 KB, application/zip)
2017-10-27 12:17 UTC, Jitendra Yejare 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 2903 0 High CLOSED - CURRENTRELEASE Process Recycling feature causes HTTP event notifier to be unreliable 2017-08-15 14:31:40 UTC

Comment 2 pulp-infra@redhat.com 2017-08-11 14:38:15 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2017-08-11 14:38:20 UTC 
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2017-08-15 14:31:41 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 6 Jitendra Yejare 2017-10-27 12:17:43 UTC 
Created attachment 1344301 [details]
[Verification] Screenshot Attached
Comment 7 Jitendra Yejare 2017-10-27 12:18:45 UTC 
Verified !

@Satellite 6.3 snap 21

Steps:
1. Created a sync plan from Content -> Sync plan with start time
2. Added RHEL6 RHEL prod and rhel7 custom prod to sync plan

Behavior:
1. The sync started on time
2. Foreman tasks are created to start sync on time
3. The Sync Status displayed the sync started.

Screenshots Attached!
Comment 8 Satellite Program 2018-02-21 16:54:37 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.