-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
libvirt: 1st worker needs more memory #1041
Comments
You have a few options here: a. Configuring larger workers. We don't have a knob for this at the install-config level, but you can use a multi-step install with a stop at
(b) and (c) are purely day-2, libvirt-provider issues. (a) is purely an installer issue. Also in this space is the fact that almost everything launched by the cluster-version operator (directly and indirectly) should tolerate masters, although there are still a handful of operators and such which don't. That's an issue with those operators, and once they get patched up, you'll be able to relieve worker contention by provisioning more master space (e.g. via #785). |
I also found that apparently this works:
Regretfully, I'm again unsuccessful at installing the whole thing end to end, but I doubt it's related. I personally think we should go for solution A. The 1st worker is just overloaded with stuff and has to be bigger. Note that like every qemu VM, it'll consume as much memory as it needs from the host, so if it only uses 3GB, it'll use them and only them, not 4GB, for example. |
Everyone can pick whichever of these options they like best. There's no need for installer source changes or otherwise forming a consensus. |
@wking - seems this can be closed, as my idea (in #1041 (comment) ) was just implemented in db5f0ae ? (I still can't complete an installation successfully, but at least it has enough memory!) |
Thanks :) |
Solution A has no effect. The changes made are not honored. |
I suspect (perhaps because of https://github.com/openshift/cluster-api-provider-libvirt/blob/da6aa0a3931761842527816a79f1072129f2cea3/test/utils/manifests.go#L67 ) that it copies the same values as the master default, and 2GB are simply not enough for it. It is using 84% of its memory if the installation succeeded.
(Is that a cluster-api-provider-libvirt issue?)
It'd be great if we could configure its properties.
The text was updated successfully, but these errors were encountered: