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:
I find it strange that the top feature of 6.2 is not enabled by default:
'Satellite 6.2 Beta - New Features and Functionality
Increase Efficiency with Automated Workflows
Satellite 6.2 introduces remote execution, automating workflows an...'
But then looking at an fresh system, with just the satellite RPMs installed i see that remote-exection is default by default:
[crash] root@li-lc-1578:~# satellite-installer --scenario=satellite --help | grep remote
--[no-]enable-foreman-plugin-remote-execution Enable 'foreman_plugin_remote_execution' puppet module (default: false)
--[no-]enable-foreman-proxy-plugin-remote-execution-ssh Enable 'foreman_proxy_plugin_remote_execution_ssh' puppet module (default: false)
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Fresh installation
2. satellite-installer --scenario=satellite --help | grep remote
3.
Actual results:
Remote execution plugins are disabled
Expected results:
Remote execution plugins is enabled
Additional info:
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-2016:1501
Description of problem: I find it strange that the top feature of 6.2 is not enabled by default: 'Satellite 6.2 Beta - New Features and Functionality Increase Efficiency with Automated Workflows Satellite 6.2 introduces remote execution, automating workflows an...' But then looking at an fresh system, with just the satellite RPMs installed i see that remote-exection is default by default: [crash] root@li-lc-1578:~# satellite-installer --scenario=satellite --help | grep remote --[no-]enable-foreman-plugin-remote-execution Enable 'foreman_plugin_remote_execution' puppet module (default: false) --[no-]enable-foreman-proxy-plugin-remote-execution-ssh Enable 'foreman_proxy_plugin_remote_execution_ssh' puppet module (default: false) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Fresh installation 2. satellite-installer --scenario=satellite --help | grep remote 3. Actual results: Remote execution plugins are disabled Expected results: Remote execution plugins is enabled Additional info: