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.
Bug 2175007 - [regression] data.yml is referring to old sync plain id which does not exist in katello_sync_plans
Summary: [regression] data.yml is referring to old sync plain id which does not exist ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.12.3
Assignee: Eric Helms
QA Contact: Griffin Sullivan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-02 20:09 UTC by Odilon Sousa
Modified: 2024-12-20 21:42 UTC (History)
13 users (show)

Fixed In Version: rubygem-foreman_maintain-1.1.12-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1997186
Environment:
Last Closed: 2023-04-04 15:20:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36024 0 Normal Closed sync-plans not in sync with foreman-maintan data.yml 2023-03-02 20:09:32 UTC
Github theforeman foreman_maintain pull 681 0 None Merged Fixes #36024 - ignore already deleted sync plans 2023-03-02 20:09:32 UTC
Red Hat Issue Tracker SAT-15078 0 None None None 2023-03-02 20:09:32 UTC
Red Hat Issue Tracker SAT-16283 0 None None None 2023-03-02 20:10:57 UTC
Red Hat Knowledge Base (Solution) 6967460 0 None None None 2023-03-02 20:09:32 UTC
Red Hat Product Errata RHSA-2023:1630 0 None None None 2023-04-04 15:20:11 UTC

Comment 2 Griffin Sullivan 2023-03-14 19:25:59 UTC 
Verified on 6.12.3 snap 1

Deleting sync plans when disabled does not disrupt foreman-maintain's ability to enable the right sync plans.

Steps to Reproduce:

1. Create 2 sync plans

2. # foreman-maintain advanced procedure run sync-plans-disable

3. # hammer sync-plan delete --id 1

4. # foreman-maintain advanced procedure run sync-plans-enable

Results:

Running ForemanMaintain::Scenario
================================================================================
re-enable sync plans: 
| Total 1 sync plans are now enabled.                                 [OK]      
--------------------------------------------------------------------------------


You can also see the proper list of enabled and disabled sync plans in /var/lib/foreman-maintain/data.yml
Comment 3 Griffin Sullivan 2023-03-24 13:16:52 UTC 
Verified in 6.12.3 snap 2

Test automation covering the following steps ran and passed successfully

1. Create 2 sync plans

2. # foreman-maintain advanced procedure run sync-plans-disable

3. # hammer sync-plan delete --id 1

4. # foreman-maintain advanced procedure run sync-plans-enable

Results:

Running ForemanMaintain::Scenario
================================================================================
re-enable sync plans: 
| Total 1 sync plans are now enabled.                                 [OK]      
--------------------------------------------------------------------------------
Comment 8 errata-xmlrpc 2023-04-04 15:20:04 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 (Important: Satellite 6.12.3 Async Security Update), 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-2023:1630
Note You need to log in before you can comment on or make changes to this bug.