Issue #8186
closed
systemctl show-environment fails without sudo on Centos
Description
roles/pulp_common/tasks/main.yml executes command systemctl show-environment, which fails on a freshly installed CentOS 7.7 or 7.9 box.
fatal: [localhost]: FAILED! => {"changed": false, "cmd": "set -o pipefail\nsystemctl show-environment | grep -E '^PATH=' | sed 's/PATH=//g'\n", "delta": "0:00:00.009917", "end": "2021-02-01 11:35:20.328111", "msg": "non-zero return code", "rc": 1, "start": "2021-02-01 11:35:20.318194", "stderr": "Failed to get environment: Operation not permitted", "stderr_lines": ["Failed to get environment: Operation not permitted"], "stdout": "", "stdout_lines": []}
Adding become: true to this step fixes the issue,
Updated by mdepaulo@redhat.com almost 4 years ago
- Assignee set to ppicka
- Triaged changed from No to Yes
- Groomed changed from No to Yes
We will verify that it is fixed by using Vagrant, because we believe that molecule is using the docker connection as root.
Updated by pulpbot over 3 years ago
- Status changed from NEW to POST
Added by ppicka over 3 years ago
Added by ppicka over 3 years ago
Revision 33ca4449 | View on GitHub
Privilege escalation
for some CentOS envs we need escalate privileges for systemctl show-environment
Updated by ppicka over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp|33ca444967a887730a7eae456b91c132dfe5b765.
Updated by ttereshc over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Sprint/Milestone set to 3.12.2
.
Privilege escalation
for some CentOS envs we need escalate privileges for
systemctl show-environmentcloses: #8186 https://pulp.plan.io/issues/8186