[Bug] Cryostat Route still exposes port 9091 jfr-jmx after upgrading from 2.4 to 3.0

[andrewazores]

Current Behavior

Since #823 , Cryostat itself does not have a JMX server enabled by default and the corresponding Service has been removed. However, the Route still contains the port definition.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

No response

Anything else?

[andrewazores]

Actually, this might only be a bug that only occurs when upgrading from 2.4 to 3.0, where this part of the Route gets left behind.

[tthvo]

Do u think it might be due to some delay during upgrading?

When I tried to reproduce, I can see the same issue for the first 1-2 minutes after the operator is marked as "upgraded". I also see the v1beta1 cryostat is stilled returned when using oc get cryostat. But after some time, all appear as expected. The service shows only http below.

[tthvo]

I built the catalog image with 2.4.0-dev and 3.0.0-dev (must be -dev to have the same alpha channel) as:

make catalog-build CATALOG_IMG=quay.io/thvo/cryostat-operator-catalog:latest BUNDLE_IMGS='quay.io/cryostat/cryostat-operator-bundle:2.4.0-dev,quay.io/cryostat/cryostat-operator-bundle:3.0.0-dev'

The image I use to create CatalogSource: quay.io/thvo/cryostat-operator-catalog:latest

[andrewazores]

It sounds like it probably just was a delay then, I noticed this right away after upgrading and didn't go back to check on it again before uninstalling.