RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1781148 - foreman plugin stopped collecting dynflow* data
Summary: foreman plugin stopped collecting dynflow* data
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos
Version: 7.8
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Jan Jansky
QA Contact: Miroslav Hradílek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-09 12:28 UTC by Pavel Moravec
Modified: 2020-03-31 20:04 UTC (History)
11 users (show)

Fixed In Version: sos-3.8-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 20:04:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github sosreport sos pull 1882 0 'None' closed [foreman] cast dynflow_execution_plans.uuid as varchar 2020-05-19 20:54:40 UTC
Red Hat Knowledge Base (Solution) 4733791 0 None None None 2020-01-14 14:11:44 UTC
Red Hat Product Errata RHEA-2020:1127 0 None None None 2020-03-31 20:04:43 UTC

Description Pavel Moravec 2019-12-09 12:28:46 UTC 
Description of problem:
foreman plugin stops collecting dynflow* data that are crucial for investigating tasks in Satellite6. This happens since Sat6.6, fix is equivalent to

https://github.com/theforeman/foreman-tasks/commit/ce676e30cc1c9909d69727ea02bedfa52d4c3335#diff-5871f1081545c0a96125e33d75d53d5c

and works on old Sat versions properly.


Version-Release number of selected component (if applicable):
sos-3.8-5 and any older
Satellite 6.6


How reproducible:
100%


Steps to Reproduce:
1. On a Sat6.6:

sosreport -o foreman --batch --build
cat <generated-dir>/sos_commands/foreman/dynflow*


Actual results:
# cat /var/tmp/sosreport-pmoravec-sat66-on-rhev-2019-12-09-hgklfcf/sos_commands/foreman/dynflow_actions
ERROR:  operator does not exist: character varying = uuid
LINE 1: ...nflow_actions on (foreman_tasks_tasks.external_id = dynflow_...
                                                             ^
HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.


Expected results:
CSV content as it was there before


Additional info:
Comment 2 Pavel Moravec 2019-12-09 12:32:43 UTC 
Requesting blocker+ since:

- On Satellite6.6, we will lack crucial information about task details, what significatly limits investigation of various types of Satellite6 issues (/me SME for Sat6, believe me)
- the change is trivial in 1 plugin only, compatible backwards on older Sat6 versions
Comment 7 Pavel Moravec 2019-12-12 12:24:14 UTC 
(fixed in upstream already, backport is trivial and successfully tested)
Comment 9 Pavel Moravec 2019-12-12 15:12:21 UTC 
Hi JJ,
could you please verify this BZ, that on Sat6.6:

- previous sos version fails to collect sos_commands/foreman/dynflow* postgres cvs exports
- this version collects them properly

(and ideally that this package collects data on Sat6.5 or older as well)


A yum repository for the build of sos-3.8-6.el7 (task 25335062) is available at:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.8/6.el7/

You can install the rpms locally by putting this .repo file in your /etc/yum.repos.d/ directory:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.8/6.el7/sos-3.8-6.el7.repo

RPMs and build logs can be found in the following locations:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.8/6.el7/noarch/

The full list of available rpms is:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.8/6.el7/noarch/sos-3.8-6.el7.src.rpm
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.8/6.el7/noarch/sos-3.8-6.el7.noarch.rpm

Build output will be available for the next 21 days.
Comment 11 Jan Jansky 2019-12-12 15:40:19 UTC 
Tested on 6.5 and on 6.6. In both cases successfully collected dynflow_actions  dynflow_execution_plans  dynflow_schema_info  dynflow_steps.
Comment 14 errata-xmlrpc 2020-03-31 20:04:15 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/RHEA-2020:1127
Note You need to log in before you can comment on or make changes to this bug.