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 1930641 - when I execute remediation from cloud.redhat.com on 1 host, it executes on Sat but on c.r.c it says "running" even after 10 minues
Summary: when I execute remediation from cloud.redhat.com on 1 host, it executes on Sa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Cloud Connector
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.9.0
Assignee: Adam Ruzicka
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks: 1884237
TreeView+ depends on / blocked
 
Reported: 2021-02-19 10:40 UTC by Jan Hutař
Modified: 2021-04-21 13:11 UTC (History)
3 users (show)

Fixed In Version: python3-receptor-satellite-1.3.2 tfm-rubygem-foreman_remote_execution-4.2.3-1,foreman-2.3.1.19-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:11:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31931 0 Normal Closed Allow searching by id on Hosts 2021-02-22 16:06:18 UTC
Foreman Issue Tracker 31932 0 Normal Closed Expose bulk outputs api as POST to handle large search queries 2021-02-22 16:06:18 UTC
Github project-receptor receptor-satellite pull 11 0 None open Fix use of Satellite's bulk output api 2021-02-19 14:21:46 UTC
Github project-receptor receptor-satellite pull 13 0 None closed Bulk output fixes 2021-02-22 16:06:18 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:11:33 UTC

Comment 2 Lukáš Hellebrandt 2021-02-22 15:27:52 UTC 
I've just reproduced on Sat 6.9 snap 13 with receptor-0.6.3-1.el7ar.noarch.
Comment 3 Lukáš Hellebrandt 2021-02-22 16:24:14 UTC 
==> /var/log/messages <==
Feb 22 11:18:25 <shortname> smart-proxy: <IP> - - [22/Feb/2021:11:18:25 EST] "GET /dynflow/tasks/79bc87b5-d071-4ae6-b6a2-cbb880801601/status HTTP/1.1" 200 12074
Feb 22 11:18:25 <shortname> smart-proxy: - -> /dynflow/tasks/79bc87b5-d071-4ae6-b6a2-cbb880801601/status
Feb 22 11:18:25 <shortname> receptor: ERROR 2021-02-22 11:18:25,427 ed608fd7-5bee-4700-a765-3df864502d81 work Error encountered while handling the response, replying with an error message ('id')
Feb 22 11:18:25 <shortname> receptor: ERROR 2021-02-22 11:18:25,428 ed608fd7-5bee-4700-a765-3df864502d81 work ['  File "/usr/lib/python3.6/site-packages/receptor/work.py", line 100, in handle\n    work_exec.result()\n', '  File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 425, in result\n    return self.__get_result()\n', '  File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 384, in __get_result\n    raise self._exception\n', '  File "/usr/lib64/python3.6/concurrent/futures/thread.py", line 56, in run\n    result = self.fn(*self.args, **self.kwargs)\n', '  File "/usr/lib/python3.6/site-packages/receptor_satellite/worker.py", line 61, in execute\n    run(Run.from_raw(queue, payload, satellite_api, logger).run())\n', '  File "/usr/lib/python3.6/site-packages/receptor_satellite/worker.py", line 52, in run\n    return loop.run_until_complete(coroutine)\n', '  File "/usr/lib64/python3.6/asyncio/base_events.py", line 484, in run_until_complete\n    return future.result()\n', '  File "/usr/lib/python3.6/site-packages/receptor_satellite/run.py", line 82, in run\n    if await self.polling_loop():\n', '  File "/usr/lib/python3.6/site-packages/receptor_satellite/run.py", line 105, in polling_loop\n    host = self.running[host_output["id"]]\n']
Comment 5 Patrick Creech 2021-03-10 16:36:17 UTC 
Adam,  I'm not seeing any artifacts for python-recepter-satellite 1.3.2 upstream.  Looks like the 1.3.2 tag isn't in the repo.  Can we get a release for it?
Comment 6 Adam Ruzicka 2021-03-10 17:02:41 UTC 
Forgot to push, it is out now
Comment 7 Lukáš Hellebrandt 2021-03-15 15:26:07 UTC 
FailedQA using Sat 6.9 snap 17.

When running a remediation, regardless of job invocation result, after ~ a minute CRC shows the status of Failed and the following is shown on the receptor machine:

```
# journalctl -fu receptor@*
[...]
Mar 15 11:11:58 <FQDN> receptor[307]: ERROR 2021-03-15 11:11:58,866 <uuid1> run Playbook run <uuid2> encountered error 'Field 'id' not recognized for searching!', aborting.
# grep 'scoped_search :on => :id' ~foreman/app/models/concerns/hostext/search.rb; echo $?
1
```
Comment 8 Adam Ruzicka 2021-03-15 15:27:50 UTC 
This seems to be missing a cherrypick of https://projects.theforeman.org/issues/31931
Comment 10 Lukáš Hellebrandt 2021-03-19 14:06:40 UTC 
Verified with Sat 6.9 snap 18.

Tried:
1) passed remediation
2) failed remediation due to broken connection between receptor and satellite
3) failed remediation due to issues on the remediated host
4) passed remediation after that remediation failed previously (i.e. issue got fixed in the meantime)

In all cases, status correctly transitions first to Pending (even in case 4) and the to either Passed or Failed.
Comment 13 errata-xmlrpc 2021-04-21 13:11:14 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 (Moderate: Satellite 6.9 Release), 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/RHSA-2021:1313
Note You need to log in before you can comment on or make changes to this bug.