-
Notifications
You must be signed in to change notification settings - Fork 192
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
disable rpmdb monitoring in build/composes #4029
Comments
copied from okd-project/okd-coreos-pipeline#12 (comment): @cgwalters hm, is this not the monitor looking for *.repo files in the compose dir? How else would rpm-ostree know about the yum repos? As the logs show, the c9s.repo is present and defines the baseos repo. If the failed monitor is not the reason, why is it not picked up and what can we do to fix this? |
Looks fatal from an strace trace:
|
Ahh OK pretty sure the problem is this If inotify fails then the libdnf code doesn't set an error and silently doesn't load the .repo files etc. (This code violates the gerror rules by returning In latest libdnf, this code also changed: rpm-software-management/libdnf#915 |
Hmm wait I may be wrong about that...not totally sure |
|
|
This addresses the root cause of coreos#4029 Basically we were calling `set_repos_dir("")` on the libdnf side and it simply did not handle that, failing to open the directory. (Though I'm not saying "Closes" since we should still fix the file monitoring stuff) I don't yet know why this seemed to work in some cases but not others though.
This addresses the root cause of coreos#4029 Basically we were calling `set_repos_dir("")` on the libdnf side and it simply did not handle that, failing to open the directory. (Though I'm not saying "Closes" since we should still fix the file monitoring stuff) I don't yet know why this seemed to work in some cases but not others though.
Seen in okd-project/okd-coreos-pipeline#12
It looks like inotify is being denied in this environment for some reason. But in any case, we shouldn't be trying to monitor the rpmdb for changes when we're doing a build.
The text was updated successfully, but these errors were encountered: