Hide Forgot
Description of problem: The setting PassEnvironment= in systemd.exec was introduced in 2015 to allow passing environment variables to daemons, which makes especially sense when the system is inside a container. Upstream discussion: https://lists.freedesktop.org/archives/systemd-devel/2015-June/033130.html Please backport the PassEnvironment= support in systemd.exec into RHEL 7.x. Version-Release number of selected component (if applicable): systemd-219-30.el7_3.6.x86_64 Actual results: No PassEnvironment= support in systemd.exec. Expected results: PassEnvironment= support in systemd.exec ;-)
Cross-filed case #01798185 on the Red Hat customer portal.
Looks backportable. https://github.com/systemd/systemd/commit/b4c14404b3e8753c41bac0b1d49369230a15c544 https://github.com/systemd/systemd/commit/4c80d201ace0377312c27143afab04e9c9f1ee64 https://github.com/systemd/systemd/commit/e1abca2ee42e5938ee1f2542c3eba9e70edb0be2
A possible test scenario: 1) # systemctl set-environment TEST_ENV=ttt1 TEST=t2t # cat /etc/systemd/system/test.service [Unit] Description=Test [Service] Environment=FOO=fffff BAR=bbbbb PassEnvironment=TEST_ENV TEST I_DONT_EXIST TEST ExecStart=/usr/bin/bash -c 'echo "$TEST_ENV::$TEST::$FOO::$BAR" ; /usr/bin/sleep 60' # systemctl start test # # Grep for expected/unexpected output in systemctl status 2) # # Again, set some environment as in 1). # systemd-run -p "PassEnvironment=TEST" /usr/bin/bash -c 'echo $TEST ; sleep 30' # # Grep for expected/unexpected output in systemctl status Ideally, it would be great to test for various combination of Environment and PassEnvironment, trying to set the values several times, passing nonexistent environment, etc.
https://github.com/lnykryn/systemd-rhel/pull/98
fix merged to upstream staging branch -> https://github.com/lnykryn/systemd-rhel/commit/ddad59f50e67a5e36cd9c40e774d28240a6a7c0c https://github.com/lnykryn/systemd-rhel/commit/f35b737bdd6e508cf73f43a1beb3f5cb8c1ebb07 https://github.com/lnykryn/systemd-rhel/commit/88d2ec272d3e503412e477d9abaebfe2ca199e78 -> post
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/RHBA-2017:2297