-
Notifications
You must be signed in to change notification settings - Fork 154
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
[rhcos-4.7] Backport patches for lsblk workaround and prjquota #905
Conversation
Since we've created a new filesystem anyway. This implicitly also works around the service racing against the `by-label/root` symlink not being up to date after reprovisioning (which `ignition-ostree-transposefs-restore.service` now intercepts and fixes). (cherry picked from commit 195ae1f)
Sometimes `lsblk` returns devices in the wrong order, so we can't rely on it to iterate over the devices in hierarchical order. Instead, use the `holders/` directory ourselves directly and use `--nodeps` when calling `lsblk`. See: https://bugzilla.redhat.com/show_bug.cgi?id=1934174#c4 See: https://bugzilla.redhat.com/show_bug.cgi?id=1940607 See: coreos/coreos-installer#453 (cherry picked from commit 5228316)
By default, we mount XFS with the `prjquota` option. Verify this. (cherry picked from commit b9dca27)
We should have those in a shared shell library. (cherry picked from commit 1b11322)
By default, we use `prjquota` for the rootfs for container orchestrators to monitor and set drive space limits. However, with the added support for rootfs reprovisioning, we made this conditional on the rootfs not being reprovisioned, with the assumption that you can just set whatever options you'd like instead. Though actually doing that is really awkward right now, and it requires surfacing prjquota in user documentations (see https://bugzilla.redhat.com/show_bug.cgi?id=1940704#c2). Since AFAICT `prjquota` doesn't actually have any significant overhead, let's just simplify the messaging to: we *always* enable prjquota on XFS root filesystems. Users who want to override this can fallback to `rpm-ostree kargs` (and eventually once we have coreos#805, to `mountOptions: []`). Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1940704 (cherry picked from commit a57a999)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will wait for CI to successfully finish before merging
CI here likely will fail unfortunately because it's building with latest cosa instead of the 4.7 branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe what we really want to do is fork this repo into openshift/ and have the branches there, and use Prow CI jobs that will naturally follow forking, etc.
Will do a local test with |
Looks good locally. Ran /lgtm |
/override continuous-integration/jenkins/pr-merge |
Oops, forgot that we don't use Prow for merging here |
ci: Enable more kola tests for SCOS
I.e. #900 (for https://bugzilla.redhat.com/show_bug.cgi?id=1934863) and #903 (for https://bugzilla.redhat.com/show_bug.cgi?id=1940966).