Bug 1558524 - Remote Execution Fails for Applying errata in Content Hosts Via Remote Execution Method.
Summary: Remote Execution Fails for Applying errata in Content Hosts Via Remote Execut...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.3.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: Lukas Pramuk
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1585839 (view as bug list)
Depends On:
Blocks: 1553017
TreeView+ depends on / blocked
 
Reported: 2018-03-20 12:10 UTC by Jaskaran Singh Narula
Modified: 2021-09-09 13:28 UTC (History)
8 users (show)

Fixed In Version: tfm-rubygem-katello-3.4.5.72-1,tfm-rubygem-katello-3.4.5.74-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1575988 1728268 (view as bug list)
Environment:
Last Closed: 2018-06-20 17:29:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23082 0 High Closed Remote Execution Fails for Applying errata in Content Hosts Via Remote Execution Method. 2021-02-01 20:01:23 UTC

Description Jaskaran 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:

Comment 9 Walden Raines 2018-04-02 13:31:47 UTC
Created redmine issue http://projects.theforeman.org/issues/23082 from this bug

Comment 10 Satellite Program 2018-04-05 16:14:55 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23082 has been resolved.

Comment 19 Lukas Pramuk 2018-06-13 10:24:35 UTC
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 20 Stephen Benjamin 2018-06-14 14:57:36 UTC
*** Bug 1585839 has been marked as a duplicate of this bug. ***

Comment 21 Bryan Kearney 2018-06-20 17:29:18 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-2018:1950


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