Upgrade from 0.6.1 to 0.6.2?

[bjorntj]

Not sure what I am doing wrong here. But I installed 0.6.1 from scratch a couple of weeks ago and expected the upgrade to 0.6.2 to go smoothly. But I see the operators are still running 0.6.1 and 0.6.2 is not available in the dropdown menu?

[MikeEdgar]

Are you using this tag for your CatalogSource?

quay.io/streamshub/console-operator-catalog:latest

[bjorntj]

Ok, killed the pod and then 0.6.2 appeared. Anything I need to do to make this pod restart?

[MikeEdgar]

Unless you have an updateStrategy in the CatalogSource making it have a longer poll period, there should not be anything to do. Does it seem as though other catalog pods have been started more recently? They would be in openshift-marketplace for OCP clusters.

[bjorntj]

updateStrategy is set to Default.
And I am not sure which pod would be the catalog source pod in that namespace but maybe it is the one called redhat-marketplace. If so, this pod has been running on almost 6 days.

[bjorntj]

Did a quick search and I guess I need to add something like this to the catalog source config:

updateStrategy:
    registryPoll: 
      interval: 30m0s

[MikeEdgar]

Yes, having a shorter registry poll interval like that should definitely help. That pod could be running longer if no new images have been published for the catalog. Others like redhat-operators-xxxx update fairly frequently.