nohz_full not equal isolcpus#2
Closed
maxmailbox wants to merge 1 commit intostarlingx:r/stx.4.0from
maxmailbox:patch-1
Closed
nohz_full not equal isolcpus#2maxmailbox wants to merge 1 commit intostarlingx:r/stx.4.0from maxmailbox:patch-1
maxmailbox wants to merge 1 commit intostarlingx:r/stx.4.0from
maxmailbox:patch-1
Conversation
starlingx-github
pushed a commit
that referenced
this pull request
Oct 8, 2024
Moved the scripts bellow to be grouped together: - remove-psp-service-parameter.py - delete-encrypted-fs-service-parameter.sh - add-tls-version-cipher-parameters.sh - oidc-service-parameters-migration.py These scripts make changes to service parameters in K8s API, related to security features. Since the API restarts on each apply, it's better to execute the scripts and perform a single apply after the last script. However, some of the parameter changes need to be done at the beginning of the upgrade, so the scripts were placed following the executed earlier amongst them (remove-psp-service-parameter.py), which was placed in position #2, so the scripts will occupy the positions 02-05. An extra script will be added in a follow up change, after 'oidc- service-parameters-migration.py' to perform the service-parameter apply and monitor the restart of K8s API, in the position #06. The other scripts were renamed to accommodate that, keeping their order of execution between themselves. Also, some scripts that had the same number were renamed to have a unique number. Test plan: PASS: Perform upgrade activation from stx 8 -> stx 10. Story: 2010676 Task: 51103 Change-Id: I6aa2ae2a9d41793bab3a9ea67b9218b11cbbbd1d Signed-off-by: Marcelo de Castro Loebens <Marcelo.DeCastroLoebens@windriver.com>
starlingx-github
pushed a commit
that referenced
this pull request
Sep 8, 2025
During node replacement, topology can change for identical CPU models. An example, CPU #1 has core 2 disabled in HW, but CPU #2 has core 3 disabled. This will cause a divergence in the core ID enumeration posted by firmware. Even though technically the CPUs are functionally equivalent. To mitigate this, during restore, sysinv will now update core_ids to the new values, but only if the rest of the topology matches. TEST PLAN PASS: AIO-SX deploy * No regressions PASS: AIO-DX deploy * No regressions PASS: AIO-SX optimized B&R * No regressions PASS: AIO-SX optimized B&R on affected system * Before backup, change some cores to application-isolated * CPU configuration successfully restored Closes-Bug: 2120725 Change-Id: Ie35f2acb4faa9c5973fead31d58533b40d6aef73 Signed-off-by: Joshua Kraitberg <joshua.kraitberg@windriver.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://bugs.launchpad.net/starlingx/+bug/1925363