Bug 1480347
| Summary: | Sync Plans not fully executing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Satellite Program <pm-sat> | ||||
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.2.10 | CC: | bbuckingham, bkearney, bmbouter, cduryee, daviddavis, dgross, dkliban, ehelms, ggainey, hmore, ipanova, jcallaha, jyejare, mhrivnak, pcreech, pthomas, rchan, ttereshc | ||||
| Target Milestone: | Unspecified | Keywords: | FieldEngineering, PrioBumpField, Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | pulp-2.13.4 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1466919 | Environment: | |||||
| Last Closed: | 2018-02-21 16:54:37 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Comment 2
pulp-infra@redhat.com
2017-08-11 14:38:15 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. Created attachment 1344301 [details]
[Verification] Screenshot Attached
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! 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
|