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.
Description of problem:
Version-Release number of selected component (if applicable):
Satellite 6.10.0 Snap 3.0
rubygem-foreman_maintain-0.8.1-1.el7sat.noarch
How reproducible:
Always
Steps to Reproduce:
1. # foreman-maintain service list --only smart_proxy_dynflow_core
Running Service List
================================================================================
List applicable services:
smart_proxy_dynflow_core.service disabled
All services listed [OK]
--------------------------------------------------------------------------------
2. # foreman-maintain health check --label services-up
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check whether all services are running: [FAIL]
Following services are not running: smart_proxy_dynflow_core
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]?, [y(yes), n(no)] y
Actual results:
Expected results:
Additional info:
https://community.theforeman.org/t/phasing-out-smart-proxy-dynflow-core/22841
Verified.
Tested on Satellite 6.10.0 Snap 5
Version: rubygem-foreman_maintain-0.8.2-1.el7sat.noarch
Steps:
1. satellite-maintain health check --label service-up
2. satellite-maintain upgrade check --target-version 6.10.z --whitelist="check-non-redhat-repository"
Observation:
smart_proxy_dynflow_core is disabled service on 6.10, so it's being skipped for foreman 2.4 onwards i.e after satellite 6.9
Also, tested the same version on Satellite 6.9.3 where this service is enabled and this service is not being excluded there.
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 (Satellite 6.10 Satellite Maintenance Release), 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-2021:4697