Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1702177 +++
Description of problem:
Procedure sync-plans-enable not working.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. # bin/foreman-maintain advanced procedure run sync-plans-disable
Running ForemanMaintain::Scenario ================================================================================
disable active sync plans:
\ Total 4 sync plans are now disabled. [OK]
--------------------------------------------------------------------------------
2. # bin/foreman-maintain advanced procedure run sync-plans-enable
Running ForemanMaintain::Scenario ================================================================================
re-enable sync plans:
/ Total 0 sync plans are now enabled. [OK]
--------------------------------------------------------------------------------
Actual results:
Showing 0 sync plans are enabled in result
Expected results:
It should enable sync-plans which are not enabled yet.
Additional info:
--- Additional comment from on 2019-04-23T07:13:04Z
Since this bug report was entered in Red Hat Bugzilla, the 'sat-backlog' flag has been set to ? to ensure that it is properly evaluated for release.
--- Additional comment from on 2019-04-23T07:13:04Z
Since this issue was entered in Red Hat Bugzilla, the pm_ack has been set to + automatically for the next planned release.
--- Additional comment from on 2019-04-23T17:10:11Z
Can you provide the release version that was being tested? (e.g. was it 6.5 and regression from 6.4?)
--- Additional comment from on 2019-04-26T12:35:28Z
@Brad,
This bug introduced in the Foreman Maintain due to new sync-plans changes in Katello.
Now, behaviour of "enabled" field of sync-plan is changed and is based on foreman_tasks_recurring_logic.state value.
I have updated version of BZ to sat 6.5 as tested on it.
--- Additional comment from on 2019-04-30T17:51:27Z
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being [proposed|marked] as a blocker for this release.
Please resolve ASAP.
--- Additional comment from on 2019-05-03T10:04:50Z
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26502 has been resolved.
--- Additional comment from on 2019-05-14T01:53:23Z
There is no release notes text enter, which is why I set the flag to negative. This will not appear in the release notes.
Just to add, this issue do not affect 6.4.3 -> 6.5 upgrade. But this will affect the future upgrades e.g. upgrade from 6.5.0 -> 6.5.1. Thus, we need to have it as part of 6.5.1.
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/RHBA-2019:1582