Skip to content
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

OADP-1002: Ignore not found err for temp vsclass in cases of data mover without PVC #215

Merged
merged 2 commits into from
Oct 28, 2022

Conversation

eemcmullan
Copy link

No description provided.

pkg/datamover/datamover.go Outdated Show resolved Hide resolved
@@ -137,6 +138,12 @@ func DeleteTempVSClass(backupName string, tempVS snapshotv1listers.VolumeSnapsho
tempVSClassName := fmt.Sprintf("%s-snapclass", backupName)
tempVSClass, err := tempVS.Get(tempVSClassName)
if err != nil {
// ignore is not found err as it is possible to create data mover

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 on the comment

@@ -137,6 +138,12 @@ func DeleteTempVSClass(backupName string, tempVS snapshotv1listers.VolumeSnapsho
tempVSClassName := fmt.Sprintf("%s-snapclass", backupName)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a little comment about what the tempVSClass ? Not a dealbreaker.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a small comment about temp vsclass in the backup controller

// backup without an existing PVC
// in which case this VSClass will not exist
if apierrors.IsNotFound(err) {
return nil

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems fine to me IF the only errors we need to be concerned about are apierrors.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAIK for this particular issue this should be the only error we're concerned about

@weshayutin
Copy link

/LGTM

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 27, 2022
@eemcmullan eemcmullan merged commit 0ce2085 into openshift:konveyor-1.9 Oct 28, 2022
@eemcmullan
Copy link
Author

/cherry-pick konveyor-1.9.2

@eemcmullan
Copy link
Author

/cherry-pick oadp-1.1

@openshift-cherrypick-robot

@eemcmullan: new pull request created: #216

In response to this:

/cherry-pick konveyor-1.9.2

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/test-infra repository.

@openshift-cherrypick-robot

@eemcmullan: new pull request created: #217

In response to this:

/cherry-pick oadp-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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants