Bug 2030489: Remove oudated subscription update logic to improve resolution delay#222
Conversation
Currently, olm logic checks for upgrade in subscription via another obsolete API that is no longer in use for dependency solution. As a result, sometimes, subscriptions display `UpgradeAvailable` status but there will be no upgrades as the upgrade is not valid in the resolver. Also, the `UpgradeAvailable` status is used to trigger the new resolution even though that status is no longer a valid indicator of having a pending upgrade. This leads to unwanted upgrade delay when the obsolete API works properly. This commit will remove the code that is using this obsolete API and allow the resolution to happen when there is a subscription change. Signed-off-by: Vu Dinh <vudinh@outlook.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 81e7a60bc7a62da4a469041ce89e3867e9f47fde
|
@dinhxuanvu: No Bugzilla bug is referenced in the title of this pull request. DetailsIn 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 kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dinhxuanvu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@dinhxuanvu: This pull request references Bugzilla bug 2030489, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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 kubernetes/test-infra repository. |
timflannagan
left a comment
There was a problem hiding this comment.
Do we need to also pull in 093e248, or is that not an issue with the 4.8 release?
|
/retest |
|
@timflannagan I didn't include that commit because that issue is not in 4.8. |
|
/retest |
|
/label cherry-pick-approved |
|
/label backport-risk-assessed |
|
@dinhxuanvu: All pull requests linked via external trackers have merged: Bugzilla bug 2030489 has been moved to the MODIFIED state. DetailsIn 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 kubernetes/test-infra repository. |
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
Upstream-repository: api Upstream-commit: 2e47b5a3bedaab35db362dff3ecb56133af16af7
|
/cherry-pick release-4.7 |
|
@sferich888: new pull request created: #373 DetailsIn 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 kubernetes/test-infra repository. |
Currently, olm logic checks for upgrade in subscription via another
obsolete API that is no longer in use for dependency solution. As a
result, sometimes, subscriptions display
UpgradeAvailablestatus butthere will be no upgrades as the upgrade is not valid in the resolver.
Also, the
UpgradeAvailablestatus is used to trigger the new resolutioneven though that status is no longer a valid indicator of having a pending
upgrade. This leads to unwanted upgrade delay when the obsolete API works
properly.
This commit will remove the code that is using this obsolete API and
allow the resolution to happen when there is a subscription change.
Signed-off-by: Vu Dinh vudinh@outlook.com
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 81e7a60bc7a62da4a469041ce89e3867e9f47fde