-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
selinux problem in omi on RHEL8 #680
Comments
I think this needs a change in https://github.com/microsoft/omi/blame/2cd827ba933a74374ca177007d4954aa8df493f3/Unix/installbuilder/datafiles/Linux.data#L366-L373 Highlighting the author: @JumpingYang001 |
maybe you also want to change this in the script that builds the spec file from the data file to generalize the solution or move it into https://github.com/microsoft/omi/blame/2cd827ba933a74374ca177007d4954aa8df493f3/Unix/installbuilder/datafiles/Linux.data#L289 |
@Klaas- thanks for reporting it! we will check the issue. |
The change you made somehow hasn't made it into the official rpm
Greetings |
side question: will this need more than one version upgrade to actually happen? on the next upgrade the current versions postuninstall script will be called right? |
@Klaas- yes, the upgrade uninstall script will be executed in next version. |
|
@Klaas- it is already in official packages, and it is by design, since upgrade a package will use exist package's uninstall script and for current package's uninstall script will be executed in next upgrade. |
@JumpingYang001
|
@Klaas- understand your question now, in fact, the 1.6.8-0 release tag wasn't updated by me... it was updated by other team member, yes, the tag is wrong... , and I check the real code for 1.6.8-0 should only includes these commits: https://github.com/microsoft/omi/commits/e6851ec20b00615d5fda8d3858cd5f142ed04528 . |
So it will take another two releases of omi until this problem is addressed on it's own :) I am guessing it was a bad idea to wait for the fix, I am seeing a couple of multi-gb log files already, so I will clean this up in configuration management ... :) |
@Klaas- yeah, if you have urgent to fix it, you can manually do it at first, thanks for pointing out the issue. |
@JumpingYang001 even loading the module is not enough :) /etc/cron.daily/logrotate: error: error accessing /var/opt/microsoft/omsconfig: Permission denied Logrotate now has enough rights to access the file, but not enough to write the rotated log because it does not have rights on the directory :) |
@Klaas- |
Ah yes, sorry I see the policy is from https://github.com/microsoft/OMS-Agent-for-Linux/blob/master/installer/selinux/omsagent-logrotate.fc , I'll raise this issue there |
It seems like there is an issue about this in that repo already, microsoft/OMS-Agent-for-Linux#781 (comment) |
Hi,
it seems the omi-logrotate selinux module is uninstalled after upgrading. I think this is a general build problem, scx has the same issue.
How to reproduce:
have a system without omi/scx
The text was updated successfully, but these errors were encountered: