Skip to content

Comments

[enterprise-4.20] OSDOCS-17125-3: MSH-STOR-1 Core Storage Concepts#106829

Merged
dfitzmau merged 1 commit intoopenshift:enterprise-4.20from
openshift-cherrypick-robot:cherry-pick-106369-to-enterprise-4.20
Feb 18, 2026
Merged

[enterprise-4.20] OSDOCS-17125-3: MSH-STOR-1 Core Storage Concepts#106829
dfitzmau merged 1 commit intoopenshift:enterprise-4.20from
openshift-cherrypick-robot:cherry-pick-106369-to-enterprise-4.20

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #106369

/assign dfitzmau

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 18, 2026

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OSDOCS-17125

Details

In response to this:

This is an automated cherry-pick of #106369

/assign dfitzmau

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Feb 18, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 18, 2026

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@dfitzmau dfitzmau merged commit b87c557 into openshift:enterprise-4.20 Feb 18, 2026
2 checks passed
@dfitzmau
Copy link
Contributor

/cherrypick enterprise-4.19

@openshift-cherrypick-robot
Copy link
Author

@dfitzmau: #106829 failed to apply on top of branch "enterprise-4.19":

Applying: OSDOCS-17125-3: MSH-STOR-1 Core Storage Concepts
.git/rebase-apply/patch:224: trailing whitespace.
** Replace `_<pod_name_a>_` with the name of the first pod. 
.git/rebase-apply/patch:360: trailing whitespace.
Sometimes pods of the same node are not able to read or write into the same PV. This happens when the pods in the node do not have the same SELinux context. 
.git/rebase-apply/patch:523: trailing whitespace.
To create a snapshot of a {microshift-short} storage volume, you must first configure {op-system-ostree} and the node. 
.git/rebase-apply/patch:685: trailing whitespace.
You can use the logical volume manager storage (LVMS) for persistent volume claim (PVC) cloning of the logical volume manager (LVM) thin volumes. A clone is a duplicate of an existing volume that can be used like any other volume. 
.git/rebase-apply/patch:776: trailing whitespace.
** Replace `_<pod_name_a>_` with the name of the first pod. 
warning: squelched 1 whitespace error
warning: 6 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/storage-persistent-storage-fsGroup.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/storage-persistent-storage-fsGroup.adoc
CONFLICT (content): Merge conflict in modules/storage-persistent-storage-fsGroup.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 OSDOCS-17125-3: MSH-STOR-1 Core Storage Concepts

Details

In response to this:

/cherrypick enterprise-4.19

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants