-
Notifications
You must be signed in to change notification settings - Fork 11
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
DNM: debug extensions build #12
Conversation
1f9c52f
to
3394adc
Compare
cc @travier @cgwalters |
Filed coreos/rpm-ostree#4029 for the monitor thing but that's just cosmetic, it's not the real issue. The real issue is:
|
@cgwalters hm, is this not the monitor looking for |
What's the mounted filesystem here? Can you add a Looking at the code it doesn't seem like inotify failing should be fatal, but maybe. I think it's more likely that the |
Running a new build now, will post logs here
That would be very helpful indeed! |
It's an OverlayFS
Full logs: |
Somewhat related to this...I personally consider the extensions container stuff as a short term crutch specifically for RHEL/OCP. The most load-bearing extension by far is |
That makes a lot of sense to me! Maybe in SCOS, instead of jumping through these hoops now, we could simply never ship the extensions image then. As of today we're not able to build it here anyway, and would thus have to disable it for the MVP release next week. |
The pipeline will continue to attempt extension builds, but won't fail if unsuccessful. I've opened openshift/machine-config-operator#3356 to remove the ext image ref from MCO for the time being. I'm closing this PR. This work can be picked up elsewhere. |
So we just now hit this in https://issues.redhat.com/browse/COS-2000 ...should have debugged it fully at the time 😦 Current status quo is that OKD/SCOS is still not shipping the extensions container? |
Yes, unfortunately :( |
|
The extensions build that is run in the SCOS base container fails with:
This seems to come from:
https://github.com/GNOME/glib/blob/main/gio/gfile.c#L5680
via
https://github.com/rpm-software-management/libdnf/blob/dnf-4-master/libdnf/dnf-repo-loader.cpp#L553
The
c9s.repo
is indeed present and contains thebaseos
repo. Logs from PipelineRun on operate-first (https://console-openshift-console.apps.smaug.na.operate-first.cloud/k8s/ns/okd-team/tekton.dev~v1beta1~PipelineRun/okd-coreos-all-y6y30e/logs):