Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Set EC2 cirrus-agent SELinux context to unconfined
Long ago, many test failures and other problems were experienced in Cirrus-CI managed google-cloud VMs. None of the problems were reproducible manually. It was discovered that because the cirrus agent starts from a metadata-downloaded script, it was executing with a more restrictive SELinux type. This is not the case when running tests manually, where root sshs in. It's been observed recently, a similar situation may be occurring in EC2. However, in this case, the agent is started by cloud-init, and was observed operating with the type `cloud_init_t`. In case this is the source of trouble now or in the future, fix the setup to match GCP. Signed-off-by: Chris Evich <[email protected]>
- Loading branch information