service-binding-operator: Infinite reconcile loop in case of two SBRs sharing an application
The acceptance test scenario for two services being bound to a single application via 2 separate SBRs reproduces this while running in a fresh and clean OpenShift cluster. After the two requests are created, the SBO constantly reconciling the two requests binding-request-1 and binding-request-2 and re-deploying the deployment’s pods over and over again.
The two SBRs are created in sequence one after the other.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (14 by maintainers)
Commits related to this issue
- Merge remote-tracking branch 'upstream/master' into GH-630-3 — committed to DhritiShikhar/service-binding-operator by deleted user 4 years ago
- Merge remote-tracking branch 'dhriti/appsvc-712-acceptance-test' into GH-630-21 — committed to DhritiShikhar/service-binding-operator by deleted user 4 years ago
- Merge remote-tracking branch 'upstream/master' into GH-630-21 — committed to DhritiShikhar/service-binding-operator by deleted user 4 years ago
- Merge remote-tracking branch 'upstream/master' into GH-630-21 — committed to DhritiShikhar/service-binding-operator by deleted user 4 years ago
- Merge remote-tracking branch 'upstream/master' into GH-630-21 — committed to DhritiShikhar/service-binding-operator by deleted user 4 years ago
@durera In this video, you can see that:
Collection of data and creation of intermediate secret is successful, thus the
CollectionReadyis true.Injection of secret did not happen because applicationSelector is missing, thus
InjectionReadyis false with reasonEmptyApplicationSelector.https://youtu.be/uTODhkkmH5w