Many thanks for your details!
> So in order to see the change in the content, you will need to delete the configmaps.
However, I have conerns about this way. Based on my understanding, the destination of the CatalogSource upgrading is to implement the updgrade of the subscription seamlessly.
To implement that, we use the `Always ImagePullPolicy` to update the CatalogSource image so that the user can use the latest index image if there are updates, and then, use the latest operator Bundle image from the index image. after that, copy the Bundle manifest to a volume.
Now, the fix of this bug is to use the `Always ImagePullPolicy` to make sure we use the latest Bundle image.
> However, after a configmap is created to hold the content of a bundle, it is persistent.
But, due to it's a persistent volume, the lastest Bundle cannot be generated. I'm not very clear here.
But, I think we should fix this issue to implement the seamless update, not let the user remove the ConfigMap manually. Or am I missing something? Thanks!
Sure, that makes sense. Verify it based on comment 5, 12, 13, 14.
Note - this was merged while master was still 4.6.0, moving the bug to 4.6.
*** Bug 1868143 has been marked as a duplicate of this bug. ***
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 (OpenShift Container Platform 4.6.6 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.