-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OADP-5888 Add Line After Include Statements #93812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,23 +12,31 @@ This document provides information about advanced features and functionalities o | |
== Working with different Kubernetes API versions on the same cluster | ||
|
||
include::modules/oadp-checking-api-group-versions.adoc[leveloffset=+2] | ||
|
||
include::modules/oadp-about-enable-api-group-versions.adoc[leveloffset=+2] | ||
|
||
include::modules/oadp-using-enable-api-group-versions.adoc[leveloffset=+2] | ||
|
||
[id="backing-up-data-one-cluster-restoring-another-cluster"] | ||
== Backing up data from one cluster and restoring it to another cluster | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Similar comment as above -- it would be good to add a short introduction here. |
||
|
||
include::modules/oadp-about-backing-and-restoring-from-cluster-to-cluster.adoc[leveloffset=+2] | ||
|
||
include::modules/oadp-pod-volume-backup.adoc[leveloffset=+2] | ||
|
||
include::modules/oadp-backing-up-opt-in.adoc[leveloffset=+3] | ||
|
||
include::modules/oadp-backing-up-opt-out.adoc[leveloffset=+3] | ||
|
||
include::modules/oadp-cluster-to-cluster-uid-and-gid-ranges.adoc[leveloffset=+2] | ||
|
||
include::modules/oadp-backing-and-restoring-from-cluster-to-cluster.adoc[leveloffset=+2] | ||
|
||
[id="oadp-storage-class-mapping"] | ||
== OADP storage class mapping | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Similar comment as above -- it would be good to add a short introduction here. |
||
include::modules/oadp-storage-class-mapping.adoc[leveloffset=+2] | ||
|
||
include::modules/oadp-storage-class-mapping-oadp.adoc[leveloffset=+3] | ||
|
||
[role="_additional-resources"] | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
// Module included in the following assemblies: | ||
// | ||
// applications/projects/working-with-projects.adoc | ||
|
||
:_mod-docs-content-type: PROCEDURE | ||
[id="openshift-adp-controller-manager-seg-fault_{context}"] | ||
= OpenShift ADP Controller segmentation fault | ||
|
||
If you configure a DPA with both `cloudstorage` and `restic` enabled, the `openshift-adp-controller-manager` pod crashes and restarts indefinitely until the pod fails with a crash loop segmentation fault. | ||
|
||
You can have either `velero` or `cloudstorage` defined, because they are mutually exclusive fields. | ||
|
||
* If you have both `velero` and `cloudstorage` defined, the `openshift-adp-controller-manager` fails. | ||
* If you have neither `velero` nor `cloudstorage` defined, the `openshift-adp-controller-manager` fails. | ||
|
||
For more information about this issue, see link:https://issues.redhat.com/browse/OADP-1054[OADP-1054]. | ||
|
||
|
||
[id="openshift-adp-controller-manager-seg-fault-workaround_{context}"] | ||
== OpenShift ADP Controller segmentation fault workaround | ||
|
||
You must define either `velero` or `cloudstorage` when you configure a DPA. If you define both APIs in your DPA, the `openshift-adp-controller-manager` pod fails with a crash loop segmentation fault. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
// Module is included in the following assemblies: | ||
// | ||
// * openshift-docs/cicd/gitops/understanding-openshift-gitops.adoc | ||
|
||
:_mod-docs-content-type: CONCEPT | ||
[id="oadp-plugins-receiving-eof-message_{context}"] | ||
= Velero plugins returning "received EOF, stopping recv loop" message | ||
|
||
[NOTE] | ||
==== | ||
Velero plugins are started as separate processes. After the Velero operation has completed, either successfully or not, they exit. Receiving a `received EOF, stopping recv` loop message in the debug logs indicates that a plugin operation has completed. It does not mean that an error has occurred. | ||
==== |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is out of the scope of this PR, but this section needs a short introduction. Otherwise, you end up with one heading being displayed just after another heading.