-
Notifications
You must be signed in to change notification settings - Fork 542
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
Bug 1905299: fix(olm): Verify ServiceAccount ownership before installing deployment #1904
Bug 1905299: fix(olm): Verify ServiceAccount ownership before installing deployment #1904
Conversation
@dinhxuanvu: This pull request references Bugzilla bug 1905299, 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. 3 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
dcacc95
to
7a83f3b
Compare
Currently, there is a timing during upgrade, the new SA is not yet being created but the deployment is successfully updated and the new pod is coming up using the old SA. As a result, the pod fails to succeed due to permission failure. When CSV is in Pending state, a permission and requirement check list is performed. A check for SA ownership is added to that check list to verify if new SA is in place before moving CSV to Installing state. If new SA is not yet in place, CSV can continue to be Pending which will prevent the deployment to be created/updated. Signed-off-by: Vu Dinh <vdinh@redhat.com>
7a83f3b
to
904003a
Compare
/retest |
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.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy, dinhxuanvu 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 |
/retest |
@dinhxuanvu: All pull requests linked via external trackers have merged: Bugzilla bug 1905299 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
/cherry-pick release-4.6 |
@dinhxuanvu: new pull request created: #1907 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 kubernetes/test-infra repository. |
Currently, there is a timing during upgrade, the new SA is not yet being
created but the deployment is successfully updated and the new pod
is coming up using the old SA. As a result, the pod fails to succeed
due to permission failure.
When CSV is in Pending state, a permission and requirement check list
is performed. A check for SA ownership is added to that check list
to verify if new SA is in place before moving CSV to Installing state.
If new SA is not yet in place, CSV can continue to be Pending which
will prevent the deployment to be created/updated.
Signed-off-by: Vu Dinh vdinh@redhat.com
Description of the change:
Motivation for the change:
Reviewer Checklist
/docs