-
Notifications
You must be signed in to change notification settings - Fork 265
Bug 1753014: Kuryr: Fix kuryr bootstrap when lbaas API has ERROR status #319
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 1753014: Kuryr: Fix kuryr bootstrap when lbaas API has ERROR status #319
Conversation
|
@MaysaMacedo: This pull request references Bugzilla bug 1753014, which is invalid:
Comment 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. |
c4660f0 to
ebfca1f
Compare
|
@MaysaMacedo: This pull request references Bugzilla bug 1753014, which is invalid:
Comment 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. |
|
/bugzilla refresh |
|
@MaysaMacedo: This pull request references Bugzilla bug 1753014, 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. 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. |
ebfca1f to
fb9d517
Compare
fb9d517 to
af46300
Compare
af46300 to
b346742
Compare
In case the API lbaas gets to a provisiong status with ERROR, the reconciliation is triggered and the same lbaas with ERROR status is used for the creation of lbaas resources, e.g. pools, listeners and members, causing Kuryr bootstraping phase to not finish. This commit fixes the issue by deleting the lbaas in case it's with ERROR status and creating a new one.
b346742 to
ce8e671
Compare
|
@MaysaMacedo: This pull request references Bugzilla bug 1753014, which is valid. 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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dulek, MaysaMacedo 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 |
|
@MaysaMacedo: All pull requests linked via external trackers have merged. Bugzilla bug 1753014 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. |
In case the API lbaas gets to a provisiong status with ERROR, the
reconciliation is triggered and the same lbaas with ERROR status
is used on the creation of the next lbaas resources, e.g. pools,
listeners and members. The operator will never finish Kuryr
bootstraping phase.
This commit fixes the issue by deleting the lbaas in case it's
with ERROR status and creating a new one.