Bug 1655595
| Summary: | Sync plans does not start 'repositories sync' first time as per defined "Start Date" and same happened for all 'hourly/daily/weekly' Intervals | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | vijsingh |
| Component: | Sync Plans | Assignee: | Samir Jha <sajha> |
| Status: | CLOSED ERRATA | QA Contact: | Stephen Wadeley <swadeley> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5.0 | CC: | aruzicka, oshtaier, swadeley, vijsingh |
| Target Milestone: | 6.5.0 | Keywords: | AutomationBlocker, Regression, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tfm-rubygem-foreman-tasks-0.14.4.2-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-14 12:39:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Created redmine issue http://projects.theforeman.org/issues/25655 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25655 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25655 has been resolved. *** Bug 1685724 has been marked as a duplicate of this bug. *** 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-2019:1222 |
Description of problem: Sync plans does not start 'repositories sync' first time as per defined "Start Date" and same happened for all 'hourly/daily/weekly' intervals Version-Release number of selected component (if applicable): Satellite 6.5.0 snap 6 How reproducible: Always Steps to Reproduce: 1. Go to Satellite GUI: Content => Sync Plans => Create Sync Plan => set internal 'hourly/daily/weekly' => Submit Click on same sync plan => Products => select and add product 2. Keep check the product repository sync as per first sync("Start Date") Actual results: No sync task will create as per defined "Start Date" . Expected results: Added product repositories should start syncing as per "Start Date". Additional info: