Bug 1995707

Summary: Ansible based satellite jobs are now allowing to monitor the runtime activity from the Job Invocation page in Satellite 6.10
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.10.0CC: aruzicka, lstejska
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-20 07:24:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sayan Das 2021-08-19 16:01:33 UTC
Description of problem:

After executing a long running playbook or ansible based job from satellite, we can only see the entire execution after the job gets completed or failed. 

We will not be able to monitor what's going on or where the job is stuck if we try to check from the Job invocation page.

The same problem is there with Convert2rhel. After starting the Convert2Rhel job from satellite, no progress is being shown for the same job.

Hence there is no way to understand which step is happening without going to the system itself and checking the /var/log/convert2rhel/convert2rhel.log file.


Version-Release number of selected component (if applicable):

Satellite 6.10


How reproducible:

Always


Steps to Reproduce:

1. Use "Ansible Commands" category to run a run a command "sleep 100" on host.example.com system

2. On the Job Invocation page, scoll down at the bottom and click open host.example.com


Actual results:

It will redirect me to the page where I should be able to see the runtime execution of the job but it's a black rectandular box only with no output in it.

After waiting for 100 seconds i.e. when the job gets completed, we get to see the entire play.


Expected results:


We should be able to see the progress here to understand where it is stuck


   1:

   2:
PLAY [all] *********************************************************************
   3:

   4:
TASK [Gathering Facts] *********************************************************
   5:
ok: [host.example.com]
   6:

   7:
TASK [shell] *******************************************************************





Additional info:


This is not reproducible in Satellite 6.7.5 [ where I had tested additionally ]

Comment 2 Adam Ruzicka 2021-08-20 07:24:05 UTC
This looks like a duplicate of BZ1987205. If there's some detail that I missed which makes the two differ, feel free to reopen.

*** This bug has been marked as a duplicate of bug 1987205 ***