Bug 1702177 - [regression] Procedure sync-plans-enable is not working
Summary: [regression] Procedure sync-plans-enable is not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.6.0
Assignee: Kavita
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-23 07:13 UTC by Kavita
Modified: 2023-03-24 14:45 UTC (History)
11 users (show)

Fixed In Version: rubygem-foreman_maintain-0.3.4
Doc Type: Known Issue
Doc Text:
Clone Of:
: 1716576 (view as bug list)
Environment:
Last Closed: 2019-10-22 16:36:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26502 0 High Closed [regression] procedure sync-plans-enable is not working 2020-11-23 10:22:14 UTC
Red Hat Knowledge Base (Solution) 4650491 0 None None None 2019-12-11 04:03:02 UTC
Red Hat Product Errata RHBA-2019:3181 0 None None None 2019-10-22 16:37:00 UTC

Description Kavita 2019-04-23 07:13:02 UTC
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:

Comment 3 Brad Buckingham 2019-04-23 17:10:11 UTC
Can you provide the release version that was being tested?  (e.g. was it 6.5 and regression from 6.4?)

Comment 6 Bryan Kearney 2019-05-03 10:04:50 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26502 has been resolved.

Comment 10 Jameer Pathan 2019-07-05 07:21:58 UTC
Verified

Verified with:
- Satellite 6.6.0 snap 9
- rubygem-foreman_maintain-0.4.3-2.el7sat.noarch

Test Steps:
- Create few sync plans
- disable and enable sync-plans using foreman-maintain

[root@qe-sat62-rhel7 ~]# foreman-maintain advanced procedure run sync-plans-disable
Running ForemanMaintain::Scenario
================================================================================
disable active sync plans: 
\ Total 5 sync plans are now disabled.                                [OK]      
--------------------------------------------------------------------------------

[root@qe-sat62-rhel7 ~]# foreman-maintain advanced procedure run sync-plans-enable
Running ForemanMaintain::Scenario
================================================================================
re-enable sync plans: 
/ Total 5 sync plans are now enabled.                                 [OK]      
--------------------------------------------------------------------------------

Observation:
- procedure sync-plans-disable disabled active sync plans. 
- procedure sync-plans-enable re-enabled sync plans.

Comment 12 errata-xmlrpc 2019-10-22 16:36:54 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/RHBA-2019:3181


Note You need to log in before you can comment on or make changes to this bug.