OLS Release Notes 1.1.2 further updates

[pabel-rh]

Version(s):
lightspeed-docs-main, lightspeed-docs-1.0, lightspeed-docs-1.1

Issue:
OBSDOCS-3549

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Fri Aug 07 09:03:35 - Prow CI generated the docs preview:

https://117406--ocpdocs-pr.netlify.app/
https://117406--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/configure/ols-configuring-openshift-lightspeed.html
https://117406--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/release_notes/ols-release-notes.html

[sriroopar]

Please include all the discussed changes. Thank you!

[pabel-rh]

Review is done through Google meet. So, we don't need to re-request for a review. We can proceed with the merge.

[openshift-ci]

@pabel-rh: 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.

[briandooley]

/cherrypick lightspeed-docs-1.1

[briandooley]

/cherrypick lightspeed-docs-1.0

[openshift-cherrypick-robot]

@briandooley: #117406 failed to apply on top of branch "lightspeed-docs-1.1":

Applying: OLS Release Notes 1.1.2 further updates
Using index info to reconstruct a base tree...
A	modules/ols-1-1-2-release-notes.adoc
A	modules/ols-about-the-offline-knowledge-portal.adoc
M	release_notes/ols-release-notes.adoc
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): modules/ols-1-1-2-release-notes.adoc deleted in HEAD and modified in OLS Release Notes 1.1.2 further updates.  Version OLS Release Notes 1.1.2 further updates of modules/ols-1-1-2-release-notes.adoc left in tree.
CONFLICT (modify/delete): modules/ols-about-the-offline-knowledge-portal.adoc deleted in HEAD and modified in OLS Release Notes 1.1.2 further updates.  Version OLS Release Notes 1.1.2 further updates of modules/ols-about-the-offline-knowledge-portal.adoc left in tree.
Auto-merging release_notes/ols-release-notes.adoc
CONFLICT (content): Merge conflict in release_notes/ols-release-notes.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 OLS Release Notes 1.1.2 further updates

Details

In response to this:

/cherrypick lightspeed-docs-1.1

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.

[openshift-cherrypick-robot]

@briandooley: #117406 failed to apply on top of branch "lightspeed-docs-1.0":

Applying: OLS Release Notes 1.1.2 further updates
Using index info to reconstruct a base tree...
M	modules/ols-1-1-2-release-notes.adoc
M	release_notes/ols-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/ols-1-1-2-release-notes.adoc
Auto-merging release_notes/ols-release-notes.adoc
CONFLICT (content): Merge conflict in release_notes/ols-release-notes.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 OLS Release Notes 1.1.2 further updates

Details

In response to this:

/cherrypick lightspeed-docs-1.0

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.