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

Do not fail DV reconcile if storage class is not found #2860

Merged

Conversation

arnongilboa
Copy link
Collaborator

What this PR does / why we need it:

Currently there is a repeating reconcile error due to exponential backoff: DataVolume.storage spec is missing accessMode and no storageClass to choose profile, however the error is not needed as we already have StorageClass watch for this case, e.g. when the DataVolume is using the default StorageClass but no default StorageClass is configured yet.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

Remove DataVolume reconcile error when storage class is not found yet

@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/S labels Aug 22, 2023
arnongilboa added a commit to arnongilboa/containerized-data-importer that referenced this pull request Aug 22, 2023
Manual backport of kubevirt#2860, fixing bz #2232347

Currently there is a repeating reconcile error due to exponential
backoff: "DataVolume.storage spec is missing accessMode and no
storageClass to choose profile", however the error is not needed as we
already have SC watch for this case, e.g. when the DV is using the
default SC but no default SC is configured yet.

Note the SC Watch() was mistakenly looking for DVs with unset phase
(like in the main/1.57 branch), but should look for Pending DVs instead.

Signed-off-by: Arnon Gilboa <agilboa@redhat.com>
@awels
Copy link
Member

awels commented Aug 22, 2023

/lgtm
/approve
/cherrypick release-v1.57

@kubevirt-bot
Copy link
Contributor

@awels: once the present PR merges, I will cherry-pick it on top of release-v1.57 in a new PR and assign it to you.

In response to this:

/lgtm
/approve
/cherrypick release-v1.57

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.

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 22, 2023
@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awels

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 22, 2023
@akalenyu
Copy link
Collaborator

akalenyu commented Aug 22, 2023

/hold
could we add a small check in test_id:8383 that we're not accumulating exponential backoff in this scenario?

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 22, 2023
@arnongilboa
Copy link
Collaborator Author

/hold could we add a small check in test_id:8383 that we're not accumulating exponential backoff in this scenario?

@akalenyu I think a utest verifying reconcile does not return error in this case is wiser here. wdyt?

@akalenyu
Copy link
Collaborator

/hold could we add a small check in test_id:8383 that we're not accumulating exponential backoff in this scenario?

@akalenyu I think a utest verifying reconcile does not return error in this case is wiser here. wdyt?

Yep that works

@kubevirt-bot kubevirt-bot added size/M and removed lgtm Indicates that a PR is ready to be merged. size/S labels Aug 24, 2023
arnongilboa added a commit to arnongilboa/containerized-data-importer that referenced this pull request Aug 24, 2023
Manual backport of kubevirt#2860, fixing bz #2232347

Currently there is a repeating reconcile error due to exponential
backoff: "DataVolume.storage spec is missing accessMode and no
storageClass to choose profile", however the error is not needed as we
already have SC watch for this case, e.g. when the DV is using the
default SC but no default SC is configured yet.

Note the SC Watch() was mistakenly looking for DVs with unset phase
(like in the main/1.57 branch), but should look for Pending DVs instead.

Signed-off-by: Arnon Gilboa <agilboa@redhat.com>

reconciler = createImportReconciler(importDataVolume)
_, err := reconciler.Reconcile(context.TODO(), reconcile.Request{NamespacedName: types.NamespacedName{Name: "test-dv", Namespace: metav1.NamespaceDefault}})
Expect(err).ToNot(HaveOccurred())
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe also
Expect(result).To(Equal(reconcile.Result{}))
To ensure requeue/requeueafter don't get set?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

arnongilboa added a commit to arnongilboa/containerized-data-importer that referenced this pull request Aug 24, 2023
Manual backport of kubevirt#2860, fixing bz #2232347

Currently there is a repeating reconcile error due to exponential
backoff: "DataVolume.storage spec is missing accessMode and no
storageClass to choose profile", however the error is not needed as we
already have SC watch for this case, e.g. when the DV is using the
default SC but no default SC is configured yet.

Note the SC Watch() was mistakenly looking for DVs with unset phase
(like in the main/1.57 branch), but should look for Pending DVs instead.

Signed-off-by: Arnon Gilboa <agilboa@redhat.com>
Currently there is a repeating reconcile error due to exponential
backoff: "DataVolume.storage spec is missing accessMode and no
storageClass to choose profile", however the error is not needed as we
already have SC watch for this case, e.g. when the DV is using the
default SC but no default SC is configured yet.

Signed-off-by: Arnon Gilboa <agilboa@redhat.com>
@akalenyu
Copy link
Collaborator

/lgtm
/hold cancel
/cherrypick release-v1.57

@kubevirt-bot
Copy link
Contributor

@akalenyu: once the present PR merges, I will cherry-pick it on top of release-v1.57 in a new PR and assign it to you.

In response to this:

/lgtm
/hold cancel
/cherrypick release-v1.57

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.

@kubevirt-bot kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 24, 2023
@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 24, 2023
kubevirt-bot pushed a commit that referenced this pull request Aug 24, 2023
#2861)

Manual backport of #2860, fixing bz #2232347

Currently there is a repeating reconcile error due to exponential
backoff: "DataVolume.storage spec is missing accessMode and no
storageClass to choose profile", however the error is not needed as we
already have SC watch for this case, e.g. when the DV is using the
default SC but no default SC is configured yet.

Note the SC Watch() was mistakenly looking for DVs with unset phase
(like in the main/1.57 branch), but should look for Pending DVs instead.

Signed-off-by: Arnon Gilboa <agilboa@redhat.com>
@kubevirt-bot kubevirt-bot merged commit 3002d32 into kubevirt:main Aug 24, 2023
18 checks passed
@kubevirt-bot
Copy link
Contributor

@awels: new pull request created: #2869

In response to this:

/lgtm
/approve
/cherrypick release-v1.57

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
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants