Given a cluster where an operator has been installed from OperatorHub. In that scenario, say the operator pod is restarted or the OperatorSource from where the operator was installed is deleted and during this time the operator was updated on Quay with a new version, it is observed that the existing Subscription does not show the update. How reproducible: Always Steps to Reproduce: 1. Install an operator from Quay 2. Remove the OperatorSource from where the operator was installed 3. Update the operator with a new version on Quay 4. Add the OperatorSource back Actual results: The Subscription object for the operator does not reflect the new version Expected results: The Subscription object should reflect the new version
test with the upstream image,and the function is ok now,will test when the new nightly payload is ok marketplaceimage commit:5a98c3c3c3e3482b5507ffef2c73a59f703fc10b
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758