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.
Bug 1995707 - Ansible based satellite jobs are now allowing to monitor the runtime activity from the Job Invocation page in Satellite 6.10
Summary: Ansible based satellite jobs are now allowing to monitor the runtime activity...
Keywords:
Status: CLOSED DUPLICATE of bug 1987205
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.10.0
Hardware: All
OS: All
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-19 16:01 UTC by Sayan Das
Modified: 2021-08-20 07:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-20 07:24:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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