Created attachment 1308139 [details] Bug demonstration video Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Have more than one page of hosts 2. Go to hosts index 3. Enter search query to match more than one page of hosts 4. Click the select all checkbox 5. Click "Select all X hosts" 6. Select action > schedule remote job Actual results: Only the hosts from the viewed page are selected as targets for REX. Expected results: All selected hosts are selected as targets for REX Additional info: See attachment
Rather than add a "select all in table" for this special case, it is my preference that we correct this, as a table pattern, for all tables in Satellite.
Created redmine issue http://projects.theforeman.org/issues/20778 from this bug
*** Bug 1508812 has been marked as a duplicate of this bug. ***
*** Bug 1531056 has been marked as a duplicate of this bug. ***
*** Bug 1540084 has been marked as a duplicate of this bug. ***
Setting as high priority as there was the `select all` option added now in the core UI
*** Bug 1543102 has been marked as a duplicate of this bug. ***
Upstream bug assigned to ddolguik
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20778 has been resolved.
*** Bug 1589120 has been marked as a duplicate of this bug. ***
FailedQA Version tested: Satellite 6.4 snap 9 # rpm -q satellite satellite-6.4.0-9.beta.el7sat.noarch # rpm -qa | grep foreman_remote_execution tfm-rubygem-foreman_remote_execution_core-1.1.2-1.el7sat.noarch tfm-rubygem-foreman_remote_execution-1.5.3-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.6-2.el7sat.noarch I see same behaviour as before(see attachment)
Created attachment 1455454 [details] select all for rex
VERIFIED Version tested: Satellite 6.4 sanp 11 Select all x hosts selects all selected hosts for remote execution. But while verifying found https://bugzilla.redhat.com/show_bug.cgi?id=1600456 also.
*** Bug 1606144 has been marked as a duplicate of this bug. ***
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/RHSA-2018:2927