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 1724494 - [Capsule][smart_proxy_dynflow_core] "PID file /var/run/foreman-proxy/smart_proxy_dynflow_core.pid not readable (yet?) after start"
Summary: [Capsule][smart_proxy_dynflow_core] "PID file /var/run/foreman-proxy/smart_pr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-27 08:15 UTC by Steffen Froemer
Modified: 2023-12-15 16:35 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-smart_proxy_dynflow_core-0.2.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:58:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27184 0 Normal Closed [smart_proxy_dynflow_core] "PID file /var/run/foreman-proxy/smart_proxy_dynflow_core.pid not readable (yet?) after start... 2021-02-11 00:42:38 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:58:53 UTC

Description Steffen Froemer 2019-06-27 08:15:44 UTC 
Description of problem:
After reboot of Capsule, the service 'smart_proxy_dynflow_core' shows message

"PID file /var/run/foreman-proxy/smart_proxy_dynflow_core.pid not readable (yet?) after start"

Version-Release number of selected component (if applicable):
tfm-rubygem-smart_proxy_dynflow_core-0.2.1-5.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Reboot cpasule server
2. systemctl status smart_proxy_dynflow_core
3.

Actual results:
   Jun 26 17:29:25 capsule01 systemd[1]: Starting Foreman smart proxy dynflow core service...
   Jun 26 17:29:29 capsule01 systemd[1]: PID file /var/run/foreman-proxy/smart_proxy_dynflow_core.pid not readable (yet?) after start.
   Jun 26 17:29:29 capsule01 systemd[1]: Started Foreman smart proxy dynflow core service.

Expected results:
The service should start without any warning/error

   Jun 26 17:29:25 capsule01 systemd[1]: Starting Foreman smart proxy dynflow core service...
   Jun 26 17:29:29 capsule01 systemd[1]: Started Foreman smart proxy dynflow core service.

Additional info:
if the service is restarted, everything runs fine

# foreman-maintain service restart --only smart_proxy_dynflow_core
Comment 6 Adam Ruzicka 2019-06-28 15:01:04 UTC 
Created redmine issue http://projects.theforeman.org/issues/27184 from this bug
Comment 7 Bryan Kearney 2020-06-19 12:03:14 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/27184 has been resolved.
Comment 9 Peter Ondrejka 2020-07-22 12:54:58 UTC 
Verified on Satellite 6.8 snap 9, smart_proxy_dynflow_core is alive and well after capsule restart, the service type has been changed

# systemctl show smart_proxy_dynflow_core
Type=notify
...
Comment 12 errata-xmlrpc 2020-10-27 12:58:39 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 (Important: Satellite 6.8 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-2020:4366
Note You need to log in before you can comment on or make changes to this bug.