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.

PCS daemon supports reading several various environmental variables that are usually set via initscript or systemd through /etc/sysconfig/pcsd, but are not documented anywhere at this point.

So far we expose following ones in /etc/sysconfig/pcsd and should mention them in man pages:

PCSD_DEBUG
RACK_ENV
DISABLE_GUI

Ideally, we should provide a general description of the supported ENV variables without being tied to /etc/sysconfig, because a user might want to set these in other ways (and also other distributions might use different approach than what we do in RHEL).

We might consider other ENV variables that pcsd already understands, but most of them are for internal use only.

To articulate that aloud, also the environment variables the underlying
components are known to honor should be mentioned.

See, for instance, https_proxy and no_proxy, just as these get documented
in WGET(1) ... related [bug 1315627].

pcsd environment variables are covered by bz1378742
pcs environment variables are covered by bz1352047

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