Details
-
Bug
-
Resolution: Done
-
Undefined
-
quay-v3.4.0
-
False
-
False
-
Undefined
-
Vader [Quay 189]
-
0
Description
During the reconciliation loop, we create an ObjectBucketClaim and then immediately check for its corresponding Secret which contains the S3 connection details, which hasn't been created yet. This causes an error in the Operator logs, but the next reconciliation loop finds the credentials so everything still works.
We can potentially solve this by putting in a slight delay, but the best fix is to move to watching all created resources rather than polling.