Open uthark opened 4 years ago
Upgrade from 6.17.1 also fails:
Enabling service datadog-agent
Created symlink from /etc/systemd/system/multi-user.target.wants/datadog-agent.service to /lib/systemd/system/datadog-agent.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/datadog-agent-process.service to /lib/systemd/system/datadog-agent-process.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/datadog-agent-trace.service to /lib/systemd/system/datadog-agent-trace.service.
Loading SELinux policy module for system-probe.
dpkg: error processing package datadog-agent (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
datadog-agent
E: Sub-process /usr/bin/dpkg returned an error code (1)
Post install fails.
when I try to do it locally:
semodule -v -i /etc/datadog-agent/selinux/system_probe_policy.pp
Attempting to install module '/etc/datadog-agent/selinux/system_probe_policy.pp':
Ok: return value of 0.
Committing changes:
libsepol.print_missing_requirements: system_probe_policy's global requirements were not met: type/attribute base_ro_file_type (No such file or directory).
libsemanage.semanage_link_sandbox: Link packages failed (No such file or directory).
semodule: Failed!
cc @smo921
Hey @uthark,
Thanks for reporting this issue! I can reproduce it and it seems that the SELinux policy we introduced in 6.18.0/7.18.0 is trying to use a type that isn't provided by Ubuntu 16.04 by default. We will start working on a bugfix right now.
In the meantime you can pin the Agent to the previous minor version 7.17.1
.
@KSerrania yes, this is what we decided to do.
Hi @uthark,
Versions 6.18.1 and 7.18.1 of the Agent are out since last week, and should resolve your issue. I have been able to install 7.18.1 without any issue on an Ubuntu 16.04 host with SELinux enabled.
Could you please confirm that the new version fixes the issue in your environment?
Output of the info page (if this is a bug)
Describe what happened:
Describe what you expected:
Steps to reproduce the issue:
Additional environment details (Operating System, Cloud provider, etc): Ubuntu 16.04 on AWS.