-
Notifications
You must be signed in to change notification settings - Fork 104
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
c9s: remove / override mitigation kargs #1311
Comments
Or use any other instance type which is either not subject to |
This problem will go away once the installer switches to use SCOS bootimages, so there's no pivot that retains default kargs from FCOS. More generally, this would be solved by coreos/rpm-ostree#3738 |
We're likely not going to be able to fix that here and the end goal is to not use the FCOS image to bootstrap OKD-SCOS as this is a downgrade operation and we don't support those. |
Just a side note: A bootc install --takeover flow would mean there's no "downgrade" because we entirely nuke and replace everything in the system (including the systemd journal, etc.). But, things like what image metadata flags are set are still relevant here. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
When OKD SCOS is being installed it may use FCOS as a starting image (for clouds where we don't upload SCOS artifacts yet). This causes default FCOS kernel arguments to be retained - which means default
mitigations=auto,nosmt
are being kept and installation fails as only half the CPUs are being used.For AWS the workaround is to use
m6a.xlarge
flavor where nosmt doesn't disable CPUs.In OKD FCOS bootstrap automatically mixes in a MachineConfig which sets
mitigations=off
and all nodes boot without this karg after pivot. Ideally, we should find a solution to this in C9S manifest (and fall back to installer script if not possible)The text was updated successfully, but these errors were encountered: