DescriptionJaskaran Singh Narula
2018-03-20 12:10:32 UTC
Description of problem:
This problem is where when you try to apply any errata to any no. of hosts ( may it be single also) then there are no jobs that are invoking which seems not to be expected. Whereas when you try to apply any package through the remote execution process it works as by creating a job for that task.
Version-Release number of selected component (if applicable):
How reproducible:
>> Satellite Web UI >> Content hosts >> Select any no. of hosts >> Select action (Drop down List) >> Manage Errata >> select Errata >> Drop Down List >> Via Remote Execution >> Pop-up (Yes)
Now how I reproduced it as I removed the ssh keys from the hosts and then tried to install the errata from the satellite web ui through remote execution method and the tasks got executed and the errata was installed on the hosts.
This will take you to Monitor >> Tasks Page. Which is not expected. Whereas this should take as to Monitor >> Jobs Page.
Actual results:
After clicking on Via Remote execution it is not creating a job in Monitor >> Jobs for this task that needs to be performed. Rather this is creating a Tasks in Monitor >> Tasks and create tasks for this action.
Expected results:
After clicking on Via Remote execution it is should create a job in Monitor >> Jobs for this task that needs to be performed and then route us to the same page. And then route us to the same page.
Additional info:
VERIFIED.
@satellite-6.3.2-1.el7sat.noarch
tfm-rubygem-katello-3.4.5.74-1.el7sat.noarch
by reproducer described in comment#6:
1) Navigate to Hosts > Content Hosts
2) Select a host for errata operations
3) Select Action > Manage Errata
4) Open browser debug console
5) In the modal window select an errata
6) Open install dropdown and select 'via remote execution'
> POST https://<SATFQDN>/katello/remote_execution HTTP/1.1
< HTTP/1.1 302 Found
Redirected to https://<SATFQDN>/job_invocations/4
100% Success
Comment 20Stephen Benjamin
2018-06-14 14:57:36 UTC
*** Bug 1585839 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/RHBA-2018:1950
Description of problem: This problem is where when you try to apply any errata to any no. of hosts ( may it be single also) then there are no jobs that are invoking which seems not to be expected. Whereas when you try to apply any package through the remote execution process it works as by creating a job for that task. Version-Release number of selected component (if applicable): How reproducible: >> Satellite Web UI >> Content hosts >> Select any no. of hosts >> Select action (Drop down List) >> Manage Errata >> select Errata >> Drop Down List >> Via Remote Execution >> Pop-up (Yes) Now how I reproduced it as I removed the ssh keys from the hosts and then tried to install the errata from the satellite web ui through remote execution method and the tasks got executed and the errata was installed on the hosts. This will take you to Monitor >> Tasks Page. Which is not expected. Whereas this should take as to Monitor >> Jobs Page. Actual results: After clicking on Via Remote execution it is not creating a job in Monitor >> Jobs for this task that needs to be performed. Rather this is creating a Tasks in Monitor >> Tasks and create tasks for this action. Expected results: After clicking on Via Remote execution it is should create a job in Monitor >> Jobs for this task that needs to be performed and then route us to the same page. And then route us to the same page. Additional info: