Browse Source

Merge "[train-only] Adding ForceNoTsx flag" into stable/train

changes/97/794197/1
Zuul 2 weeks ago
committed by Gerrit Code Review
parent
commit
6059d84f17
2 changed files with 30 additions and 0 deletions
  1. +10
    -0
      deployment/kernel/kernel-boot-params-baremetal-ansible.yaml
  2. +20
    -0
      releasenotes/notes/add-forcenotsx-36fc6dce46518f5b.yaml

+ 10
- 0
deployment/kernel/kernel-boot-params-baremetal-ansible.yaml View File

@ -57,6 +57,14 @@ parameters:
default: 900
type: number
description: Timeout in seconds to specify the wait time for ansible node reboot
ForceNoTsx:
default: false
description: >
This will disable the TSX flag validation in KernelArgs for this specific role.
More information available here: https://access.redhat.com/solutions/6036141
type: boolean
tags:
- role_specific
resources:
RoleParametersValue:
@ -69,11 +77,13 @@ resources:
- tuned_profile: TunedProfileName
isolated_cores: IsolCpusList
kernel_args: KernelArgs
force_no_tsx: ForceNoTsx
- values: {get_param: [RoleParameters]}
- values:
TunedProfileName: {get_param: TunedProfileName}
IsolCpusList: {get_param: IsolCpusList}
KernelArgs: {get_param: KernelArgs}
ForceNoTsx: {get_param: ForceNoTsx}
outputs:
role_data:


+ 20
- 0
releasenotes/notes/add-forcenotsx-36fc6dce46518f5b.yaml View File

@ -0,0 +1,20 @@
---
fixes:
- |
RHEL-8.3 kernel disabled the Intel TSX (Transactional
Synchronization Extensions) feature by default as a preemptive
security measure, but it breaks live migration from RHEL-7.9
(or even RHEL-8.1 or RHEL-8.2) to RHEL-8.3.
Operators are expected to explicitly define the TSX flag in
their KernelArgs for the compute role to prevent live-migration
issues during the upgrade or update process.
We now introduce this validation in tripleoclient to ensure
early failure.
The `ForceNoTsx` flag will disable this validation on a per-role
basis.
More information here:
https://access.redhat.com/solutions/6036141

Loading…
Cancel
Save