F OpenNebula/one#7426: Add resolved issues for issue 7426 - #3344
Merged
Merged
Conversation
aaizel1
marked this pull request as draft
September 11, 2026 09:10
3 tasks
aaizel1
marked this pull request as ready for review
September 14, 2026 11:48
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
2 participants
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.
Description
Summary
Document issue #7426 as resolved in OpenNebula 6.10.6, covering direct entry of precise memory values when range-based memory modification is enabled.
Modified files
source/intro_release_notes/release_notes_enterprise/resolved_issues_6106.rstBranches to which this PR applies