-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OADP-6294: Mod-work for the OADP Troubleshooting user story #95005
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?
OADP-6294: Mod-work for the OADP Troubleshooting user story #95005
Conversation
@apurvabhide17: This pull request references OADP-6294 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.20.0" version, but no target version was set. In response to this:
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. |
/label OADP |
@apurvabhide17: all tests passed! Full PR test history. Your PR dashboard. 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. |
|
||
* For resource-specific errors, that is, `Cluster` and `Namespaces` errors, the `restore describe --details` output includes a resource list that lists all resources that Velero succeeded in restoring. For any resource that has such an error, check if the resource is actually in the cluster. | ||
|
||
* If there are `Velero` errors, but no resource-specific errors, in the output of a `describe` command, it is possible that the restore completed without any actual problems in restoring workloads, but carefully validate post-restore applications. |
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.
I would break this into at least two sentences. It will make the content easier to understand. Also, I was a tad confused by "but no resource-specific errors, in the output of a describe
command," The comma in-between threw me off.
|
||
:_mod-docs-content-type: PROCEDURE | ||
[id="creating-alerting-rules_{context}"] | ||
= Creating an alerting rule | ||
|
||
The {product-title} monitoring stack allows to receive Alerts configured using Alerting Rules. To create an Alerting rule for the OADP project, use one of the Metrics which are scraped with the user workload monitoring. | ||
The {product-title} monitoring stack allows to receive Alerts configured using Alerting Rules. To create an Alerting rule for the OADP project, use one of the Metrics, which are scraped with the user workload monitoring. |
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.
Maybe change:
To create an Alerting rule for the OADP project, use one of the Metrics, which are scraped with the user workload monitoring.
To:
To create an Alerting rule for the OADP project, use one of the Metrics scraped with the user workload monitoring.
Up to you!
OADP provides an `openshift-adp-velero-metrics-svc` service which is created when the DPA is configured. The service monitor used by the user workload monitoring must point to the defined service. | ||
|
||
Get details about the service by running the following commands: | ||
OADP provides an `openshift-adp-velero-metrics-svc` service, which is created when the Data Protection Application (DPA) is configured. The service monitor used by the user workload monitoring must point to the defined service. |
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.
Maybe change:
The service monitor used by the user workload monitoring must point to the defined service.
To:
The user workload monitoring service monitor must point to the defined service.
|
||
.Procedure | ||
|
||
. Ensure the `openshift-adp-velero-metrics-svc` service exists. It should contain `app.kubernetes.io/name=velero` label, which will be used as selector for the `ServiceMonitor` object. | ||
|
||
. Ensure that the `openshift-adp-velero-metrics-svc` service exists. It should contain `app.kubernetes.io/name=velero` label, which will be used as selector for the `ServiceMonitor` object. |
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.
I'd leave out, "will be".
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.
replace with "is"
|
||
It is recommended to use the `info` `logLevel` value for most logs. | ||
+ | ||
It is recommended to use the `info` `logLevel` value for most logs. |
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.
Style guide recommends that we not use recommends. :-)
In this case, we could say why they should use....
Or, simpler, just say, "Use the info
logLevel
value for most logs."
@@ -39,7 +40,7 @@ metadata: | |||
---- | |||
<1> Add this option or set to `true` | |||
|
|||
. Wait a short period of time to verify the User Workload Monitoring Setup by checking if the following components are up and running in the `openshift-user-workload-monitoring` namespace: | |||
. Wait a short period of time to verify if the User Workload Monitoring Setup by checking if the following components are up and running in the `openshift-user-workload-monitoring` namespace: |
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.
The added "if" makes the sentence a tad confusing. If that if is needed, the sentence could use a rewording to make it clear.
|
||
Velero does not recreate or update the Restic repository from the `ResticRepository` manifest if the Restic directories are deleted from object storage. For more information, see link:https://github.com/vmware-tanzu/velero/issues/4421[Velero issue 4421]. | ||
|
||
If you create a Restic `Backup` CR for a namespace, empty the object storage bucket, and then recreate the `Backup` CR for the same namespace, the recreated `Backup` CR fails, the `velero` pod log displays the following error message: |
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.
IMO, too much in this sentence. I'd break it up. The way it reads, I'm thinking that the last comma could be replaced by "and".
|
||
:_mod-docs-content-type: PROCEDURE | ||
[id="creating-alerting-rules_{context}"] | ||
= Creating an alerting rule | ||
|
||
The {product-title} monitoring stack allows to receive Alerts configured using Alerting Rules. To create an Alerting rule for the OADP project, use one of the Metrics which are scraped with the user workload monitoring. | ||
The {product-title} monitoring stack allows to receive Alerts configured using Alerting Rules. To create an Alerting rule for the OADP project, use one of the Metrics, which are scraped with the user workload monitoring. |
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.
The {product-title} monitoring stack allows to receive Alerts configured using Alerting Rules. To create an Alerting rule for the OADP project, use one of the Metrics, which are scraped with the user workload monitoring. | |
The {product-title} monitoring stack allows to receive Alerts configured using Alerting Rules. To create an Alerting rule for the {oadp-short} project, use one of the Metrics scraped with the user workload monitoring. |
OADP provides an `openshift-adp-velero-metrics-svc` service which is created when the DPA is configured. The service monitor used by the user workload monitoring must point to the defined service. | ||
|
||
Get details about the service by running the following commands: | ||
OADP provides an `openshift-adp-velero-metrics-svc` service, which is created when the Data Protection Application (DPA) is configured. The service monitor used by the user workload monitoring must point to the defined service. |
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.
OADP provides an `openshift-adp-velero-metrics-svc` service, which is created when the Data Protection Application (DPA) is configured. The service monitor used by the user workload monitoring must point to the defined service. | |
{oadp-short} provides an `openshift-adp-velero-metrics-svc` service, which is created when the Data Protection Application (DPA) is configured The user workload monitoring service monitor must point to the defined service. |
|
||
.Procedure | ||
|
||
. Ensure the `openshift-adp-velero-metrics-svc` service exists. It should contain `app.kubernetes.io/name=velero` label, which will be used as selector for the `ServiceMonitor` object. | ||
|
||
. Ensure that the `openshift-adp-velero-metrics-svc` service exists. It should contain `app.kubernetes.io/name=velero` label, which will be used as selector for the `ServiceMonitor` object. |
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.
. Ensure that the `openshift-adp-velero-metrics-svc` service exists. It should contain `app.kubernetes.io/name=velero` label, which will be used as selector for the `ServiceMonitor` object. | |
. Ensure that the `openshift-adp-velero-metrics-svc` service exists. It should contain `app.kubernetes.io/name=velero` label, which is used as selector for the `ServiceMonitor` object. |
Version(s):
OCP 4.20
Issue:
OADP-6294
Link to docs preview:
QE review:
Note -
This is a modularization work for the OADP Troubleshooting user story.
As discussed with Kathryn, skipping the QE review because this PR focuses on changing structure and there are no technical changes.